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


Chapter 24 Cache OM and Cluster Configuration : Configuring Cluster Discovery and Internal Communication

Configuring Cluster Discovery and Internal Communication
When you add a CDD file and select Cache OM type, you must configure how the members of the cache cluster discover each other at runtime and communicate with each other once the cluster is established.
This section has summary steps for both cache providers, and pointers to sections with more details.
To Configure a TIBCO BusinessEvents DataGrid Cluster (Metaspace)
1.
2.
be.engine.cluster.as.discover.url
be.engine.cluster.as.listen.url
The properties can be omitted if you use PGM multicast with default values. See the following sections for details on configuring these properties:
3.
a.
      be.mm.cluster.as.listen.url MMHostIP: Port
Specify the IP of the computer hosting the MM server, and an unused port.
b.
Add the value of the be.mm.cluster.as.listen.url property to the list of addresses in the be.engine.cluster.as.discover.url property, which should be present at the cluster level (so the value is identical for all potential cluster members).
The discover URL for well-known address configuration uses the following format:
   tcp://ip:port[;ip:port]*
To Configure an Oracle Coherence Cluster
1.
2.
3.
4.
To Configure Cache-Related Object Management Settings
1.
2.
Support for Hostaware Replication
Hostaware replication for ActiveSpaces is controlled by the property be.engine.cluster.as.hostaware.enable.
Hostaware replication requires that the member name be a 2-part name separated by a "."
By default, this property is true ( or enabled ).
If true, the ActiveSpaces member name will be set as:
hostname.be-engine-name
where be-engine name is what is given on the -n command line option
When hostaware replication is enabled, if the cache nodes are not deployed on multiple machines to satisfy replication by the host, then replication will not happen (or will happen only according to the number of hosts available).
For example, if "Number of Backup Copies" is set to "1" and all cache nodes are deployed on a single host, then replication will be disabled (regardless of the number of cache nodes on that single host). If "Number of Backup Copies" is set to "2", and cache nodes are deployed only on 2 hosts, then only "1" backup copies will be maintained.
If the property is false, hostaware replication will be disabled and the ActiveSpaces member name will be set as be-engine-name.
Disabling hostaware replication will honor "Number of Backup Copies", provided that there are enough cache nodes deployed in the cluster.

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