Setting Up the Agent for Java EE/JMX (Tomcat)

The following guide describes how to install an agent in an AE system in which authentication is not used. Additional installationnull 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.

Procedure

	1.	Setting up the JMX Agent"Programm, das die Ausführung von Verarbeitungen auf Zielsystemen wie z.B. Rechner oder Geschäftslösungen ermöglicht. Auch ein eigener Objekttyp in der Automation Engine. [Früher ""Executor"" genannt.] Siehe auch ""Host""."

• HostRechner, Zielsystem.
• Start Tomcat and call the Tomcat Web Application Manager.
• Select the file ucxjjmx.war in the section "Install - load local WAR file for installation." The installation can then be started using the button of the same name.
• Note that the role "administrators" must exist. Adjust the file tomcat-users.xml if it does not yet exist. Enter the role and add it to a user.

Example:

<role rolename="administrators"/>
<user username="admin" password="" roles="admin,manager,administrators"/>

Restart Tomcat to apply the roles.

• The JMX agent is displayed in the section "applications" of the Web Application Manager.

	2.	Using the web configuration interface

• Host
• A web configuration interface is available for the JMX agent. To call it, click on the available link for the JMX agent entry in the section "Applications".
• Use this interface to adjust the JMX agent to your system environment. It is particularly important to configure the following:
• The agent name
• The name of the computer on which a communication process is available
• The port number of a communication process

Note that the configuration file will be overwritten when you deploy the WAR file again. As a result you will have to redefine your configuration settings. Instead, you can also save a copy of your configuration file (INI file) before you start the deployment and copy it to the folder that includes the web application after the deployment has taken place.