Deploying ADM packages - Siebel - CRM

In contrast to the somewhat heterogeneous process of exporting and packaging data and files for ADM, the deployment process is driven by a single batch file. This fileis generated during the ADM setup and is named deploy_EnterpriseName.bat, where EnterpriseName is replaced with the name of the target Siebel enterprise for which the ADM setup was completed.If we have more than one target Siebel enterprise, there will be one deployment batch file per enterprise.

The enterprise deployment batch file serves as a wrapper for calls to the underlying Java functionality and allows administrators to use a simple syntax for the complete deployment cycle. Below is an example of the syntax of the enterprise deployment batch file.


The first parameter passed to the deploy_SIEBELEVAL batch file is the name of the command—load in the example—to be executed.The second and third parameter is a valid username and password combination.The fourth parameter is the name of an ADM package directory.

To see a complete list of possible commands and syntax examples,we can use the help command:

deploy_SIEBELEVAL help

The above command results in the display of the usage information for the deployment batch file including all available commands. If we wish to see a detailed explanation of a specific command such as load, we can simply type it after the help command.

deploy_SIEBELEVAL help load

The above command displays details about the load command.

The most important commands and their typical sequence for a successful and safe deployment are described in the following table:


typical sequence for a successful and safe deployment are described

The following is a simple example script that gives us the general idea of how the deployment batch commands are used:

The script accomplishes the following:

  • Calls the load command to write package information to the ADM database
  • Calls the create command to create a new session for the package
  • Uses the list_detail and status_detail commands to output information about the package content and deployment status
  • Uses the copy and activate commands to copy the package content to the target enterprise and activate it
  • Invokes the status_detail and report commands to obtain information about the session status and runtime information
  • Calls the acknowledge command to confirm and close the session

Script files similar to that above can be used by administrators to automate the ADM deployment process. As indicated in this section, the deployment process must include a strict testing regimen in order to ensure that the migrated configuration changes do not affect the functionality or performance of the target system in a negative manner.

All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd Protection Status

Siebel - CRM Topics