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


Chapter 3 Basic MM Configuration : Basic MM Settings in MM.cdd

Basic MM Settings in MM.cdd
The MM server uses the MM.cdd file to perform basic configuration and also to configure alerts, health metric rules, and actions. See Chapter 4, MM Metrics and Features Configuration for more details on those tasks.
Configurations for alerts, health metric rules, and actions are uniform across all the clusters monitored by the MM server. Note that these configurations cannot be customized for each cluster individually.
In order to edit the CDD using the CDD editor, import the eMonitor project into TIBCO BusinessEvents Studio.
Expert users can also edit the XML file using a text editor, but using the UI protects you from editing errors. Back up the file before editing it.
To run the MM server with the installation defaults, the MM.cdd file must remain in the installed location.
Within the CDD file change only the settings for the mm-class agent. The mm-class agent is defined using an internal type of agent class (Monitoring & Management) used only in the MM.cdd file.
Whenever you change the MM.cdd file you must restart the BEMM server so that it uses the updated values.
Import the emonitor Project for CDD Editing
It is not possible to edit this file in TIBCO BusinessEvents Studio outside of its project context. In order to edit the CDD in TIBCO BusinessEvents Studio, you must import the project into your workspace.
1.
In TIBCO BusinessEvents Studio, choose File > Import > Existing Projects into Workspace and select the following project:
   BE_HOME/mm/project/emonitor
2.
To edit the CDD file in its original location, uncheck the Copy the projects into workspace checkbox. (If you do copy the emonitor project into your workspace, remember to copy the edited CDD file to its original location.)
3.
In Studio Explorer, double-click MM.cdd to open it in the CDD editor.
Configuring the Basic Settings in the MM CDD File
1.
2.
3.
To monitor engines running in memory mode, add the property, be.mm.monitor.in.mem, to the properties and set its value to true.
To monitor engines running in cluster mode, set the value of the property to false.Alternately, you can remove the property from the properties sheet.
You must also specify the host address in the tibco.clientVar.HTTPHost property, and specify the port as needed.
If you are running on AIX  you must add an additional property to the mm-agent class CDD properties. See Property for Cache Based Object Management on AIX for details.
4.
The monitored cluster’s topology file must be located on the MM server under BE_HOME/mm/config. (see Site Topology Overview). You can copy the file from its design-time location as needed.To monitor and manage other projects, ensure that the property be.mm.topology.file is either deleted from the MM.cdd file, or the property is set to “”(empty string).
5.
Save the CDD. If you imported it to your workspace, copy it to BE_HOME/mm/project/emonitor and to BE_HOME/mm/bin.
Whenever you change the MM.cdd file you must restart the BEMM server so that it uses the updated values.

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