The bind settings should include the URL and port of the Orchestrator instance.

The logs parameter takes the path to the location where you want the Orchestrator's logs to be collected.

Each cache to be replicated must have at least one Master instance identified in the wan-config.xml.

The ehcacheConfigURI should provide the path to the ehcache.xml configuration file for the cache.

Each master parameter should provide the host name and port for the instance of the Master cache.

maxConnectionRetryCount - Specifies the maximum number of connection attempts a disconnected Replica cache should try for each Master cache, before attempting to connect to another Master cache in the wan-config.xml. The default is 5. Note that this applies only when the replicaDisconnect behavior is set for reconnectResync (see below).

replicatorIntervalMillis - Specifies how frequently the Orchestrator should send replication updates to the regions, in milliseconds. Depending upon the amount of RAM available to your Orchestrator, you may be able to optimize WAN replication by increasing the interval.

replicationMode - Selects the type of replication, unidirectional or bidirectional. If unspecified, the default is unidirectional. Bidirectional mode must be specified for active-active deployments. For more information, refer to Replication Modes and Bidirectional WAN Replication.

replicaDisconnectBehavior - Specifies the behavior of the Replica caches if they become disconnected from their Master cache. The options are:

reconnectResync (default) - When a Replica is disconnected from its Master, it attempts to reconnect to the Master and to any failover Masters listed in the wan-config.xml. Upon reconnection to a Master cache, the Replica is deactivated, cleared, resynchronized to the Master cache, and then reactivated. All local changes on the Replica region will be dropped in favor of whatever is in the Master region. Note: When a WAN-enabled cache is deactivated, it follows the nonstop behavior specified in the ehcache.xml. For more information, refer to "Configuring Nonstop Operation" in the BigMemory Max Configuration Guide.

remainDisconnected - When a Replica is disconnected from its Master, it remains isolated from the Master from this point on. The Replica will not attempt to connect to the failover Masters listed in the wan-config.xml. The disconnected Replica cache does remain active locally, however, but no replication will take place.

monitoringEnabled - Specifies that the monitoring capability for the WAN Replication Service is enabled for each Orchestrator. If you want to disable the monitoring capability, set the monitoringEnabled parameter to false in each Orchestrator's wan-config.xml file.