JMX Jobs

JMX Jobs define the necessary parameters to run scripts on JMX platforms. JMX jobs can run independently or they can be added to a Job Group (JOBG) or to a Workflow. For more information about the integration between the Automation Engine and JMX, see Java EE/JMX Agent.

Overview

Your Automation Engine system is connected to JMX via the Agent. The JMX Agent interprets and transforms the commands sent by the Client so that JMX understands them.

Prerequisites:

To create JMX Jobs in the Automic Web Interface and execute them in the JMX client, the following prerequisites must be met:

• The JMX Agent is active
• The JMX Agent is assigned to the job on the Attributes page
• The Job has a Login (LOGIN) object assigned that contains the credentials to log in to the JMX system

JMX Commands

SAP Jobs in the Automation Engine are supplied with sets of predefined commands. A command is a group of SAP-specific strings or functions. You build the logic of an SAP Job on its Process page by adding commands to it. For more information, see Process Pages.

User-Friendly Scripting Using Forms

The script editor of the Process page in an SAP Job has two views. The usual one that is available for all Jobs, and the Form view. The Form view is an intuitive, user-friendly way of depicting the values you must enter for a particular command. The Form view of a command can contain dropdown lists, input fields, radio buttons, and so on. For more information, see Forms View on the Process Page.

Defining JMX Jobs

An JMX Job definition is made up of the following pages:

• Standard pages that are always available, no matter what type of object you are defining:
  • General Page
  • Version Management Page
  • Documentation Page
• Additional pages that are always available for executable objects:

  • Process Pages

    Note: JMX Jobs have an extra Child Post Process page. You build the logic of the child processes on this page.

  • Attributes Page
  • Output Pages
  • Variables Page
  • Prompt Sets Page
  • Rollback Page
• The JMX page described here.

Server Settings Section

• MBean Server: Local Java VM

  Select this option if the MBean server is on the same computer as the JMX agent and select the server to be used from the Server Connection dropdown list.

  The options are:

  • Use any existing MBean Server

    If you select this option, an arbitrary MBean server is retrieved automatically.

    The option Create new instance if not found is displayed.

  • Specify MBean Server

    Select this option if you want to specify the agent that will process the JMX jobs and enter it in the Agent ID field. It can contain up to 20 characters.

  • Via JNDI

    Select this option if the connection is established to a local MBean server that is located in an SAP Java EE server.

    The Object Name field is displayed, where you enter the name of the object that will be called. It can contain up to 22 characters.

• MBean Server: Remote Java VM

  Select this option if the MBean server is on a different computer than tn the JMX agent an specify it using the following options:

  • Initial Context Factory

    Depending on the vendor of the MBean server, you might need to enter a value here.

  • Server URL

    URL of the computer on which the MBean server is located.

Job Report Section

For information on the Job Report section, see Job Reports.

Creating JMX Jobs with Oracle

1. Select Remote Java VM .
2. Enter weblogic in the Initial Context Factory field.
3. Enter the URL with the following format:

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

Creating JMX Jobs with IBM WebSphere

To create Jobs using the RMI connector:

1. Select Remote Java VM .
2. Enter websphere in the Initial Context Factory field.
3. Enter the URL with the following format:

   Host name of the WebSphere:port of BOOTSTRAP_ADDRESS

To create Jobs using the SOAP connector, that is, WebSphere with activated administrative security:

1. Select Remote Java VM .
2. Enter websphere in the Initial Context Factory field.

   Important! As of WebSphere version 7, there is the option to not include any settings in the [WEBSPHERE] INI file section. In this case, you must enter websphere soap in the Initial Context Factory field.

3. Enter the URL with the following format:

   Host name of the WebSphere:SOAP port

   Retrieve the port number as follows:

   1. Log on to the administrator console.
   2. Click on Servers > Application server.
   3. Click on your server.
   4. Select Transfers > Ports.

      Use the port number shown here in the URL. The SOAP port's default value is 8880

   5. Return to the Automic Web Interface and specify the three passwords in the job's Login object: User, Keystore and Truststore.

Important! The SOAP connector must be activated. Its port is usually 8880.

Creating JMX Jobs with JBoss

1. Select Local Java VM.
2. Select Use existing MB Server

   It is not necessary to activate the Create new instance if not found option.

Creating JMX Jobs with Oracle Containers for Java EE

1. Select Remote Java VM .
2. Enter oc4j in the Initial Context Factory field.
3. Enter the URL with the following format:

   service:jmx:rmi://Host name of the Java EE server:port/oc4j

Creating JMX Jobs with SAP Netweaver

1. Select JNDI.
2. Enter jmx in Object Name.

Creating JMX Jobs if the JMX Agent Runs Outside an Application Server

1. Select Local Java VM.
2. Activate both Use existing MBean Server and Create new instance.

See also:

Jobs (JOBS)