General Limitations & Restrictions
IBM Maximo and TRIRIGA SaaS Architecture - General Limitations and Restrictions
Operating Systems
All SaaS TEST and PROD Server Operating Systems are 64-bit Linux
Maximo SaaS Flex Enhanced Access (DEV) Operating Systems are Windows Server 2012 R2
Customers cannot request use of specific operating systems
Operating System Access
Customers do not have access to Server Operating systems running in the IBM Cloud. They cannot connect to the Linux operating system using telnet or other remote access software like putty, except to download logs via SFTP. Customers cannot connect to the file systems mounted in the virtual server using SFTP client software. The management of virtual servers is performed solely by the IBM SaaS Team.
Customers of Maximo SaaS Flex can be provisioned an Enhanced Access (DEV) environment at an additional cost. This environment allows customer access to the Windows 2012 R2 Operating System console as a standard winodws user via Remote Desktop Console (RDC) for up to five (5) named users. Note: Administrator access is not permitted.
Log File Access
Application Log files can be accessed using secure FTP (SFTP). Customers (or their system integrators) who need access to log files should submit a case through the IBM Support Community to request access to the log files. A userid and password will be provided for the customer to download the logs whenever they wish.
Database Platform
IBM DB2 is the standard database platform for SaaS. Oracle is also supported, but is subject to IBM legal review / input and the customer must supply the license. Oracle must be run on a bare metal IBM Cloud server, it is not supported on Virtual Machines (VMs). Microsoft SQLServer is not supported in IBM Maximo or TRIRIGA SaaS environments.
Database Access
Customers of IBM Maximo or TRIRIGA SaaS do not have direct write access to the development or production DB2 database holding schema and application data. The only exception to this is in Maximo Enhanced Access DEV environments. Configuration of the product, including data dictionary (tables, views, indexes), must be performed using Maximo or TRIRIGA's native web-based configuration tools. Direct read-only database access can be configured through setup of OpenVPN account(s) or a Site-to-Site IPsec VPN tunnel. These are not configured by default. Customers must submit a case (ticket) if they would like these configured for their SaaS environment(s).
Application Server Platform
Only IBM WebSphere Application Server is supported.
WebSphere Application Server (WAS) Access
Customers of IBM Maximo and TRIRIGA SaaS do not have direct access to the application server (the WAS Administration console). WAS configurations such has JVM heap size, JMS queues are pre-configured. In the case of JMS queue configuration, the configured queue definitions have been linked to the Maximo External Systems application.
Customers of Maximo SaaS Flex can be provisioned one or more Enhanced Access DEV environment(s) at additional cost. These environments do allow wasadmin access to the IBM WebSphere console.
Third Party Applications
Third Party Applications are permitted for Flex (commercial) customers only. However, all applications that customers wish to have installed and run on IBM Cloud servers must be first be reviewed and approved by the SRE team. See Maximo Third Party Applications or TRIRIGA Third Party Applications for further details. Note: Third Party Applications are not permitted in FedRAMP (US Federal) environments.
Disclaimer: Information provided in this wiki is for informational purposes only. Content is not to be considered part of any existing IBM®️ Maximo or TRIRIGA customer subscription, agreement, license or contract. From time to time, this site may contain technical inaccuracies or typographical errors, and IBM do not warrant the accuracy of any posted information. The information contained in this wiki is subject to change without notice. By visiting this wiki, you consent to use of cookies and other tracking technologies by IBM’s subcontractor, Atlassian, in accordance with the Atlassian Cookies & Tracking Notice found at https://www.atlassian.com/legal/cookies. If you do not consent to the collection of your data by Atlassian at any time, please leave the wiki and delete the cookies and other web-tracking technologies through your browser.