JMX Jobs

This subtype of the JOBS object is used to define the necessary parameters to run scripts on JMX platforms. Like all other job objects (JOBS), JMX jobs can run independently or they can be added to a group (JOBG) or to a workflow. For details on the integration between the Automation Engine and JMX please refer to Java EE/JMX Agent.

The page contains the platform-specific execution parameters:

Server Settings Section

The following table describes the available options:

Field Description
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 a 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.

  • 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

The following table describes the available options:

Field Description
Store to
  • Database: As soon as the job has been processed, the process log available on the target system is stored in the database.
  • File: The process log is stored as a file on the target system.

You can select one option or both of them simultaneously.
Generate

Define when the operating system process log is written.

  • Always: The process log is always written.
  • On error only: The process log is written only when an error occurs, for example, when the job is canceled or aborted.
Add Agent Log Activate this checkbox if you want also the agent messages on the execution of the job to be also included in the task.

ClosedCreating 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

ClosedCreating 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.

    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.

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

ClosedCreating 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.

ClosedCreating 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

ClosedCreating JMX Jobs with SAP Netweaver

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

ClosedCreating 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.

Next Steps

The list below tries to depict a possible road-map to define and work with Job objects and provides short descriptions of the actions you can take, additional information that can help you understand how they work and links to topics that further describe them:

  1. Define the job general settings, which include the following:

    • The basics, on the General Page.
    • If required, apply a Sync object to the job; You do so on the Sync Page.
    • On the Runtime Page specify the job runtime settings.
    • Fine-tune access rights at object level on the Managing Authorizations at Object Level.
    • Specify the object Attributes on the Attributes Page.
    • Register the output files that will be produced when processing them on the Output Page.
    • To be able to carry out searches in those output files and, if required, perform follow-up actions, specify these settings on the Output-Scan Page.
    • You may want to use variables or prompts. You do so on the Variables & Prompts Pages.
    • You may want to define the settings to backup and restore a job task when included in a workflow. This is useful to recover the last successful status in case of failed processes. You do this on the Rollback Page.
    • The Version Management Page lists all the versions of an object and allows you to restore it to an older version in case of a misconfiguration.
    • Enter information on the job you are defining on the Documentation Page.

  2. Job objects (JOBS) have three pages on which you enter the scripts to be processed. They provide a number of convenience functions to help you with your work. If you enter scripts on all of them, they are processed in the following order:

    1. Pre-Process Page
    2. Process Pages
    3. Child Post-Process (SAP and PeopleSoft only), see Child Post-Process Page.
    4. Post-Process Page
  3. You can easily reuse code using Include Object (JOBI), which saves time and helps you keep your scripts consistent.

  4. Execute the job.

    There are multiple ways to do this that can be grouped as follows:

    • By a parent task.

      This is the case of jobs that are included in a parent object (for example a Workflow or a Group). When defining them, take into account that their activation time can be different from their start time; the latter usually depends on the parent object.

      See Superordinate Tasks (Parents).

    • Stand alone

      This is the case when the job is not part of a parent object or, even if it is, you execute it independently of its parent. You have three possibilities:

    When executable objects are processed, they go through the following four stages: 1. Activation, 2. Generation, 3. Processing and 4. Completion. Take a look at these topics to understand what happens with every processing stage.

  5. When processing jobs, the Automation Engine generates output files and reports that guarantee traceability and auditability. Have a look at the following topics to learn more about this:

  6. Monitor the generated object.

    As soon as the job is activated, it is available as task in the Process Monitoring perspective. In the Task list you can see its status.

    Right-click it to open its monitor (see Monitoring Jobs); it contains three pages that provide the most important information on the job parameters.

    You can also access the Job Monitor from the Process Assembly perspective.

  7. In the Process Monitoring perspective a number of functions are available, depending on the status of the job. See Working with Tasks.

See also:

JMX Forms