CDD Cluster Tab Coherence Properties Reference
Coherence properties can be configured using the CDD Cluster Tab. Refer to the following table for a list of properties that you can use to retrieve data from the 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. See Oracle Coherence Cluster Discovery for details.
Property | Notes |
---|---|
Multicast Discovery Properties
If you will define cluster members using multicast discovery properties, use the properties in this section, instead of those in the section Well-Known Address Properties . |
|
be.engine.cluster.as.minSeeders |
|
TIBCO BusinessEvents sets the value of minimum seeders for user defined spaces to the same value as the quorum size, by default.To override the default value of minimum seeders, you can specify the new value using this property. | |
be.engine.cluster.minCacheServers.strict |
|
When this property is set to true and if the number of Cache nodes drops below Quorum, then the cluster is placed into suspend mode. Default value is false. | |
be.engine.cluster.minCacheServers.strict.selfRepair |
|
When this property is set to true, the system tries to resume operations if and only when the Quorum is reached again. If this property is set to false once the operations are suspended, then the system will stay in that mode until you manually intervene. Default value is false. | |
tangosol.coherence.clusteraddress |
|
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.
Possible values are addresses between (and including) 224.0.0.0 and 239.255.255.255. Default value is 224.3.3.1 |
|
tangosol.coherence.clusterport |
|
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.
Possible values are integers between 1 and 65535. Default value is 35463. |
|
tangosol.coherence.ttl |
|
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. Set the single-host cluster to the value of 0 (zero). Set the simple switched backbone to the value of 1 (one). Set the advanced backbone with intelligent switching to the value of t may require a value of 2 (two) 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. It is required for multicast configuration.
Possible values are integers between 0 and 255. Default value is 4. |
|
Localhost and Localport Properties
Use the localhost and localport properties for the following cases:
Add these properties at the PU level when well-known address discovery is used, as explained in Configuring Well-Known Address Cluster Discovery. Default values are provided at the cluster level. However if you need to specify these properties at the PU level, add them as Processing Units tab properties and provide the values as needed. |
|
tangosol.coherence.localhost |
|
Specifies the IP address that the socket will listen to or publish on.
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. Default value is localhost. |
|
tangosol.coherence.localport |
|
Specifies the port that the socket will listen to or publish on.
Possible values are 1 to 65535. Default value is 8088. |
|
Well-Known Address Properties
See Configuring Well-Known Address Cluster Discovery . Note: If you discover cluster members using well-known addresses, use the properties in the referenced section and remove the multicast discovery properties shown in the section
Multicast Discovery Properties .
|
|
tangosol.coherence.wkan.port |
|
The following are 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. For example (in the UI the properties are not entered quite this way): tangosol.coherence.wka1 10.97.118.151 tangosol.coherence.wka1.port 8088 tangosol.coherence.wka2 10.97.118.152 tangosol.coherence.wka2.port 8088 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 ) |
|
Other Coherence Properties
These properties are used in various situations. |
|
tangosol.coherence.distributed.threads |
|
Specifies the number of Coherence domain threads used by the distributed cache service when Oracle Coherence is used as the cache provider.
This property is mainly used with write-behind database strategy. However, when used with the cache aside strategy, this setting is used for handling cache operations only (gets and puts). In this release, the property must be set to the same value across the. The value must be set to processing unit. A value of zero 0 signifies that all of the relevant tasks are performed on the service thread. See Write Behind Options in TIBCO BusinessEvents Architect’s Guide. Default value is0. |
|
tangosol.coherence.override |
|
Specifies the location of an Operational Descriptor Override File. A sample value is:
file:/c:/tmp/my_tangosol-coherence-override.xml
.
An example of an override file is provided in BE_HOME/lib/cep-datagrid-oracle.jar. Use of an operational descriptor override is not generally required. For details on override files, see Coherence documentation. |
|
tangosol.coherence.localport.adjust |
|
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.
To turn off auto-incrementing, add this property tangosol.coherence.localport.adjustand set the value to false. Default value is true. |
|
tangosol.coherence.guard.timeout |
|
When infrastructure latency occurs such as remote databases, you can improve the performance of inference engines by setting the property value to
0 in
be-engine.tra..
For example: tangosol.coherence.guard.timeout=0. |