Siebel Application Deployment Manager Guide > Guidelines for Deploying Siebel ADM > Business Case Scenarios for Siebel ADM >

Scenario for a Major Functional Update Using ADM

This topic is part of Business Case Scenarios for Siebel ADM.

This topic gives one example of how Application Deployment Manager (ADM) can be used. You may use ADM differently, depending on your business model.

A Siebel administrator reviews the current production deployment on a quarterly basis, based on user feedback and management reviews of current business practices. At this time, a major functional update is planned to implement new features and business processes. This internal release includes customizations and compiled repository objects, as described in Scenario for a Minor Functional Update Using ADM, and changes to the database schema. A repository migration is not used for this limited repository update.

In this scenario, a Siebel administrator creates multiple ADM packages similar to the Scenario for a Minor Functional Update Using ADM. In a refreshed test environment, the Siebel administrator logs all users off the system, deploys the ADM package containing the schema changes, shuts down the Siebel Enterprise Server, then synchronizes the database with the repository schema. Restarting the target Siebel Enterprise Server, the administrator then deploys and activates the remaining ADM customizations. For information on running a synchronization on a new or updated schema, see Going Live with Siebel Business Applications.

After reviewing the customizations updates in the test environment and verifying the correct application of the customizations, the administrator deploys and activates the ADM package to the production environment in a similar fashion.

The actual length of time to deploy to the production environment depends on the volume of data being deployed and can be determined during the deployment to the test environment, factoring in the differences between the test environment and the production environment.

NOTE:  You must run the Synchronize Database Definition option (DDLSync) in the Database Configuration Wizard after any database schema changes are migrated from one environment to another. For more information about the Database Configuration Wizard, see Siebel Database Upgrade Guide and Siebel Installation Guide for the operating system you are using.