Siebel Data Warehouse Installation and Administration Guide > 7.7 Analytics Bridges >

Setting Up the Siebel Transactional Database for the 7.7 Analytics Bridge

After you install the 7.7 Analytics Bridge application, follow this procedure to set up the Siebel transactional database.

To set up the Siebel transactional database

1. Import new transactional database schema definitions:
   1. Copy the appropriate .sif file for the 7.7 Analytics Bridge you installed:

      Bridge Application	Copy	From	To
      6.3 to 7.7 Analytics Bridge (Siebel eBusiness Applications)	objects_63_bridge.sif	SiebelAnalytics\dwrep	\tools\objects
      7.5.3 to 7.7 Analytics Bridge (Siebel eBusiness and Industry Applications)	SRW_76.sif	SiebelAnalytics\dwrep	\tools\objects

   2. Open Siebel Tools and point to the development database.
   3. Lock the appropriate project:
      • For Siebel eBusiness Applications, lock the Newtable project
      • For Siebel Industry Applications, lock the Table ETL and Table ETL CCM projects.
   4. Navigate to Tools > Import from Archive.
   5. Select Open.

      The Import Wizard—Preview screen appears, listing the Analytics Bridge tables.

   6. In the Conflict Resolution area, select the option Merge the object definition from the archive file with the definition in the repository, and click Next.
   7. A dialog box appears, informing you that the operation will modify your repository and asking if you want to proceed. Click Yes.
   8. The Import Wizard — Summary screen appears, showing a summary of the .sif changes to the repository files. Click Finish.
2. Apply the new schema definitions to the transactional database:
   1. In Siebel Tools, go to the Table screen and search for the tables S_ETL*.
   2. Select all the S_ETL* tables that appear, and click Apply at the top of the screen.
   3. In the Apply Schema dialog box, under the entry Tables, select Current Query from the dropdown list.
   4. Under the subsequent entries, enter the connection parameters for the development database. (Your connection information will vary depending on your particular database platform and on the configuration of your particular database environment.)
   5. Click Apply.
3. Create Image tables:
   1. In the DAC, navigate to Design > Tables.
   2. On the toolbar, click Query.
   3. In the Image Suffix field, enter !Null.
   4. Select a record.
   5. Right-click and select Change Capture Scripts > Generate Image and Trigger Scripts.
   6. In the Trigger and Image Tables dialog box, select All Tables in the List.
   7. Select the appropriate database type, and check the Unicode Database option if the database is Unicode.
   8. Check the Generate Image Table Scripts option, and click OK.

      This process generates a SQL script.

   9. Save the SQL script and pipe it to the transactional database.
4. For the 6.3 to 7.7 Bridge, import language-independent Siebel seed data.

   NOTE:  This step is not required for the 7.5.3 to 7.7 Bridge.

   1. Copy the following files:

      Copy	From	To
      seed_63_bridge.dat	SiebelAnalytics\dwrep	Local machine
      seed_63_bidge_<xxx>.inp (where xxx corresponds to the database platform being used)	SiebelAnalytics\dwrep	Local machine

   2. Open a command line, and go to the same directory where you copied the .dat and .inp files.
   3. Replace each of the connection parameters with the values appropriate to your database environment, and then run the appropriate import command from the following table.

      Database Platform	Run Import Command
      DB2UDB	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_63_bridge.dat /w y /q 100 /h Log /x f /i seed_63_bridge_db2udb.inp /l seed_63_bridge_db2udb.log
      MSSQL	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_63_bridge.dat /w y /q 100 /h Log /x f /i seed_63_bridge_mssql.inp /l seed_63_bridge_mssql.log
      Oracle	$SIEBELSERVERROOT\bin\dataimp /u $UserName /p $Password /c "$ODBCDataSource" /d $DatabaseOwner /f seed_63_bridge.dat /w y /q 100 /h Log /x f /i seed_63_bridge_oracle.inp /l seed_63_bridge_oracle.log

5. Using the DAC, run the Complete ETL execution plan to perform a full load of data into the data warehouse.

   For instructions on running an ETL using the DAC, see Executing an ETL with the DAC.