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


Chapter 3 Basic MM Configuration : MM Agent Basic Configuration Reference

MM Agent Basic Configuration Reference
This section provides a reference to the properties that are to be set in the Master CDD file.
See Basic MM Settings in MM.cdd for the related procedure.
This property is deprecated in 5.1. The MM server locates and picks up all the site topology files present under BE_HOME\mm\config. To monitor and manage other projects, ensure that this property is either deleted from the file, or the property is set to “”(empty string).
Note  The topology file must be located on the same machine as the machine where the MM server is running.
Used only if be.mm.email.authentication is set to true.
Used only if be.mm.email.authentication is set to true.
The SweepFreq property determines how often the system checks for inactive unpredefined cluster members to be purged, and the SweepThreshold property determines for how long an item must remain inactive before it is eligible for purging.
Note  Do not change unless advised by TIBCO.
Default is 300000 (that is, five minutes)
Note: Do not change unless advised by TIBCO.
Default is 600000 (that is, ten minutes)
Configuring Broker Properties for Working with Coherence Cache Provider
A broker process enables the MM cluster to communicate and retrieve information from the target cluster. A multi-cluster configuration must have one broker per cluster, with each broker specifying it’s own set of properties. Each broker must have its unique RMI port. The RMI port is specified using the property be.mm.broker.rmi.port. The value of this property must be an integer and the default value is 11200.
The broker properties must be specified in the Master CDD file at the cluster level. In the Master CDD file, only the properties present at the cluster level with the prefix tangosol.coherence or be.mm.broker are passed to the broker process.
For backward compatibility, the broker properties defined in the MM.cdd file with the prefix be.metric.cluster.property are still loaded. However, if a property with the same name exists in the MM.cdd file and the Master CDD file, the value specified in the Master CDD file takes precedence.
Default is logs/mm-broker.log
If the server is hosted on an AIX machine, set this property to True. Remember to also add a similar property to the be-mm.tra file. See Property for Cache Based Object Management on AIX for general details (note that the property name is different here than in the to-be-monitored engine TRA file.

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