Table of Contents
Advertisement
3.2 Walkthrough: Scheduling a System Job
This section demonstrates how you can use the Orchestrate Development Client to deploy and
schedule an existing system job named
directory of your PlateSpin Orchestrate installation.
examples
This section includes the following information:
Section 3.2.1, "Deploying a Sample System Job," on page 41
Section 3.2.2, "Creating a New Schedule for the Job," on page 42
Section 3.2.3, "Defining the New Schedule," on page 43
Section 3.2.4, "Activating the New Schedule," on page 48
Section 3.2.5, "Running the New Schedule Immediately," on page 48
3.2.1 Deploying a Sample System Job
Before a job can run, the PlateSpin Orchestrate administrator must deploy it, which involves moving
it from a developed package state to a state where it is ready and available for users. Only the
administrator has the necessary rights to deploy a job.
There are four methods you can use to deploy a job:
Deploy it from the PlateSpin Orchestrate Development Client by right-clicking the Jobs
container in the Explorer panel.
Deploy it from the PlateSpin Orchestrate Development Client by selecting the Actions menu in
the Orchestrate Development Client.
Deploy it from the
zosadmin
Copy the deployable component to the "hot" deployment directory under the Orchestrate
Server instance directory. Typically, this directory is located at
zos/server/deploy
PlateSpin Orchestrate monitors this directory.
A runnable job can also be scheduled, which means that the schedule for running the job and the
trigger or triggers that initiate or "fire" the schedule (or both) are configured and packaged with the
job.
For this walkthrough, you deploy one of several system jobs (
PlateSpin Orchestrate customers to demonstrate how system jobs are deployed and run. This job
package, which is actually a
component. It does not have a
Development Client to add the
NOTE: A PlateSpin Orchestrate job developer can create and package jobs that include a
a
file, a
file (trigger), and a .
.policy
.trig
in the job package is also typical of the predeployed discovery jobs installed with PlateSpin
Orchestrate, which run without intervention when the criteria for firing the schedule are satisfied.
Such jobs are visible in the Job Scheduler because they already include the
For more information about developing jobs and schedules in a job archive, see
the
PlateSpin Orchestrate 2.0 Developer Guide and
auditcleaner.job
command line (
zosadmin deploy path_to_job
. Using this method, deployment proceeds within a few seconds.
archive, includes only a
.jar
component. You can use the Job Scheduler in the Orchestrate
.sched
component separately.
.sched
sched
. This example job is included in the
/var/opt/novell/zenworks/
auditCleaner.job
component and a
.policy
file (schedule). The presence of the
.sched
Reference.
The PlateSpin Orchestrate Job Scheduler
).
) developed for
.jdl
file,
.jdl
file
.sched
components.
"Job
Scheduling" in
41
Advertisement
Table of Contents
