Siebel Analytics Server Administration Guide > Setting Up and Working with a Repository > The Steps to Setting Up a Repository >

Importing the Physical Schemas


Every repository contains a Physical layer, a Business Model and Mapping layer, and a Presentation layer. You can work on each layer at any stage in creating a repository, but the usual order is to create the Physical layer first, the Business Model and Mapping layer next, and the Presentation layer last. You can set up security when you are ready to begin testing the repository.

The first step in creating the Physical layer is to import schemas or portions of schemas from existing data sources.

NOTE:  Physical metadata imports have to connect using an ODBC connection; native database gateways for metadata import are only supported for DB2 (using DB2 CLI or DB2 CLI Unicode) and XML. To import XML data using the Siebel Analytics Server XML gateway, see Siebel Analytics Server XML Gateway Example.

To import a schema

  1. In the Administration Tool, select File > Import.
  2. Select a connection type and a data source to import from, and then click OK.
  3. If a logon screen appears, enter a valid user ID and password for the data source, and then click OK.
  4. The Import dialog box appears.

  5. Check the type of metadata you want to import.
  6. NOTE:  It is recommended that you not import foreign keys from an Oracle database, because the process is lengthy when importing a large number of tables.

    The default varies based on your data source. For most databases, the default is to import tables, primary keys, and foreign keys. Note that you can also import database views, aliases, synonyms, and system tables. Import these other objects only if you want the Siebel Analytics Server to generate queries against them.

  7. Select the tables and columns you want to import.
  8. When the objects are selected, either click Import or drag and drop the objects into the Physical layer. This imports the metadata for the objects into the Physical layer.

NOTE:  When you import physical tables, be careful to limit the import only to those objects that are likely to be used as sources of data in the business models you create. Importing too many extraneous objects will complicate your job as an administrator, increase the size of the repository, and potentially affect the performance of the Administration Tool.


 Siebel Analytics Server Administration Guide 
 Published: 23 June 2003