Siebel Application Deployment Manager Guide > Deploying a Siebel ADM Package >

Process of Deploying a Siebel ADM Package

The process of deploying a Siebel Application Deployment Manager (ADM) package is the secondary phase in migrating application customizations to a target environment using the ADM framework.

For more information on the overall migration process, see Overview of the Siebel ADM Deployment Process. For more information on creating an ADM package, see Creating a Siebel ADM Package.

To complete the deployment of an ADM package, perform the following tasks:

1. Reviewing the Siebel ADM Predeployment Checklist

   This task confirms the readiness of the package and the environment prior to deployment.

2. Loading a Siebel ADM Package

   This task loads the ADM package into the ADM framework.

3. Reviewing the Siebel ADM Package on the Management Server

   This task confirms the presence of the ADM package in the ADM framework.

4. Backing Up Before Deploying Siebel ADM Packages

   This task backs up the target environment before deployment.

5. Deploying and Activating a Siebel ADM Package

   This task represents the actual deployment of customizations data to the new environment. At this stage, there are several options or contingencies available, which are described in Administering the Siebel ADM Deployment Execution.

6. Verifying a Siebel ADM Deployment

   This task verifies whether the data is successfully deployed by ADM to the target environment. See also About Verifying a Siebel ADM Deployment.

7. Acknowledging a Siebel ADM Deployment

   This task acknowledges that the deployment is complete. When the package has been acknowledged, you cannot restore the original application customizations in the target environment or perform any more operations for that deployment session.

8. Reviewing Postdeployment Tasks

   This task completes the deployment process for those data types that require additional action outside the ADM framework.

NOTE:  Steps 1 and 2 need to be performed only once for each package on each Siebel Server. For example, you can deploy the same package on the same Siebel Server to different Siebel Enterprise Servers, but it is necessary to run the checklist and load the package only once.