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

Scenario for a Minor 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 weekly or monthly basis and reviews the update requests from users. These requests include minor modifications to existing business processes, the addition of new business processes, and minor customizations updates as described in Scenario for a Minor Customization Update Using ADM. These updates include:

• 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 ten new assignment rules
• Updates to four workflow policies and the addition of one new policy
• Updates to 20 SmartScripts and the addition of thirty new scripts
• Updates to 10 repository objects, three SRF files, 20 browser scripts, and three report files

NOTE:  These updates and enhancements represent minor changes in the business processes and compiled repository objects, but do not require schema changes.

The Siebel Business Application administrator uses ADM to create one ADM package containing the updates and enhancements and another ADM package containing the SRF file:

• ADM package 1. The LOV, responsibilities, views, assignment rules; workflow policy and SmartScript updates; repository objects, browser scripts, and report files.
• ADM package 2. The SRF file.

Starting first with ADM package 2, shut down the target environment before deployment. Restart the environment after the deployment of ADM package 2, and then deploy ADM package 1, which should not require a shutdown before or a restart after deployment. However, you may need to restart the environment after the activation of some of the customizations. Any dependencies between deployment units in ADM package 1 must be controlled through the category level deployment feature. For more information on individual data types and their requirements, see ADM Supported Data Types.

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 new and updated changes are now available to the business users of the Siebel application with minimal downtime. Because this type of deployment requires downtime, it is recommended that it take place outside working hours. The length of downtime is best determined during the deployments to the test environment.