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

Usage with Application Server

Setting up the Agent for Java EE/JMX (JBoss)

---

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

The following document includes information about installing and configuring J2EE/JMX agents with an IBM WebSphere Application Server.

This installation guide applies to WebSphere version 6.0 with activated administrative security.

	1.	Setting up the JMX Agent

• Host
• Select the menu item Applications -> Install new application on the WebSphere interface.
• Enter the path to the file ucxjjmx.war in "Local file system." The "Context root" can be used to name the application.

• In the next window you can activate the option Generate standard connections or configure other settings.
• Follow the installation procedure until the individual steps are displayed. Step 4 requires the selection of "Everyone?" in the administrators field.

• When all six steps are completed, click Finish to complete the installation process. The log shows whether the installation was successful.
• Click Store in master configurationA set of constituent components that make up a system. This includes information on how the components are connected including the settings applied., and then click Store.
• Call the menu item Applications -> Enterprise applications. The list also includes the agent.

	2.	Configuring the INI file

• Host
• Search for the file ucxjjmx.ini in the WebSphere folder.
• Open the INI file and append the new section [WEBSPHERE] with the following parameters:

[WEBSPHERE]
javax.net.ssl.trustStore=C:\DummyClientTrustFile.jks
javax.net.ssl.keyStore=C:\DummyClientKeyFile.jks

• Adjust the values for the javax.* properties according to your environment.
• Store and close the INI file.

This installation step is optional as of Websphere version 7 optional. Note when you skip this step that you must enter the value "webshere soap" in the Initial Context Factory field in the JMX tab of the Job object.

	3.	Starting the Agent

• Host
• Start the agent application via the WebSphere console.

	4.	Using the Web configuration interface

• Host
• The JMX agent has a Web configuration interface which can be called with a Web browser via the following address:

http://Server name:Port/context root

• Adjust the settings of the JMX agents to your system environment. The following are particularly important:
• Agent name
• 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.

• Start the agent
• Click View log files and select the most current log file (it has the number "00"). The section [WEBSPHERE] must be included in the log file.

	5.	Important notes for the creation of jobs

• Host
• The agent now uses the SOAP Connector. Therefore, select "Remote Java VM" in the Job object's JMX tab.
• Enter the term "websphere" in the field "Initial Context Factory."

Host name of the WebSphere:SOAP Port

•  Retrieve the port number as follows: Click Servers -> Application server, and then click on the name of your Server. Select "transmittals" -> "Ports." Use the port number shown here in the URL. The default value of the SOAP port is 8880.
• Enter three passwords separated by commas in the job's Login object.
• The 1st passwordA secret combination of characters for a Automation Engine user. is the user password.
• The 2nd password is the keystore password.
• The 3rd password is the truststore password.