Configuring ESP Schedulers
This topic explains how to add, configure, view, edit and delete a scheduler for ESP. You can add ESP schedulers before installing the ESP Connector. However, you will not be able to use them until the Connector is up and running.
For more information, see AAI Integration for ESP Workload Automation.
This page includes the following:
Adding an ESP Scheduler
ESP schedulers can only be created through the Web UI.
-
Go to System and click the Add Scheduler button.
-
Enter a descriptive Name that the people who will work with the data from this scheduler can easily recognize. The name must be unique in your system. The dialog to configure the scheduler is displayed.
-
In Type select ESP.
-
Specify the following parameters:
-
Connector
If there is an ESP connector registered, it is listed in the Connector dropdown list.
-
Default Time Zone
Time zone used in ESP.
Consult with the ESP administrator to learn the correct time zone that ESP uses.
-
Messaging Host
Domain name or IP address of the host where the Message Service Hub is running.
-
Messaging Port
Listening port on the host where the Message Service Hub is running.
-
Messaging User
User name that is used to connect to the Message Service Hub. If there is no one, leave this value empty.
-
Messaging Password
Password that is used to connect to the Message Service Hub. If there is no one, leave this value empty.
-
Token
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
Preferable transport level. Select one from the following available options:
-
tcp
Specify IT to use TCP/IP connection with no encryption.
-
jks
Specify IT 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.
-
-
-
Job Definition Refresh Times
Times of day when job definitions will be refreshed.
-
Projected Start Time Period (days)
How far forward the Connector should look for planned start times.
-
Event Polling Interval (seconds)
Event polling interval for a particular scheduler.
-
-
Click Save Changes. The new scheduler is added to the list of already connected systems. Initially, its status is In Progress until the scheduler is completely connected to AAI.
Viewing a Scheduler
Click and existing scheduler in the list. The dialog that is displayed provides the scheduler configuration data as you entered when adding it. You cannot edit anything here. For details about each field, see the Adding a Scheduler section above.
Editing a Scheduler
-
Click the scheduler that you want to modify and click Edit on the dialog that is displayed.
-
The resulting dialog provides the scheduler configuration data in two tabs, Monitoring Details and Connection Configuration, as you entered them when you added it. For details about each field, see Adding a Scheduler above.
-
Click the Edit button at the top of this dialog to make the fields editable, then make your changes and save them.
Deleting a Scheduler
-
In the Schedulers list select the scheduler that you want to delete.
-
Click Delete on the dialog that is displayed.
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: