CDD Configuration Procedures : Configuring Oracle Coherence Cluster Discovery

Configuring Oracle Coherence Cluster Discovery
See Enabling Use of Oracle Coherence as the Cache Provider for prerequisite actions you must take before you can use Oracle Coherence as the cache provider.
You can use either multicast or well-known-address (WKA) discovery, as appropriate. See Cache Cluster Member Discovery in TIBCO BusinessEvents Architect’s Guide for guidelines. Procedures for both methods of discovery are explained below.
Configuring Multicast Cluster Discovery
1.
2.
   tangosol.coherence.clusteraddress
   tangosol.coherence.clusterport
   tangosol.coherence.ttl
Specifying one or more well-known addresses disables all multicast communication. Remove any well-known address properties, if any.
See Multicast Discovery Properties for details
3.
   tangosol.coherence.localhost
   tangosol.coherence.localport
Configuring Well-Known Address Cluster Discovery
To understand how Oracle Coherence well-known address discovery works see Cluster Member Discovery Using Well-Known Addresses in TIBCO BusinessEvents Architect’s Guide.
To Configure Well-Known Address Cluster Member Discovery
To configure well-known address discovery, you must configure machine-specific settings at the cluster level and at the processing unit level. Machines where WKA PUs are to be deployed are called WKA machines in this procedure.
One processing unit deployed to a WKA machine must have the additional WKA configuration. Additional processing units can be deployed to a WKA machine, configured in the usual way, and they will discover and join the cluster in the usual way at runtime.
For details about the properties, see Well-Known Address Properties.
1.
2.
Open the cluster tab Properties sheet and add a pair of WKA properties for each machine you want to configure as a well-known address machine:
   tangosol.coherence.wkan HostIP
   tangosol.coherence.wkan.port Hostport
For example at the cluster level you might have these two WKA machines:
Property: tangosol.coherence.wka1       Value: 10.97.118.151
Property: tangosol.coherence.wka1.port  Value: 8098
Property: tangosol.coherence.wka2       Value: 10.97.118.152
Property: tangosol.coherence.wka2.port  Value: 8098
Property: tangosol.coherence.wka1       Value: 10.97.118.151
Property: tangosol.coherence.wka1.port  Value: 8098
Property: tangosol.coherence.wka2       Value: 10.97.118.151
Property: tangosol.coherence.wka2.port  Value: 8099
3.
Open the Processing Units tab properties sheet for a processing unit (PU). Configure one set of WKA properties to match one of the cluster level set of WKA properties:
   tangosol.coherence.localhost HostIP
   tangosol.coherence.localport Hostport
   be.engine.hostaddress HostIP
Use the same the value as the value of the tangosol.coherence.localhost property. See Configuring for Coherence WKA Cluster Discovery for more steps you must take when configuring MM, and read Chapter 6, Basic MM Configuration to understand more about deployment using MM.
Make sure the PU level property values match corresponding values set at the cluster level. That is, set the localhost property to the IP of the host where you will deploy the PU, and set the localport property to the port defined in the cluster properties localport property.
Repeat this step until you have configured a PU with matching PU-level properties for each cluster-level (that is, machine-level) set of WKA properties.
Each of these PUs must be deployed to the machine with the specified IP.
For example, if you configured the two well-known addresses shown in step 2, then at the processing unit level you would configure two processing units, each using one pair of to be deployed on one of those machines as follows:
Property: tangosol.coherence.localhost. Value: 10.97.118.151
Property: tangosol.coherence.localport. Value: 8098
Property: tangosol.coherence.localhost. Value: 10.97.118.152
Property: tangosol.coherence.localport. Value: 8098
At deploy time you must select those processing units to deploy on the appropriate (matching) WKA machine. It can be helpful if the name of the PU contains the machine name or other reminder that this PU must be deployed to a specific machine.
See Localhost and Localport Properties
4.
Continue cluster-level configuration at step 4 after you have finished the WKA configuration.