The MIF Error Message is not displayed on both servers’ applications. Some of the MIF Error xml files were sent to MIF server and some of them were sent to UI server.
MIF and UI Maximo instances are installed on different servers. That is, there is one server for the UI cluster and another sever for the MIF.
Both the UI and MIF instances are referencing the same table in the same database. However error message details are not visible in the UI instance Message Tracking application. However, in the MIF instance, the error messages are visible.
This issue is related to this Integration global directory system property setting:
In a clustered environment, the Integration global directory must be accessible to all members of the cluster.
The error xml file will be written under the root folder of the Integration Global Directory. If WebSphere application servers are distributed in a multi-node environment, the integration global directory must exist in a shared location that all application servers can access.
This shared location can be either a UNC path (Windows), or a mount point (Unix).
When installing Websphere, you created the Windows service in Control Panel Administrative Tools - Service. You can see the user in the "Log On As" field.
The above user is specified to run WebSphere services and must have access to read and write to this share or mount point. In Windows, do not use a local system account to start Windows services but rather a domain account. Local system accounts do not have access to mapped drives or UNC shares.
The MIF error messages are actually stored in the file system and only its entries are in the database. So when you go to the Maximo Message Tracking application, you fetch the error entries from the database, but the actual error messages are picked up from the file system, parser and displayed in the Maximo applications. If the current JVM is not accessing the right file system, the error XML is not found and the fields will be empty in the Maximo applications.
The actual MIF error xml files are stored in the Integration Global Directory - Error folder separated by the queue name. For example:
If you set each server with its own Integration Global Directory, but they are not shared by both MIF and UI instances. If an error occurs when importing the data using the CQIN, an error xml file will be generated in the MIF server - Integration Global Directory - error folder - jms.maximo.int.queues.cqin sub-folder.
If an error occurs when exporting the data using the SQOUT, an error xml file will be generated in the UI server - Integration Global Directory - error folder - jms.maximo.int.queues.sqout sub-folder.
That is why when you log onto the MIF instance, you can see the error xml file only for the CQIN queue. When logging onto the UI instance, you can see the error xml files for queue SQOUT only.
Resolving The Problem
To fix up this issue, you need to use a UNC path (Windows) for the Integration Global Directory. And use a domain account user to create the Websphere services in Windows Services.
The Local system account user in Windows can see the files in the local system only.
17 June 2018