Jobs can be added to a job container to allow for a number of jobs to be grouped together. Job containers are implicitly created when setting up jobs for computers or computer groups. There are several ways to create a job container:
By using the left mouse button during the drag operation, the job is set up immediately using default settings. By using the right mouse button, a small popup menu is displayed on drop, allowing you to use customized options.
The wizard can be launched in context of a library item, computer, or computer group, and from the software jobs folder.
By using the customized method, you can assign a name to the job container, and establish job linkage options for the container. With the job linkage options, you can specify if jobs in the container are run independently of one another (no linkage), or if upon failure of one job, the remaining jobs for that target are aborted (batch).
Note: The batch behavior can be customized using the 'Enable Transaction' property of the job container. If this property is checked, all jobs in the job container, regardless of software procedure type, for a target which has at least one failed job will be set to error during evaluation at the domain manager. If the 'Enable Transaction' property is not checked, all jobs after the failed job will set to error during evaluation at the domain manager, but any successfully set up jobs before the failed job will be allowed to run.
Regardless of a job container linkage, procedures of type SXP, PKG, PIF, RPM, or MSI are, if possible, rolled back on execution failure. If the job container linkage is batch and the 'Enable Transaction' property of the job container is set, then entire chains of consecutive jobs of procedures of types SXP, PKG, and RPM will be treated as a single atomic operation by the agent. On failure, the entire chain will automatically get rolled back, if possible. Note that if the job container only contains procedures of types SXP, PKG, PIF, and RPM, the entire container forms one single chain. However, it is possible to mix SXP, PKG, PIF, and RPM procedures with other procedure types, like MSI or generic. In this case, multiple chains may be formed within a single job container, but only the active chain will be considered for complete rollback on failure. In addition, the execution order set by the manager for jobs within the job container may not be honored by the agent for procedures of types SXP, PKG, PIF, and RPM. The Software Management component of the software delivery (SD) agent sorts the jobs in an order suiting it best. This means, if the job order on the SD manager is A, B, C for three jobs, it may very well be executed in the order B, C, A on the SD agent. Furthermore, if the 'Enable Transaction' property of the job container is not set and, for example, job B fails, Software Management does not stop, but tries to execute jobs C and A, too.
Job execution can also be synchronized, meaning that a job is only activated when the previously contained job has completed successfully, that is, all target computers have executed the job successfully.
For job containers with batch or synchronized job linkage, the automatic cascade of dependent packages can be disabled. For job containers with no linkage, the automatic cascade of dependent packages is always disabled.
If you click Set as default, you can save the settings in the Registry of the computer you are currently using. If there is more than one person connecting to the same SD manager, and each is using Set as Default, then each user has unique settings in a personal user registry.
|
Copyright © 2013 CA.
All rights reserved.
|
|