Clustered? Consider this before you chat using SmartCloud Control Desk 7.5.1
Lili Orozco 110000J4HM Visits (2173)
When you deploy SmartCloud Control Desk 7.5.1 in a clustered environment, an instance of a chat server is running in every Java Virtual Machine (JVM) configured. Before a chat session can be established between two chat users connected to different chat server instances, the CometD Oort Cloud needs to be set up.
Live Chat in SmartCloud Control Desk 7.5.1 is based on CometD technology and Oort is the clustering solution used by CometD.
Setting up the CometD Oort Cloud requires "registering" the URL address of each of the chat server instances. The Oort Cloud is established at application startup and once established, the chat servers can communicate with each other and establish chat sessions regardless where the chat users or chat agents are connected.
So how does SmartCloud Control Desk know the URL address of each of the chat servers? You need to tell it using instance properties. Each JVM URL address needs to be registered via an instance property value in TPAE.
In order to do this:
To uniquely name each of the instances, add the -Dmxe.name= parameter to the JVM arguments of each of the JVM instances.
Note that the servers need to be restarted for the parameter to take effect.
To add an instance value:
Repeat these steps to create new instance values for all of the JVMs in the cluster. Note that all of the JVMs must be up and running for their values to be displayed in the Server Selection dialog. Restart the cluster for the live chat servers to be initialized correctly.