1. System Administration Guide
  2. Renaming Servers for an Existing Siebel CRM Deployment

Renaming Servers for an Existing Siebel CRM Deployment

This topic describes the steps to take when one or more host names have changed for servers that host Siebel CRM server modules in an existing deployment of Siebel CRM. Such cases require updates to be made in multiple locations and involve mandatory downtime. Perform the following tasks on all applicable nodes. Review all of the tasks first and confirm the specific requirements for each particular case.

Note: Before you perform these steps, first shut down the Siebel deployment by stopping all of the Siebel services and processes, including the application containers, as described in Shutting Down a Siebel CRM Deployment and related topics. Steps for restarting all of the services and processes are included in these procedures.

To perform the necessary steps on each Siebel Application Interface node

  1. Back up the SIEBEL_ROOT\applicationcontainer_external\webapps\applicationinterface.properties file.

  2. Open the applicationinterface.properties file in a text editor like Wordpad or vi.

  3. Where the Siebel Gateway that this instance of Siebel Application Interface connects to has moved to a different server or has been renamed, modify the host name for the Siebel Gateway, which is defined in the CGHostURI property.

  4. Save the applicationinterface.properties file.

To perform the necessary steps on each Siebel Gateway node

  1. Where this Siebel Gateway has moved to a different server or has been renamed, modify the host name in the gateway.properties file, as follows:

    1. Back up the SIEBEL_ROOT\applicationcontainer_internal\webapps\gateway.properties file.

    2. Open the gateway.properties file in a text editor like Wordpad or vi.

    3. Modify the Siebel Gateway host name, which is defined in the Gateway, TLSGateway, and Registryhostname properties.

    4. Save the gateway.properties file.

  2. If you are using Oracle Enterprise Manager for Siebel CRM, then, where the Siebel Gateway has moved to a different server or has been renamed, modify the host name in the EMdiscovery.properties file, as follows:

    1. Back up the SIEBEL_ROOT\EMdiscovery.properties file.

    2. Open the EMdiscovery.properties file in a text editor like Wordpad or vi.

    3. Modify the Siebel Gateway host name defined in the AIConnStr property.

    4. Save the EMdiscovery.properties file.

  3. Where any Siebel CRM module has moved to a different server or has been renamed, modify the host name as follows:

    1. Back up the SIEBEL_ROOT\gtwysrvr\registry\conf\registry.cfg file.

    2. Back up the SIEBEL_ROOT\gtwysrvr\registry\conf\version_2 directory.

    3. Open the registry.cfg file in a text editor like Wordpad or vi.

    4. Modify the host names for all applicable Siebel CRM modules.

    5. Save the registry.cfg file.

  4. Modify the Gateway Registry service (ZooKeeper), as follows:

    1. Start the Gateway Registry service (ZooKeeper).

    2. Connect to the Gateway Registry using any ZooKeeper client.

    3. Navigate to /ROOT/Config/Profiles/Enterprises.

    4. Select the profile that is used to deploy the Siebel CRM enterprise and modify the host name defined in the NameserverHostName parameter.

    5. Navigate to /ROOT/Config/Profiles/SWSM.

    6. Select the profile that is used to deploy the Siebel Application Interface and modify the host name defined in the GatewayHost parameter. Repeat this step for all the profiles that are used to deploy Application Interface nodes.

    7. Navigate to /ROOT/Config/Profiles/Servers.

    8. Select the profile that is used to deploy the Siebel Server and modify the host name defined in the NameserverHostName parameter. Repeat this step for all the profiles that are used to deploy Siebel Server nodes.

    9. Navigate to every hierarchy up to the leaf level under /ROOT/Config/Deployments. Modify the host name defined in the PhysicalHostIP parameter.

To perform the necessary steps on each Siebel Server node

  1. Start the Siebel Gateway Name Server system service.

  2. Start Server Manager and connect to the enterprise.

  3. Execute the following commands to see the current values for these parameters:

    • list hidden param DSGatewayAddress for named subsystem ServerDataSrc(

    • list param DSConnectString for named subsystem GatewayDataSrc

    • list param HOST for server <$ServerName>

    Repeat this command for all the servers.

  4. Execute the following commands to modify the current values for these parameters:

    • change param DSGatewayAddress=<value> for named subsystem ServerDataSrc (where the Siebel Gateway has moved to a different server or has been renamed)

    • change param DSConnectString=<value> for named subsystem GatewayDataSrc (where the Siebel Gateway has moved to a different server or has been renamed)

    • change param host=<value> for server <$ServerName> (where the Siebel Server has moved to a different server or has been renamed)

    Repeat this command for all the servers.

  5. Recreate the Siebel Server services, as follows:

    1. Navigate to <SIEBEL_ROOT>\siebsrvr\bin.

    2. Execute the following commands:

      • siebctl -h <$SIEBEL_ROOT> -S siebsrvr -i "<enterprise name>_<Siebel Server name>" -d

      • siebctl -h <$SIEBEL_ROOT> -a -f -S siebsrvr -i "<Enterprise name>_<Siebel Server name>" -g <Gateway New Hostname>:<Gateway Port> -e <Enterprise name> -s <Siebel Server name> -l <language> -u "<User Id>" -e <Enterprise name) -A Yes (where the Siebel Gateway has moved to a different server or has been renamed)

    3. Start all the Siebel Server services.

    4. Start all the Application Interface services.

  6. Verify that all modules have started correctly and are functioning normally.

    For more information, see Siebel Installation Guide.