User Guide > Objects > Alphabetical Listing > JMX

JMX

The document shown below explains the platform-specific settings for a JMX job.

Description

Field/Control	Description
Job report
Database	The job report is managed in AE. When the job has been processed, the Automation Engine takes the process protocol which has been stored on the agent computer and stores it to the AE databaseA database is an organized collection of data including relevant data structures..
File	The job report is managed in AE. After the execution of a job, the process protocol is available in the target system as a file.
On error only	The job report is stored in the AE database and/or a file in the target system only if the job has been canceled. This function is only available when "Database" and/or "File" have been selected.
Optional reports
Agent log	Activating this checkbox has the effect that a report including the agent's messages about the job execution is added to the task.
MBean Server
Local Java VM	The MBean Server is on the same computer as the JMX agent.
Use any existing MBean Server	The MBean Server is automatically retrieved.
Create new instance if not found	Setting for instance creation
Specify MBean Server	A given MBean Server is used.
Agent ID	An agent ID can be indicated if a particular agent should be used.
JNDI	The connection is established to a local MBean Server which is located in a SAP J2EE Server.
Name of the object	The name of the object that should be called.
Remote Java VM	The MBean Server can explicitly be indicated.
Initial Context Factory (optional)	It depends on the vendor of the MBean Server whether this connection parameter should be indicated.
Server URL	URL to the computer on which the MBean Server is found

Important Notes for Creating Jobs

Oracle WebLogic:

Select "Remote Java VM" in the Job object's JMX tab.
Enter the term "weblogic" in the field Initial Context Factory .
Specify the Weblogic server for the server URL in the format shown below:

t3://name of the Weblogic server:port of the Weblogic server

IBM WebSphere:

Using the RMI connector:

"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

Using the SOAP connector (Websphere with activated administrative security):

The agent now uses the SOAP connector. Select "Remote Java VM" in the Job object's JMX tab.
Enter "websphere" in the field Initial Context Factory .
Note that when the INI-file section [WEBSPHERE] does not include any settings (which is an option as of Websphere version 7), you must enter the value "webspere soap" in the Initial Context Factory field.
Specify the Server URL in the following format:

Host name of the WebSphere:SOAP port

Retrieve the port number as follows: Log on to the administrator console. Click on Servers -> "Application server", then on your Server. Select "Transfers" -> "Ports". Use the port number shown here in the URL. The SOAP port's default value is 8880.
Three passwords separated by commas must be specified 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.

The Soap Connector must be activated. Its port is in most cases 8880.

JBoss:

Select the option Local Java VM in the Job object's JMX tab.
Activate the sub-menu "Use existing MB Server".
It is not necessary to select the option "Generate new instance...".

Oracle Containers for J2EE:

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

service:jmx:rmi://Host name of the Oracle J2EE server:port/oc4j

SAP Netweaver:

Select "JNDI" in the JMX tab of the Job object. Enter the object name "jmx".

The JMX agent runs outside of an application server:

Select the option Local Java VM in the Job object's JMX tab.
Activate the sub-items "Use existing MBean Server" and "Create new instance...".