Sometimes, you may need to run only part of an Application. For example, you may want to run part of an Application to rerun one or more jobs or to run a job when a request comes in for it to run.
To run part of an Application, you can choose a subset of jobs within the Application when you trigger the Event that runs it. The jobs within the subset are named root jobs.
To specify the root jobs, you can specify any one of the following:
Example: Root Jobs
Suppose that, in an Application, jobs A, B, C, and D run daily, job E runs Friday, and job F runs on the last workday of the month.
The following table shows the result of using different syntax to specify root jobs:
|
Root jobs to run |
Result |
|---|---|
|
A |
The server selects job A. Job A runs |
|
D+ |
The server selects and runs job D. If it is Friday, the server also selects and runs job E. If it is the last workday of the month, the server also selects and runs job F. |
|
A, E |
The server selects job A and job E. Job A and job E run. Job E runs regardless of the day because it is specified explicitly. |
|
A, D+ |
The server selects job A and job D. Job A and job D run. If it is Friday, the server also selects and runs job E. If it is the last workday of the month, the server also selects and runs job F. |
When the server builds the Application containing the root jobs, it inherits the relationships between jobs unless the Application definition overrides job inheritance. The server also considers release conditions when it generates the Application containing the root jobs.
To ensure you run the correct jobs within your Application, you should simulate the Event before you trigger it, specifying the same root jobs to run in the simulation.
Note: You can use symbolic variables to specify root jobs if the job names are defined using variables. You can specify the job name as a variable or as the resolved name.
|
Copyright © 2014 CA.
All rights reserved.
|
|