Siebel Remote and Replication Manager Administration Guide > Architecture of Siebel Remote > How Siebel Remote Creates Local Databases >

How Siebel Remote Extracts Local Databases


The first step in creating a local database for a new user is to extract the server database on the Siebel Server. You run the Database Extract server component to extract a remote client. It extracts visible data for the user to a snapshot file in the Mobile outbox folder of the Web client on the Siebel Server. This extract gets data according to the routing rules that define the level of access to information for each remote client. It creates compressed files that contain data that Siebel Remote loads to a local database when the remote client starts a synchronization with the server database. Each local database is unique. A user cannot use multiple computers with the same remote client.

Figure 4 illustrates how Siebel Remote extracts a local database.

Figure 4. How Siebel Remote Extracts a Local Database
Explanation of Callouts

Siebel Remote does the following work to extract a local database:

  1. Prompt for connect information. Prompts the user to enter the user ID, the name of the remote client, and a password. A user might use multiple clients, such as two clients on two separate computers. If the user starts the remote client to initialize the database, then Siebel Remote sets the user ID to the value that the user provides, by default.
  2. Connect. Siebel Remote does the following work:
    • If the user can access the Siebel Server, and if the port for the Synchronization Manager is open, then the Synchronization Client connects to the Siebel Server.
    • If the user specifies to use a modem, then the Synchronization Client dials the modem and connects to the Siebel Server.
    • Siebel Remote starts a new synchronization thread for the remote client. For example, a VPN setup might require the user to enter a special PIN (personal identification number) and security number, such as an RSA key (Rivest, Shamir and Adleman).
  3. Validate remote client. The Synchronization Manager does the following work:
    1. Validates the node name of the remote client with the list of valid users that exist in the server database.
    2. Makes sure that the remote client is connected to the correct Siebel Server.
    3. If authentication for Siebel Remote is turned on, then it authenticates the remote client credentials.
  4. Confirm status of database extract. The Synchronization Manager does the following work:
    1. Verifies that a database extract is pending in the outbox on the Siebel Server.
    2. Determines if uaf files or toc files exist in the outbox folder for the user. If it does not find these files, then the Synchronization Client prompts the user to contact the Siebel administrator to do a database extract.
  5. Download snapshot and file attachments. Prompts the user to download a new database. The Synchronization Client downloads the extract and file attachments to the inbox folder on the remote client.
  6. Disconnect. The Synchronization Client closes the connection with the Synchronization Manager. The user can disconnect from the network.
  7. Create and load database. The Synchronization Client shuts down the remote client or Siebel Remote program, and then starts the Siebel Upgrade Wizard. This wizard does the following work:
    • Creates a new local database
    • Loads data from the extract file to the local database
    • Applies file attachments to the local file system

For more information, see Initializing the Local Database, and Configuring Siebel Remote to Use Siebel QuickStart to Start the Remote Client.

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