The Job Scheduler Expert is a AutoPilot Service that is used in the background to schedule changes to the environment. See What is scheduling and how is it used? for more information. Below are the requirements and installation steps to use the scheduler.
Prerequisites
Confirm that the following requirements are met before installing the Job Scheduler Expert:
- Job Scheduler Expert version 10.1.5.18 or higher.
- Service Update AP60_SU31.pkg or higher.
- Java 1.8 or higher.
- One of the following supported configurations:
-
Option 1: Utilize multiple schedulers with a common corporate database. These scheduler database tables cannot be shared, but allow for a unique prefix for each of the scheduler tables (see configuration below). A single schema could support multiple scheduler instances.
-
Option 2: Using a local dedicated database for scheduler. This scheduler database requires minimal maintenance which makes it a good candidate for a local instance. The WGS DB could be shared or separate in this model. In this case, default prefix is sufficient for scheduler tables.
-
Option 1: Utilize multiple schedulers with a common corporate database. These scheduler database tables cannot be shared, but allow for a unique prefix for each of the scheduler tables (see configuration below). A single schema could support multiple scheduler instances.
Installation steps
- Install the package, JOB_SCHEDULER-0.1xx.pkg. The scheduler can be found in the same media or website from where you obtained the WGS expert.
- Locate and run the SQL files that will create the scheduler tables for your specific database. The SQL files are located in the following location:
AutoPilotM6/scheduler/config/db/
The SQL file names are as follows. Run them from the command client or database Admin tool.
AutoPilotM6/scheduler/config/db/upgrades (if upgrading from earlier version)ap-sched-<db>.sql
upgrade-0.x.xx-sched-<db>.sql - Create the quartz tables by running the following SQL file:
AutoPilotM6/scheduler/config/db/quartz_<db>.sql
If you plan to use a prefixed version (option 1 above), change QRTZ_ to your prefix. For simplicity, we recommend the WGS name as the prefix. For example, QRTZ_FIRED_TRIGGERS would become WGSPROD_FIRED_TRIGGERS. - Open the Job_Scheduler Properties screen by right clicking on Job_Scheduler and select Properties from the menu.
-
Configure the Database tab to the database where you ran the scripts and click Deploy if this is a new installation or Apply if you are editing an existing installation.
In the DB Table Prefix field specify the prefix used when creating the tables in step 3. This can be an environment variable such as {WGS}. - Restart the CEP server.
- Verify that the scheduler service starts.
- The scheduler is now ready to be used. See Scheduling jobs for information on how to implement this feature.