Siebel Unleashed

This is going to be a series in which I will discuss details about Application Deployment Manager (ADM) functionality available in Siebel. It is quite less known and used but very useful to reduce manual effort of moving various entities between environments. This post is going to be an introduction about Application Deployment Manager (ADM)

Application Deployment Manager (ADM):

We all (may be not all but most of us) has been part of Siebel release at one time or the other. Dev2Prod utility provided by Siebel can automated movement of Repository related data between enviornments but it cannot move application related data.

By Application related data I mean:

• List of Values
• View
• Responsibilities
• Business Services
• Runtime Events

and many more things.

We have to move them manually and we have to keep track of what we have changed. ADM provided by Siebel can move them automatically so basically our task is just to keep the track of what we want to move.

Note: ADM is only recommended if the amount of data that is to be moved is less otherwise EIM is the preferred option.

There are only few entities that are available in vanilla ADM funtionality that we can move such as LOV, Views, State Model, Assignment Rules etc. but ADM is not confied to that only we can add customized entities such as Business services, Runtime Events.

You can see ADM related views by going to Site Map > Application Deployment Manager

In the next post I will discuss details about how to implement ADM in Siebel 7.7 and Siebel 7.8 environment.