How can multiple TIBCO Collaborative Information Manager(CIM) instances share a single Enterprise Messaging Service (EMS) Server?
Article ID: KB0088486
Updated On:
| Products | Versions |
|---|---|
| TIBCO Collaborative Information Manager | - |
| Not Applicable | - |
Description
Resolution:
How can multiple TIBCO Collaborative Information Manager(CIM) servers share a single Enterprise Messaging Service (EMS) Server?
Environment:
TIBCO Product name and version: TIBCO Collaborative Information Manager 7.x
Operating System(s): All Operating Systems
Symptoms:
Not Applicable.
Cause:
Not Applicable.
Resolution:
In a clustered environment each of the CIM instance has to use same (JAVA Messaging Service) JMS/EMS, common directory and Database. EMS server details provided in each of the CIM instances ConfigValues.xml should be same, to gain the performance expected out of a clustered environment.
If it is required to use custom names for the Queues and Topics instead of the out-of-box names, then it can certainly be done.. But even in that case EMS has to be shared between the CIM instances.
For example: If it is required to rename Q_ECM_CORE_WORKFLOW queue as XYZ_CIM_WORFKLOW_QUEUE, then first it is required to create a Queue with that name in EMS and change the occurrences of Q_ECM_CORE_WORKFLOW to XYZ_CIM_WORFKLOW_QUEUE in ConfigValues.xml on each of the CIM instances.
In other words one has to share the Queues and Topics between the two instances of CIM servers if it is a clustered CIM environment
However for a non-clustered setup, it will need to create and use different set of queues and topics for each of the CIM instance on same instance of EMS. For example:
Q_ECM_CORE_WORKFLOW_1 for CIM Instance 1 and Q_ECM_CORE_WORKFLOW_2 for CIM Instance 2.
Attachments:
None.
References:
None
How can multiple TIBCO Collaborative Information Manager(CIM) servers share a single Enterprise Messaging Service (EMS) Server?
Environment:
TIBCO Product name and version: TIBCO Collaborative Information Manager 7.x
Operating System(s): All Operating Systems
Symptoms:
Not Applicable.
Cause:
Not Applicable.
Resolution:
In a clustered environment each of the CIM instance has to use same (JAVA Messaging Service) JMS/EMS, common directory and Database. EMS server details provided in each of the CIM instances ConfigValues.xml should be same, to gain the performance expected out of a clustered environment.
If it is required to use custom names for the Queues and Topics instead of the out-of-box names, then it can certainly be done.. But even in that case EMS has to be shared between the CIM instances.
For example: If it is required to rename Q_ECM_CORE_WORKFLOW queue as XYZ_CIM_WORFKLOW_QUEUE, then first it is required to create a Queue with that name in EMS and change the occurrences of Q_ECM_CORE_WORKFLOW to XYZ_CIM_WORFKLOW_QUEUE in ConfigValues.xml on each of the CIM instances.
In other words one has to share the Queues and Topics between the two instances of CIM servers if it is a clustered CIM environment
However for a non-clustered setup, it will need to create and use different set of queues and topics for each of the CIM instance on same instance of EMS. For example:
Q_ECM_CORE_WORKFLOW_1 for CIM Instance 1 and Q_ECM_CORE_WORKFLOW_2 for CIM Instance 2.
Attachments:
None.
References:
None
Issue/Introduction
How can multiple TIBCO Collaborative Information Manager(CIM) instances share a single Enterprise Messaging Service (EMS) Server?
Feedback
Yes
No
Powered by
