Deploying an ADM Session or Export File

The following Siebel Application Deployment Manager (ADM) deployment options are available for database data types only. These deployment options require the creation of an ADM session or an export file representing that ADM session.

The ADM deployment options are as follows:

"Deploying ADM Sessions Using the Application Deployment Manager GUI"
"Deploying ADM Sessions Using Export Files and the ADM GUI"
"Deploying ADM Sessions Using Command-Line Interface"

Deploying ADM Sessions Using the Application Deployment Manager GUI

Deploying sessions by using the ADM GUI is one of the means of migrating ADM database data types from one Siebel application environment to another. This topic is part of "Deploying an ADM Session or Export File", which also provides information about other deployment options.

Before using this deployment option, make sure an ADM session exists in the source environment. To create an ADM session, follow tasks 1 through 5 as outlined in "Process of Creating Siebel ADM Deployment Units from Database Types".

Note:

Make sure that the parameters Target System and Target User Name are provided when creating the ADM Project.

Tip:

When using this deployment method, it is recommended to use a project filter for each database item being deployed.

To migrate a deployment session

Navigate to the Application Deployment Manager screen, then the Deployment Sessions view.
Select the deployment session of interest. Make sure that the Deployment Lock field is checked.
Click the Deploy button.
Enter the password for the target system user, and then click the Deploy button.

The Status field of the deployment session record changes to Submitted. Click the Refresh button to further update the status of the deployment.

Note:
The volume of data and the number of items within a session contribute to the processing time.
Check the details of the deployment by reviewing the EAI queue.

Deploying ADM Sessions Using Export Files and the ADM GUI

Deploying sessions using export files is one of the means of migrating ADM database data types from one Siebel application environment to another. This topic is part of "Deploying an ADM Session or Export File", which also provides information about other deployment options.

Before using this deployment option, make sure that an ADM session exists and that the deployment unit XML file has been exported as outlined in the tasks 1 through 6 of "Process of Creating Siebel ADM Deployment Units from Database Types".

To deploy an ADM session by importing an ADM XML deployment session file

Access the target system; that is, the system to which you want to migrate data.
Make sure that the source file is accessible.
Navigate to the Application Deployment Manager screen, then the Deployment Sessions view.
In the Deployment Sessions list, click the menu button and then Deploy from File.
Enter the network path and filename for the import file, then click the Import button.

Note:
The import process requires the filename as input. If the export session generated multiple files, then the import step must be executed for each file.
Check the details of the deployment by reviewing the EAI queue of the target Application Object Manager.

Deploying ADM Sessions Using Command-Line Interface

Deploying sessions using the Server Manager (srvrmgr) command-line interface is one of the means of migrating ADM database data types from one Siebel application environment to another. This topic is part of "Deploying an ADM Session or Export File", which also provides information about other deployment options.

This procedure runs a workflow process, named UDA Batch Import, on the target environment. This workflow process imports the data into the target environment, based on a session ID provided, using Siebel EAI as the transport. The Server Manager command line can be used to generate export files multiple times and can provide basic automation for the export step.

Note:

Before you run this workflow process, you must modify its Import File Directory property to specify the location where the customizations file, with a name like Session_ID.ini, was generated during export. After modifying this property, publish and activate the workflow process, as described in Siebel Business Process Framework: Workflow Guide.

The Workflow Process Manager component (WfProcMgr) must be running on the target Siebel Server in order for this procedure to run correctly.

To import deployment session file using the Server Manager command-line interface

Make sure that the export deployment file exists in a shared network location.

Note:
You do not need to create a deployment session in the target environment to import a deployment session file.
Start the Server Manager command-line interface with your user ID in the target system.

For more information about this procedure, see Siebel System Administration Guide.
Verify that the server component Workflow Process Manager (alias WfProcMgr) is online.

If it is not, then enable the Workflow Management component group (alias Workflow) and restart the Siebel Server. For more information about these tasks, see Siebel System Administration Guide.
Enter the following command at the Server Manager command-line interface prompt:
```
start task for comp WfProcMgr server Siebel_Server_Name with ProcessName="UDA Batch Import", RowID="Session_ID"
```
where:
- Siebel_Server_Name is the name of the Siebel Server.
- UDA Batch Import is the name of the workflow process. This value is case-sensitive.
- Session_ID is the session ID of the deployment session used to generate the export files.
  
  Note:
  This session ID does not exist anywhere in the target database. It is the session ID used to export files. This value maps to an .ini file generated during the export.
Check the details of the batch deployment by reviewing the source system EAI queue.

Note:

One import step reads all of the previously generated files by the export session executed on the source system.