1. Remote and Replication Manager Administration Guide
  2. What's New in This Release

4Configuring the Siebel Server

Configuring Server Properties and Environment Variables

This topic describes how to configure server properties and environment variables. It includes the following information:

You can do these tasks in any order.

Configuring Virtual Memory for the Siebel Server

This task is a step in Process of Configuring the Siebel Server.

The size that you set on the Siebel Server for virtual memory for Windows, or that you set for the swap space for UNIX, affects performance. For best results, it is recommended that you set this size to 1.5 times the size of the physical memory (RAM) of the Siebel Server. You can use typical operating system configurations to accomplish this.

To configure virtual memory for a Siebel Server

  • For a Windows server, from the desktop, right-click the My Computer icon, and then choose Properties.

    1. In the System Properties dialog box, choose the Advanced tab, and then click Settings.

    2. In the Performance Options dialog box, click the Advanced tab, and then click Change in the Virtual memory section.

    3. In the Virtual Memory dialog box, choose Custom Size, and then enter a value that is twice the size of the physical memory.

    4. Click Set, and then click OK.

  • For a UNIX server, you can use the following typical command to set swap space size: swap

    For more information about the swap command, see the documentation for the server operating system.

Configuring Server Environment Variables for IBM DB2 for z/OS

If your Siebel Server runs on IBM DB2 for z/OS, then you must set the environment variable that this topic describes. For more information, see the information about configuring environment variables in Siebel System Administration Guide, Siebel Installation Guide for UNIX, and Implementing Siebel Business Applications on DB2 for z/OS.

To configure server environment variables for IBM DB2 for z/OS

  1. If you use a Windows server, then do the following:

    1. On the desktop of the Siebel Server, right-click My Computer.

    2. Choose Properties, and then click the Advanced tab.

    3. Click Environment Variables.

    4. In the System variables section, click New.

    5. In the New System Variable dialog box, add a new system variable using values from the following table.

    Variable Name Variable Value

    SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING

    t

  2. If you use a UNIX server, and a Bourne shell or a Korn shell, then enter the following commands at the shell prompt:

    SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING=t
export SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING

    As an alternative, you can enter the following command:

    export SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING=t

  3. If you use a UNIX server, and a C shell, then enter the following command at the shell prompt:

    setenv SIEBEL_REMOVE_COMPENSATION_EMPTY_STRING_MATCHING t

  4. Restart the Siebel Server.

Process of Configuring System Preferences for the Siebel Server

This task is a step in Process of Configuring the Siebel Server.

To configure system preferences for the Siebel Server, you do the following:

  1. Process of Completing the Remote System Preferences Form

  2. Configuring System Preferences for Transaction Logging

  3. Configuring System Preferences for Timestamps

  4. Configuring System Preferences for Resolving Conflicts

Extracting the Server Database After You Modify System Preferences

A number of system preferences affect the way Siebel Remote manages the modifications that it makes to the server database. You can use the Remote System Preferences view to set the system preferences for Siebel CRM during the initial implementation.

Caution: If you modify a system preference after you extract the server database, then you must reextract the server database for all remote clients. For more information, see Requirements for Extracting the Server Database.

You can examine the Dock Object Visibility Rules under the SystemPref Dock Object in Siebel Tools to identify the modifications that Siebel Remote routes to clients. For more information, see Transaction Router Server Component and Configuring Siebel Business Applications.

Setting Password and Lockout Preferences

This task is a step in Process of Completing the Remote System Preferences Form.

You set system preferences on the Remote System Preferences form. You begin by setting password and lockout preferences.

To set password and lockout preferences

  1. On the Siebel Server, navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences view.

  2. Optional. Enable the user password to expire:

    1. Make sure the Enable Mobile Password Expiration check box contains a check mark.

    2. In the Expiration Period field, specify the number of days that each user can continue to use the same password.

      The Expiration Period applies only if the Enable Mobile Password Expiration check box contains a check mark.

    3. In the Warning Period field, specify the number of days to display a warning to the user before the user password expires.

      The user receives a warning before the password expires. The value you enter in the Warning Period field determines the lead time between the warning and the expiration. If the user modifies a password, then the expiration period starts again. The warning period applies only if the Enable Mobile Password Expiration check box contains a check mark.

    To allow the user to use the password indefinitely, do not place a check mark in the Enable Mobile Password Expiration check box.

  3. Optional. Configure the Siebel Server to validate the password format:

    1. Make sure the Enable Mobile Password Syntax Check check box contains a check mark.

    2. In the Minimum Number of Characters field, specify the minimum number of characters that the password must contain for each user account that resides on the remote client.

      The Minimum Number of Characters field applies only if the Enable Mobile Password Syntax Check check box contains a check mark.

    3. In the Password Content field, specify the type of characters that the password must include. Use a value from the following table.

      Value Description

      Alphanumeric

      The password must contain at least one alphabetic character and one numeric character.

      Alphanumeric Special Character

      The password must contain at least one alphabetic character, one numeric character, and one valid special character. The Description column for the Special Characters value in this table lists these characters.

      None

      Siebel CRM does not require that this password include any character types.

      Special Characters

      The password must contain at least one special character. For more information, see Setting Password and Lockout Preferences.

      The Password Content field applies only if the Enable Mobile Password Syntax Check check box contains a check mark.

  4. Optional. Set a limit for login attempts.

    1. Make sure the Enable Mobile Web Client Lockout check box contains a check mark.

    2. In the Failed Login Attempts field, specify the number of consecutive unsuccessful user login attempts that Siebel CRM counts.

      If the count reaches the value you specify, then the remote client prevents the user from logging in for the number of days that you specify in the Lockout Period field. The Failed Login Attempts field applies only if the Enable Mobile Web Client Lockout check box contains a check mark.

    3. In the Lockout Period field, specify the number of days that the user cannot log in after the user exceeds the value that you specify in the Failed Login Attempts field.

      The Lockout Period field applies only if the Enable Mobile Web Client Lockout check box contains a check mark.

List of Special Characters

The following items are special characters relevant to the Password Content field:

  • * (asterisk)

  • @ (at sign)

  • ^ (caret)

  • : (colon)

  • , (comma)

  • - (dash)

  • $ (dollar sign)

  • = (equal sign)

  • ! (exclamation point)

  • > (greater than symbol)

  • ( (left parenthesis)

  • < (less than symbol)

  • # (number sign)

  • % (percent sign)

  • . (period)

  • + (plus sign)

  • ) (right parenthesis)

  • ? (question mark)

  • _ (underscore)

Setting Preferences for Visibility, Logging, Timestamps, and Conflict Resolution

This task is a step in Process of Completing the Remote System Preferences Form.

To set preferences for visibility, logging, timestamps, and conflict resolution

  1. In the Remote System Preferences form, place a check mark next to the Optimized Visibility Check check box.

    For more information, see Configuring System Preferences for Transaction Logging.

  2. Make sure the Enable Transaction Logging field is set correctly to enable transaction logging.

    To use Siebel Remote, you must enable transaction logging. For more information, see Configuring System Preferences for Transaction Logging.

  3. In the Docking Timestamp Source field, specify the source for the timestamp.

    For more information, see Configuring System Preferences for Timestamps.

  4. In the System Conflict Resolution field, specify how Siebel Remote resolves conflicting database updates. Use a value from the table in Dock Objects.

    Caution: For important caution information about setting system conflict resolution, see Requirements for Extracting the Server Database.

    For more information, see Update Conflict.

  5. In the Intersection Table Conflict Resolution field and in the Intersection Table Merge Rule field, specify how to handle a record that is involved in an insert conflict.

    For more information, see Configuring System Preferences for Resolving Conflicts.

How Optimized Visibility Can Improve Performance

If the Optimized Visibility Check check box contains a check mark, then the Transaction Router server component uses a predefined algorithm to examine visibility. This algorithm uses information that an individual transaction carries to reduce the number of visibility rules that Siebel Remote examines. The algorithm reduces the number of database queries that the Transaction Router requires which improves performance. It is recommended that you use this algorithm in most situations.

Setting Preferences for Update Notifications, Visibility Rules, and Routing Rules

This task is a step in Process of Completing the Remote System Preferences Form.

To set preferences for update notifications, visibility rules, and routing rules

  1. In the Merger Friendly Notification field, specify how Siebel Remote writes information about database updates to the Siebel Remote Status view on the remote client. Use a value from the following table.

    Value Description

    Conflicts

    Siebel Remote writes information about database updates that caused conflicts.

    FALSE

    Siebel Remote does not write information about database updates.

    TRUE

    Siebel Remote writes information about database updates.

  2. In the Merger Transactions per Commit field, specify how many database transactions the Transaction Merger server component processes before it sends a database commit:

    • You can set a low value, such as 1, to reduce how often the user encounters a locked database row, and to reduce the risk of deadlock.

    • You can set a high value, such as 10, to minimize processing overhead.

    For default values and recommended settings for various databases, see Values for System Preferences.

  3. Specify how to handle visibility and routing rules:

    1. In the Visibility Rules per Statement field, specify the number of visibility or routing rules that the Transaction Router server component for each SQL statement examines.

    2. In the Visibility Rules per Statement 1 field, specify the number of visibility or routing rules according to the following items:

      • Examine each SQL statement that the Database Extract server component processes.

      • Examine only the first SQL statement that includes header information.

      • In the Visibility Rules per Statement N field, specify the number of visibility or routing rules that Siebel Remote examines for each SQL statement that the Database Extract server component processes for other SQL statements.

    Do not modify these values without assistance. For help with visibility and routing rules, see Getting Help from Oracle.

    For more information, see Controlling the Data That Siebel Remote Routes to Clients and Values for System Preferences.

Configuring System Preferences for Transaction Logging

This task is a step in Process of Configuring System Preferences for the Siebel Server. The Enable Transaction Logging field allows you to enable or disable transaction logging.

Caution: If Siebel Remote does not rebuild the dobjinst.dbf visibility database file when Transaction Logging is enabled, then remote clients might experience data discrepancy or visibility problems.

For more information, see Using Transaction Logging with EIM or Assignment Manager.

To configure system preferences for transaction logging

  1. On the Siebel Server, navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences view.

  2. In the Remote System Preferences form, make sure the Enable Transaction Logging check box contains a check mark.

  3. Restart the Transaction Processor.

  4. For each active remote client, reextract and reinitialize the local database for that client to make sure that it contains data this is current.

    An active remote client is any client that contains no set End Date. This step is necessary because Siebel Remote does not route any transaction that is not logged to the remote client that otherwise receives the transaction. This situation is true even if you choose Enable Transaction Logging again.

Disabling Transaction Logging

You can disable transaction logging.

Caution: Disabling Transaction Logging prevents Siebel Remote from working.
To disable transaction logging

  1. Navigate to the Administration - Siebel Remote screen, and then the Remote System Preferences view.

  2. In the Remote System Preferences form, make sure the Enable Transaction Logging check box does not contain a check mark.

  3. Restart the Siebel Server.

Transaction Logging and Database Extract

To log modifications to the local database, you must enable transaction logging when you do a database extract.

Configuring System Preferences for Timestamps

This task is a step in Process of Configuring System Preferences for the Siebel Server.

A row in a table on the server database includes the date that Siebel CRM last modified the row. If a remote client updates a row, then Siebel Remote can stamp the date in one of the following ways:

  • Client transaction time. The time when Siebel Remote modified the remote client. Using the client timestamp promotes consistency across local and server databases, but it can be misleading if the clock for a remote client is not set correctly, or if this client resides in a different time zone.

  • Server database merge time. The time when Siebel Remote modified the Siebel Server. Using the server timestamp makes sure that the timestamp is accurate, but it also causes the timestamp for the same row on the remote client to be different from the timestamp that resides on the server.

To configure system preferences for timestamps

  • Set the Docking Timestamp Source parameter to client transaction time or to server database merge time.

Setting the Docking Timestamp Source parameter does not affect conflict resolution or the priorities for Siebel Remote. Siebel Remote stores updated timestamps only for informational purposes.

Configuring System Preferences for Resolving Conflicts

This task is a step in Process of Configuring System Preferences for the Siebel Server. This topic describes system preferences that you can configure to resolve conflicts.

Setting the Intersection Table Conflict Resolution Field

If a record that is involved in an insert conflict is associated with extension records and child records, then Siebel Remote uses the same conflict resolution process to resolve these records that it uses to resolve the parent record. The user can navigate to the User Preferences screen, and then the Remote Status view to examine the results of conflict resolution operations that reside in the local database.

Caution: For important caution information about setting the Intersection Table Conflict Resolution field, see Requirements for Extracting the Server Database.
To set the Intersection Table Conflict Resolution field

  • Set the Intersection Table Conflict Resolution field using values from the following table.

Value Description

First In

Keeps the existing record and the associated extension records and child records. Deletes all values from the record where Siebel Remote attempted an insertion. It also deletes the extension records and child records that are associated with the record where Siebel Remote attempted an insertion.

Last In

Replaces the existing record with the record that Siebel Remote is inserting. Replaces the associated extension records and child records of the existing record with the associated extension records and child records of the record Siebel Remote is inserting.

Merge

(Default value) Combines values from these records and their extension records and child records. The exact behavior that Siebel Remote uses depends on the fields that it populates with non-NULL values and on the value of the Intersection Table Merge Rule system preference. For more information, see Setting the Intersection Table Merge Rule Field.

Intersection Table Conflict Resolution

You can determine how Siebel CRM handles insert conflicts on intersection tables in enterprise, regional, and local databases. For more information, see About the Siebel Enterprise and the Siebel Enterprise Server.

Setting the Intersection Table Merge Rule Field

The Intersection Table Merge Rule field depends on the following value that you set in the Intersection Table Conflict Resolution field:

  • Merge. The Intersection Table Merge Rule field determines the field values that survive when Siebel Remote merges two records to resolve an insert conflict on an intersection table.

  • A value other than Merge. Siebel Remote ignores the Intersection Table Merge Rule field.

Caution: For important caution information about setting the Intersection Table Merge Rule field, see Requirements for Extracting the Server Database.

For more information about resolving insert conflicts, see Setting the Intersection Table Conflict Resolution Field.

To set the Intersection Table Merge Rule field

  1. Set the Intersection Table Conflict Resolution field to Merge.

  2. Set the Intersection Table Merge Rule field to one of the following values:

    • First In. (Default value) Siebel Remote applies the following rules to fields in parent records, child records, and associated extension records:

      • Siebel Remote replaces existing NULL values with new, non-NULL values

      • Siebel Remote preserves existing, non-NULL values

    • Last In. Siebel Remote applies the following rules to fields in parent records, child records, and associated extension records:

      • Siebel Remote replaces existing NULL values and non-NULL values with new, non-NULL values.

      • If the corresponding new value is NULL, then Siebel Remote preserves existing, non-NULL values.

Configuring Server Components for Synchronization and Transactions

This task is a step in Process of Configuring the Siebel Server.

To configure server components for synchronization and transactions

  1. Make sure the following field of the Components list is in an Online state for each of the server components that Siebel Remote requires:

    State (Icon)

    For a basic implementation, all the components that are listed in the table in Server Components That Siebel Remote Uses must be online, except for Parallel Database Extract and Replication Agent. For more information about using the Components list, see Using the Administrative Interface to Administer Server Components.

  2. Configure start-up parameters for the Synchronization Manager server component.

    1. Configure parameters for encryption.

      For more information, see Process of Configuring Encryption and Authentication for the Remote Client.

    2. Configure parameters to manage the cache.

      For more information, see Using Synchronization Manager to Manage the Cache.

  3. Configure start-up parameters for the Transaction Processor server component.

    For more information, see Optimizing the Transaction Processor Server Component.

  4. Configure start-up parameters for the Transaction Router server component.

    For more information, see Optimizing the Transaction Router Server Component.

  5. Configure start-up parameters for the Transaction Merger server component.

    For more information, see Optimizing the Transaction Merger Server Component.

For more information, see Server Component Parameters.

Running the Generate New Database Server Component

This task is a step in Process of Configuring the Siebel Server.

This topic includes the following information:

A database template is a database that contains no user data but does contain the structure that Siebel Remote requires for use with a Siebel application. You run the Generate New Database (alias GenNewDb) server component to create a new database template. If you modify the server database schema, then you must create a new database template. The following are examples of modifying the server database schema:

  • You install the Siebel database

  • You upgrade to a new version of a Siebel application

  • Use Siebel Tools to extend the server database schema, except if you use Oracle’s Siebel Anywhere to deliver a database schema upgrade kit. An extension can include extension tables, extension columns, or extension indexes. For more information, see Using a Character Datatype with an Extension Column.

For more information, see Controlling the Data That Siebel Remote Routes to Clients.

Siebel Remote No Longer Supports Dbinit

Some earlier versions of Siebel Remote supported the creation of a new empty database file through the Dbinit utility that Siebel Remote used with a local database. Siebel Remote no longer supports this utility. You must still create a new database template before you can extract a database. Siebel Remote uses these files to create a new database template. They are not a substitute for a database template.

Creating a New Database for Siebel Remote

This topic describes how to run the Generate New Database server component (alias GenNewDb) to create a new local database template.

Caution: If the Siebel Gateway uses LDAP authentication, then, when you run a job for Generate New Database, you must explicitly specify valid database credentials to connect to the Siebel database. Otherwise, the component task fails, with this message: Unable to connect to Database. For example, you might run the job by entering a command like this on the srvrmgr command line: start task for comp gennewdb with username=user_name, password=pwd

To create a new database for Siebel Remote

  1. Log in to the Siebel Server with administrator privileges.

    For more information, see Logging in to the Siebel Database as an Administrator.

  2. Navigate to the Administration - Server Management screen, and then the Jobs view.

  3. In the Jobs list, click New.

  4. In the Component/Job field, choose Generate New Database.

  5. In the Requested Server field, enter the name of the Siebel Server where the job for Generate New Database runs.

    The Execution Server field displays the name of the Siebel Server that runs the job after the job finishes.

  6. In the Job Parameters list, modify the values for parameters, as needed. For more information, see Parameters of the Generate New Database Server Component.

  7. In the Jobs list, with the Generate New Database job still chosen, click Submit Job.

    Siebel CRM creates a new database file. This step typically requires a few minutes to complete.

  8. Optional. Monitor the progress of the job:

    1. Navigate to the Administration - Server Management screen, and then the Components view.

    2. To view status information, choose the Generate New Database component, and then click the Tasks view tab.

  9. If necessary, distribute database templates to Siebel Servers:

    1. To set the environment variables, open a DOS window and then run the siebenv.bat file.

    2. To create the destination folders and the server database template files, run the distmpl.bat file.

      For more information, see Distributing Database Templates to Siebel Servers.

Distributing Database Templates to Siebel Servers

If your deployment includes multiple Siebel Servers, then you must distribute the server database templates. You can run the distmpl.bat file to distribute the templates to each Siebel Server. This file creates the proper folder on each Siebel Server and it copies the server database template to the folder. As an alternative, you can run the Generate New Database server component on each Siebel Server to create the database template file.

For more information, see Creating a New Database for Siebel Remote.

Examples of Running the Distmpl.bat File

This topic includes two examples of running the distmpl.bat file.

In this example, you specify the following computer name:

distmpl \\appsrvr1\siebapp

where:

  • appsrvr1 is the computer name of the Siebel Server

  • siebapp is a folder that resides on the Siebel Server

In this example, you specify the following drive:

distmpl c:\siebapp

where:

  • c: is a drive that resides on the Siebel Server

  • siebapp is a folder that resides on the Siebel Server

Using a Character Datatype with an Extension Column

If you create a new extension column in the Siebel schema, and if you define the datatype as Character (CHAR), then Transaction Merger might not work properly if the length is greater than 1. If the length is greater than 1, then you must use VARCHAR as the datatype.

Using Assignment Manager to Reduce Traffic

You can configure the Assignment Manager server component to determine the transactions that Siebel Remote sends to a remote client. During typical operations, Assignment Manager frequently updates the timestamps for large numbers of records even if there are no other modifications to many of those records. You can use the LogTxnChgOnly parameter to avoid sending large numbers of transactions to a remote client when the only modification is to the timestamp. For more information, see Siebel Assignment Manager Administration Guide.

To use Assignment Manager to reduce traffic

  • Set the LogTxnChgOnly parameter of the Assignment Manager server component to TRUE at the component level.

If you set the LogTxnChgOnly parameter to TRUE, then Assignment Manager logs transactions only if you modified an assignment, such as modifying the membership of a team or modifying the primary for a team. This parameter affects only the Assignment Manager transactions. Siebel Remote sends any record modifications made in an other way to remote clients.

Using Time Filters to Prevent Sending Old Data

You can use the Time Filters feature to prevent Siebel Remote from sending some kinds of older data to remote clients during database extraction or synchronization. Reducing the amount of data that Siebel Remote sends can reduce the amount of time that it requires to extract and synchronize with the server database. Time filtering can also improve response time for the remote client.

Siebel Remote deploys time filtering for each dock object. You can choose a cutoff date for a dock object, such as Activity. If the user modifies data before the cutoff date occurs, then Siebel Remote does not include this data in the extraction or synchronization.

The cutoff date for each dock object is a fixed date that Siebel Remote does not dynamically adjust. If you modify the cutoff date, then you must reextract the remote client. If you do not reextract the remote client after you modify the cutoff date, then this client retains unnecessary older data in the local database. Storage of this old data can degrade performance.

For more information, see Transaction Router Server Component.

Starting Time Filtering for Dock Objects

This topic describes how to start time filtering for a dock object.

Caution: For important caution information setting time filtering, see Requirements for Extracting the Server Database.
To start time filtering for dock objects

  1. Log in to a remote client that is connected to the Siebel Server.

  2. Navigate to the Administration - Siebel Remote screen, and then the Time Filters view.

  3. In the Time Filters list, click New to display an empty record.

  4. In the Dock Object field, choose the dock object where you must configure time filtering.

    If the remote client does not display the dock object you require, then you can define it. For more information, see Defining a New Dock Object for Time Filtering.

  5. Specify a date and time in the Cutoff Time field.

    Specifying this date and time limits the data that Siebel Remote extracts and synchronizes for the dock object that you chose in Step 4.

  6. To save the time filter, step off the record.

  7. Restart the Transaction Router server component.

    You can create a time filter while the Transaction Router is running. The time filter you create affects database extracts that Siebel Remote starts after it saves the time filter. To affect synchronizations, you must restart the Transaction Router server component after you save the time filter.

Stopping Time Filtering for Dock Objects

If you use time filtering but determine that your business requires Siebel Remote to synchronize older data, then you can stop time filtering for a dock object.

To stop time filtering for dock objects

  1. Log in to the Siebel Server with administrator privileges.

    For more information, see Logging in to the Siebel Database as an Administrator.

  2. Navigate to the Administration - Siebel Remote screen, and then the Time Filters view.

  3. In the Time Filters list, choose the record that lists the dock object where Siebel Remote must synchronize older data.

  4. Click Delete.

    Repeat Step 3 and Step 4 for other dock objects that no longer require time filtering.

  5. Restart the Transaction Router server component.

    You can delete a time filter while the Transaction Router is running. The time filter you delete affects database extracts that Siebel Remote starts after it deletes the time filter. To affect synchronizations, you must restart the Transaction Router server component after you delete the time filter. For more information, see Configuring Server Components for Synchronization and Transactions.

  6. Reextract local databases for remote clients that require access to the older data.

    For more information, see Extracting and Initializing a Remote Database.

Defining a New Dock Object for Time Filtering

This topic describes how to make time filtering available for a dock object that is not predefined for time filtering. You can customize the dock objects that you specify with a time filter. Time filtering is predefined on the following dock objects:

  • Activity

  • Expense

  • Expense Report

  • Invoice

  • Opportunity

  • Price List

  • Project

  • Project Item

  • Quote

  • Service Request

You can define more dock objects for time filtering. For many Siebel implementations most of the benefits that time filtering provides comes from using predefined dock objects.

Note: Do not use time filtering for dock objects that are based on the Party data object, which has different characteristics than other data objects. Using time filtering does not produce the desired result for such dock objects.
To define a new dock object for time filtering

  1. If necessary, expose the Dock Object object type.

    For more information, see the following.

  2. In the Object Explorer, choose Dock Object.

  3. In the Dock Objects list, examine the list of names in the Name property to locate the dock object where you must use time filtering, and then make a note of the exact spelling of the name.

  4. Log in to the Siebel Server with administrator privileges.

    For more information, see Logging in to the Siebel Database as an Administrator.

  5. Navigate to the Administration - Data screen, and then the List of Values view.

    This example adds a new value to a List of Values (LOV). For more information, see Siebel Applications Administration Guide.

  6. In the Type field of the List of Values list, enter the following query:

    *DOCK_OBJ_TIME_FILTER*

  7. Choose a record, click Menu, and then chose the Copy Record menu item.

  8. In the Language-Independent Code field of the new record, enter the exact name of the dock object that you identified in Step 3.

  9. In the Display Value field of the new record, enter the name to display in the Siebel application when you configure time filtering for this dock object.

  10. Examine the copied values in the other fields of the new record, make required modifications, and then save the record.

  11. Start time filtering for the dock object.

    For more information, see Starting Time Filtering for Dock Objects.

Preparing Siebel Tools to Configure Siebel Remote

This topic describes how to prepare Siebel Tools to configure Siebel Remote.

To prepare Siebel Tools to configure Siebel Remote

  1. Log in to Siebel Tools.

  2. Choose the View menu, and then the Options menu item.

  3. Click the Object Explorer tab.

  4. In the Object Explorer Hierarchy window, make sure there is a check mark with a white background next to the Dock Object check box.

  5. Click OK.

Disabling Local Access to Views

You can disable local access to some views. If you allow the user to use the All views filter when connected to a local database, and if the table that a business object references possess limited visibility, then the remote client attempts to fix foreign key relationships when displaying data, and Siebel Remote sends the modified data to the server database and other remote clients. This behavior corrupts these databases. You must not allow the user to use the All views filter in this situation.

Consider an example that illustrates this behavior. If the remote client cannot locate an account for an opportunity in the local database, then the All Opportunity List view resets the value of the primary account of the opportunity to NULL. Siebel Remote copies the opportunity to the local database because an activity that the user owns references the opportunity. Siebel Remote copies the opportunity so that the remote client can display the opportunity name and the activity in the Activity List view. If the user is not a member of the sales team for the opportunity, then Siebel Remote does not copy the primary account of the opportunity.

If the user accesses the All Opportunity List view to display the opportunity, and if the remote client does not find the primary account of the opportunity in the local database, then Siebel Remote resets the primary account of the opportunity to NULL, and then copies this modification to other databases. In this situation, limited visibility is related to the following types of visibility that are available with Siebel Remote:

  • Enterprise

  • Limited

  • Private

To disable local access to views

  1. Log in to an administrative client.

  2. Navigate to the Administration - Application screen, and then the Views view.

  3. In the Views list, choose a view, such as the All Opportunity List view.

  4. In the Responsibilities list, make sure the Local Access check box does not contain a check mark.

  5. Repeat Step 2 through Step 4 for each view that Siebel CRM assigns to the user responsibilities.

Optimizing the Transaction Processor Server Component

Only one Transaction Processor can run for each database installation in a Siebel Enterprise that includes more than one Siebel Server. At startup, the Transaction Processor verifies that another Transaction Processor is not running on the same Siebel Server. This configuration makes sure that the Transaction Processor is not kept from running because it cannot find a valid node during synchronization. For example, assume two Siebel Servers run in the same Siebel Enterprise and reference the same database. Siebel Remote extracts a remote client for one of the Siebel Servers during synchronization, and then correctly applies all the updates from the local database to the server database. It does not apply any server updates to the local database and the Siebel application creates an error similar to the following: 

Transaction Processor determined that this node does not have any mobile clients or 
regional servers that need to receive transactions. Please do a DB extract on one 
of these nodes before restarting this component.

In this situation, Siebel Remote does not apply any server updates to the local database during synchronization. To correct this problem, you can reextract and reinitialize the remote client on the Siebel Server where it failed. To avoid the problem entirely, you must use only one transaction process for each database installation.

For more information, see the following topics:

Optimizing the Transaction Router Server Component

The Transaction Router server component takes transactions from the docking\txnproc folder and constructs DX files. It then sends these DX files to the outbox that corresponds to the user.

Caution: Do not run a Transaction Router and Ddlsync at the same time. It can cause Transaction Router to shut down.

For more information, see Transaction Router Server Component, and Parameters of the Transaction Router Server Component.

Running Multiple Transaction Router Processes

You must run at least one Transaction Router on each Siebel Server. To improve performance, it is recommended that you start multiple Transaction Router processes on the same Siebel Server. This configuration increases the throughput of transactions to the user outbox:

  • Each Transaction Router process can simultaneously route transactions from the server database to a different remote client. For example, if you start four Transaction Router processes, then these four processes can simultaneously route transactions to four different remote clients.

  • Using multiple Transaction Router processes reduces the total time that Siebel Remote requires to route transactions to remote clients.

You can start as many concurrent Transaction Router processes as the server database and the Siebel Server can support:

  • Monitor the server database and Siebel Server to make sure the concurrent Transaction Router processes do not overload the Siebel application.

  • Start with two Transaction Router processes, and then increase the number of processes.

  • You typically run multiple Transaction Router processes for each server.

For more information, see Optimizing Server Components.

Routing Transactions from the Siebel Server

Only one Transaction Router process can route transactions from the Siebel Server to a remote client at any one time:

  • The Transaction Router locks the following folder on the remote client to prevent other Transaction Router processes from routing transactions to the same remote client:

    outbox

  • If another Transaction Router process is already processing a remote client, then other Transaction Router processes skip this remote client.

  • The Transaction Router finishes routing transactions to the remote client, and then it releases the lock and searches for another unlocked remote client to process.

Modifying Routing Rules

A Siebel application includes predefined user routing rules. These routing rules include a combination of implicit security rules, according to responsibility, and assignment rules that determines the information the user can access. For help with configuring routing rules for optimal performance with a large number of objects, such as assets, accounts, or activities, see Getting Help from Oracle.

Setting the Threshold That Siebel Remote Uses to Route Transactions

You can use the Operation Routing Rate Threshold parameter of the Transaction Router to set the number of transactions that Siebel Remote routes in one second. You can adjust this threshold to avoid receiving the following system alert:

Router is experiencing lower performance throughput than expected

This alert is an informational alert. It does not indicate that an error occurred.

To set the threshold that Siebel Remote uses to route transactions

  1. Locate the record for the Transaction Router server component.

    For more information, see Disabling Transaction Logging.

  2. In the bottom applet, click the Parameters tab, and then query the Parameter field for the following parameter:

    Operation Routing Rate Threshold

  3. In the Value on Restart field, enter a numeric value.

    The default value is 2.8, representing the number of transactions that Siebel Remote routes in one second. You can decrease the value in this field to prevent Siebel Remote from logging excessive messages in the Transaction Router log file. You can also disable notification for the Transaction Router server component.

Optimizing the Transaction Merger Server Component

The Transaction Merger server component gets DX files from the inbox in the docking folder that resides on the Siebel Server, and then applies these files to this server. It also resolves conflicts. You must run at least one Transaction Merger process on each Siebel Server. You can run multiple Transaction Merger processes on the same Siebel Server to improve performance. For more information, see the following topics:

Optimizing Server Components

The optimal number of Siebel Servers and the number of tasks for the Transaction Processor, Transaction Router, and Transaction Merger depends on the number of users, the number of transactions that Siebel CRM creates, and other aspects of Siebel CRM. For more information, see the following topics: