-
Language:
English
-
Language:
English
11.2. Monitor Red Hat JBoss Data Grid Applications in Red Hat JBoss EAP
Ensure that all requirements outlined as prerequisites are met. Follow the listed steps to monitor Red Hat JBoss Data Grid applications in JBoss Enterprise Application Platform using JBoss Operations Network or RHQ.
Procedure 11.1. Monitor JBoss Data Grid Applications in JBoss Enterprise Application Platform
Configure RHQ/JBoss Operations Network
Add an RHQ/JBoss Operations Network specific property (namedorg.rhq.resourceKey
) to the/bin/
standalone.conf
file as follows:JAVA_OPTS="$JAVA_OPTS -Dorg.rhq.resourceKey=MyEAP"
This command adds the property to the JBoss Enterprise Application Platform's command line indirectly.Check RHQ/JBoss Operations Network is Running Using a Full JDK
Ensure that the RHQ/JBoss Operations Network agent started using a full JDK instead of a JRE. This is because the agent requires access to the JDK'stools.jar
file.To configure your RHQ/JBoss Operations Network agent to use the JDK, follow the instructions relevant to your operating system:- For Linux users, set the
RHQ_AGENT_JAVA_HOME
environment variable to the JDK home directory in the agent'srhq-agent-env.sh
file. - For Windows users, set the
RHQ_AGENT_JAVA_HOME
environment variable to the JDK home directory in the agent'srhq-agent-env.bat
file.
Ensure the Agent is Local to the JBoss Enterprise Application Platform Instance
Ensure that the RHQ/JBoss Operations Network agent runs locally to and under the same user as the JBoss Application Platform instance. This is required for the Java Attach API to connect to the process.Import Resources to the Agent Inventory
RHQ/JBoss Operations Network can now discover resources. These resources can subsequently be imported into the agent inventory.When a JBoss Data Grid user deployment enables JMX statistics to expose JBoss Data Grid Cache Managers or caches, the resources appear as children resources of the JBoss Enterprise Application Platform instance.