Contribute in GitHub:
Edit online
Limitations & Exclusions
Maximo Application Suite SaaS is implemented using a defined set of technologies and operates within a security profile designed to ensure our client's data is secure and the applications operate efficiently and effectively. As a result of the decisions made regarding technologies and to meet the high security standards, there are differences between what is available via the SaaS offering and what a client could do if they hosted and operated the Suite themselves.
The following items are not included or allowed in the Maximo Application Suite SaaS offering:
Databases
The following are database limitations of the MAS SaaS offering:
-
IBM DB2 Warehouse is the default database. MS SQL is available for Standard Edition and Premium Edition for an additional fee. Oracle is not currently supported.
-
The source database must be DB2. It should be fully tested and verified prior to providing an export to IBM when migrating.
-
IBM must be informed if the source database was converted from a different source platform (MS SQL, Oracle)
-
Conversion effort must include all custom saved queries, reports, max relationships, conditions, restrictions, properties etc.
-
If converting from Oracle to DB2, Oracle compatibility mode is not supported.
-
Text Search is not supported in IBM DB2 Warehouse.
-
Running SQL statements (update/insert/delete) directly on the database is not allowed and the IBM SRE team will not be able to execute those statements for you. DBC scripts are not allowed. Customers should carry out these changes using the Maximo UI via Automation Scripts or the Maximo Integration Framework.
Database Access
The following table shows database access based on MAS SaaS Edition:
| Database Access Type | Essentials | Standard | Premium |
|---|---|---|---|
| Execute Database Configuration Changes | Y 1 | Y 1 | Y 1 |
| PROD DB Read Access | N | N | N |
| PROD DB Write Access | N | N | N |
| PROD Replica DB Read Access | N 2 | Y | Y |
| PROD Replica DB Write Access | N 2 | N | N |
| Non-PROD DB Read Access | N | Y 3 | Y 3 |
| Non-PROD DB Write Access | N | Y 3 | Y 3 |
| Triggers / Procedures | N | N | N |
1 Customers must use the Database Configuration Application in Manage to Create/Update Tables/Columns/Indexes/Sequences. They can then use the Self Service Portal (SSP) to commit and execute these changes
2 Replica DB not available in Essentials Edition
3 Customers should use the Self Service Portal (SSP) to request access
Java Extensions
Java extensions supported only in Premium Edition, Non-Shared Cluster for clients migrating to MAS SaaS that already have Java extensions in use. Maximo Manage Automation Scripting capability should be used by new clients and are preferred for migrating clients. Existing Maximo customers who have Java extensions are encouraged to migrate / convert these functions into automation scripts within the application.
3rd Party Applications
Maximo Application Suite SaaS will not host or support 3rd party applications. Third party applications hosted outside the of the MAS SaaS environment can be integrated to applications with the Suite provided they follow standard MAS integration protocols.
AWS and MAS Administrator Functions
Direct access to ROSA clusters is not available. Changes required must be submitted using an IBM support case and the IBM SRE team will execute. Clients will not have access to the operating system, file system, database or overall system administration of the Suite. MAS User Admin Access is allowed.
| Admin Access Type | Essentials | Standard | Premium |
|---|---|---|---|
| AWS Admin Access | |||
| ROSA OpenShift Cluster Admin | N | N | N |
| MAS Admin Access | |||
| MAS Admin (Deploy New App, Configure SSO, SMTP) | N | N | N |
| MAS User Admin (Manager users, Configure license type, license usage) | Y | Y | Y |