Cisco Cisco Workload Automation 6.3 Betriebsanweisung
176
Jobs and Job Groups
Defining Jobs Interface
Unscheduled allowed – Select this option to search for jobs that can be inserted into a schedule on an ad hoc basis.
Unscheduled not allowed – Select this option to search for jobs that can only be run on a scheduled basis.
Intermaster Dependencies
You can create jobs with variable dependencies that are determined by jobs processed on another master. A job with an
intermaster dependency resides on a local master subscribing to a remote master that publishes the value of a variable.
intermaster dependency resides on a local master subscribing to a remote master that publishes the value of a variable.
For the purpose of an intermaster dependency, the local master becomes a type of client to the remote master. The
variable is defined on the remote master and made available to other masters. The local master subscribes to a variable
managed by another master by creating a special remote master connection. Because the local master is a client to the
remote master, the communication port is the same one used by the client of the remote master. If the remote master is
using fault tolerance than the connection is configured to automatically switch to the backup machine of the remote
master if a failure occurs. This connection displays in the Connections pane as a Remote Master connection. The
Connection Definition dialog also displays the variables that the remote master is publishing. These variables are
regularly updated and cached on the local master and the actual variable values are published at the time required by
the specific job.
variable is defined on the remote master and made available to other masters. The local master subscribes to a variable
managed by another master by creating a special remote master connection. Because the local master is a client to the
remote master, the communication port is the same one used by the client of the remote master. If the remote master is
using fault tolerance than the connection is configured to automatically switch to the backup machine of the remote
master if a failure occurs. This connection displays in the Connections pane as a Remote Master connection. The
Connection Definition dialog also displays the variables that the remote master is publishing. These variables are
regularly updated and cached on the local master and the actual variable values are published at the time required by
the specific job.
When defining a variable dependency, you specify which master manages the variable. If no remote connections have
been set up, then the local master is the default. If you selected a remote master, you can select a published variable
from a drop-down list of variable names.
been set up, then the local master is the default. If you selected a remote master, you can select a published variable
from a drop-down list of variable names.
You control which variables are available for remote master use through the Variable Definition dialog. You can keep a
variable for use only on the local master or publish the variable for use by remote masters. You can also elect to either
publish the variable in unalterable form or allow others to modify the variable.
variable for use only on the local master or publish the variable for use by remote masters. You can also elect to either
publish the variable in unalterable form or allow others to modify the variable.
A system event can be created to notify a user if connection between the remote and local master is lost. A lost
connection prevents a job from completing since the variable value cannot be determined. A user can also check on the
status of an intermaster variable by studying the Dependencies tab of the Job Details dialog. An intermaster variable
will show a value of Unavailable if the connection to the remote master is lost.
connection prevents a job from completing since the variable value cannot be determined. A user can also check on the
status of an intermaster variable by studying the Dependencies tab of the Job Details dialog. An intermaster variable
will show a value of Unavailable if the connection to the remote master is lost.
Note: It requires a separate license to use intermaster dependencies. You cannot define a remote master or publish
intermaster variables without a license for intermaster dependencies.
intermaster variables without a license for intermaster dependencies.
The methodology described here can be extended to apply to dependencies between any number of jobs on any number
of masters. In brief, the technique to implement intermaster dependencies uses a job event on one master to set a
variable value on another master whose job(s) will depend on that variable.
of masters. In brief, the technique to implement intermaster dependencies uses a job event on one master to set a
variable value on another master whose job(s) will depend on that variable.
For example: Master2:JobB depends on Master1:JobA
1.
Install an agent on the same machine as Master2 or one of its clients. This agent will service Master1. (If there are
cross-dependencies such that Master1:JobC depended on Master2:JobB, you would install an agent on the same
machine as Master1 or one of its clients to service Master2). An agent is required for each unique intermaster
relationship. Remember, more than one agent can be installed on a single machine to service multiple masters.
cross-dependencies such that Master1:JobC depended on Master2:JobB, you would install an agent on the same
machine as Master1 or one of its clients to service Master2). An agent is required for each unique intermaster
relationship. Remember, more than one agent can be installed on a single machine to service multiple masters.
2.
On Master1 create a linking job that runs on the agent installed on Master2 (or one of its CWA Web Clients). This
job will run the
job will run the
varset command from the client's command line interface to set the value of a variable on Master2
to indicate that the dependency has been met; for example, the job definition for the linking job would contain the
following:
following:
—
In the Command field, type
C:\Program Files\Tidal\TESCmdLine\bin\sacmd.bat
—
In the Command Parameters
field, type
varset –n master1_joba –v “normal”
—
In the Agent Name field, type