See Specify the Site Topology File and Basic MM Settings in MM.cdd for the related procedure.
Fully qualified path to the site topology file for the cluster to be monitored. As shipped, points to the example project Fraud Detection Cache. See Site Topology Overview and sections following for more details.Note The topology file must be located on the same machine as the machine where the MM server is running. A broker process enables the MM cluster to retrieve information from the target cluster. If MM stops, the broker terminates after about three minutes.By default, if MM restarts before the previous broker terminates, it uses that broker. If the previous broker has terminated, however, then MM creates a new broker process, using the target cluster properties in the master CDD that is specified in the topology file.When set to true, the existing broker process is never reused on startup. For example, if you want to monitor a different cluster when you restart MM (by specifying a different topology file), then you would set this property to true. Location of the log file for the broker relative to the working directory. The broker connects to the cluster that is to be monitored. This file relates to cluster activities.Default is logs/mm-broker.log Specifies the port that the socket will listen to or publish on.If more than one cluster is running on the same subnet, then even though they have different cluster names and cluster addresses, you may need to specify this property to avoid conflict. 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 For Cache Based Object Management on AIX for general details (note that the property name is different here than in the TRA file. Authentication is optional. Authentication topics are documented in Chapter 13, Configuring User Authentication.To configure for LDAP authentication, add the properties specified in Chapter 13, Configuring User Authentication and remove the file-based authentication properties or remove their values.For file based authentication you can share the same file used by other components that also use file based authentication, as desired and appropriate. Location of the JAAS login configuration file. You can substitute a different implementation of the JAAS login module than the one provided. Default is BE_HOME/mm/web-root Configure the properties needed to send emails in response to alerts or health levels. Required only if you will use the Actions feature. Replace default values for host, email addresses and passwords. Possible values are true and false. If set to true then also configure the username and password properties. Used only if be.mm.email.authentication is set to true. Used only if be.mm.email.authentication is set to true. Default value is localhost These properties define how frequently certain checks and updates are done. Modify as needed to ensure best performance. Specifies the time interval between two consecutive calls to the monitored cluster to fetch the latest (current) cluster topology (in milliseconds). The purpose of this check is to ensure that the Cluster Explorer topology matches the actual cluster topology.Default is 30000 Specifies the time interval between two consecutive calls to get metrics of each monitored entity in the cluster (in milliseconds). The purpose of this check is to ensure that metrics at all monitored entity levels are updated regularly.Adjust as needed. For example, if the requests are affecting performance, increase the time interval. If you want more immediate notifications, decrease the time interval.Default is 30000 Specifies the time interval between two consecutive two health pings to each machine and process in the monitored cluster (in milliseconds).This property is used to determine which monitored entities are inactive. Inactive items are indicated in Cluster Explorer. See Inactive Members for more details.Default is 30000 This setting applies only to unpredefined cluster members. Predefined cluster members (those defined in the topology file) are never purged.The time interval between two sweep checks to physically delete inactive purged cluster members in the discovered topology (in milliseconds).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.If a user is viewing an inactive cluster member that another user has purged, the cluster member remains visible until the user has finished viewing the details.Note Do not change unless advised by TIBCO.Default is 300000 (that is, five minutes) The length of inactivity for a purged cluster member to be qualified for physical deletion (in milliseconds).Also see notes for Sweepfreq.Note: Do not change unless advised by TIBCO.Default is 600000 (that is, ten minutes) tibco.clientVar.Domain=TIBCO Hawk Domain
Copyright © TIBCO Software Inc. All Rights Reserved.