[copy-edit approved][SME-Approved] Importance of identity with domain GLN in FileWatcher and need to synchronize this name with the username stored against the GLN domain in the CIM MEMBER table.
Article ID: KB0089396
Updated On:
| Products | Versions |
|---|---|
| TIBCO Collaborative Information Manager | - |
| Not Applicable | - |
Description
Resolution:
Description:
============
After copying XML files from one CIM installation to another, a customer may find that their target CIM installation fails to come up after a restart.
Environment:
============
CIM / MDM, for all versions of CIM / MDM
Cause:
======
After copying XML files from one CIM installation to another (e.g., production to development), a customer may find that their target CIM installation fails to come up after a restart. Entries in the logs reveal the following message:
[main] DEBUG com.tibco.mdm.session.directory.member.VUValidationSsnBean - Could not find Member with UserName '<username>' and Domain 'GLN' and EnterpriseId '-1
- followed a couple of lines later by the MqException code SEC-5501.
Cross-examining the database reveals that the username stored against the GLN domain in the CIM MEMBER table:
SELECT * FROM MEMBER WHERE DOMAIN LIKE 'GLN'
reveals either a username that is different from the one reported in the logs above or no username at all.
Resolution:
===========
In the case(s) where an incorrect username exists with a correct username available, edit the file:
$MQ_HOME/config/FileWatcher.xml
and change the following construct, wherever it is present, to use the correct username(s) as returned previously in the SQL query:
<Credential domain="GLN">
<Identity><<username>></Identity>
</Credential>
Repeat for any other CIM XML files that contain the above element.
In the case(s) where an incorrect username exists create a new GLN user in the CIM MEMBER table and then edit the file:
$MQ_HOME/config/FileWatcher.xml
and change the following construct, wherever it is present, to use the new username(s) as returned previously in the SQL query:
<Credential domain="GLN">
<Identity><<username>></Identity>
</Credential>
Repeat for any other CIM XML files that contain the above element. Once all changes have been made, restart the CIM system. It should now start correctly.
Description:
============
After copying XML files from one CIM installation to another, a customer may find that their target CIM installation fails to come up after a restart.
Environment:
============
CIM / MDM, for all versions of CIM / MDM
Cause:
======
After copying XML files from one CIM installation to another (e.g., production to development), a customer may find that their target CIM installation fails to come up after a restart. Entries in the logs reveal the following message:
[main] DEBUG com.tibco.mdm.session.directory.member.VUValidationSsnBean - Could not find Member with UserName '<username>' and Domain 'GLN' and EnterpriseId '-1
- followed a couple of lines later by the MqException code SEC-5501.
Cross-examining the database reveals that the username stored against the GLN domain in the CIM MEMBER table:
SELECT * FROM MEMBER WHERE DOMAIN LIKE 'GLN'
reveals either a username that is different from the one reported in the logs above or no username at all.
Resolution:
===========
In the case(s) where an incorrect username exists with a correct username available, edit the file:
$MQ_HOME/config/FileWatcher.xml
and change the following construct, wherever it is present, to use the correct username(s) as returned previously in the SQL query:
<Credential domain="GLN">
<Identity><<username>></Identity>
</Credential>
Repeat for any other CIM XML files that contain the above element.
In the case(s) where an incorrect username exists create a new GLN user in the CIM MEMBER table and then edit the file:
$MQ_HOME/config/FileWatcher.xml
and change the following construct, wherever it is present, to use the new username(s) as returned previously in the SQL query:
<Credential domain="GLN">
<Identity><<username>></Identity>
</Credential>
Repeat for any other CIM XML files that contain the above element. Once all changes have been made, restart the CIM system. It should now start correctly.
Issue/Introduction
[copy-edit approved][SME-Approved] Importance of identity with domain GLN in FileWatcher and need to synchronize this name with the username stored against the GLN domain in the CIM MEMBER table.
Feedback
Yes
No
Powered by
