Administration Guide > Installation > New Installation > Setting up the Agent for Java EE/JMX

Setting Up the Agent for J2EE/JMX

The JMX agent can be run outside of an application server. This installation guide describes the required steps.

The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installation steps are required before the agent can be started and used if you intend to use one of the available authentication methods. More detailed information is provided in the document Advanced Security.

Automic strongly recommends installing the agent in a separate directory (such as UC4/Agent/jmx or C:\AUTOMIC\Agent\jmx).

Before you start the installation, make sure that the Java agents can only connect to CP port numbers that are lower than 65536. If they use a higher port number, the agent cannot start and aborts with an error message. This limitation is caused by Java and affects the agents for JMX, Databases, SAP and RA.

Supplied Files

The files that belong to the J2EE/JMX agent are stored in the directory IMAGE:AGENTS\JMX.


Procedure

1. Installing Java Standard Edition

This installation step can be omitted if the required version of Java Standard Edition is already available.

2. Setting up the Agent
3. Starting the Agent

The agent can also be started by using the ServiceManager.

Note that the storage limit should be set to at least 256MB (or 512MB) for starting Java agents (Databases, RA, JMX, SAP). You can specify a value for the storage limitation of Java applications by using the start parameter -XmX. Specifying a value that is too low can cause the agent to crash. The default value depends on the Java version that is used.The Java parameter -Xrs ensures that the agent ends properly when a normal end is initiated. Automic recommends using this parameter. More detailed information is provided in the Java documentation.

4. Important notes for creating jobs