CX Tables

Overview

The tool uses Hazelcast IMDG for clustering the runtime server JVMs. Even if only a single JVM is in use, you still need to configure the cluster name and network settings to avoid conflicts with other existing or potential Hazelcast configurations.

For example, if the tool is installed separately for different environments, such as testing and production, each installation must have its own distinct cluster. This ensures that tasks submitted to one cluster, such as testing, do not execute on another cluster, such as production.

The following Hazelcast configuration files are required. Both files must specify the same cluster name, address, and port.

  1. hazelcast.xml — Used by the rtserver Runtime Server.
  2. hazelcast-client.xml — Used by the web server to monitor the cluster’s status for the online dashboard.

hazelcast.xml

Update the config/override/hazelcast.xml file by specifying a unique cluster-name and port.

<cluster-name>dih-dev</cluster-name> 
   <network> 
        <port auto-increment="false">5701</port> 
        <join> 
            <multicast enabled="false"> 
                <multicast-group>224.2.2.3</multicast-group> 
                <multicast-port>54327</multicast-port> 
            </multicast> 
            <tcp-ip enabled="true"> 
                <interface>localhost</interface> 
            </tcp-ip> 
        </join> 
    </network>

hazelcast-client.xml

Update the config/override/hazelcast-client.xml file by specifying a unique cluster-name and port.

<cluster-name>dih-dev</cluster-name> 
    <instance-name>DIH Client</instance-name> 
    <network> 
        <cluster-members> 
            <address>localhost:5701</address> 
        </cluster-members> 
        <connection-timeout>2000</connection-timeout> 
    </network>