Cluster Deployment Descriptor Reference : Cluster Tab — Cache OM — Coherence Properties

Cluster Tab — Cache OM — Coherence Properties
Oracle Coherence Cache Provider  This section is relevant only if you use Oracle Coherence as the cache provider.
TIBCO BusinessEvents Express  This section relates to Cache OM functionality and does not apply to TIBCO BusinessEvents Express edition.
Add properties as needed to configure multicast cluster member discovery, or well-known address cluster member discovery.
Use this setting if multicast discovery is used and if you need a non-default value. Specifies the multicast IP address that the socket will listen to or publish on.
Use this setting if multicast discovery is used and if you need a non-default value. Specifies the port that the socket will listen to or publish on.
Specifies the time-to-live setting for the multicast, that is, the maximum number of "hops" a packet can traverse. A hop is defined as a traversal from one network segment to another via a router.
For production use, set this value to the lowest integer value that works. Setting the value too high can use unnecessary bandwidth on other LAN segments and can even cause the operating system or network devices to disable multicast traffic.
On a single-host cluster, set to zero (0). On a simple switched backbone, set to 1. On an advanced backbone with intelligent switching, it may require a value of 2 or more.
Note: A value of 0 is intended to keep packets from leaving the originating machine. However, some operating systems do not implement this correctly, and the packets may in fact be transmitted on the network.
Default values are provided at the cluster level. However if you need specify these properties at the PU level, add them as Processing Units tab properties and provide the values as needed.
As needed, you can set the value of the localhost property to the value localhost. However, if localhost is used as the loop back address (127.0.0.1) you must enter a machine name or IP address.
Specifies the port that the socket will listen to or publish on.
Note  If a specified port is not available, the object management layer (by default) increments the port number until it finds an available port. Avoid potential conflicts by choosing a number that is not close to a port used by other software in your environment.
Tip  To turn off auto-incrementing, add this property:
Note  If you will discover cluster members using well-known addresses, use the properties in this section, and remove the multicast discovery properties shown in the section Multicast Discovery Properties.
tangosol.coherence.wkan.port
The addresses and ports for machines used by the well-known address cluster discovery protocol. At least one of these machines must be running at any time so that others can join the cluster.
For tangosol.coherence.wkan, enter the IP address.
For tangosol.coherence.wkan.port, enter a value between 1 and 65535.
tangosol.coherence.wka1        10.97.118.151
tangosol.coherence.wka2        10.97.118.152
Also at the Processing Units tab, configure localhost and localport properties for one processing unit that will be deployed to the WKA machine. Set the localhost value to the value of the wkan property. Set the localport value to the value of the wkan.port property. (See Localhost and Localport Properties)
Note  You can configure two well-known addresses for the same machine, and use a different port number for each. In this case you would also configure two processing units, each of which matches one set of WKA properties.
Tip  To turn off auto-incrementing, add this property:
Specifies the number of Coherence daemon threads used by the distributed cache service when Oracle Coherence is used as the cache provider. Used only with write-behind database strategy (not used with cache aside). Value is per cache agent (but the property must be set to the same value across the cluster).
An auto-incrementing feature ensures that a different port is used if one specified is already in use. However in various situations you may want to turn off this behavior. For example, if you use TIBCO BusinessEvents Monitoring and Management, and the MM server runs on the same machine as any of the monitored cluster engines, you must explicitly ensure that all ports used by MM and the monitored cluster are unique. Therefore the auto-incrementing feature may not be appropriate.