![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
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.
• 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.See Multicast Discovery Properties for details
2.
Property: tangosol.coherence.wka1 Value: 10.97.118.151
Property: tangosol.coherence.wka1.port Value: 8098Property: 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: 8098Property: tangosol.coherence.wka2 Value: 10.97.118.151
Property: tangosol.coherence.wka2.port Value: 8099tangosol.coherence.localhost HostIPtangosol.coherence.localport Hostport
be.engine.hostaddress HostIPUse 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. 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:
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |