Configuring ESP Workload Automation Schedulers

This topic explains how to add and configure a scheduler for ESP Workload Automation (ESP).

You can add ESP schedulers before installing the Automic Automation Connector. However, you will not be able to use them until the Connector is up and running. For more information, see Setting Up the ESP Connector.

To Add an ESP Scheduler

Go to System > Schedulersand define the following parameters:

In the Add Scheduler section:

  • Name

    Supplied by the user

  • Scheduler Type

    ESP

  • Time Zone

    Enter the time zone

    Important !

    Keep in mind that the time zone that is specified in the scheduler must match the one that is used in ESP. Consult with the ESP administrator to learn the correct time zone that ESP uses.

  • Connector

    If there is an ESP Connector registered, it is listed below this field.

  • Messaging Hub Host

    Specify the domain name or IP address of the host where the Message Service Hub is running.

  • Messaging Hub Port

    Specify the listening port on the host where the Message Service Hub is running.

  • Messaging Hub User

    Specify the user name that is used to connect to the Message Service Hub. If there is no one, leave this value empty.

  • Messaging Password

    Specify the password that is used to connect to the Message Service Hub. If there is no one, leave this value empty.

  • Token

    Specify the token that is used to match the appropriate ESP Adapter and ESP Connector. This value must match the one that is specified in the adapter.connection.mq-token property of the ADPTPROP.

    mq-transport

    Specify the preferable transport level. Select one from the following available options:

    • tcp

      Specify this to use TCP/IP connection with no encryption

    • jks

      Specify this to use TCP/IP connection with encryption when the certificate and the certificate authority certificate are stored in the Java keystore or truststore.

      Jks requires the following properties:

      • mq-jks-keyStore

        Specify the keystore, for example keyStore: "c:\\keystore.jks"

      • mq-jks-keyStorePassword

        Specify the keystore password.

      • mq-jks-trustStore

        Specify the truststore, for example trustStore: "c:\\trust-store.jks"

      • mq-jks-trustStorePassword

        Specify the truststore password.

In the Advanced Settings section

  • Projected Start Time Period (days)

    How far forward the Connector should look for planned start times

  • Event Polling Interval (seconds)

    Specific event polling interval for a particular scheduler

  • Job Definition Refresh Times

    Times of day when job definitions will be refreshed

Troubleshooting

Problem

Command java not Found

Indications

Output similar to the following when running software manually or when started automatically (OS-specific):

$ cd /opt/terma/jobtrac-connector

$ java -jar jobtrac-connector-1.0.0.jar

Command 'java' not found, did you mean:
    command 'java' from deb default-jre 
    command 'java' from deb openjdk-11-jre-headless			
    command 'java' from deb openjdk-11-jre-headless
command 'java' from deb openjdk-8-jre-headless

Problem Description

This message indicates a Java virtual machine is either not installed or available in the path for the current user on the host or container. The software requires an available, compatible Java virtual machine in order to work.

Resolution

Install a Java 8-compatible Java Runtime Environment (JRE) or Java Development Kit (JDK). For more information, see Prerequisites. Re-run the software normally, once complete.

See also:

Schedulers