Upgrading and Migrating Siebel Janna Applications > Database Upgrade Tools > Database Upgrade Tools >

Step 3: Schema Integration

The database upgrade is based on a logical Siebel Janna database. Prior versions need to upgrade to Siebel Janna using standard Siebel Janna upgrade scripts before the upgrade to a Siebel database can begin.

The database schema integration requires:

• Mapping the data elements from the Siebel Janna database to a Siebel database
• Extracting the data using Informatica's data migration utility, PowerMart
• Using Siebel EIM to import the data into the Siebel database

You can also upgrade client-specific custom extension tables by following a methodology similar to that used for the base tables—requirements and differences, data mapping, PowerMart, and Siebel EIM.

Installing the Siebel Janna Upgrade Sample Informatica Repository

This procedure assumes that Informatica PowerMart has been installed, in particular the client software.

To install the Siebel Janna Upgrade Sample Informatica Repository

1. Start Informatica Repository Manager.
2. Use the Restore Repository feature to install the sample repository file (Siebel_Janna_Migration.rep) to a database of your choice. Name the repository, Siebel_Janna_Migration, when prompted.
3. Run the Create.sql and Insert.sql scripts applicable to your database platform to create the Siebel Janna tables required by the sample mappings. Note that these scripts do not create or populate the tables required by the Object Extraction Utility (See Step 2: Siebel Janna Upgrade Object Extraction Utility for further information).

Mapping Data Elements

Data elements in the Siebel Janna data model must be mapped to functionally equivalent elements in the Siebel data model. Basic data elements include information about Users, Contacts, Accounts, Interactions, and so forth. Details on the Siebel Janna elements are found in Siebel Janna Data Objects. The difference report from Step 1: Siebel Janna Difference Reporting Utility reveals the differences between the Siebel Janna base tables and any client configuration. New tables and types are identified with this report and assist with mapping the data. Other mapping considerations follow:

• Siebel Janna Document Manager records are upgraded to the Siebel Literature module. The names of the upgraded documents in the Siebel Literature Module are made up of the fully qualified folder name and document name of the document in Siebel Janna.
• Records are assigned to the default organization. Implement organizational hierarchy after the data migration by creating business units and divisions. The Siebel Janna branch field is mapped to the NAME column in the S_ORG_EXT table to make this information visible. However, the company/branch hierarchy has been maintained at the database level.
• Where possible or required, map International Address Attributes (for example, House Number) stored in Siebel Janna to the appropriate Siebel Data Model.
• Based on specific needs, map data elements from Siebel Janna Custom Fields, Categories, or Document Custom Fields to similar fields in the Siebel data model, such as Region, Birthday, Territory, Spouse's Name, Dun & Bradstreet ID, and so on. Currently, this data is mapped to extension tables and columns so that there is no data loss.
• Siebel Janna remote rules are not migrated to the Siebel deployment.

Extracting Data

The extraction of data is implemented using a third-party data-migration utility, Informatica's PowerMart. Core tables are mapped with standard mappings. Custom fields are manually mapped for each client as part of the Database Upgrade Methodology. Extracted data from Siebel Janna database is moved with the utility to Siebel EIM Interface tables. Siebel EIM is then used to import the data to the Siebel database.

Caution:  The upgrade is one way and overwrites existing and previously upgraded Siebel data. After you start using the Siebel database, for production data, you cannot synchronize data back to the Siebel Janna database.

You must maintain functionally equivalent security to that of Siebel Janna applications after the upgrade. However, Siebel Janna record-level security data is not migrated. The security process is manually configured.

Using Siebel Enterprise Integration Manager (Siebel EIM)

Siebel EIM is the Siebel utility used to move data from interface tables to the Siebel database. Extracted data from the Siebel Janna database is moved with Informatica's PowerMart utility to the interface tables used by Siebel EIM. For detailed information on Siebel EIM, see Siebel Enterprise Integration Manager Administration Guide.

A Siebel EIM configuration script is required, and provided, to import data elements from the interface tables.