Bookshelf v7.5: Data Migration

Siebel Interactive Selling Applications Upgrade Guide > Upgrading to eAuction Version 7 > Upgrade Tasks >

Data Migration

Figure 16 summarizes the various steps involved in the data migration process.

Figure 16. Data Migration Process

Data Migration Steps for OSA and Siebel eAuction Version 4.3.x MidMarket Edition Customers

OSA and Siebel eAuction version 4.3.x MidMarket Edition customers should read the information on data migration in this section.

NOTE: DPT and Siebel eAuction version 4.3.x Enterprise Edition customers should skip ahead to Data Migration Steps for DPT and Siebel eAuction Version 4.3.x Enterprise Edition Customers.

Preparing for Data Migration

To begin the process of data migration, first verify that the following conditions are met:

Users, Bids, Offers, and Categories tables are migrated.

All auctions are closed. Customers must not have access to the auction site during the migration.

You have access to the Data Migration Utilities CD.

All scripts run with either Oracle SQLPLUS or SQL Server Console Manager.

Creating a Temporary DPT Database

Load the Data Migration Utilities CD and verify that the following utilities are included:

OSADPEMigration.exe

Migration.ini

CreateOracleCybrCashDB.sql

IniDataOracleCybrCash.sql

CreateSqlSvrCybrCashDB.sql

IniDataSqlSvrCybrCash.sql

CreateGallery.sql

OSADPTValidation.sql

To create a clean instance of the temporary DPT database and populate it with seed data

Use the following seed data:


For Oracle Source Databases	For SQL Server Databases
Execute `CreateOracleCybrCashDB.sql`	Execute `CreateSqlSvrCybrCashDB.sql`
Execute `IniDataOracleCybrCash.sql`	Execute `IniDataSqlSvrCybrCash.sql`

To prepare and execute CreateGallery.sql

Using Notepad, open CreateGallery.sql.

Set Gallery ID=2.

Execute CreateGallery.sql.

To invoke the data migration process

Double-click the OSADPEMigration.exe executable file.

The Data Migration dialog box appears, as shown in the following figure.

In the Data Migration dialog box, enter the following information:

Source database type (SQL or Oracle)

User ID (login) for source server or service

Password for source server or service

Destination database type (SQL or Oracle)

User ID (login) for destination

Password for destination

Click the Test Source Connection button to test the source database connection.

Click the Test Destination Connection button to test the destination database connection.

Click the Start Data Migration button to begin the migration process.

To verify migration success

Run OSADPTValidation.sql.

Check that counts in the Siebel eAuction version 4.3.x database match those in the intermediate database.

If the counts do not match, start the migration process over.

Proceed toData Migration Steps for DPT and Siebel eAuction Version 4.3.x Enterprise Edition Customers.

Data Migration Steps for DPT and Siebel eAuction Version 4.3.x Enterprise Edition Customers

DPT and Siebel eAuction version 4.3.x Enterprise Edition customers should read the information on data migration in this section.

NOTE: OSA and Siebel eAuction version 4.3.x MidMarket Edition customers should skip this section in favor of Data Migration Steps for OSA and Siebel eAuction Version 4.3.x MidMarket Edition Customers.

Preparing for Data Migration

Before beginning the process of data migration, first verify that the following conditions are met:

You have reviewed the list of table mappings (see Table 11) and you now know which of your existing tables will map into Siebel 7 eAuction.

You have access to a base Siebel application (Siebel Sales).

All auctions are closed. Customers must not have access to the auction site during the migration.

You have access to the Data Migration Utilities CD.

You are familiar with Siebel Tools and Workflow.

Using the Data Migration Utilities CD

Use the data migration utilities CD to start the data migration.

To access the utilities

Insert the Data Migration Utilities CD.

Launch Windows NT Explorer and access the drive running the migration CD.

View the list of utilities on the CD and verify they are all there. Here is the list of utilities:


`bsafe41.lib`	`std12d.lib`
`DataMigration.exe`	`std15d.lib`
`dbt12d.lib`	`std315d.lib`
`dbt15d.dll`	`sync2015d.dll`
`dbt15d.lib`	`thr12d.lib`
`DPTAtoms.dll`	`thr15d.lib`
`DPTAtoms.lib`	`thread2015d.dll`
`DPTDynamicPropertObjects.dll`	`threxcept2015d.dll`
`DPTDynamicPropertObjects.lib`	`tls12d.lib`
`DPTEncryptionMgr.lib`	`tls15d.lib`
`Mapping Database.mdb`	`tls7012d.dll`
`Mfc42d.dll`	`tls7015d.dll`
`Mfc042d.dll`	`trace2012d.dll`
`Msvcirtd.dll`	`trace2015d.dll`
`Msvcp60.dll`	`DataMigration.exe`
`Msvcp60d.dll`	`Mapping Database.mdb`
`Msvcrtd.dll`	`Migproj.sif`
`ODPTAPI.lib`	`Migflows.xml`

NOTE: If any of the utilities listed above are missing from your migration CD, contact Siebel Technical Support to request a new CD or to receive the missing files by FTP.

Copy all the utilities from the CD into the Siebel 7 BIN directory.

To import and compile the Migrate Project utility

Import the migproj.sif. This is the Migrate Project utility provided on the CD.

Once the import has completed, a new project will be available (Migtable).

Navigate to Menu > Tools > Compile.

Select the newly imported project (Migtable).

Compile the .srf file.

To make the new workflows available

Launch Siebel Sales.

From the application-level menu, choose View > Site Map > Workflow Administration > Workflow Processes.

Click the Import button to import the XML processes file (migflows.xml).

Run a query on the dcommerce data migration process to verify that the file exists.

From the Workflow Processes applet, find the picklist of actions you can perform.

From the picklist, choose New Query.

A new applet appears.

Enter *dcommerce*.

Choose Run Query.

The application will populate the workflow name with the appropriate workflow.

To invoke the data migration process

Within Siebel Sales, navigate to Screens > Workflow Administration > All Processes.

Click the Process Simulator tab.

A set of action buttons appears.

Click the Start button to invoke the migration process.

A dialog box appears through which you can choose to continue.

Click the Continue button to invoke the migration utility.

The Step 1 dialog box of the Data Migration Tool appears, as shown in the following figure.

Click the radio buttons to specify the following selections:

Legacy application. Select DPT.

Database type. Select your source database type (ODBC, SQL Server, or Oracle).

Click the Next button to continue.

The Step 2 dialog box of the Data Migration Tool appears as follows. You are now ready to test the database connectivity.

To run the database connection test

Click the Enter Values button.

A dialog box like this one appears, in which you can enter your database connection variables.

Complete the fields in the dialog box according to your specific connection variables, and then click OK.

In the Step 2 dialog box, click the Test Database Connectivity button.

When a DataMigration message appears saying that the database connection test is successful, you have completed the test. Click OK.

In the event the connectivity test fails, an error message is generated. Verify that the database is up and running and that the database name, user ID, and password have all been input correctly. Then, rerun the database connectivity test. If the problem persists, contact your database administrator or Siebel Technical Support.

You are now ready to select the tables to migrate. In the Step 2 dialog box, click the Next button.

The Step 3 dialog box appears, as shown in the following figure.

To select the tables to migrate

In the Step 3 dialog box, select the check boxes to specify which tables to migrate.

NOTE: It is strongly recommended that you select all the tables for migration. If you choose not to migrate all the tables, your postmigration auction site may not contain the same data as your premigration auction site.

Click the Next button to continue.

The Step 4 dialog box appears, as shown. You are now ready to migrate the data.

To migrate the data to the Siebel data format

In the Step 4 dialog box, verify that all tables you have selected for migration are displayed.

Click the Migrate Data button.

The migration process begins and can take several minutes depending on the amount of data to be migrated. In the dialog box, you can check the progress of the migration in the status bar underneath the Migrate Data button. When the status bar has reached the far right, the FINISH button is now available.

Click the Finish button.

The output from the data migration process is some or all of the XML files listed in the following table. Your specific output is determined by the files you selected for migration.


Base Data	Extended Data
ListOfUsers.xml	ListOfExtUsers.xml
ListOfGalleries.xml	ListOfExtGalleries.xml
ListOfCategories.xml	ListOfExtCategories.xml
ListOfItems.xml	ListOfExtItems.xml
ListOfBids.xml	ListOfExtBids.xml
ListOfFees.xml	ListOfExtFees.xml
ListOfAssignedFees.xml	ListOfExtCCInvoices.xml
ListOfCCInvoices.xml	ListOfExtCharges.xml
ListOfCharges.xml	ListOfExtAuctionRating.xml
ListOfAuctionRating.xml	ListOfExtAuctionWatch.xml
ListOfAuctionWatch.xml

NOTE: No extension data migration of the Assigned Fees table will be available as this is an intersection table in the Siebel database.

Move the XML files into the Siebel bin directory.

NOTE: This process will have decrypted any data that was encrypted in the legacy database. The data now shows up decrypted within the XML files.

The next workflow subprocess steps that automatically execute use these XML files or update services to import the legacy data into the Siebel database through the EAI XML utility called "Siebel Read from File and Insert." Each subprocess operates on a particular Siebel data object. All subprocesses or the entire process can be rerun without incident. If you find data problems in the data to be imported, you may choose to adjust the data within the XML file and safely rerun the particular subprocess to which it corresponds.

The migration process will yield several output log files also located in the Siebel bin directory, as listed in Table 10.

Table 10. Output Log Files
File Name	Comment
`Migration Log.txt`	A complete log of the success or failure of the legacy data written to XML.
`Encrypted Fields.txt`	A complete log of the tables and fields within the legacy database that have been decrypted and placed in the XML (for reference by the operator after completing the migration process, for entering into Siebel Tools and setting the field user properties appropriately to force the encryption of this data in the Siebel database).
`Extension Tables Mapping.txt`	A complete log of the tables and fields within the legacy database that were extended and how they map to the Siebel extension tables (for reference during UI migration).

Table 11 shows the Siebel tables into which your legacy data is imported.

Table 11. Mapping of Legacy Tables to Siebel Tables
Legacy Table Name	Siebel Table Name
`S_USER / S_CONTACT / S_PER_PAY_PRFL`	`USERS`
`S_CTLG / S_CONTACT / S_ORG_EXT / S_ADDR_ORG`	`GALLERIES`
`S_CTLG_CAT`	`CATEGORIES`
`S_AUC_ITEM / S_AUC_ITEM_X`	`ITEMS`
`S_AUC_ITEM / S_AUC_ITEM_X`	`OFFERS`
`S_AUC_BID / S_CONTACT / S_ADDR_ORG`	`BIDS`
`S_AUC_FEE`	`FEES`
`S_AUC_FEE_ASSIGN`	`ASSIGNEDFEES`
`S_INVOICE`	`INVOICES`
`S_INVOICE / S_ORDER / S_ORG_SYN / S_DOC_ORDER`	`CCINVOICES`
`S_INVOICE_ITEM`	`CHARGES`
`S_AUC_RATING`	`AUCTIONRATING`
`S_AUC_WATCH`	`AUCTIONWATCH`

Table 12 shows the legacy data tables that will not be migrated to the Siebel database.

Table 12. Legacy Tables Not Migrated
File Name	Comment
`INITIALIZATIONDATA`
`TRANSACTIONLOG`
`USERPRIVELEGES`
`COLUMNSTOENCRYPT`	Read by the migration process to determine data to be decrypted, but not directly migrated.
`OPTIONS`	Read by the migration process to add to ITEM information, but not directly migrated.
`ITEMS`	Read by the migration process to add to ITEM information, but not directly migrated. Exists in Siebel together with information from the OFFERS table to make up the new Siebel Item Table.
`INVOICES`	Read by the migration process to add to INVOICE information, but not directly migrated. Exists in Siebel together with information from CCINVOICES table to make up the new Siebel Item Table.

Table 13 shows the legacy data tables that will be migrated to the Siebel database. All fields within these legacy data tables will be migrated, with the exception of those listed. The fields listed are not migrated because they have been deemed irrelevant in the Siebel architecture.

Table 13. Legacy Tables Migrated
Table Name	Fields Within Table That Are Not Migrated
`USERS`	`OSKEY_ID`
	`JOIN_DATE`
	`PAYMENT`
	`TERMS`
	`TOTAL_BIDS`
	`TOTAL_WINNING_BIDS`
	`DELETED`
	`DELETED_DATE_TIME`
	`TAX_REGISTRATION_ID`
	`STATE_TAX_EXEMPTION_ID`
	`COUNTY_TAX_EXEMPTION_ID`
	`LOCAL_TAX_EXEMPTION_ID`
	`BID_PLACED_NOTIFY`
	`SELLER_REQUEST`
	`SELLER_APPROVED`
	`DESIRED_LOCALE`
`GALLERIES`	`ID`
	`OSKEY_ID`
	`DESCRIPTION`
	`ENFORCE_CONFIG_LIMITS`
	`MAX_OFFERS`
	`MAX_CATEGORIES`
	`PRIVATE_CATEGORIES_ALLOWED`
	`TEMPLATE_STYLE`
	`DELETED`
	`DELETED_DATE_TIME`
	`COMP_TAX_ID`
	`CUST_SUPPORT_EMAIL`
	`COMP_INFO_EMAIL`
	`AVS_OPTION`
	`PROCESS_MODEL`
	`CONFIGURATION_FILE`
	`STATE_TAX_EXEMPT`
	`STATE_TAX_EXEMPTION`
	`COUNTY_TAX_EXEMPT`
	`COUNTY_TAX_EXEMPTION`
	`LOCAL_TAX_EXEMPT`
	`LOCAL_TAX_EXEMPTION`
	`TW_COMPANY_ID`
	`TW_LOCATION_ID`
	`P2P`
`CATEGORIES`	ID
`CATEGORIES`	DELETED
`BIDS`	All fields are migrated.
`OFFERS`	Some fields in the `OFFERS` table in addition to the `ITEMS` table map to the Siebel `ITEMS` table. The following fields, however, are the exceptions and will not be migrated from the current `OFFERS` Table.
	`OSKEY_ID`
	`TITLE`
	`STATUS`
	`HOT_OFFER`
	`FEATURE_OFFER`
	`DURATION`
	`DAYS_OF_AUCTION`
	`DELETED`
	`DELETED_DATE_TIME`
	`BID_SORT_ORDER`
	`PAPER_INVOICING`
	`TAX_PRODUCT_CODE`
	`SHIPPING_INCLUDED`
	`PAYMENT_TYPES`
	`MODIFIED_CLOSE`
	`BID_COEFFICIENT3`
	`BID_COEFFICIENT4`
`FEES`	`DESCRIPTION`
`FEES`	`CONTEXT`
`ASSIGNEDFEES`	All fields are migrated.
`CCINVOICES`	Some of the fields in this table along with some fields in the `INVOICES` table will migrate to comprise the Siebel Invoice table. The following fields are exceptions and will not migrate.
	`MAIL_TRACKING_NUM`
	`TRACKING_ORDER_ID`
`CHARGES`	`ID`
`CHARGES`	`CHARGE_DATE`
`AUCTIONRATING`	`ID`
`AUCTIONWATCH`	All fields are migrated.