Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 3 Basic MM Configuration : Configuring for Coherence WKA Cluster Discovery

Configuring for Coherence WKA Cluster Discovery
If you are using the Oracle Coherence cache provider, and you have configured the monitored project to discover cluster members using well-known addresses (WKA) then you must make some additional changes to the project CDD so that MM can monitor and manage the cluster.
You must also configure the MM.cdd to work with the cluster to be monitored, but the MM cluster itself does not use well-known address discovery
See Chapter 24, Cache OM and Cluster Configuration in TIBCO BusinessEvents Developer’s Guide for more details about WKA discovery.
Use unique ports — including for MM Server engine  If any of the monitored cluster engines are configured to run on the same machine as the MM server, ensure that the values for localport are unique across the MM server and the monitored clusters on that machine.
 
Task A Configure the To-Be-Monitored Project’s CDD
This section assumes that the CDD for the cluster to be monitored has already been configured for WKA cluster discovery. The additional configuration below enables MM to communicate with the cluster to be monitored.
Cluster configuration is documented in TIBCO BusinessEvents Developer’s Guide.
1.
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, you can put these properties into a property group, named as desired.
3.
   tangosol.coherence.wka = IP_of_machine_hosting_MMServer
   tangosol.coherence.wka.port = Unused_port_on_machine_hosting_MMserver
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, you must rename such 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.
Task B Configure the MM.CDD File
1.
2.
   tangosol.coherence.localhost
   tangosol.coherence.localport
Set localhost to the IP of the host where the MM server will run and set the localport property to a different port than any used by any monitored cluster engines on this host machine.
Task C Configure the be-engine.tra Files for Hosts with Multiple NIC Cards
For all host machines with multiple network cards (NIC), add the following property to the be-engine.tra file on each host:
java.property.java.rmi.server.hostname
The default value is localhost.
Set this property to the IP address of the desired NIC. This IP address must match the value specified in other properties where host IP is specified.
This property is required so that the engine is discovered by the MM cluster and appears as an active predefined engine. It is also required so that remote users can connect to any agents running on this host using a JMX client like JConsole.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved