Modifying the Siebel Configuration File for Siebel Remote

This task is a step in Process of Configuring the Remote Client.

The remote client reads configuration parameters in the Siebel configuration file to determine the location of the Siebel Server folders, the Siebel File Server folders, and the server database installation. The siebel.cfg file for Siebel Sales is an example of a configuration file.

You must set the values for the configuration parameters before you configure Siebel Remote. If you install a Siebel application, then the Siebel installation program creates a siebel.cfg file in the bin folder on the remote client. This file includes default values for each configuration parameter.

Siebel Remote reads the configuration parameters from the configuration file that the Windows shortcut specifies for the remote client or for the synchronizer, depending on whether the user starts synchronization while using the remote client or uses the stand-alone synchronizer. The Installer sets up the shortcut to use siebel.cfg as the configuration file, by default. You can modify this setting.

Siebel Remote reads the configuration information from the configuration file when it does a synchronization. For example, if you use Siebel Call Center, then it reads configuration information from the uagent.cfg file. The user can choose the File menu, Database, and then the Synchronize menu item to start a synchronization.

To modify the Siebel configuration file for Siebel Remote

  1. Locate, and then open the configuration file in a text editor.

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

  2. Locate the [Siebel] section, and then do the following:

    1. Set the ClientRootDir parameter.

      The ClientRootDir parameter is the name of the installation folder that resides on the remote client.

    2. Set the DockRepositoryName parameter.

      The DockRepositoryName parameter is the name of the Siebel runtime repository that you are currently using, such as Siebel Repository. This parameter must contain the same value as the Siebel runtime repository on the Siebel Server.

    3. If the user connects to a VPN and the connection is lost, then Siebel Remote might display the following error message:

      Page cannot be displayed.
      

      If you encounter this, and restarting the Mobile Web Client does not reconnect, then set EnableFQDN to False. Setting EnableFQDN to False might affect other functionality, such as the behavior of a pop-up blocker. For more information, see the Siebel Installation Guide.

  3. Locate the [LOCAL_SE] section, and then do the following work:

    1. Set the DockConnString parameter.

      The DockConnString parameter is the logical network address of the Siebel Server where Siebel Remote connects to synchronize. For more information, see Formatting the DockConnString Parameter and Using VPN When Synchronizing Through the Internet.

    2. Set the TableOwner parameter.

      The TableOwner parameter is the name of the account on the local database where the Siebel schema resides. The default value is SIEBEL.

    3. Set the DockTxnsPerCommit parameter.

      For more information, see Recommended Configurations for Setting the Number of Transactions That Siebel Remote Applies Before a Commit.

  4. Optional. Modify the configuration file to use a different data source.

    If your organization requires data and applications that are stored on separate devices, then you can use a data source that is different from the one that you specify in the [LOCAL_SE] section of the configuration file.

    Caution: Make sure you modify the description of the existing local data source in the configuration file. Do not add more local data sources to the configuration file because Siebel Remote does not support these additional local data sources.
  5. Save your modifications, and then close the configuration file.

  6. Implement your modifications across the Siebel Enterprise.

    You must apply any modification that you make to the Siebel runtime repository to the Siebel Servers that serve the modified application to the Web clients. For more information, see Upgrading a Regional Node.