How to disable Monitoring Service inActiveMatrix Service Grid version3.3.0.
Article ID: KB0085162
Updated On:
| Products | Versions |
|---|---|
| TIBCO ActiveMatrix Service Grid | - |
| TIBCO ActiveMatrix BusinessWorks Service Engine | - |
| Not Applicable | - |
Description
Description:
By default, the option to deploy the monitoring service is unchecked in the TIBCO Configuration Tool (TCT) screen during ActiveMatrix Service Grid Admin Server creation for version 3.3.0. If this option is selected during Admin creation time, the monitoring service will be configured in the Admin server. Enabling monitoring may create performance issues, and if monitoring needs to be disabled completely at a later stage, the steps below should be followed.
Resolution
Step 1). Disable the MCR (Metrics Collection Runtime) service probe in each logical environment.
{
Note: ANT scripts used in the following procedures are attached to this article.
(Filename: Build File: disable_mcr_logger_build.xml).
(Filename: Data File: disable_mcr_logger_data.xml).
}
A). Copy the attached Admin CLI scripts (Filenames: disable_mcr_logger_build.xml and disable_mcr_logger_data.xml) to <config-home>/admin/<enterprise>/samples directory on the Admin machine, where the SystemNode is located.
B). If you have replicated SystemNode, update the disable_mcr_logger_data.xml file to uncomment the node configuration for SystemNodeReplica, and update the node name to match yours.
C). Under CONFIG_HOME/admin/<enterprise>/samples directory, run "ant -f disable_mcr_logger_build.xml -Denv.name=<environmentName> -Dnode.name=<nodeName>", where <environmentName> is the name of each of your environments and <nodeName> is the name of each node in the environment. If no ANT is being installed on the system, use the antpackage JAR distributed with AMX and run:
TIBCO_HOME/tibcojre(or tibcojre64)/1.7.0/bin/java -Xmx1024m -XX:MaxPermSize=512m -Xms256m -classpath TIBCO_HOME/tools/lib/antpackage.jar org.apache.tools.ant.Main -f disable_mcr_logger_build.xml -Denv.name=<environmentName> -Dnode.name=<nodeName>
D). Repeat step C for every node in each logical environment. This needs to be repeated for all nodes regardless if the monitoring application is deployed/running on those nodes.
Note:
===
CONFIG_HOME - The folder that stores configuration data generated by TIBCO products. Configuration data can include sample scripts, session data, configured binaries, logs and so on.
TIBCO_HOME - The folder into which the product is installed.
===
After Step 1, there should be no more messages being sent to the "amx.governance.stats" queue. You may still see messages being sent to the "amx.governance.stats.internal" queue.
Step 2). Login to ActiveMatrix(AMX) Admin UI.
Step 3). Click on the Applications tab, select SystemEnvironment and stop application amx.governance.mcr.aggregator. You can also optionally undeploy it. Now messages being sent to the "amx.governance.stats.internal" queue should also have been stopped.
The steps above are to stop MCR metrics data probing and collecting.
Note: Step 4 and 5 are to stop the governance plugin on the SystemNode (and replica) from syncing governed objects. These steps should not be done if TIBCO Activematrix Policy Director is also in use.
Step 4). Add the following property to SystemNode.tra file under <CONFIG_HOME>/tibcohost/<SYSTEMHOST_INSTANCE_NAME>/data_3.2.x/nodes/SystemNode/bin directory:
Alternatively, select Infrastructure > Hosts, click SystemHost and then the Resource Instance tab. Force-uninstall TIBCO ActiveMatrix Governance JDBC Resource Instance from SystemNode. Repeat this step for replicated SystemNode, if applicable.
java.property.com.tibco.governance.sync.synchronous=false
Repeat this step for replicated SystemNode if applicable.
Step 5). Restart SystemNode (and replicated SystemNode if applicable).
Step 6). Finally, purge the queues "amx.governance.stats" and "amx.governance.stats.internal". Monitor and do some activities such as deploy/undeploy, stop/start some applications or nodes to ensure no messages are being added to them.
After this procedure, you will still see one producer being created on the "amx.governance.stats" queue for each node (including new nodes created after this procedure) in existing environments. No messages will be sent to the queue. Nodes in the new environments created after this procedure will not create a producer on the "amx.governance.stats" queue.
Issue/Introduction
How to disable Monitoring Service inActiveMatrix Service Grid version3.3.0.
Additional Information
Ant scripts attached
build file: disable_mcr_logger_build.xml
data file: disable_mcr_logger_data.xml
Feedback
Yes
No
Powered by
