IBM Support

Collecting Data: User Synchronization from MAS to Manage

Troubleshooting


Problem

This document describes the process for collecting data for problems with the User Synchronization from MAS to Manage.

Problems with the User Synchronization from Manage to MAS are discussed in a separated document. 
Problems related to LDAP Synchronization are not discussed in this document.

Collecting this MustGather information helps understand the problem and save time analyzing the data.

  1. Set INTEGRATION logger to DEBUG and SQL logger to INFO (Change then back to error);
  2. Collect error information mentioned in UI;
  3. After loggers are turned on and issue reproduced, collect logs in related pods: usersyncagent, internalapi and mea (mea pod can be included in all pods), informing timestamp;
  4. Collect how many users are not synchronized and how many users are already synchronized in Manage database (MAXUSER table):
    1. Collect the results of SQL statement: SELECT * FROM MAXUSER;
    2. Collect MongoDB information: db.User.find({})

How to collect referenced information

Users who have an entitlement to Maximo Manage are synchronized from Maximo Application Suite to Maximo Manage by an agent process that continuously queries the user registry in Maximo Application Suite.

The user synchronization process from Maximo Application Suite to Maximo Manage uses the Maximo integration framework. It uses an enterprise service to post data to Maximo Manage. 

Users who have a PENDING or DELETE_PENDING status are synchronized to Maximo Manage. The synchronization status for a user who is synchronized successfully is SUCCESS. The synchronization status for a user who fails to be synchronized is ERROR. You can view status information in the administrative console of Maximo Application Suite or in the output logs.

Synchronized user data is processed as a series of messages by an enterprise service of the integration framework in Maximo Manage.

Synchronized users are listed in the Users application. Users who are updated to be deleted or to have no access entitlement in Maximo Application Suite are made inactive in Maximo Manage, but they are not deleted.

This document contain further information about User synchronization: User creation, authentication, and synchronization

 
  • Check system information of environment on which this issue is occurring (include MAS version);
  • Check if the problem began after an upgrade to a new version;
  • Gather the steps to reproduce the problem, including screenshots or videos;
  • Check if unique fields were added: userid, username and primary email address;
  • Check if the error happens for all the users or specific ones;
  • Check if the value for mxe.int.dfltuser system property is mxintadm;
  • Check if pods are running correctly in OpenShift Container Platform;
  • Check if Manage database is case sensitive.
There are common issues already reported and in the Support team's knowledge. The errors and solutions are described in the document Troubleshooting User Synchronization Problems.
Title Description
Search all usersync documents on IBM Support Portal Shows a list of all documents tagged with this topic.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSRHPA","label":"IBM Maximo Application Suite"},"ARM Category":[{"code":"a8m50000000CbHdAAK","label":"System Administration-\u003EUsers"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
10 December 2024

UID

ibm17167093