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

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

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

The Siebel administrator creates two ADM packages containing the updates and enhancements and a third ADM package containing the SRF files:

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

The Siebel Business Applications administrator deploys ADM package 2 to the target environment. Then the administrator shuts down the target environment to deploy ADM package 3, and restarts the environment after deploying ADM package 3. The administrator then compiles the SRF file (such as with the name siebel_repo_changes.srf) and runs SRFDiff to check for differences from the existing siebel.srf file.

Because there are changes to repository objects, the SRF files are different, so the administrator adds the updated SRF file (now renamed as siebel.srf) to ADM package 2 as a file item, then redeploys ADM package 2, and also deploys ADM package 1.

After reviewing the customizations updates in the test environment and verifying the correct application of the customizations, the administrator deploys and activates the ADM packages to the production environment. After activation, 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 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.