Siebel Remote and Replication Manager Administration Guide > Administering Siebel Remote > Administering the Remote Client >

Moving Remote Clients to a Different Siebel Server

To modify the Siebel Server for a remote client in releases prior to Siebel CRM version 8.0, you must reextract the user from the new server. With Siebel CRM version 8.0 and higher, you can move one or more remote clients from one server to another server without reextracting the user or restarting server. Moving a remote client from one server to another server occurs in the same enterprise server.

To move a remote client, you do the following:

• Run the movehelper.exe utility on the source server. This Siebel Server currently serves the remote client.
• Run the nodemove.exe utility on the target server. This Siebel Server serves the remote client after you finish the move.

These utilities move the following types of information:

• Attributes of the remote client
• Docking status of the remote client
• Files and folders that exist in the docking folder for the remote client

To move remote clients to a different Siebel Server

1. Initialize the remote client with the source server.
2. Shut down the transaction processor on the source server and enable the transaction router to route all DX files.

   Shutting down the source transaction processor makes sure that the destination transaction processor or node is synchronized with the remote client node. If this node and client are not synchronized, then you might encounter an error that is similar to the following:

   Warning: can't move nodes because the node's last routed transactions cannot be found in current txnproc dx files.

3. Make sure the destination server and the source server reference the same gateway and use the same Siebel database.
4. Start the destination server with the Remote component group running.
5. Open a command window on the source server.
6. Navigate to the SIEBEL_ROOT/bin folder.

   where:

   • SIEBEL_ROOT is the root folder of your Siebel Server installation
7. Run the movehelper.exe utility using values from the following table.

   Parameter	Description
   N node_name	The name of the remote client that you are moving.
   @file_name	Optional. If you must move multiple remote clients between two servers, then use the @file_name parameter instead of the node_name parameter. where: file_name is the name of a text file that contains a list of clients to move. Each line in the text file must include only the name of a single remote client.
   W option	Optional. You can set the option for the W parameter to Y or N. You use Y to instruct the Movehelper utility to wait for other processes to release their locks on the relevant folders before proceeding. This parameter is set to the following value, by default: not used This value configures the Movehelper utility to exit if another process locked the relevant folders. It exits with a message that indicates that the remote client is processing another component.
   M option	Required. You can set the option for the M parameter to P or C. You can choose one of the following: To prepare to move one or more remote clients between two servers, use M P. To cancel a move that is already in progress, use M C. The specified client or clients return to full functionality on the source server.

   For more information, see Example Movehelper Commands.

8. Open a command window on the target server.
9. Navigate to the SIEBEL_ROOT/bin folder.
10. Make sure the destination server can access the file system of the source server.
11. Run the nodemove.exe utility using values from the following table.

    Parameter	Description
    C odbc_data_source	ODBC data source of the source server.
    D tableowner	Owner of the S_NODE table in the server database.
    U username	User name of the Siebel administrator on the source server.
    P password	Password of the Siebel administrator that you specify for the username parameter.
    n node_name	Name of the remote client that you are moving.
    @file_name	Optional. To move multiple remote clients between two servers, use the @file_name parameter instead of the /N node_name parameter. where: file_name is the name of a text file that contains a list of clients to move. Each line in the text file must include only the name of a single remote client.
    A target_server_name	The name of the Siebel Server where you are running nodemove and that Siebel Remote uses to communicate with the remote client.
    S source_docking_folder	The path to the folder on the source server that holds the docking folders for the remote clients.

    For more information, see Example Nodemove Commands.

12. Use a text editor to open the configuration file on the remote client.

    For more information, see Locating the Siebel Application Configuration File.

13. To specify how the remote client connects to the new server, modify the value of the DOCKCONNECTSTRING parameter.
14. Repeat Step 5 through Step 13 for each combination of source server and target server.

    This procedure assumes that the same source server serves all the remote clients that you must move, and that you must move all these clients to the same target server. If this situation is not true, then you must repeat this procedure for each combination of source server and target server.

Example Movehelper Commands

The following example commands for the Movehelper utility renames the docking folders for the specified users to names of the format node_name_MOVING:

movehelper /N jsmith /W Y /M P

movehelper @d:\tmp\mwcs_to_move.txt /W Y /M P

movehelper /N jsmith /M C (for canceling a move that is already in progress)

Example Nodemove Commands

The following example commands for the Nodemove utility copies the docking folder of the node from the source server to the destination server, and then redirects the node to communicate with the destination server for future synchronizations:

nodemove /C Siebel1 /D SADMIN /U username /p password /n jsmith /A Siebel2 /S SIEBEL_ROOT\DOCKING

nodemove /C Siebel1 /D SADMIN /U username /p password @d:\tmp\mwcs_to_move.txt
/A Siebel2 /S SIEBEL_ROOT\DOCKING

Reversing the Outcome of a Nodemove Operation

The Nodemove utility does not provide cancel or roll back functionality. This topic describes how to reverse the outcome of a Nodemove utility.

To reverse the outcome of a nodemove operation

1. Allow the nodemove operation to successfully finish.
2. Run a new nodemove operation.

   This new operation copies the docking folder of the node back to the source server and redirects the node to use this source server for future transactions.