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


Chapter 24 Cache OM and Cluster Configuration : 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 basic guidelines. Procedures for both methods of discovery are explained below.
Guidelines for Managing Coherence Clusters
Provided Files
The following files are located in BE_HOME/lib/cep-datagrid-oracle.jar:
coherence-cache-config-jdbc.xml is an example cache configuration descriptor file.
tangosol-coherence-override-tibco-be.xml is an example operational descriptor override file. To reference such a file, use the property tangosol.coherence.override in the CDD file.
To understand when and how to use them, read the Coherence documentation.
The following links to Coherence documentation provide helpful information for use of Coherence as the cache provider.
Checklist and Guidelines Before Architecting a New Project
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/deploy_checklist.htm
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/deploy_plat_consid.htm
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/tune_perftune.htm
Coherence Network Protocol
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/cluster_tcmp.htm
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/tune_datagramtest.htm
Coherence Metrics
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/appendix_mbean.htm
http://download.oracle.com/docs/cd/E15357_01/coh.360/e15723/appendix_operational.htm
Configuring Multicast Cluster Discovery for Coherence Clusters
Multicast is the default option. If default values for multicast properties work in your environment, you can omit this procedure.
To Configure Multicast Cluster Discovery
1.
   tangosol.coherence.clusteraddress
   tangosol.coherence.clusterport
   tangosol.coherence.ttl
See Multicast Discovery Properties for details
2.
   tangosol.coherence.localhost
   tangosol.coherence.localport
Configuring Well-Known Address Cluster Discovery for Coherence Clusters
You can add up to nine well-known addresses. If you need to add more refer to Coherence documentation for instructions about using override files.
To configure well-known address discovery, you must configure machine-specific settings at the cluster level and at the processing unit level.
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.
To Configure Well-Known Address Cluster Member Discovery
For details about the properties, see Well-Known Address Properties.
1.
   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
2.
   tangosol.coherence.localhost HostIP
   tangosol.coherence.localport Hostport
Use the same the value as the value of the tangosol.coherence.localhost property. See Configuring for Coherence WKA Cluster Discovery in Chapter 3, Basic MM Configuration in TIBCO BusinessEvents Administration for more steps required when configuring MM.
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.
3.
Repeat step 2 until you have configured a PU with matching PU-level properties for each cluster-level (that is, machine-level) set of WKA properties.
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 as follows:
tangosol.coherence.localhost. Value: 10.97.118.151
tangosol.coherence.localport
. Value: 8098
tangosol.coherence.localhost. Value: 10.97.118.152
tangosol.coherence.localport
. Value: 8098
At deploy time you must deploy the processing units on the appropriate (matching) WKA machine. It can be helpful if the name of the PU contains the machine name as a reminder that this PU must be deployed to that machine.
See Localhost and Localport Properties.

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