Siebel Application Deployment Manager Guide > Guidelines for Deploying ADM > Business Case Scenarios for Application Deployment Manager >
Scenario for a Major Functional Update Including Full Repository Changes 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 an annual basis primarily based on the management or executive reviews of the current business practices. At this time, a major functional release is planned to implement the new features and business processes. This major internal release includes the customizations and compiled repository objects described in Scenario for a Minor Functional Update Using ADM, in addition to changes to the schema and a full repository update. In this scenario, due to the large number of repository updates, the repository migration feature is used instead of an ADM package containing repository updates. For information on running a repository migration, see Going Live with Siebel Business Applications.
In this scenario, in a refreshed test environment, a Siebel Business Application administrator runs a repository migration to update the new repository. The administrator then performs other customizations migrations using ADM as described in Scenario for a Major Functional Update Using ADM.
After reviewing the customization 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.
Carefully run this scenario in test or a staged environment prior to production to determine actual downtime impact of this update.