Going Live with Siebel Business Applications > Migrating Customizations Between Applications >

Deploying Sessions Using Command-Line Interface

Deploying sessions using the Server Manager command-line interface (srvrmgr program) is one means to migrate data from one Siebel application environment to another, and is a task in the Process for Migrating Customizations Between Applications. For other deployment options, see the following sections:

• Deploying Sessions Using the Application Deployment Manager GUI
• Deploying Sessions Using Export Files

Before deploying sessions using the command-line interface, make sure that required configurations are complete and deployment sessions exist. See Creating Deployment Sessions Using ADM for information on creating deployment sessions and other required configurations. Also make sure ADM batch workflows are configured in Siebel Tools. See Configuring Batch Workflows for ADM Command-Line Interface Deployment for a description of this task.

To migrate deployment sessions using the Server Manager command-line interface, perform the following tasks:

1. From the source system Server Manager command-line interface, deploy sessions using export files to a shared network path.
2. From the target system Server Manager command-line interface, import the deployment session files to the target system.

To export a deployment session file using Server Manager command-line interface

1. In the source system, make sure deployment sessions intended for srvrmgr deployment have the field Export to File checked. See Creating Deployment Sessions Using ADM for further information on deployment sessions.
2. In the source system, make sure the Deployment Lock value is checked and your Server Manager user ID is in the Locked By field for each session.

   NOTE:  You can only migrate locked deployment sessions with your user ID.

3. Start Server Manager command-line interface (srvrmgr program) with your user ID.

   For details on this procedure, refer to Siebel System Administration Guide.

4. Verify the server component Workflow Process Manager (WfProcMgr) is online.

   If not, enable the Workflow component group and restart the Siebel Server. For details on these procedures, see Siebel System Administration Guide.

5. 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 Deployment", RowID="Session_ID"

   where:

   Siebel_Server_Name = Name of the Siebel Server.

   UDA Batch Deployment = Name of the workflow process. This value is case-sensitive.

   Session_ID = Session ID of deployment session created earlier through the ADM GUI.

6. Check the details of the deployment by reviewing the source system ADM log files and EAI queue. By default, an EAI queue entry is created in case of any deployment errors on the target system See Reviewing the ADM Data Migration for further information on these tasks.

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

1. Make sure 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.

2. Start Server Manager command-line interface (srvrmgr program) with your user ID in the target system.

   For details on this procedure, refer to Siebel System Administration Guide.

3. Verify the server component Workflow Process Manager (alias WfProcMgr) is online.

   If not, enable the Workflow Management component group (alias Workflow) and restart the Siebel Server. For details on these procedures, see Siebel System Administration Guide.

4. 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 = Name of the Siebel Server.

   UDA Batch Import = Name of the workflow process. This value is case-sensitive.

   Session_ID = 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.

5. Check the details of the batch deployment by reviewing the source system ADM log files and EAI queue. See Reviewing the ADM Data Migration for further information on these tasks.

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