Contents

• Title and Copyright Information
• Preface

1 What’s New in This Release

• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 21.10 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 21.5 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 21.3 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 20.8 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 20.5 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 20.1 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 19.6 Update
• What’s New in Siebel Remote and Replication Manager Administration Guide, Siebel CRM 19.1 Update

2 About Siebel Remote

• About Siebel Remote
• Overview of Siebel Remote
  • Siebel Bookshelf
• Siebel Mobile Products That Siebel CRM Supports
  • Mobile Product Components and Client Devices That Siebel Remote Supports
  • Mobile Products That Siebel CRM Supports
  • Tablet Personal Computers That Siebel Remote Supports
• About Using This Book
  • How This Book Indicates Computer Code and Variables
  • How This Book Describes Objects
    • About Objects and Metadata
    • How This Book Describes Relationships Between Objects
• Getting Help from Oracle

3 Architecture of Siebel Remote

• Architecture of Siebel Remote
• Overview of the Siebel Remote Architecture
  • How Siebel Remote Flows Data Through the Architecture
• How Siebel Remote Uses Siebel Servers
  • About the Siebel Enterprise and the Siebel Enterprise Server
  • Server Folders That Siebel Remote Uses for Remote Clients
  • Server Components That Siebel Remote Uses
    • Generate New Database Server Component
    • Database Extract Server Component
    • Synchronization Manager Server Component
    • Transaction Processor Server Component
    • Transaction Router Server Component
    • Transaction Merger Server Component
    • How Siebel Remote Makes Sure Server Components Can Run Concurrently
    • About Redundant Disks on the Siebel Server
• How Siebel Remote Uses Mobile Web Clients
  • How Siebel Remote Handles Files on Remote Clients
  • Requirements for Remote Clients
  • Configuration Options That You Can Specify for Remote Clients
  • Synchronization Options That Users Can Choose
  • How Siebel Remote Uses TrickleSync to Manage Synchronization Frequency
  • Visibility Modifications That Affect Access to Records
  • Remote Client Usage in a Development Environment
• How Siebel Remote Creates Local Databases
  • How Siebel Remote Extracts Local Databases
  • How Siebel Remote Initializes Local Databases
• How Siebel Remote Synchronizes Local Databases
  • Overview of How Siebel Remote Synchronizes Local Databases
    • How Siebel Remote Minimizes Connect Time
  • How Siebel Remote Synchronizes Data That Users Modify
    • Scenario for Synchronizing Modified Data with Connected Users
    • Scenario for Synchronizing Modified Data with Disconnected Users
  • How Siebel Remote Resolves Conflicts in Data It Synchronizes
    • Update Conflict
    • Insert Conflict
    • Delete Conflict
    • Merge Conflict
  • How Siebel Remote Synchronizes File Attachments
• How Siebel Remote Manages the Amount of Data It Synchronizes
  • How Siebel Remote Filters the Data It Synchronizes
    • Dock Objects
    • Routing Rules
    • Routing Models
    • Selective Retrieval Routing Model
• How Siebel Remote Validates and Authenticates Information
  • How Siebel Remote Validates Synchronization
    • Validating the Remote Client Name
    • Validating the Siebel Server
    • Validating the User Credentials
  • How Siebel Remote Uses Security Adapter Authentication
    • Guidelines for Using a Security Adapter
  • How Siebel Remote Authenticates Passwords
    • How Siebel Remote Sets the Local Database Password
    • Features You Can Use to Manage Remote Passwords
  • How Siebel Remote Encrypts Fields
• Other Considerations for Design and Development
  • Modifying the S_DOCK_TXN_LOG Table
  • Modifying Siebel Tables Directly Through SQL
  • Using Oracle Real Application Clusters with Siebel Remote
• Roadmap for Implementing Siebel Remote

4 Configuring the Siebel Server

• Configuring the Siebel Server
• Process of Configuring the Siebel Server
• Configuring Server Properties and Environment Variables
  • Configuring Virtual Memory for the Siebel Server
  • Configuring Server Environment Variables for IBM DB2 for z/OS
• Process of Configuring System Preferences for the Siebel Server
  • Extracting the Server Database After You Modify System Preferences
  • Process of Completing the Remote System Preferences Form
    • Setting Password and Lockout Preferences
    • Setting Preferences for Visibility, Logging, Timestamps, and Conflict Resolution
    • Setting Preferences for Update Notifications, Visibility Rules, and Routing Rules
  • Configuring System Preferences for Transaction Logging
    • Disabling Transaction Logging
    • Transaction Logging and Database Extract
  • Configuring System Preferences for Timestamps
  • Configuring System Preferences for Resolving Conflicts
    • Setting the Intersection Table Conflict Resolution Field
    • Setting the Intersection Table Merge Rule Field
• Configuring Server Components for Synchronization and Transactions
• Running the Generate New Database Server Component
  • Siebel Remote No Longer Supports Dbinit
  • Creating a New Database for Siebel Remote
  • Distributing Database Templates to Siebel Servers
    • Examples of Running the Distmpl.bat File
  • Using a Character Datatype with an Extension Column
• Options for Configuring the Siebel Server
  • Using Assignment Manager to Reduce Traffic
  • Using Time Filters to Prevent Sending Old Data
    • Starting Time Filtering for Dock Objects
    • Stopping Time Filtering for Dock Objects
    • Defining a New Dock Object for Time Filtering
  • Disabling Local Access to Views
  • Optimizing the Transaction Processor Server Component
  • Optimizing the Transaction Router Server Component
    • Running Multiple Transaction Router Processes
    • Routing Transactions from the Siebel Server
    • Modifying Routing Rules
    • Setting the Threshold That Siebel Remote Uses to Route Transactions
  • Optimizing the Transaction Merger Server Component
  • Optimizing Server Components

5 Configuring the Remote Client

• Configuring the Remote Client
• Process of Configuring the Remote Client
  • Configuring the Siebel Remote Hardware, Software, and Network
  • Modifying the Siebel Configuration File for Siebel Remote
    • Recommended Configurations for Setting the Number of Transactions That Siebel Remote Applies Before a Commit
    • Verifying Database Connectivity on UNIX
    • Formatting the DockConnString Parameter
    • Using VPN When Synchronizing Through the Internet
• Creating a Remote Client
  • Using an Administrative View to Create a Remote Client
    • Views That Siebel Remote Users Require
    • How Siebel Remote Populates the App Server Name Field
    • Format That Siebel Remote Uses for the Remote Client Name, Database Name, Login ID, and Windows Password
    • User Language Preferences
  • Using EIM to Create Multiple Siebel Remote Clients
    • Using Transaction Logging with EIM or Assignment Manager
    • Using Set-Based Logging for EIM
    • Avoiding Transaction Processor Failures That Are Caused by Moving the File System
• Process of Configuring Encryption and Authentication for the Remote Client
  • Configuring TLS Encryption for Siebel Remote
  • Configuring Encryption for the Local Database Password
    • Configuration File Parameters That Siebel Remote Uses to Encrypt the Local Database Password
  • Creating Accounts and Passwords
    • How the Change Password Functionality Affects Authentication
    • Summary of Accounts, User IDs, and Passwords That Siebel Remote Uses
  • Setting the Local Database Password
• Controlling the Data That Siebel Remote Routes to Clients
  • Using Selective Retrieval to Route Data
    • Enabling Records for Selective Retrieval While Logged in as a User
    • Enabling Records for Selective Retrieval While Logged In as an Administrator
  • Using Responsibilities to Route Data
  • Modifying a Routing Model
• Limiting the Views That a Remote Client Displays
  • Limiting Access to Views by Modifying Responsibilities
  • Limiting Access to Views by Disabling Local Access in Routing Model Responsibilities
  • Limiting Access to Views for All Responsibilities
  • Limiting Access to the Global Accounts View

6 Extracting and Initializing a Remote Server

• Extracting and Initializing a Remote Database
• Process of Extracting the Server Database
  • Verifying the Reporting Hierarchy and Employee Status
    • How Positions, Organizations, and Responsibilities Affect Access
    • Keeping Organization Information Current on the Remote Client
    • Updating a Responsibility
  • Extracting the Server Database
    • Requirements for Extracting the Server Database
    • Rerunning a Database Extract to Avoid a Concurrency Error
    • Monitoring Performance of a Server Database Extract
    • How Siebel CRM Manages Modifications in the S_DOCK_SESSION Table
• Options for Extracting the Server Database
  • Extracting a Database for Multiple Users
  • Extracting a Database for Hundreds of Users
  • Running Multiple Instances of Database Extract
  • Using a Transaction Log to Optimize Performance
  • Setting Encryption on the Local Database Password
  • Extracting a Database to a CD-ROM or Other Portable Media
  • Truncating the dobjinst.dbf Database Tables
  • Saving Transactions That Siebel Remote Does Not Include in an Extract
• Initializing the Local Database
  • Initializing the Local Database by Using the GUI
  • Initializing the Local Database from the Command Line
  • Initializing the Local Database During Login
  • Options for Initializing the Local Database
    • Initializing the Local Database as a Nonadministrative User When Using Microsoft Windows
    • Initializing the Local Database When Using IBM DB2 for z/OS

7 Synchronizing the Remote Client

• Synchronizing the Remote Client
• Synchronizing the Remote Client
  • User Preferences for Synchronization
    • Retrieving Auto Update Files
  • About the Siebel Remote Dialog Box
    • Synchronization Actions
    • Item Status Notice
    • Progress Indicator for Transfer Time Remaining
    • Skip File Button
    • Progress Indicator for Overall Transfer Progress
    • Transfer Time Remaining Notice
    • Synchronize Button
• Options for Synchronizing and Starting the Remote Client
  • Configuring the Remote Client to Automatically Synchronize
    • Situations Where the User Must Manually Enter Credentials
    • Using Local Database Credentials to Automatically Synchronize
    • Using the Remember Credentials Feature to Automatically Synchronize
  • Using the Stand-Alone Synchronizer
    • Downloading and Uploading Transactions Without Applying Them to the Local Database
    • Applying Downloaded Transactions to the Local Database
    • Command Line Options of the Stand-Alone Synchronizer
  • Deploying a Predefined Routing Model
    • Example of How Modifying a View Might Compromise Data Integrity
    • What Happens If a View Does Not Reference a Routing Rule
    • Expected Results from the Field Test of a Predefined Routing Model
  • Opening Multiple Remote Client Sessions
  • Using Synchronization Manager to Manage the Cache
• Configuring TrickleSync
  • Configuring TrickleSync from the Siebel Server
    • Configuring TrickleSync from the Siebel Server for Multiple Users
    • Configuring TrickleSync from the Siebel Server for One User
    • How Siebel Remote Synchronizes TrickleSync Modifications from the Siebel Server
  • Configuring TrickleSync from the Remote Client
  • Options for Configuring TrickleSync
    • TrickleSync Options That You Can Specify
    • Options for Configuring How Frequently Siebel Remote Uses TrickleSync
    • Options for Date and Time Scheduling of TrickleSync

8 Monitoring and Reporting for Siebel Remote

• Monitoring and Reporting for Siebel Remote
• Monitoring and Logging for Siebel Remote
  • Naming Conventions for Log Files
    • Log Files on the Siebel Server
    • Log Files on the Remote Client
  • Automatic Notification of Critical Conditions
  • Monitoring the Transaction Backlog
  • Monitoring Various Transaction Logs
    • Monitoring Transaction Logs
    • Monitoring Transaction Logs by Operation
    • Monitoring Transaction Logs by Node
    • Monitoring Transaction Logs by Table
    • Support for Fields That Include the CLOB Data Type
  • Monitoring the Status of the Siebel Server
  • Configuring Traces for a Server Component
    • Configuring Traces for a Server Component by Using an Administrative Screen
    • Configuring Traces for a Server Component by Using a Command Line
    • How the Siebel Server Traces a Lock
    • Server Components That You Can Use with Tracing
    • Using Event Logging with Server Components
    • Information Sources for Tracing
  • Configuring Logs on the Remote Client
    • Temporarily Setting Event Levels
    • Setting the Event Level
  • Using Siebel Audit Trail with Siebel Remote
• Viewing Reports
  • Viewing Reports for Synchronization Sessions
    • Viewing the Remote Status View
    • Viewing the Current Siebel Remote Session Report
  • Viewing Administrative Status Reports
  • Viewing Reports on the Remote Client
    • Using the Client Status View
    • Using the Client Status Diagnostics View
    • Using the Synchronization Sessions View
    • Using the Upload Statistics View
    • Using the Download Statistics View
    • Displaying Local Time in the User Preferences Screen

9 Administering Siebel Remote

• Administering Siebel Remote
• Doing Basic Configuration and Administrative Tasks
  • Logging in to the Siebel Database as an Administrator
  • Logging in to the Local Database
  • Making Advanced Server Parameters Visible
  • Locating the Siebel Application Configuration File
  • Locating the Record for a Server Component
• Process of Administering Siebel Remote
• Administering Server Components for Siebel Remote
  • Using the Administrative Interface to Administer Server Components
  • Using the Command Line Interface to Administer Server Components
    • Opening the Command Line Interface for Server Manager
    • Using the Command Line to Administer Server Components
    • Using the Command Line to Stop or Start the Siebel Remote or Disconnected Mobile Synchronization Component Group
    • Using the Command Line to Start a Task for a Server Component
    • Using the Command Line to Start Multiple Tasks for a Server Component
• Managing Synchronization
  • Determining How Frequently to Synchronize
  • Optimizing Transaction Routing by Extracting All Remote Clients
  • Sending a Message to a User During Synchronization
• Administering the Remote Client
  • Adding a New Remote Client
  • Deactivating a Remote Client
    • Deactivating a Large Number of Remote Clients
  • Reactivating a Remote Client
    • Locating the Record of a Remote Client
  • Deleting a Remote Client
  • Resetting the Password of a Remote Client
    • Restoring Password Reset Privileges
  • Refreshing the Local Database of a Remote Client
  • Moving Remote Clients to a Different Siebel Server
    • Example Movehelper Commands
    • Example Nodemove Commands
    • Reversing the Outcome of a Nodemove Operation
  • Modifying the Routing Model for a Remote Client
• Maintaining Siebel Remote
  • Cleaning the Cache of the Dispatch Board

10 About Siebel Replication Manager

• About Siebel Replication Manager
  • Overview of Siebel Replication Manager
    • Hierarchy of a Siebel Replication Manager Implementation
      • Headquarters Node
      • Regional Node
      • Benefits of Siebel Replication Manager
      • Comparison Between Siebel Remote and Siebel Replication Manager
    • How Siebel Replication Manager Uses Routing Groups
      • About the Regional Server - Full Copy Routing Group
      • About the Regional Server - Standard Routing Group
      • Advantages and Disadvantages of Full Copy and Standard Routing Groups
      • Assignment to Multiple Databases
    • Server Components That Siebel Replication Manager Uses
      • Server Component Usage on Headquarters and Regional Nodes
    • Support for Siebel Server Features on a Regional Node
    • How Siebel Replication Manager Filters a Regional Workflow

11 Implementing Siebel Replication Manager

• Implementing Replication Manager
• Process of Implementing Siebel Replication Manager
• Installing Servers and File Systems on the Headquarters Node
• Installing Servers and File Systems on the Regional Node
  • Requirements for Connectivity with the Siebel Gateway
  • Requirements for the ODBC Driver
  • Requirements for Installing the Siebel Server on the Regional Node
  • Installing the Database Configuration Utilities and the Regional Siebel Database on the Regional Node
    • Implementing Srvrinit on the Regional Node
    • Options for Installing the Siebel Database on the Regional Node
  • Creating the Siebel File System on the Regional Node
• Defining the Regional Node
  • Requirements for the Parent Node
  • Requirements for Organization, Territory and Assignment Manager
  • Requirements for the Siebel Server Name and Local Database Names
  • Requirements for Adding a User to a Regional Node
• Extracting the Regional Database
  • Extracting the Regional Database by Using the Single Thread Option
    • Extracting the Regional Database by Using the Single Thread Option in the Administrative Interface
    • Extracting a Regional Database by Using the Single Thread Option in the Server Manager Command Line Interface
  • Extracting Regional Databases in Parallel
    • Extracting Regional Databases in Parallel by Using the Administrative Interface
    • Extracting Regional Databases in Parallel by Using the Command Line Interface
    • Adjusting the Shared Pool Size for Parallel Database Extract
  • Options for Extracting the Regional Database
    • Concurrently Extracting Multiple Regional Nodes
    • Using Parallel Database Extract with Local Databases
    • Parameters That You Can Specify When Extracting a Regional Database
    • Example Folder Tree of the Parent Node
• Initializing the Regional Database
  • Initializing the Regional Database from the Administrative Interface
  • Initializing the Regional Database from the Command Line Interface
  • Requirements for Running the Regional Database Initialization Program
  • Error Messages That You Can Ignore
  • Options for Initializing the Regional Database
  • Recovering from a Failure While Initializing a Regional Database
    • Restarting the Procedure to Initialize a Regional Database
• Configuring the Regional Node to Support Remote Clients
• Configuring the Replication Agent Server Component
  • Starting and Stopping the Replication Agent Server Component
    • Starting Replication Agent in the Administrative Interface
    • Starting and Stopping Replication Agent in the Server Manager Command Line Interface
    • Setting the HQ Application Server Name Parameter
  • Setting Tasks to Start Automatically for the Replication Agent When the Siebel Server Starts
    • Using Server Manager to Set the Default Tasks Parameter
  • Using Replication Agent to Control Synchronization
  • Resolving Synchronization Conflicts
• Installing Another Siebel Server on the Regional Node

12 Administering Siebel Replication Manager

• Administering Siebel Replication Manager
• Process of Administering Siebel Replication Manager
  • Adding a Connected User to a Regional Node
    • Locating the Record for the Regional Database
  • Adding a User to a Regional Node
    • Requirements for a User on a Regional Node
  • Deleting a Remote Client from a Regional Node
  • Managing Synchronization for a Regional Node
  • Modifying the Routing Group for a Regional Node
  • Deactivating a Regional Node
  • Reactivating a Regional Node
  • Upgrading a Regional Node
    • Finishing the Upgrade with Siebel Anywhere
    • Finishing the Upgrade without Siebel Anywhere
    • Language Requirements
    • Generating Reporting Relationships
  • Modifying Authentication for Siebel Replication Manager
  • Maintaining Siebel Replication Manager
    • Backing Up and Recovering a Database on the Headquarters Node or Regional Node
    • Backing Up and Recovering the Siebel Enterprise Server
    • Administering Monitoring and Logging
• Guidelines for Doing Administrative Work
  • Do Administrative Work on the Headquarters Node

13 Troubleshooting Siebel Remote

• Troubleshooting Siebel Remote
• Troubleshooting a Merge Problem
  • Troubleshooting an Assignment Manager Merge Problem
    • Why LogTxnChgOnly Affects the Quantity of Merge Conflicts
    • Scenario for a Harmless Merge Conflict
    • Distinguishing Between a Harmless and a Meaningful Merge Conflict
  • Troubleshooting a Transaction Merger Problem
    • Example Log File for Transaction Merger
• Troubleshooting a Synchronization Manager Problem
  • Troubleshooting a Problem That Synchronization Manager Logs in the Log File
  • Troubleshooting an Initialization or Synchronization Problem
  • Troubleshooting an Initialization or Synchronization That Requires Too Much Time to Complete
  • Troubleshooting a Bad Connection During Synchronization Problem
    • Examining the DockConnString Parameter
    • Troubleshooting a Problem with the Port Number
    • Registering a New Password with the Siebel Gateway
• Troubleshooting a Problem Where the User Cannot View Records Locally
  • Troubleshooting a Situation Where the Visutl Utility Reports That the Record Is Visible
  • Requesting Assistance If the Visutl Utility Reports That the Record Is Visible
  • Examining Visibility Rules of the Dock Object
  • Troubleshooting an Unexpected Read-Only Field
• Troubleshooting a Large Transaction Backlog Problem
• Recovering from a Failure
  • Recovering from a Failed Siebel Server
  • Recovering from Failed Media That Resides on the Siebel Server
    • Example Where You Must Delete the Local Database
    • Protecting Against a Media Failure
  • Recovering from Corrupted Transactions That Reside on the Siebel Server
  • Recovering from a Failed Siebel Database
  • Recovering from Truncated or Deleted Siebel Database Records
  • Recovering from Failed Media That Resides on a File Server
  • Restoring the File System After Recovering from a Previous Image
  • Recovering from a Failed Local Database
  • Recovering from a Failed Client Initialization
  • Recovering from a Failed Transmission
• Using Troubleshooting Utilities
  • Using the Endtxnutl Utility to Adopt Orphaned Records
    • How the Endtxnutl Utility Finds an Adoptive Parent
    • Situations That Create Orphans
    • Querying for Orphan Records
  • Using the Txnskip Utility to Examine Skipped Transactions
  • Using the Txnutl Utility to Examine Corrupt Transactions
  • Using the Txnutlr Utility to Create Statistics
  • Using the Visutl Utility to Determine Visibility for a User
    • Running the Visutl Utility on a Cluster
  • Configuring Session Parameters for a Utility

14 Predefined Routing Models

• Predefined Routing Models
• Predefined Routing Models for Siebel Remote
  • About the Standard Routing Model
• Predefined Routing Models for Siebel Financial Services
  • Institutional Finance Sales Manager Routing Model
  • Institutional Finance Analyst Routing Model
  • Credit Originator Routing Model
  • Insurance Sales Manager Routing Model
  • Insurance Sales Agent Routing Model
  • Claims Manager Routing Model
  • Claims Adjuster Routing Model
  • Business Components That Are Associated with Predefined Routing Models for Financial Services
  • Differences in the Literature List When Connected to the Local Database

15 Reference Materials for Siebel Remote

• Reference Materials for Siebel Remote
• Values for System Preferences
• Server Component Parameters
  • Parameters of the Synchronization Manager Server Component
  • Parameters of the Transaction Processor Server Component
  • Parameters of the Transaction Router Server Component
  • Parameters of the Transaction Merger Server Component
  • Parameters of the Generate New Database Server Component
  • Parameters of the Database Extract Server Component
    • Specifying Client Names
    • Using the Move Siebel Remote Client Parameter
  • Parameters of the Replication Agent Server Component
• Field Descriptions for Administration Screens
  • Fields in the Siebel Remote Client Status Form
  • Fields in the Siebel Remote Client Diagnostics Form
  • Fields in the Synchronization Sessions List
  • Fields in the Siebel Remote Upload Statistics Form
  • Fields in the Siebel Remote Download Statistics Form
  • Operation Types for the Operation Field of the Transaction Log List
• Predefined Administrative Reports
• Siebel Server Features on a Regional Node
• Parameters of the Regional Database Initialization Program