Beruflich Dokumente
Kultur Dokumente
BI Applications 11.1.1.7.1 introduced a number of changes; adding new components and processes and enhancing
others. As a result many customers and partners are re-learning how to install, configure and manage the application
and naturally a number of questions have arisen. This post walks through the steps of registering a source
application system in BI Applications, and then looks a little deeper into what has actually been setup behind the
scenes and how to troubleshoot those connections.
In the second page of the wizard the physical connections for the source are setup. Each source system has both a
relational and a flat file technology associated with it. Most ETL tasks extract from the source database but several
ETL tasks extract from flat files that are associated with that particular source system. The relational and flat file
details are registered directly into ODI as separate Data Servers and each Data Server must have a unique name.
When configuring the relational connection, you are defining the details required to connect to the source system.
The ETL process will use this information to connect to the source system in order to extract data. First give a name
for theODI Data Server Name, as discussed this needs to be unique so an example might be: EBS R12.1 EMEA
Dev Database. Next give the details required to connect to the source application database using a JDBC
connection, i.e. the JDBC URL, the Database Username and Database Password. For example, to connect to an
E-Business Suite database you generally provide the APPS database user and corresponding password, and to
connect to a Siebel database you provide the SIEBEL database user. To clarify, these are neither the database
details and credentials to connect to the BI Apps Component Repository database schema nor the BI Applications
Data Warehouse database schema.
You must also define the details for the Flat File connection. A value for the ODI Data Server Name must be
provided, this must be distinct from the the relational connection an example for this connection might be: EBS R12.1
EMEA Dev Source Files. The Host Name is the machine where the flat files are stored this host must be
accessible by the ODI agent. This is generally the same machine where ODI Agent is deployed or a network path
accessible from that machine. Path to file is a relative or absolute path to the location where the files associated
with the source system can be found. Each source system needs to have its own dedicated subfolder under the
SrcFiles folder.
Physical Schema
Physical Schema
2.
3. Restart the ODI Agent. The ODI Agent does not automatically reflect changes to the connection. You must
restart the ODI agent otherwise it will continue to use the old credentials. The ODI Agent can be restarted from
Enterprise Manager or the WebLogic Server Console
Restarting the ODI Agent from Enterprise Manager:
Connect to Enterprise Manager and under Deployments scroll down and drill on oraclediagent
Click on the Application Deployment menu option and select Shut Down and Start Up
When registering a source in BIACM, we assume the database user defined is the owner of the OLTP tables or at
least the users schema is populated with objects that can be selected from. ODI will generate SQL in the form:
SELECT FROM <Database User Defined in BIACM>.TABLE
If you define a read-only user that has select privileges on the OLTP tables but there are no objects in this users
schema, the SQL will fail with Table or View not found errors. You must populate this users schema with objects
that can be selected from either replicas of the actual tables that are populated with data else with synonyms or
views that point to the actual tables in the base schema. Otherwise, you must go into the ODI Studio and update the
physical schema under the OLTP data server definition and provide the schema name where the tables can be
found. This will allow ODI to log on with the alternate ETL user but generate SQL in the following form:
SELECT FROM <Base Schema>.TABLE
A future blog article will provide more information on how to configure an alternate ETL user. The most important
thing to be aware of is that in some cases, ETL tasks may execute packages or procedures on the OLTP database
(this is most commonly done when extracting from an Oracle eBusiness Suite database) you must be sure to grant
Execute privileges on these to your ETL user.