此内容没有您所选择的语言版本。
20.8. Monitor JBoss Enterprise Application Platform 6 Applications Using Library Mode
20.8.1. Prerequisites 复制链接链接已复制到粘贴板!
复制链接链接已复制到粘贴板!
The following is a list of common prerequisites for both Section 20.8.2, “Monitor an Application Deployed in Standalone Mode” and Section 20.8.3, “Monitor an Application Deployed in Domain Mode”
- A correctly configured instance of JBoss Operations Network (JON) 3.1.x or better.
- A running instance of JBoss Operations Network (JON) Agent on the server where the application will run. For more information, see Section 20.4, “JBoss Operations Network Agent”
- An operational instance of the RHQ agent with a full JDK. Ensure that the agent has access to the
tools.jar
file from the JDK in particular. In the JBoss Operations Network (JON) agent's environment file (bin/
rhq-env.sh
), set the value of theRHQ_AGENT_JAVA_HOME
property to a full JDK. - The RHQ agent must have been initiated using the same user as the JBoss Enterprise Application Platform instance. As an example, running the JBoss Operations Network (JON) agent as a user with root privileges and the JBoss Enterprise Application Platform process under a different user does not work as expected and must be avoided.
- An installed JBoss Operations Network (JON) plugin for Library Mode. For more information, see Section 20.6.1, “Installing the JBoss Operations Network Plug-in (Library Mode)”
- A custom application using Red Hat JBoss Data Grid's Library mode. This application must have
jmxStatistics
enabled (either declaratively or programmatically). For more information, see Section 19.4, “Enable JMX for Cache Instances” - The Java Virtual Machine (JVM) must be configured to expose the JMX MBean Server. For the Oracle/Sun JDK, see http://docs.oracle.com/javase/1.5.0/docs/guide/management/agent.html
- A correctly added and configured management user for JBoss Enterprise Application Platform.