Adding/Editing/Deleting AutoSys Schedulers (Web UI)

This topic explains how to add, configure, view, edit, or delete a scheduler for AutoSys and how to update the job definitions manually. You can add AutoSys schedulers either from the thick client or from the AAI Web UI. This topic explains how to add them from the AAI Web UI.

You can add AutoSys schedulers before installing the AutoSys Connector. However, you will not be able to use them until the connector is up and running. For more information, see AAI Integration for AutoSys .

Adding an AutoSys Scheduler

Configuring a scheduler involves defining the following:

• Scheduler-specific parameters: Name, type, connector and time zone.

• Connection data to the corresponding workload automation engine.

• Intervals, periods and times that AAI will apply to retrieve data.

To Add an AutoSys Scheduler

1. Go to System and click the Add Scheduler button.

2. 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. Select the Scheduler Type AutoSys.

   The dialog to configure the scheduler is displayed. It contains four tabs.

3. In the Primary tab, specify the primary connection data of the AutoSys instance that you want to connect to.

   • Scheduler DBMS

     The type of the AutoSys database, which can be either Oracle, Sybase, or SQL Server.

     When using a Oracle database, you can set up Kerberos to handle the authentication. To do so, select the Use Kerberos for authentication checkbox and select one or the following options:

     • Use a keytab file: Define the database user (principal) and the path to the keytab file stored in your working directory.

     • Use cache credentials: Define the path to the credential cache file.

     Alternatively, you can use the add_scheduler command available in the AAI CLI, see Scheduler Commands.

   • Host Name

     Hostname of the AutoSys database.

   • Port

     Port that the AutoSys database is on.

   • Database

     Name of the database.

   • User ID (with read access) and Password

     Credentials that you need to connect to the AutoSys database.

   • Timeout in minutes

     (Optional) JDBC socket/read timeout in minutes different from the default of 0 (no timeout). Only use it if needed and under guidance from our technical Support team.

   • Custom JDBC URL

     Optionally activate this checkbox and enter the custom JDBC connection string in the field below.

4. If you are running AutoSys in a high availability environment, you enter the secondary connection in the Secondary tab. If the instance that you defined as the Primary Connection fails, AAI will use the Secondary Connection to receive both definition and run data from AutoSys.

   In the Secondary tab, make sure you select the Use Secondary Connection checkbox to activate it.

   The fields in this tab are identical to the field in Primary but for the following:

   • AutoSys-implemented High Availability (Dual-database)

   • Non-AutoSys-implemented Mirroring or Replication DB

   The Secondary tab also allows you to set up Kerberos to authenticate the secondary database connection. The Kerberos authentication definition for the secondary database is the same as for the primary one.

   Alternatively, you can use the add_scheduler command available in the AAI CLI, see Scheduler Commands.

5. You can also specify an AutoSys API connection. If so, enter the Host Name and Port.

   Prerequisites

   • The AutoSys client must be installed on the AAI server.

   • A 32-bit Java JDK must be set as default on the PATH environment variable of the AAI server.

     If Java is running with 64-bit, this 32-bit Java set in addition to the 64-bit Java pointed to from the JAVA_HOME environment variable.

   • If AAI is not run directly from the install directory, set an environment variable called JAWS_HOME. This variable should have the path to the AAI install directory.

6. In Advanced you specify the parameters to add historical run data to AAI's database.

   When adding a new instance of AutoSys, you have the option of reading Archived files. This has the advantage of pre-populating AAI with historical data that you can later see and analyze in AAI. By providing AAI with the location of those archived files, AAI will load in all the archived job runs.

   These files, updated daily, will also provide the ability to recover missing data due to AAI downtime, if any.

   Enter the following parameters:

   • Archive File Directory 

     Full path to the location of the archived events. AAI must have read access to the location.

   • Archive File Pattern

     AAI includes the three most regularly used patterns:

     • MM.dd.yyyy

     • MM.dd.yyyy.HH.mm.ss

     • yyMMdd

     The default is MM.dd.yyyy. If the pattern is not one of these three, you can enter a new pattern.

   • Archive File Delimiters

     AAI will always use the pipe character (|) for AutoSys 4.x schedulers no matter what you select here.

     For AutoSys r11, the comma (,) is the default. However, you can enter your own delimiter, if needed.

   • Security

     AAI can Honor the eEM AutoSys security policies defined to eEM. When this is selected, non-scheduling specific job properties, such as the command and machine properties, are hidden from users who do not have the authority to see them.

   • Prediction Model

     • Next generation (default)

       The next generation predictions consider cross-instance dependencies between AutoSys scheduler instances as well as cross-scheduler dependencies between AutoSys and CA7 or IWS scheduler instances. Furthermore, because the prediction engine also calculates AutoSys jobstream simulations, cross-instance and cross-scheduler dependencies can be considered in the simulations. Finally, to support job-based analytics, this prediction model generates predictions for all jobs in the scheduler, not only for jobs that are part of jobstreams.

     • Classic

       The classic predictions can consider cross-instance dependencies within AutoSys, but not cross-scheduler dependencies. Also, it predicts runs only for the AutoSys jobs that are part of jobstreams in AAI.

     Important!

     Once you save your changes, you cannot change the Prediction Model used for the scheduler. The options are not available on the Edit dialog.

     We recommend that you use the next generation prediction model unless you have a very specific use case in its favor.

7. Click Test Connection. AAI checks the connection to he database and lets you know the result.

8. 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 two tabs:

• Monitoring Details

  Displays current scheduler update status. On this tab, the Update Now button provides an on-demand job definition update function. If you click it, AAI retrieves the latest job definition data from the scheduler.

• Connection Configuration

  Displays the configuration data as entered when adding the scheduler

You cannot edit anything here. For details about each field, see the Adding a Scheduler section above.

Updating the Job Definition Data

When you define a new scheduler, you specify the times at which the job definitions should be refreshed in the Job Definition Refresh Times field. You can also reload the job definitions manually at any time. Do the following:

1. In the Schedulers list click the name of the scheduler.

2. On the resulting dialog, click the Edit button to make the fields editable.

3. In the Monitoring Details tab click the Update Now button that is under Job Definitions Updated.

   The last time that this data has been updated is displayed between the label and the button. This gives accurate information about the age of the data that AAI is surfacing.

Editing a Scheduler

1. In the Schedulers list click the name of the scheduler.

2. On the resulting dialog, click the Edit button to make the fields editable.

3. This dialog provides the scheduler configuration data in two tabs, Monitoring Details and Connection Configuration, as you entered them when you added it. Makes your changes. For details about each field, see Adding a Scheduler .

Deleting a Scheduler

1. In the Schedulers list select the scheduler that you want to delete.

2. Click Delete on the dialog that is displayed.

See also:

• View Log (JIL Syntax Conversion)

• Edit WCC (AutoSys)

• Schedulers