Bookshelf v7.5: Running the Wizard

The Database Wizard and Database Adapter support standard ODBC drivers. The drivers listed below are validated for Siebel 7.0.

Siebel Tools Configuration

In tools.cfg locate the [DBWizSubSys] section and update the following parameters

Database	ODBC Driver
DB2	IBM
Oracle	Merant
SQL Server	Microsoft


DBWIZUserName	The Wizard uses this Username to access table definitions.
DBWIZPassword	Password for the Username.
DBWIZODBCDataSource	ODBC data source name.
DBWIZTableOwner	Table owner (prefix).

Wizard Initial Selections

Before proceeding, make sure you have a project locked to create the new Integration Object into. If the starting connection is successful, the wizard prompts you to select one of the following:

Choose the selection that contains the minimum number of tables and still contains all tables and views of interest. The "All" option will cause the wizard to return a selection containing all tables visible to the user specified in the [DBWizSubSys] section. The second textbox on this dialog prompts for the name of the integration object to be created. Choose a unique name.

Wizard Component Selections

Tables, Views, Synonyms, Aliases
Tables
System Tables
Views
Temporary Tables
All

After you click NEXT, the wizard will proceed to query the external database. Depending on various factors (especially the number of tables in the database), this operation may take several minutes. The wizard then brings up the component explorer. You will see all tables listed under one root component. This is only for visual representation—you can ignore the hierarchy and select the components (tables) of interest.

NOTE: You can jump to a component of interest by typing (without pauses) the first few character of the component name.

Completing the Integration Object

Before the generated integration object is usable, the following items need to be configured manually to establish the hierarchy.

Parent Integration Component

The generated object has no parent child relationship. But before the object can be used, exactly one component should be designated as the root, and every other component should be a child component.

Navigate to Integration Object > (select the generated integration object) > Integration Component. Notice that the Parent Integration Component column is empty for all components. For each component, you need to fill this column with its parent integration component's name. At the end of this step, every component except the root integration component should have a value in the Parent Integration Component column.

Target Key

A child integration component's foreign keys cannot point to just any field in the parent integration component. The parent integration component needs to be aware of which fields are being utilized by its children as foreign keys and needs to mark these fields by creating an Integration Component Key. A key can contain several fields. The relation between the parent's target key fields and the child's foreign key fields is established using the Key Sequence Number. The Key Type column should be set to Target Key.

Foreign Key

Once a parent has grouped some of its fields and created a target key, the children can then create a foreign key. The child component should create a key with Key Type column set to Foreign Key and the Target Key column point to the parent's target key. The number and data type of the constituent fields of the foreign key and the target key should match and the fields should always have a sequence number.

User Keys

For operations that need components to be identified uniquely (example: upsert), you need to setup user keys. Navigate to Integration Component Key and create User Keys and User Key Fields in the usual manner. The Key Type should be set to User Key. Typically, the logical primary key of the table becomes the User Key of the corresponding integration component.

Running the Wizard

ODBC Sources