Configuration Guide for Siebel Offline Client for Life Sciences > Overview of the Offline Client for Life Sciences >

Data Sources and Offline Databases


Each application for the Offline Client for Life Sciences uses a set of filter object definitions that is synchronized with a specific Siebel CRM instance. The combination of filter definition files and a Siebel CRM instance for each application is called a data source. The data source is defined as part of the Sync application configuration in the datasources.xml file.

The Sync application uses the data source information to determine which databases and tables to create for the Offline Client for Life Sciences when it first downloads data from the Siebel CRM instance. Applications for the Offline Client for Life Sciences (for example, Sales) use the local database and tables created by the Sync application.

Two database files are created for each data source synchronized by the Sync application as shown in Table 2. There is also one database for the Offline Client for Life Sciences called System.db. This database contains the active data source information and the connection names that allow the Sync application to communicate with the other applications for the Offline Client for Life Sciences.

Table 2 shows the Siebel CRM database files created for each data source synchronized by the Sync application.

Table 2. Siebel CRM Database Files for the Offline Client for Life Sciences
Database File Name
Description

Sales (CRM On Premise).db.

For example: Sales(OfflineClient2).db.

Contains transaction data for your Siebel CRM instance.

Sales (CRM On Premise)Blob.db.

For example: Sales(OfflineClient2)Blob.db.

Contains BLOB (binary large objects) data for your Siebel CRM instance.

Configuration Guide for Siebel Offline Client for Life Sciences Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.