MM Agent Basic Configuration Reference
This section provides a reference to the properties to be set in the Master CDD file.
Property | Notes |
---|---|
be.mm.monitor.in.mem |
|
Enables the MM server to monitor engines running in memory mode when this property is set to true.
You can either delete this property, or set the property to false to indicate monitoring engines running in cluster mode. |
|
be.mm.topology.file |
|
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).
Fully qualified path to the site topology file for the cluster to be monitored as shipped, points to the example project Fraud Detection Cache in TIBCO BusinessEvents® . See Site Topology and the sections following for more details. |
|
Authentication Properties (auth section)
Authentication is optional.To avoid conflicts between authentication for MM and for add-on products that also use authentication, MM has its own set of property names. Authentication topics are documented in User Authentication . |
|
HTTP Properties
Do not change unless advised by TIBCO. |
|
be.channel.http.propertiesAsXML |
|
Do not change unless advised by TIBCO.
Default is true. |
|
Email Properties for Actions Feature
actions_email 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. |
|
be.mm.email.protocol |
|
Email protocol. Supported protocols are smtp and smtps.
Default value is smtp. |
|
be.mm.email.authentication |
|
Specifies whether the user must authenticate to the email server.
Possible values are true and false. If set to true then also configure the username and password properties. Default is false. |
|
be.mm.email.host |
|
Specifies the email host. | |
be.mm.email.from |
|
Specifies the From address. | |
be.mm.email.username |
|
Specifies the username used to authenticate to the email server.
Used only if be.mm.email.authentication is set to true. |
|
be.mm.email.password |
|
Specifies the password used to authenticate to the email server.
Used only if be.mm.email.authentication is set to true. |
|
Global Variable Overrides — HTTP
global_variable_overwrite > http Overrides for the project global variables. |
|
tibco.clientVar.HTTPHost |
|
Used by the emonitor project HTTP channel. Set to the IP address of the machine hosting the MM server.
Default value is localhost |
|
tibco.clientVar.HTTPPort |
|
Used by the emonitor project HTTP channel. Specify as needed to avoid port conflicts.
Default is 9000. |
|
tibco.clientVar.BEMMDocRoot |
|
The directory from which static HTML content is served.
Do not change unless advised by TIBCO. Default is ../web-root. |
|
tibco.clientVar.BEMMDocPage |
|
The name of the default static HTML file stored in the document root. Do not change unless advised by TIBCO.
Default is \index.html. |
|
Global Variable Overrides — Frequencies
global_variable_overwrite > frequencies These properties define how frequently certain checks and updates are done. Modify as needed to ensure best performance. Overrides for the project global variables. |
|
tibco.clientVar.TopologyUpdateFreq |
|
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. |
|
tibco.clientVar.JMXUpdateFreq |
|
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.
A monitored entity in a cluster can be a cluster, a machine, a process unit or an agent. 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. |
|
tibco.clientVar.HealthCheckFreq |
|
Specifies the time interval between two consecutive 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. |
|
tibco.clientVar.SweepFreq |
|
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. |
|
tibco.clientVar.SweepThreshold |
|
The length of inactivity for a purged cluster member to be qualified for physical deletion (in milliseconds).
Also see notes for Sweepfreq. |
|
Global Variable Overrides — Hawk
global_variable_overwrite > hawk Overrides for the project global variables. If you use non-default values, specify them here. |
|
tibco.clientVar.Domain |
|
Name of the TIBCO Hawk domain. | |
tibco.clientVar.TIBHawkService |
|
Rendezvous service used by TIBCO Hawk. | |
tibco.clientVar.TIBHawkDaemon |
|
Rendezvous daemon used by TIBCO Hawk. | |
tibco.clientVar.TIBHawkNetWork |
|
Rendezvous network used by TIBCO Hawk. |