Deploy Job - Package
The Package panel lets you identify the BLPackage you want to deploy. If the BLPackage includes its own local properties, the Package panel lets you edit them.
To edit the BLPackage local properties, you must have the DeployJob.Modify authorization — the same authorization required for most of the other edits that you perform in the Deploy Job. Only the Deploy Job properties listed in the Deploy Job - Properties panel are controlled by the DeployJob.ModifyProperties authorization.
If you are deploying a BLPackage with local properties to target components, you may need to specify property values that are applicable to each target component. The Properties list on this panel differs from other Properties lists throughout the BMC Server Automation system. On this panel the list includes two columns labeled Assignment Type and Value/Name. The Assignment Type column gives you the following options:
- Setting a value that always applies for this local property.
- Choosing a component property. When the job deploys a BLPackage to a target component, the job uses the value of the component property as the value for this local BLPackage property. If you have defined instances for a component property, the property values set in each instance determine the property values for each component. Those, in turn, are used to replace the value of local BLPackage property. For a detailed example showing how to map BLPackage properties to component properties, see Using properties to deploy multiple versions of an application to the same server.
- Automatically mapping the local property on the BLPackage to a component property. For automatic mapping to occur, the name of the local property on the BLPackage must exactly match the name of the property defined for a component. If you choose this option and you have defined instances for a component property, the property values set in each instance determine the property values for each component. Those, in turn, are used to replace the value of local BLPackage property.
If you map a BLPackage property to a component property, the mapping is ignored when you deploy the package to a target server rather than a target component.
The Package panel also lets you choose between a basic or advanced deploy. The two approaches to defining BLPackage Deploy Jobs have the following characteristics:
- Basic — Defines the job so if it fails, it is automatically reset, which means you can immediately run the job again. Also, basic BLPackage Deploy Jobs are defined to flow by server rather then by phase. Basic BLPackage Deploy Jobs are recommended if you are including the job in a Batch Job. When you choose the Basic option, other panels in the BLPackage Deploy Job wizard do not show some of the more complex options for managing the flow and scheduling of the job.
- Advanced — Provides full flexibility when defining the job. For advanced BLPackage Deploy Jobs, you can choose to control the flow of the job by server or phase and schedule execution of each job phase. If the job fails to complete, you can re-execute it on a server-by-server and phase-by-phase basis rather than have the job automatically reset.
Choose the package to be deployed by clicking Browse. The Select Depot Object dialog box opens. Use it to select a package from the Depot.
In a Deploy Job for patch remediation, which deploys multiple BLPackages to multiple targets, only the first detected BLPackage (of multiple BLPackages) is displayed in the Package field. You cannot choose a different BLPackage.
To view the full list of BLPackages in such a Deploy Job, access the job's display of dependencies, in the downward view, as described in Viewing dependencies.
Required column in Properties table
Set to True if a value for this property is required.
Select Deploy Job Type
Select Basic or Advanced.