IBM Maximo Application Suite - 8.11.0 APARs fixed

This list of Known Issues fixed in Maximo Application Suite 8.11.0.

DT209860 - Case sensitive issue when synchronizing groups 

DT213769 - Manager's access mode property for PVC configuration is not properly displayed on the workspace configuration UI

DT212451 - Import user feature is sending salted password to the user email

DT196144 - SAML users replacing local user login 

DT215063 - LDAP Bind user with "\" character does not work

DT214769 - Coreapi pod crashing during initialization

DT222586 - scimsync-agent failing comparison when adding user group members

DT222765 - SAML issue with wrong link field

DT216022 - Number cast issue when numeric userID

DT222884 - Diff secretName than the expect is crashing the deployer

DT230445 - Importuser/coreapi is not accepting "-"

DT225038 - LDAP customMaxSearchResults CR information being replaced when updating UI config 

DT223861 - Reduce render on the config page

DT212073 - SMTP/sendmailapi: Password change notification email is not sent to users with Japanese display name

DT223701 - Error saving a synchronized LDAP user - Mismatched input parameters

Reference Link : 

https://www.ibm.com/support/pages/node/7039339

https://www.ibm.com/support/pages/node/7038760

Maximo Application Suite Admin APIs 8.11.x

IBM  Maximo Application Suite provides powerful AI-driven asset and analytics solutions for your enterprise needs.

Maximo Application Suite is a powerful collection of:

• Applications
• Industry solutions
• Add-ons
• Tools

These APIs provide a mechanism for performing administrative operations against an installation of Maximo  Application Suite.

Reference link : https://developer.ibm.com/apis/catalog/maximo--maximo-application-suite-admin-apis/Introduction

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