Configuring Siebel Server for Siebel Mobile Disconnected Application Synchronization

This task is a step in "Roadmap for Setting Up Siebel Mobile Disconnected Applications". The Siebel Server installer copies the necessary DLLs to create a Siebel Application Object Manager for enabling server synchronization for Siebel Mobile disconnected applications. It also creates and configures a server component and component group. This topic describes which options you must select to install the software correctly, along with creating or configuring additional Siebel Application Object Managers.

This topic includes the following information:

• "Configuring Logging Levels for Siebel Mobile Disconnected Application Synchronization"

• "Optimizing Siebel Server Process Management for Siebel Mobile Disconnected Application Synchronization"

• "Roadmap for Configuring Incremental Synchronization for Siebel Mobile Disconnected Applications"

Configuring Logging Levels for Siebel Mobile Disconnected Application Synchronization

To set the logging level, you must perform the following tasks:

• "Configuring Siebel Server Logging Using the Server Manager"

• "Configuring Siebel Server Logging Using the Server Configuration Screen"

You set the logging level to a value between 1 and 5 as shown in Table 6-2.

Table 6-2 Logging Levels for Siebel Mobile Disconnected Application Synchronization

Logging Level	Results
1	Error listing
2	Warning listing
3	Information listing, including SQL tracing
4	Information listing
5	Debug information

Configuring Siebel Server Logging Using the Server Manager

The following procedure shows you how to configure Siebel Server logging levels using the Server Manager.

To configure Siebel Server logging levels 

1. Log in to the command Server Manager from a prompt.

2. Run the following command:

   change evtloglvl HandheldSyncLog=[LogLevel] for comp [OMName],
   where [LogLevel] = an integer between 1 - 5   /*(5 enables all logging)*/
   and [OMName] = the OM name   /*(for example,<ApplicationName>ePharmaMObjMgr_enu)*/
   

Configuring Siebel Server Logging Using the Server Configuration Screen

The following procedure shows you how to configure Siebel Server logging levels using the Server Configuration screen.

To configure Siebel Server logging using the Server Configuration screen 

1. Navigate to Administration - Server Configuration screen, then the Servers view.

2. Select the appropriate Siebel Server in the top applet.

3. In the Components applet, query for the appropriate component.

   For example: Handheld Sales CE (ENU)).

4. Select the Events tab and then do the following:

   1. Query for the event type, Handheld Sync Logging.

   2. Set the value to a number between 1-5, and then save the change.

   See Table 6-2 for the logging-level results.

Optimizing Siebel Server Process Management for Siebel Mobile Disconnected Application Synchronization

Several parameters help to optimize Siebel Server processing for Siebel Mobile disconnected application synchronization.

To set parameters to optimize Siebel Server process management 

1. Log in to the Siebel application as a user with administrator privileges.

2. Navigate to the Administration - Server Configuration screen, then the Servers view.

3. Select the appropriate Siebel Server in the top applet.

4. In the Components applet, query for the appropriate component.

   For example: ePharmaMObjMgr_enu.

5. Select the Parameters tab and then update the parameters as described in the following table.

   Parameter	Description
   Max Tasks	Determines the maximum number of threads that can run concurrently for a given component. Set the value of this parameter to a number equal to that of the expected peak number of concurrent synchronizations for each Siebel Server.
   Min MT Servers	Determines how many multithreaded server processes are started by default for the Siebel Application Object Manager.
   Max MT Servers	Defines the maximum number of processes supported by the instance of Siebel Application Object Manager. The value for this parameter must be the same as the Min MT Servers parameter. Set it so that the threads for each process (Max Tasks and Max MT Servers) are optimized.