Configuring the Project’s CDD to Communicate with the Cluster

This section assumes that the CDD for the cluster to be monitored has already been configured for WKA cluster discovery, so that the additional configuration enables MM to communicate with the cluster.

Procedure

  1. Open the project to be monitored in TIBCO BusinessEvents Studio and open its CDD file in the CDD editor.

    This CDD must be copied for use as the master CDD. See Project Master and Deployed Locations of CDD and EAR Files to understand the purpose of these copies of the CDD.

  2. For each PU you will deploy to a WKA machine, add the be.engine.hostaddress property (in addition to the tangosol.coherence.localhost and tangosol.coherence.localport properties as needed for WKA configuration). Set it to the same value as the localhost property:
       tangosol.coherence.localhost HostIP
       tangosol.coherence.localport Hostport
       be.engine.hostaddress HostIP

    For better organization, put these properties into a property group, named as desired.

  3. Add the following WKA properties to the cluster level properties:
       tangosol.coherence.wka = IP_of_machine_hosting_MMServer
       tangosol.coherence.wka.port = Unused_port_on_machine_hosting_MMserver
    Note: If the CDD has already been configured for WKA cluster discovery and either one or both of the properties, tangosol.coherence.wka and tangosol.coherence.wka.port, already exist in the CDD under the cluster level properties, rename such a pair of properties to tangosol.coherence.wkan and tangosol.coherence.wkan.port, where n is the first unused integer in the WKA list. All the other WKA properties can remain as they are.

    Cluster configuration is documented in TIBCO BusinessEvents Configuration Guide.