'); $("#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 > Use the Java API to monitor data. IBM Tivoli Monitoring, Version 6.3
Run the Java application
Information about the initialization of the Java application and its dependencies
Initializing the Java application
The agent starts the Java application while the agent is starting and initializing. Configuration settings are used to control which Java run time is used to start the process. Java virtual machine arguments and the Java logging level can also be specified in the configuration. For more information about Java API configuration, see (Java API configuration). The Java process inherits the environment variables that are defined for the agent. Runtime configuration settings are also placed in the environment and can be queried by using API calls.
The Java application must be a long-running process. It must not terminate unless it receives a shutdown request from the API. If the Java application does terminate after it is registered with the agent, the agent will attempt to restart the Java application up to three times. If data collection is successfully resumed, this restart count is reset. The agent logs an error when a Java application terminates and when a restart is initiated.
If the Java application terminates before attribute group registration is completed, no restart is attempted.
Dependencies
A Java application must use a Java runtime environment. The following versions of Java are supported:
- Oracle Corporation Java Version 5 or later
- IBM Corporation Java Version 5 or later
Java must already be installed on the agent system when the agent is configured and started. The JAR file that contains the API used to communicate with the agent is included with the agent runtime and included in the classpath of the JVM. Any additional JAR files that are needed by your Java application must be defined as Supplemental Files to the Java API attribute groups. Any supplemental files that have a File Type of Java resource are automatically added to the base classpath of the Java application, along with the Java API JAR file.
Any JAR files that are necessary for the runtime operation of the Java application that are not included with the agent, must be included in the Classpath for external jars configuration setting.
Parent topic:
Use the Java API to monitor data.