Administrator tasks
All Administration tasks are subject to the IBM® Change Management Process and, unless otherwise agreed upon, will follow the standard change deployment path through the system, (e.g. Development, Test, Production).
- Tasks managed by the IBM SRE team
-
For changes that require system level access, these will be managed by the IBM SRE team. For example, the tasks below are all within the scope of SRE:
-
Class file updates
-
Applying FixPacks (patches) and Upgrades
-
EAR re-build & redeploy
-
Database backups
-
Database Configuration (running configdb)
-
WebSphere® Updates/Upgrades
-
HTTP Updates/Upgrades
-
Database Updates/Upgrades
-
Network Updates/Upgrades
-
Executing SQL scripts or procedures (e.g. language updates, data updates)
-
OS Updates/Upgrades
-
OS Level batch Jobs
-
- Tasks managed by the Customer
-
For changes that can be made through the front-end UI, these should be managed by the client or the implementation team. For example, this could include:
-
Adding Maximo® Cron tasks or Escalations
-
Application designer changes
-
Data loading
-
Migration manager package deployments
-
User Management (adding users/security groups)
-
Workflow updates
-
Automation Script creation
-
- Tasks managed by the Customer - (Maximo on Cloud Flex DEV only)
-
For changes that do not require system level access, these will be managed by the customer.
For example, the tasks below are all within scope:
-
Application Configuration in UI
-
Class file updates
-
EAR re-build & redeploy
-
Database Configuration (running configdb)
-
Executing SQL scripts or procedures (e.g. language updates, data updates)
Please note: There may be additional tasks that are not included in the lists above
-
- Important Note regarding Maximo database configuration changes
-
Although Maximo database configuration (configdb) can be executed through the Maximo front end (using the Database Configuration application >> Apply Configuration Changes), it is strongly recommended that no structural changes are made using configdb through the application because there are several issues that could be encountered. For example, configdb might fail, or time out part way through the process due to a table lock. Views may not be created, and it is possible triggers do not get created or are missing. This can lead to severe errors which show as BMXAA- 'type' errors being displayed in the application. Examples of structural changes:
-
Adding/removing tables and columns
-
Changing field sizes or data types
Non-structural changes are considered lower risk and can be done using configdb through the Maximo front end. Examples of non-structural changes would be:
-
Adding/removing a domain or class file
-
Changing the title/label/search type values from a field
-