Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > How Siebel Remote Validates and Authenticates Information >

How Siebel Remote Validates Synchronization


This topic describes the data that the Synchronization Manager server component validates when a remote client synchronizes with the Siebel Server. The Synchronization Manager authenticates incoming client requests to make sure that the remote client is valid.

Siebel Remote does not route the data that the Data Validation Manager uses. For help with Data Validation Manager, see Getting Help from Oracle.

Validating the Remote Client Name

The Synchronization Manager validates the name of the remote client with the list of valid clients that the server database contains. It validates that the effective end date for the client name is valid or is NULL.

Validating the Siebel Server

The App Server Name field identifies the name of the Siebel Server. It resides in the Mobile Clients view of the Administration - Siebel Remote screen. The DockConnString parameter identifies the local database. This parameter resides in the configuration file of the Siebel application on the remote client. For more information, see Modifying the Siebel Configuration File for Siebel Remote.

If the value of the App Server Name field does not equal the value of the DockConnString parameter, then the Synchronization Manager does the following work:

  • Reroutes the connection to the Siebel Server that the App Server Name field identifies
  • Sets the value of the DockConnString parameter to the value that the App Server Name field contains

Validating the User Credentials

If the Authentication Method parameter of the Synchronization Manager is not set to None, then the Synchronization Manager validates the authentication credentials for synchronization with the remote client. The authentication credentials that Siebel Remote uses depends on when the user attempts to synchronize:

  • User synchronizes before Siebel Remote initializes the local database. Siebel Remote uses the user ID and password that the user provides during the login.
  • User synchronizes after Siebel Remote initializes the local database. Siebel Remote uses the user ID and password from the DB Synchronization view of the User Preferences screen on the remote client.

The authentication method is a Synchronization Manager parameter that identifies the type of authentication that Siebel Remote uses during synchronization. For more information, see Parameters of the Synchronization Manager Server Component.

Siebel Remote and Replication Manager Administration Guide Copyright © 2018, Oracle and/or its affiliates. All rights reserved. Legal Notices.