Siebel Application Deployment Manager Guide > Guidelines for Deploying ADM > Business Case Scenarios for Application Deployment Manager >
Scenario for a Minor Customization 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. The following scenario illustrates the use of ADM to deploy a simple change.
A Siebel Business Application administrator reviews the current production deployment on a daily basis and schedules an update to the deployment once a week. This weekly update includes minor changes and enhancements. Several users of the production application have requested the following:
- Updates to three List of Values (LOVs) and the addition of five new LOVs
- Updates to 10 responsibilities and views and the addition of two new responsibilities and views
- Updates to 50 assignment rules and the addition of 10 new assignment rules
NOTE: These minor updates and enhancements represent no new changes in business processes and do not require schema changes or compiled repository objects.
The Siebel Business Application administrator uses ADM to create one single ADM package containing the updates and enhancements. The ADM package contains the customizations data for each ADM data type. Starting first with a refreshed test environment, the administrator deploys and activates the ADM package. In this scenario, the target Siebel Enterprise Server requires minimal or no downtime.
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. The new and updated LOVs, responsibilities, views, and assignment rules are now available to the business users of the Siebel application with minimal downtime. This type of deployment can take place during working hours. However, it is always recommended that such changes be made when the system is offline or during periods of low load. The length of downtime is best determined during the deployments to the test environment.