Siebel Application Deployment Manager Guide > Guidelines for Deploying ADM > Business Case Scenarios for Application Deployment Manager >
Scenario for a Major Functional Update Using ADM
This topic gives one example of how Application Deployment Manager (ADM) may be used. You may use ADM differently, depending on your business model.
A Siebel Business Application 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 in addition to changes to the schema. A repository migration is not used for this limited repository update.
In this scenario, a Siebel Business Application 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.
NOTE: You must run DDLSync after any schema changes are migrated from one environment to another.
Run this scenario carefully in a test or staged environment prior to production to determine the downtime impact of this update.