Information about the software policy: name and linkage of the job container that is generated when the policy is evaluated.
Enter a name for the software policy or select it from the drop-down list.
Name of the Asset Group linked to the software policy.
Priority of the job.
Highest: 1
Lowest: 10
Default: 5
Note: For sealed Job Containers on the Domain Manager (not the Enterprise Manager) the priority may be changed without unsealing the Job Container.
Note: Migrated Software Policies from Legacy servers and all existing tasks with containers and policies will be assigned priority 5. This priority can be changed before sealing the policy.
Unsealing and modifying the policies is possible.
Specifies the way of job execution:
For each target, all jobs in the container will be run as a single piece of work. If a job fails for any target, all remaining jobs in the container for that target will be aborted. Batch jobs constitute a critical region; no other jobs are allowed to come in between them. This is important because an unrelated job can cause problems with the machine and cause the rollback to fail. This is also the reason why all batch jobs must have the same activation time.
This check box is only available if you have selected the Batch Job check box. When the Enable Transaction check box is selected, jobs for SXP, PKG, and PIF packages can be automatically rolled-back in case of failure. Upon a failure, all previous jobs in the container for that target are rolled back, if possible. If roll-back is not selected, the agent will install as much as it can. If one job in the container fails, only that job will be rolled back; the remaining jobs will not execute.
Check this box if you do not want the jobs that will be part of this container (when the job container is being evaluated) to be automatically cascaded. Jobs that will be set up as part of the cascade will originate from the Procedure dependencies folder of each procedure that is part of the job container.
Check this box if you do not want the jobs that will be part of this container (when the job container is being evaluated) to be automatically cascaded.
Jobs that will be set up as part of the cascading will originate from the Procedure Dependencies folder of each procedure that is part of the job container. The folder consists of children for each procedure.
This box will be grayed out, if No Linkage has been selected (since cascading is of no importance with the No linkage selection).
Note: When renewing a job container the property "Ignore cascading install of dependent packages" is automatically checked and disabled for edit. The reason for this is to make sure the renewed job container includes the exact same jobs as the failed job container. If the original job container failed because of a missing procedure dependency, the renewal of that job container will ignore the procedure dependency and attempt to install the depending software package. This will only happen if the procedure is physically missing. If the cascaded procedure exists and simply fails to install, a renewal will include it.
The job is activated when the previous job in the container has completed correctly.
Tick the box if you want to use this feature.
Defines the custom administrator message text to display to the end users.
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|