8 Deploying the ODI Repository for Non-Oracle Source Databases

This section provides information about deploying the Oracle Data Integrator (ODI) repository for non-Oracle source databases.

During installation and setup of Oracle Business Intelligence Applications (Oracle BI Applications), if your source database is Oracle, then an instance of the ODI repository is automatically deployed and no further setup steps are required. If your source database is MS SQL Server, UDB DB2, or UDB 400, then you must perform these configuration steps to deploy a new instance of the ODI repository.

If you have multiple sources and one or more of the source databases is non-Oracle, you must follow these procedures for all source databases, including any Oracle source databases. The following non-Oracle source databases are certified:

  • JD Edwards (JDE) 91, JDE 90 Adaptors are certified with DB2 (AS 400) , DB2 UDB (DB2 v9.7.0.5) and Microsoft SQL Server 2008 source databases.

  • People Soft 92 HCM is certified with Microsoft SQL Server 2014 source databases.

  • People Soft 90 SIA (Student Information Analytics) is certified with Microsoft SQL Server 2012 source databases.

Perform these steps in order:

  1. Export Security Settings from Original ODI Repository.
  2. Exporting Topology Settings from Original ODI Repository.
  3. Create a New Master ODI Repository.
  4. Connect to the New Master ODI Repository.
  5. Create a New Work Repository.
  6. Import Source Adaptor Metadata Content into the New ODI Repository.
  7. Import Security Settings Into the ODI Repository.
  8. Importing Connection Details Which Configures the Data Servers.
Next Steps:

In Oracle BI Applications Configuration Manager, register sources, configure parameters, and generate load plans.

Note:

After you perform these procedures for a particular source and you then want to add a new source, you only need to perform the steps in Importing Source Adapter Metadata Content into the New ODI Repository. This is true regardless of the database technology of the second source.

For example, if you have a PeopleSoft 9.0 source on a SQL Server database, then you would perform the steps in Exporting Security Settings from Original ODI Repository through Importing Connection Details Which Configures the Data Servers. If you then wanted to add a second source, for example Siebel 8.1 (on an Oracle, DB2, or SQL Server database), you would only need to perform the steps in Importing Source Adapter Metadata Content into the New ODI Repository.