Siebel Sales Handheld Guide for Windows-Powered Devices > Deployment > Server Installation >

Server Installation for Direct Server Sync


The server components that are required for Siebel Handheld are installed when you install the Siebel server. See Siebel Server Installation Guide for Microsoft Windows for details on installing and configuring Siebel server. The Siebel server installer copies the necessary DLLs to create an Object Manager for Direct Server Sync and creates and configures a Server Component and Component Group. The rest of this subsection describes which options you must select to correctly install the software, along with creating or configuring additional Object Managers.

Installing the DSS Components Using the Siebel Server Installer

Install the Siebel server, following the instructions in the Siebel server installation guide for the operating system you are using. When you reach the Setup Type screen in the Installer wizard, you will see three installation options:

To install the Direct Server Sync components with your Siebel Server installation

  1. Choose the Custom setting, and then click Next.
  2. NOTE:  At this screen, you may also choose a different directory for your Siebel server installation.

  3. Choose from the following components:
  4. Click Next.
  5. Continue with the installation in Siebel Server Installation Guide for Microsoft Windows.

The install wizard automatically installs and configures the DSS components. In addition, the installer creates a configuration file that includes the parameters necessary to properly run the DSS server components and the Business Component filters file.

Editing the DSS Object Manager Configuration File

You must edit the configuration (.cfg) file associated with the DSS server components that you installed and configured to reflect your company's environment.

To edit your configuration file

  1. In Windows Explorer, navigate to the directory where the Siebel server is installed and locate the configuration file associated with the DSS server component. By default, this directory is C:\Siebel Root\ siebsrvr\BIN\ENU.
  2. NOTE:  By default, the name of the DSS Object Manager configuration file is salesce.cfg, but you can change the name of this file.

  3. Create a backup copy of the configuration file and name it salesce.cfg.bak.
  4. This step allows you to recover the original version of the file if you encounter errors.

  5. Open the configuration file using Microsoft Notepad.
  6. Enter parameter values appropriate for your deployment.
  7. The following parameters in the .cfg file may need to be edited to reflect your environment. All other parameters in this section should not require change.

 
Parameter
Default Value
Description
[Siebel] section
ApplicationName
Siebel Sales for CE
The handheld application. This value must match the name of the application as it is specified in Siebel Tools.
ApplicationTitle
Siebel Sales
The name of the Siebel Handheld application as shown on the Title bar on the browser. This parameter is only used if the Siebel Tools application developed for the handheld is run on the Web client.
ApplicationSplashText
Siebel Sales
The Siebel Handheld application name as shown on the splash screen. This parameter is only used if the Siebel Tools application developed for the handheld is run on the Web client.
ComponentName
Siebel Sales Client
Required for Direct Server Sync, it is entered in the registry on the handheld device.
[PDA] section
AppDir
hhsync\salesce
The directory location for the user's synchronization files.
PDAQBEFile
salesceqbe.txt
The Business Components filtering file used by the synchronization process.
RemoteCfgName
 
Name of the Siebel Mobile Web Client configuration file. If the parameter is not specified in the .cfg file, the default is siebel.cfg. This parameter is used by Siebel Handheld Sync to invoke Siebel Remote. It applies only when synchronizing using the Integrated Sync option.

  1. Save your changes.
  2. Restart the component or server.

 Siebel Sales Handheld Guide for Windows-Powered Devices 
 Published: 18 July 2003