Vault deployment tasks integrate with Dimensions CM and ChangeMan ZMF to secure deployment of deployment units.
If you are using a ChangeMan ZMF vault, you can create a vault deployment task used to deploy a deployment unit, or ZMF change package, for a release package into a particular stage site.
You can do the following:
Associate the task to a release package stage.
Specify which deployment units, or change packages, to deploy.
Specify the sites, or LPARS, to which to deploy.
Specify the deployment area, or promotion level, to which the deployment applies.
Specify owners for the task.
The sequence number is used to specify order of execution of the tasks associated with a request package. The vault deployment task is specific to a single stage.
To execute a vault deployment task for deployment of files stored in ChangeMan ZMF, Serena Release Manager needs information on the ChangeMan ZMF site and promotion level.
To create a ChangeMan ZMF vault deployment task:
From a release package or deployment process template view, navigate to the Deployment tab and then select the Deployment tasks tab.
Select a stage for which this task will be executed.
Click Create Task.
The Create Deployment Task dialog box appears.
In Task Type, select Vault.
The Task Type: Vault form appears in the dialog box.
Fill out the Vault form.
For example:
Enter Task name and Sequence number.
Optionally enter a description.
Click Get units to refresh the list of deployment units, or change packages, stored in ChangeMan ZMF, and then select a deployment unit.
Click Get sites to refresh the list of sites for the selected deployment unit, and then select a site.
Click Get areas to refresh the list of promotion levels for the selected site, and then select an area.
Select the primary and secondary owners for the task.
NOTE When you create a deployment task for a deployment process template, you may not be prompted for some of the details. These should be added later when you add the deployment tasks to a release package.
Click OK.
The vault task is saved. It will be executed according to its sequential order when the release package to which it is associated is deployed to the specified stage.
|