Adding/Editing/Deleting AutoSys Schedulers (Web UI)

This topic explains how to add, configure, view, edit and delete a scheduler for AutoSys. 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 .

This page includes the following:

Adding a Scheduler

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

The dialog to configure the scheduler is displayed. It contains four tabs.
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.
  Important!
  - AAI reads a specific set of tables to get information out of AutoSys. The user ID that you specify here must have read access to those tables. For a complete list per AutoSys version, see Required Access to Tables.
  - You may want to create a dedicated database user for the purposes of AAI. In the case of Oracle, if you do this, you must create synonyms on those tables first so that the user can get to those tables in an unqualified way. This is because Oracle assumes by default that the user that runs a query on the database is also the owner of the table.
- 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.
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.
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.
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
  
  AutoSys lets you select between two models:
  - Classic
    
    This model allows for cross-instance dependencies within AutoSys only. Also, it predicts only the jobs that are in jobstreams.
  - Next generation
    
    This model allows for cross-instance dependencies between scheduler types. It generates predictions for the entire scheduler and not only for jobs that are in jobstreams. This is necessary for job-based analytics.
    
    Tip:
    We recommend you use the next generation prediction model unless in very specific use cases.
  You select the prediction model when adding a new scheduler. Once you save your changes, you cannot modify this setting any more. This means that these options are nor available on the Edit dialog.
Click Test Connection. AAI checks the connection to he database and lets you know the result.
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.

Required Access to Tables

These are the tables to which the user must have read access for the connection to AutoSys to work. The tables vary depending on the AutoSys version:

AutoSys Version	Tables
Pre-R11.x AutoSys instances	alamode calendar event glob job job2 job_con job_status machine proc_event timezones
AutoSys R11.1	ujo_alamode ujo_calendar ujo_event ujo_glob ujo_job ujo_job2 ujo_job_cond ujo_job_status ujo_jobtype ujo_machine ujo_proc_event ujo_timezones
AutoSys R11.3	ujo_alamode ujo_calendar ujo_command_job ujo_event ujo_file_watch_job ujo_ftp_job ujo_glob ujo_i5_job ujo_job ujo_job_cond ujo_job_resource_dep ujo_job_status ujo_jobtype ujo_machine ujo_meta_enumerations ujo_meta_properties ujo_meta_types ujo_micro_focus_job ujo_monitor_object_job ujo_monitor_winevent_log ujo_oraapps_steps ujo_oraapps ujo_peoplesoft_job ujo_proc_event ujo_real_resource ujo_sap_arcspec ujo_sap_infodetail ujo_sap_jobstep ujo_sap_job ujo_sap_prtspec ujo_sap_recipient ujo_sched_info ujo_service_desk ujo_snmp_job ujo_sql_job ujo_sql_proc_parms ujo_strings ujo_timezones ujo_uninotify ujo_virt_resource_lookup ujo_web_services2 ujo_web_services ujo_wol_job ujo_zos_condcodes ujo_zos_dsn_trigger ujo_zos_job
R11.3.5 and later	Read access to the R11.3 tables plus the following ones: ujo_oraapps_props ujo_ws_criteria ujo_ws_parm ujo_ws_security

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.

Note:

When setting up this type of scheduler, you specify the intervals in which the job definitions are automatically refreshed through the Config tool.

The Update Now button on this dialog provides an on-demand job definition update function. If you click it, AAI retrieves the latest job data from the scheduler.

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.