How to isolate inbound message processing and user operations in CIM Engine in a clustered environment?.
Article ID: KB0086951
Updated On:
| Products | Versions |
|---|---|
| TIBCO Collaborative Information Manager | - |
| Not Applicable | - |
Description
Resolution:
Assuming there are 4 instances of CIM on 4 separate machines.
First, cluster the first 3 instances where the web server is clustered (load balance mode), and JMS, COMMONDIR, Database is shared/common. Then cluster the 4th instance only up to the database and the commondir, JMS queues (queue.prop) but not the topics (bus.prop).
The main point to be noted is that for all the above four instances use the same Tangosol cache servers.
With the above setup in place, all the UI related stuff will be directly handled by the 4th Instance and the messages sent back or forth by this instance will be picked by the same instance as the JMS is not shared.
Please find the attached viso diagram for pictorial representation.
Assuming there are 4 instances of CIM on 4 separate machines.
First, cluster the first 3 instances where the web server is clustered (load balance mode), and JMS, COMMONDIR, Database is shared/common. Then cluster the 4th instance only up to the database and the commondir, JMS queues (queue.prop) but not the topics (bus.prop).
The main point to be noted is that for all the above four instances use the same Tangosol cache servers.
With the above setup in place, all the UI related stuff will be directly handled by the 4th Instance and the messages sent back or forth by this instance will be picked by the same instance as the JMS is not shared.
Please find the attached viso diagram for pictorial representation.
Issue/Introduction
How to isolate inbound message processing and user operations in CIM Engine in a clustered environment?.
Attachments
Feedback
Yes
No
Powered by
