How to create a Entity Relationship Document (ERD) for MAS 8

The following are the steps for MAS 8.11 and beyond as well as 8.10 and prior versions

Steps

For MAS 8.10 and prior, do the following steps; 

• Access Manage Admin pod terminal - /tools/maximo/internal
• execute the cli  - generd.sh
• This generates the erd files inside /tools/maximo/erd
• You then need to download that folder with contents into a local device with browser 
• Then, access the erd/index.html by using the local browser - and browse the erd pages.

Reference Link : https://www.ibm.com/docs/en/mas-cd/maximo-manage/continuous-delivery?topic=utilities-generating-entity-relationship-documents-erds

IBM - MAS : - Error AIUCO1026E: Unable to create user with id=, since it is already taken by a previously-deleted user.

The only way to restore the user or permanently delete the user from MAS is to update or delete the document in the mongoDB database.

Steps

1- Connect to the mongoDB shell 

https://www.ibm.com/support/pages/how-open-mongo-shell-mas-mongodb

2- List the databases:

show dbs

3- Use the mas core database:

use mas_<mas instance id>_core

4- find the user you want to restore or delete:

db.User.find({"_id" : "testuser"})

When the user is deleted, the document will end with the deleted information, i.e. user who deleted the record and the time of deletion, for example:

"deleted" : { "id" : "masadmin", "timestamp" : "2023-11-28T09:56:29.840785" }

You can then either restore the user or remove it from the database

To restore the user, execute the following command:

db.User.update({username: "testuser"},{$unset: {deleted:""}})

Once the command is executed, the user is visible again in MAS, however it is not visible in Manage.

An update to the user in MAS will lead to a syncronization failure with Manage. You need to reactivate the use in Manage.

To remove the user, execute the following command:

db.User.deleteone({username: "testuser"})

If you create a new user with the id of the user that you deleted, the synchronization with Manage will fail, you will have to reactivate the user in Manage.

The instructions to reactivate the user in Manage are here:

https://www.ibm.com/support/pages/reinstating-deleted-person-record-maximo

NOTE: removing the user from the database is permanent, it is recommended to have a working backup before attempting such operation. 

Reference link : https://www.ibm.com/support/pages/node/7085329

Maximo Application Suite 8.11: How to undelete a MAS User

Normally, it is impossible to re-create a MAS user within the UI after they are deleted. This error is reported when the user is re-created:

AIUCO1026E: Unable to create user with id=XXXX, since it is already taken by a previously-deleted user.

Steps

Once a mongo shell has been opened for your MAS mongo database, you have two options to re-create the user. You can either undelete the specific user to restore the old user, or delete the data record completely allowing you to re-create the user manually. 

This first command restores the old user (in this case, user1), making them once again visible within the MAS User Administration UI.

db.User.update({username: "user1"},{$unset: {deleted:""}})

Alternatively, you can run this second command to delete the user from your database. This allows you to re-create the user manually within the UI. 

Note this command deletes the old user completely, causing their user data to be lost forever.

db.User.deleteMany({username: "user1"})

Reference Link : https://www.ibm.com/support/pages/node/7087805

IBM Maximo Developer Area - SDKs and Samples for Maximo Development

 Reference Link : 

 https://github.com/ibm-maximo-dev

 

Backing & Restore Maximo Manage namespace with a script

1)  Use the manage-backup-restore.sh script to back up the Maximo Manage namespace.

Run the following command to back up the Maximo Manage namespace.

• manage-backup- restore.sh -w <mas-workspace-id> -i <MAS_INSTANCE_ID> -f <BACKUP_FOLDER> -m backup 

 

-w, --mas-workspace-id

The Maximo Manage workspace ID that you are backing up.

-i, --mas-instance-id

The Maximo Application Suite instance ID that you are backing up.

-f, --backup-folder

The folder where the backup artifacts are written to.

-m, --mode

Indicates whether to backup or restore. Use the value restore.

• manage-backup-restore.sh -w <mas-workspace-id> -i dev -f ./ -m backup

 Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=namespace-backing-up-maximo-manage-script&mhsrc=ibmsearch_a&mhq=MAS%20backup%20and%20restore

2) Restore your backed up Maximo Manage namespace manually or by using the manage-backup-restore.sh script.

To restore manually, use the oc cli command to restore the resources that you backed up.

The command applies the configuration that is specified in the file that is provided. Run the command for each *.yaml file that you created when you did the backup.

• oc apply -f <filename>

To restore the Maximo Manage namespace by using the manage-backup-restore.sh script, run the following command.

• manage-backup-restore.sh -w <mas-workspace-id> -i <MAS_INSTANCE_ID> -f <BACKUP_FOLDER> -m restore
• manage-backup-restore.sh -w <mas-workspace-id> -i dev -f ./ -m restore 

The script runs the oc apply command on all the *.yaml files in a specified folder, which restores the files.

Reference Link : https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=mm-namespace&mhsrc=ibmsearch_a&mhq=MAS%20backup%20and%20restore

IBM Maximo Application Suite installation with Ansible collection

 To automate some of the manual steps that are involved with installing Maximo® Application Suite and its components, use the Ansible collection roles that match your installation path or use case.

The IBM® Maximo Application Suite development team maintains a public Ansible collection that automates the installation and configuration of Maximo Application Suite and its dependencies. The Maximo Application Suite DevOps Ansible collection includes a number of automated tasks, referred to as roles and playbooks. These automated tasks can be used to streamline processes from having a simple Red Hat® OpenShift® cluster, to having Maximo Application Suite including multiple applications and its required dependencies.

Please find the below link for more information : 

https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=installing-ansible-collection

What's new in Maximo Application Suite 8.11

 Installation 

•  Support for MongoDB 5.0 and 6.0

Configuration

• Manage trusted certificate authorities
• Customizing the workload
• Horizontal and vertical pod scaling
• Pod scheduling with affinity and anti-affinity
• Pod scheduling with tolerations

Suite administration

• Configuring multiple login options
• Login notification
• Activate and deactivate users
• Enhancement to delete users
• Support for roll back and version lock
• API keys for user management
• Audit log generation to support the Federal Information Security Management Act (FISMA)
• Configuring passwords settings page moved to local authentication

Maximo Application Suite enhancements on Microsoft Azure

• Support for new databases  :Starting in Maximo Application Suite 8.11, configure databases such as Microsoft SQL Server or Oracle Database for using IBM Maximo Manage.
•  These databases can be hosted on private subnet of another VPC.

Maximo Application Suite enhancements on Amazon Web Services

Support for new databases :Starting in Maximo Application Suite 8.11, configure databases such as Microsoft SQL Server or Oracle Database for using IBM Maximo Manage. These databases can be hosted on private subnet of another VPC.

VPC peering is used to establish connection between the VPC of Amazon Web Services stack to the VPC of a database to establish database connection when the stack is deployed.

Support for selecting EBS volume type

Starting in Maximo Application Suite, support for selecting either gp3 or io1 as EBS volume type for worker nodes.

• FIPS and FISMA support for Maximo Application Suite on Amazon Web Services Marketplace in US GovCloud regions
• A Federal Information Processing Standard (FIPS) and Federal Information Security Management Act (FISMA) supported Maximo Application Suite can now be installed in the Amazon Web Services US GovCloud regions.
• The BYOL option is available for installing Maximo Application Suite in private hosted zone for existing Red Hat OpenShift cluster and New Red Hat OpenShift cluster by using the User Provisioned Infrastructure (UPI).

User assistance improvements

• Upgrading from IBM Maximo Asset Management to IBM Maximo Manage

Applications, industry solutions, accelerators, and add-ons

IBM Maximo IT

IBM Maximo IT is now available in Maximo Application Suite. Maximo IT provides a single point of user support and enterprise service management of information technology (IT) and operational technology (OT) assets and processes.

Reliability Strategies

Reliability Strategies is now available in Maximo Application Suite. 

By using Reliability Strategies, you can access a library of maintenance strategies that are based on reliability-centered maintenance and include both failure details and mitigation activities for each failure.  The library was developed by industry and domain experts and contains hundreds of assets and tens of thousands of possible failures across all known operating contexts.

New accelerators in the Maximo Application Suite catalog

Accelerators are solutions that are provided by IBM and IBM partners to complement or extend Maximo Application Suite capabilities. 

IBM Maximo Models for Electrical Distribution

IBM Maximo Models for Electrical Distribution provides model templates to enhance the reliability of energy and utility assets to anticipate downtime, degradation, and failures. 

This accelerator includes prebuilt notebooks and configuration files for several transmission and distribution asset classes, incorporating features available in IBM Maximo Health and IBM Maximo Predict.

Maximo Manage has new function to reduce system downtime when you do an update

After you upgrade to IBM Maximo Application Suite operator version 8.11, configure a database state to reduce Maximo Manage system downtime as you upgrade to Maximo Manage 8.7. and subsequent Maximo Manage upgrades.

Removal of Maximo Health and Predict - Utilities and Parts Identifier

Starting in Maximo Application Suite 8.11, the following industry solution and add-on are no longer available:

• Maximo Health and Predict - Utilities
• Parts Identifier

For More information please follow the below link.

https://www.ibm.com/docs/en/mas-cd/continuous-delivery?topic=new-in-811