Setting up the Agent for Java EE/JMX (Oracle Weblogic)

Installing the Agent for Java EE/JMX (Application-Server)

Setting up the Agent for Java EE/JMX (IBM WebSphere) with SOAP Connector

---

Setting Up the Agent for J2EE/JMX (IBM WebSphere) with RMI Connector

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.

Supplied Files

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

Procedure

	1.	Setting up the JMX Agent

• Host
• Select the menu item Applications -> Install New Application on the WebSphere interface.
• Specify the path to ucxjjmx.war in "Local File System." "Context root" can be used to name the application.

• The next window can be used to activate the option Generate Default Bindings." If required, other settings can also be specified.
• Follow the installation procedure as described. In step 4, select the option Everyone? next to "administrators."

• When all six steps are complete, complete the installation procedure by clicking FINISH. Refer to the log to verify that the installation was successful. Click "Save to Master Configuration", and then Click Save.
• Click Applications -> Enterprise Applications. The list now also includes the agent. Activate it by clicking the button of the same name.  
• The agent can be started via the configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied. WebInterface.

	2.	Using the configuration WebInterface

• Host
• The JMX agent has a configuration web interface that can be called with a Web browser using the following address:

http://Server name:port/context root

• Adjust the settings of the JMX agent to your system environment. The most important settings are:
• Name for the agent
• Name of the computer on which a communication process is available
• 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 applicationA web application is an application that is accessible over a network (Internet or intranet) and is typically coded in a programming language like Java or JavaScript, combined with a markup language like HTML. Web applications are provided on web servers and web browsers are used as GUI on client computers. after the deployment has taken place.

	3.	Important notes for  creating jobs

• Host
• "Remote Java VM" must be selected in the Job object's JMX tab.
• Enter the term "websphere" in the field Initial Context Factory .
• Specify the Server URL in the following format:

Host name of the WebSphere:port of BOOTSTRAP_ADDRESS

•   Retrieve the port number as follows: Log on to the administrator console. Click "Servers" -> "Applications servers", and then click the name of your server. Select "Communications" -> "Ports." The table contains the entry BOOTSTRAP_ADDRESS. Use the port number shown in the URL.