GOALOverride the cluster properties of the mule-cluster.properties file using the wrapper.conf, this could be useful when need to avoid modifying mule-cluster.properties, which is not viable when the cluster configuration is managed.
PROCEDURE
WARNING
This procedures is only provided for cases in that you have no other alternative that enforce/override the values set by other tools.
If the cluster configuration is managed by Runtime Manager or MMC it could be modified automatically without warning. It is the user responsibility to keep the overriding configurations in sync. Use at your risk.
You can configure the following parameter into the wrapper.conf in order to enforce your network configuration into the cluster.
Please note that the value of the cluster are illustrative , you should use the values from your mule-cluster.properties.
wrapper.java.additional.<n>=-Dmule.clusterId=271948
wrapper.java.additional.<n>=-Dmule.clusterNodeId=2
wrapper.java.additional.<n>=-Dmule.clusterSize=2
wrapper.java.additional.<n>=-Dmule.cluster.tcpinboundport=7517
wrapper.java.additional.<n>=-Dmule.cluster.tcpipenabled=false
wrapper.java.additional.<n>=-Dmule.cluster.nodes=10.8.8.50:7517,10.8.8.50:7555
wrapper.java.additional.<n>=-Dmule.clusterSchema=partitioned-sync2backup
wrapper.java.additional.<n>=-Dmule.cluster.multicastenabled=false
wrapper.java.additional.<n>=-Dmule.clusterPartitioningMode=OPTIMIZE_PERFORMANCE
<n> should be changed to the sequence of the wrapper.conf properties.
To override all the properties is optional.
