'); $("#tabs").tabs({ selected: 1 }); $("#ic-homepage__ic-tips").append( quickTipHTML() ); unhideOneProductTip(); $("#ic-homepage__product-tips").wrapInner('
'); $("#ic-homepage__feed-tips").wrapInner('
'); });
IBM Tivoli Monitoring > Version 6.3 > User's Guides > Agent Builder User's Guide > Monitor Java Management Extensions (JMX) MBeans IBM Tivoli Monitoring, Version 6.3
JMX configuration
When you define a JMX data source in your agent, some configuration properties are created for you.
JMX runtime configuration is unique because it provides you with some control over how much configuration is displayed. The JMX client for the agent can connect to several different types of application servers. However, it is not necessary to support all of those types of application servers in any one agent. You can determine which types of application servers to support, and unnecessary configuration sections are not included in the agent.
In most cases, an agent is designed to monitor one JMX application server type. When you create the JMX data source, you can use the JMX Browser. When you use the JMX Browser, the JMX server configuration options that are used to browse the MBean server are added to your agent automatically. To change the types of application servers to which you can connect after the agent is created, click Global JMX Options in the JMX Information area, (Figure 10). In the JMX Agent-Wide Options page (Figure 11), change any selections that you want.
You can design a generic agent that monitors more than one type of JMX application server. In this case, more than one JMX server configuration choice can be selected on the JMX Agent-Wide Options page (Figure 11). When more than one type of JMX connection is supported, the runtime configuration prompts you for the connection type that are used for that agent instance.
An instance of an agent can connect only to one type of JMX application server. Subnodes can be used to connect to different JMX application servers of the same type within an agent instance. To connect to more than one type of JMX application server, you must configure at least one agent instance for each JMX application server type.
You can view, add, and change the configuration properties using the Agent Editor. See (Change configuration properties using the Agent Editor). If a JMX data source is defined in a subnode, you are also able to specify Subnode Configuration Overrides. See (Subnode configuration).
If you define a JMX data source in your agent, the agent must use Java to connect to the JMX application server. Java configuration properties are added to the agent automatically.
The following Java configuration properties are specific to the agent runtime configuration:
- Java Home
- Fully qualified path that points to the Java installation directory
Configure the agent to use the same JVM that the application you are monitoring uses, particularly for the WebLogic Server and WebSphere Application Server.
- JVM Arguments
- Specifies an optional list of arguments to the Java virtual machine.
- Trace Level
- Defines the amount of information to write to the Java trace file. The default is to write-only Error data to the log file. See (Trace log format).
The Agent Builder does not require these properties because it uses its own JVM and logging, which is configured through the JLog plug-in.
If you define a JMX data source in your agent, the following required, common configuration fields are added to the agent automatically:
- Connection
- The type of connection to the MBean server
- User ID
- User ID that is used to authenticate with the MBean server.
- Password
- Password for the user ID.
- Base paths
- Directories that are searched for JAR files that are named in Class path, or directories that are named in JAR directories, that are not fully qualified. Directory names are separated by a semi-colon (;) on Windows, and by a semi-colon (;) or colon (:) on UNIX systems.
- Class path
- Explicitly named JAR files to be searched by the agent. Any that are not fully qualified are appended to each of the Base Paths until the JAR file is found.
- JAR directories
- Directories that are searched for JAR files. Directory names are separated by a semi-colon (;) on Windows, and by a semi-colon (;) or colon (:) on UNIX systems. The JAR files in these directories are not required to be explicitly identified; they are found because they are in one of these directories. Subdirectories of these directories are not searched. Any directory names that are not fully qualified are appended to each of the Base Paths until the directory is found.
For remote monitoring, the JAR files and all of their dependent JAR files must be installed locally on the computer where the agent is running. These JAR files are the files that are required to connect to the application that is being monitored. These JAR files must be configured in JAR directories, and in Base paths and Class path. In addition, locally install a supported JVM for the application you are monitoring and specify the path in the Java Home configuration field.
Examples:
- For WebLogic 10, the class path is server/lib/wlclient.jar;server/lib/wljmxclient.jar. The base path points to the WebLogic application server directory where the server/lib directory is located.
- For WebSphere, the base path points to the location where the WebSphere Application Server is installed. Multiple base paths are listed in this example to provide a default for Windows and UNIX. The class path lists the JAR files relative to the base path. The relative value lib for the JAR directories field causes all JAR files in this directory under the base path to be loaded.
- Base paths: C:\Program Files\IBM\WebSphere\AppServer;/opt/IBM/WebSphere/AppServer
- Class path: runtimes/com.ibm.ws.admin.client_6.1.0.jar;plugins/com.ibm.ws.security.crypto_6.1.0.jar
- JAR directories: lib
Depending on which JMX server types are selected in the JMX Agent-Wide Options page, some or all of the following configuration properties are added. Default values are provided by the Agent Builder, and can be modified:
- JSR-160 Compliant Server and WebSphere Community Edition connection-specific configuration properties:
- MX Service URLJ
- JMX Services URL to connect to for monitoring.
- WebSphere Application Server 6.0, 6.1, and 7.0 connection-specific configuration properties:
- Host name
- Host name of the system where the application server you are monitoring is located. For local monitoring, the name is the local system name. For remote monitoring, the name is the host name of the system where the application server is located.
- Port
- Port number to use on the host name to be monitored.
- Connector protocol
- Connector protocol to be used by the monitoring connection. RMI and SOAP are supported.
- Profile name
- Name of the profile to use for configuring the connection.
- JBoss Application Server connection-specific configuration properties:
- JNDI Name
- JNDI Name that is used to look up the MBean server.
- Provider URL
- JMX Services provider URL to connect to for monitoring.
- WebLogic Server version 9 and 10 connection-specific configuration properties:
- Service URL
- JMX Services provider URL to connect to for monitoring that includes the JNDI name.
If WebSphere administrative security is enabled, you must make sure that client login prompts are disabled in the appropriate client connection properties files. For RMI connections, to prevent clients from prompting the user, you must modify the com.ibm.CORBA.loginSource property in the sas.client.props file in the profile properties directory of your WebSphere Application Server. For a SOAP connection, you must modify the com.ibm.SOAP.loginSource propertyin the soap.client.props file in the same directory. In both cases, the loginSource property must be set to not contain a value.
You can view, add, and change the configuration properties using the Agent Editor. See (Change configuration properties using the Agent Editor). If a Windows data source is defined in a subnode, you can also specify Subnode Configuration Overrides. See (Subnode configuration).
Parent topic:
Monitor Java Management Extensions (JMX) MBeans