| Oracle® Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications 11g Release (11.1.1) Part Number E16814-02 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications 11g Release (11.1.1) Part Number E16814-02 |
|
|
PDF · Mobi · ePub |
This chapter provides instructions for setting up Oracle Business Intelligence Applications (Oracle BI Applications) after installing it as part of the Oracle Fusion Applications installation and provisioning process.
This chapter contains the following sections:
Note:
This chapter provides instructions for deploying Oracle BI Applications into a single BI domain with the WebLogic Administration Server and Managed Server in the same domain home. To deploy Oracle BI Applications components for high availability, see "Configuring Oracle Business Intelligence Applications" in Oracle Fusion Applications Enterprise Deployment Guide.Before you set up Oracle BI Applications, do the following:
Review the Certification Document for Oracle BI Applications and ensure that your environment meets the listed requirements:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Install Oracle BI Applications using the Oracle Fusion Applications installation and provisioning process. See Oracle Fusion Applications Installation Guide.
Read Chapter 3, "Pre-installation and Pre-deployment Requirements for Oracle BI Applications."
Read Section 4.2, "Overview of Setting Up Oracle BI Applications".
After you complete the tasks listed above, proceed to Section 4.3, "Setting Up Oracle BI Applications" for detailed instructions on how to set up Oracle BI Applications.
This section provides an overview for setting up Oracle BI Applications, and includes the following topics:
Section 4.2.2, "About the Components in an Oracle BI Applications Environment"
Section 4.2.4, "Overview of Tasks for Setting Up Oracle Business Intelligence Applications"
Oracle Business Intelligence Enterprise Edition is installed and provisioned as part of the Fusion Applications install and provisioning process. The BI Provisioning step creates a WebLogic domain, the BI Web application (J2EE) components, and the BI Server and BI Presentation Services, which are deployed on the computer that hosts the domain. The resulting environment is referred to as the "Business Intelligence domain" or "BI Domain".
The following occur as part of the Oracle Business Intelligence provisioning that occurs during Fusion Applications installation and provisioning:
Analytics View Objects and the BI Broker servlet are deployed to the appropriate Fusion Applications WebLogic domains.
The following are configured in the BI metadata repository file (OracleBIApps.rpd):
WebLogic connection pools for the three applications pillars
SQL Bypass connections FSCM_OLTP, CRM_OLTP, HCM_OLTP, and FBI_OLTP
Static Variables
The security roles required by Oracle BI Applications and Oracle Transactional Business Intelligence are provisioned.
For Oracle BI Applications, the software components of Oracle BI Applications are installed in the Business Intelligence Oracle Home but are not deployed.
This chapter describes the steps required to additionally install and set up the Oracle BI Applications components.
The following figure shows the main tools and components that you set up in an Oracle BI Applications environment:
Tools
Informatica PowerCenter Clients - use the third-party Informatica PowerCenter Client tools to set up the Informatica platform, and make ETL customizations if required.
Oracle BI Applications Configuration Manager - a Web application used to perform some system setup, manage functional setup data.
Functional Setup Manager - a Web application leveraged by Oracle BI Applications Configuration Manager that is used to configure Offerings using guided Tasks.
DAC Client - orchestrates the ETL process and configures the DAC Server.
BI Administration Tool - a Windows client tool used to manage BI metadata repositories.
Components
Informatica PowerCenter Services - third-party Informatica PowerCenter server that is used to perform ETL.
Informatica Repository - prebuilt ETL logic for each BI Application.
Functional Setup Data - Functional Configuration choices made in Functional Setup Manager and monitored in Configuration Manager.
OLTP data source - transactional data in the Fusion Applications source system.
DAC Server - Data Warehouse Administration Console server that is used to orchestrate ETL processes.
BI Presentation Services Catalog - prebuilt reports and dashboards, common file for Oracle Transactional Intelligence, and Oracle BI Applications.
Oracle Business Analytics Warehouse - the target data warehouse into which source system data is loaded.
DAC Repository - stores the metadata that represents the data warehouse processes.
Oracle BI Presentation Services - provides the framework and interface for the presentation of Business Intelligence data to Web clients.
Oracle BI Server - provides the query and data access capabilities at the heart of Oracle Business Intelligence, and provides services for accessing and managing the enterprise semantic model (stored in a file with an .rpd extension).
The following table defines the Home directories for the components in an Oracle BI Applications deployment:
Table 4-1 Summary of Home Directories for Oracle BI Applications
| Home Directory | Description |
|---|---|
|
Location of the Oracle WebLogic BI Domain (for example, /instance/domains/hostname/BIDomain). |
|
|
Location of the user-specified Informatica installation directory on the computer that hosts Informatica PowerCenter (for example,\informatica\861\). |
|
|
Location of the Oracle Fusion Middleware home (for example,\FMW_11g\). It includes the WebLogic home and one or more Oracle homes. |
|
|
This is the root directory of Oracle Business Intelligence. For example, the Oracle home for Oracle Business Intelligence is typically MW_HOME/Oracle_BI1. |
|
|
Location of the Oracle Instance home (for example, MW_HOME\Oracle_BI1\instances\instance1). |
To properly set up Oracle BI Applications, you must complete the following tasks, in order:
Create databases for the Oracle Business Analytics Warehouse, DAC Repository, and Informatica Repository. See Section 4.3.1, "Step 1: Create the Required Database."
Create the required Oracle BI Applications schemas (DAC Repository schema and Oracle Business Analytics Warehouse schema). Also, if you have implemented the Sales Prediction Engine module of Oracle Fusion Customer Relationship Management, run the Sales Prediction Engine RCU to create Oracle Business Analytics Warehouse objects. See Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications"and Section 4.3.2.2, "Creating Data Warehouse Objects with the Oracle Sales Prediction Engine RCU."
Apply seed data patches, which are required for Oracle BI Applications. See Section 4.3.3, "Step 3: Apply Patches."
Install and configure Informatica PowerCenter, which includes Informatica PowerCenter Client and Informatica PowerCenter Services. See Section 4.3.4, "Step 4: Install and Set Up Informatica PowerCenter."
Install the BI Administration Tool. See Section 4.3.5, "Step 5: Install Oracle BI Administration Tool."
Extend the BI Domain by deploying Configuration Manager, Functional Setup Manager, and DAC Server. See Section 4.3.6, "Step 6: Extend the BI Domain."
Configure connection pools in the RPD using the provided Python script. See Section 4.3.7, "Step 7: Configure the Oracle BI Repository File (RPD)."
Grant user access to Oracle BI Applications components. See Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components."
Create a user for running ETL. See Section 4.3.9, "Step 9: Create a User for ETL."
Configure Oracle HTTP Server. See Section 4.3.10, "Step 10: Configure Oracle HTTP Server."
Configure single sign-on (SSO) for Configuration Manager and Functional Setup Manager. See Section 4.3.11, "Step 11: Configure SSO for Configuration Manager and Functional Setup Manager."
Install the DAC Client on a Windows-based computer where the Informatica PowerCenter Client Tools are installed. See Section 4.3.12, "Step 12: Install the DAC Client."
Configure the DAC Server URL. See Section 4.3.13, "Step 13: Configure the DAC Server URL."
Register Informatica in DAC. See Section 4.3.14, "Step 14: Configure DAC Integration Settings."
Configure Physical Data Source connections in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Configure Relational connections in Informatica. See Section 4.3.16, "Step 16: Configure Relational Connections in Informatica."
Set SiebelUnicodeDB property in Informatica Integration Services. See Section 4.3.17, "Step 17: Set SiebelUnicodeDB Property in Informatica Integration Services."
Enable user currency preferences. See Section 4.3.18, "Step 18: Enable User Currency Preference Settings."
Trim and merge the RPD. See Section 4.3.19, "Step 19: Optimize the Repository File (RPD) for Oracle BI Applications."
Register Sources and enable Offerings in Configuration Manager. See Section 4.3.20, "Step 20: Register Source Systems and Enable Offerings."
Set languages for data load in Configuration Manager. See Section 4.3.21, "Step 21: Set Languages for Data Load."
Run Domains ETL. See Section 4.3.22, "Step 22: Run Domains ETL."
Verify that Duty Roles Exist for Oracle BI Applications. See Section 4.3.23, "Step 23: Verifying Duty Roles required for Oracle BI Applications."
This section provides detailed instructions on the tasks for setting up Oracle BI Applications. Before you complete the tasks described in this section, ensure that your environment meets the prerequisites and that you understand the recommendations described in Section 4.1, "Before You Set Up Oracle BI Applications."
This section contains the following topics:
Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications"
Section 4.3.4, "Step 4: Install and Set Up Informatica PowerCenter"
Section 4.3.5, "Step 5: Install Oracle BI Administration Tool"
Section 4.3.7, "Step 7: Configure the Oracle BI Repository File (RPD)"
Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components"
Section 4.3.11, "Step 11: Configure SSO for Configuration Manager and Functional Setup Manager."
Section 4.3.14, "Step 14: Configure DAC Integration Settings"
Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC"
Section 4.3.16, "Step 16: Configure Relational Connections in Informatica"
Section 4.3.17, "Step 17: Set SiebelUnicodeDB Property in Informatica Integration Services"
Section 4.3.18, "Step 18: Enable User Currency Preference Settings"
Section 4.3.19, "Step 19: Optimize the Repository File (RPD) for Oracle BI Applications"
Section 4.3.20, "Step 20: Register Source Systems and Enable Offerings"
Section 4.3.23, "Step 23: Verifying Duty Roles required for Oracle BI Applications"
Install Oracle Database 11.2.0.2 or later for Oracle Business Analytics Warehouse, the DAC Repository, the Informatica Repository, and the Informatica Domains Repository. For more information, including the list of supported database versions, see the Oracle Fusion Applications system requirements and supported platforms documentation.
Ensure your Oracle Database instance is configured for the ALT32UTF8 character set. Also, this release supports the data movement mode Unicode to Unicode. For more information, see Section 3.4, "Code Page and Data Movement Requirements."
For the database that hosts Oracle Business Analytics Warehouse, perform the following additional steps:
Apply database patches 9739315 and 9255542
For additional database guidelines for the Oracle Business Analytics Warehouse, see Chapter 3, "Pre-installation and Pre-deployment Requirements for Oracle BI Applications".
For prerequisite information for the Informatica Repository and Informatica Domains Repository databases, see the Informatica Installation Guide. Informatica documentation is included in the Informatica files provided in the Oracle Fusion Applications Media Pack on eDelivery. See Section 4.3.4.2, "Locations of Installation Files for Informatica PowerCenter and Hotfix 11."
Oracle BI Applications requires the following database schemas, which you create with the Oracle BI Applications edition of the Repository Creation Utility (RCU):
If your organization has deployed the Sales Prediction Engine module of Oracle Fusion Customer Relationship Management, you must also create data warehouse database objects using the Sales Prediction Engine RCU.
To continue, refer to the following topics:
Section 4.3.2.1, "Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU"
Section 4.3.2.2, "Creating Data Warehouse Objects with the Oracle Sales Prediction Engine RCU"
Use the Oracle BI Applications RCU to create the Oracle BI Data Warehouse Administration Console and Oracle Business Analytics Warehouse schemas, which are required by Oracle BI Applications.
Before you create Oracle BI Applications schemas using the Oracle BI Applications RCU, ensure that you understand the following:
The Oracle BI Applications RCU supports Oracle Database 11.2 and later, as described in Section 4.3.1, "Step 1: Create the Required Database." The database in which you create the RCU schemas must meet the minimum requirements specified in the Certification Document for Oracle BI Applications:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
On the database where you intend to create the Oracle BI Applications schemas, ensure the following grant is given to PUBLIC:
grant execute on UTL_FILE to PUBLIC;
To create schemas with RCU on Oracle databases, you must possess the DBA privilege and be logged in as SYSDBA (for example, as user SYS). Although you can use another database user that has been granted the SYSDBA role, this is not recommended. Using database users other than SYS requires additional steps, which are described in "RCU Requirements for Oracle Databases" in Oracle Fusion Middleware System Requirements and Specifications.
When you run RCU, you create databases schemas and tablespaces using CREATE ANY SCHEMA, ALTER ANY SCHEMA, CREATE TABLE, CREATE TABLESPACE, and so on. RCU updates the schema_version_registry by writing entries to the system.schema_version_registry$ system table.
Before running the Oracle BI Applications RCU to create database schemas, you must transfer dump files (.dmp) for these schemas to a directory on the computer that hosts your database. The required dump files are for the following products:
Oracle Business Analytics Warehouse (obia.dmp), which includes the Oracle BI Applications Configuration Manager repository and the Oracle Functional Setup Manager repository.
Oracle Business Intelligence Data Warehouse Administration Console (dac.dmp), which includes the Oracle Business Intelligence DAC repository.
These dump files can be found in the following locations:
If you downloaded and extracted the Oracle Business Intelligence Applications RCU .zip file, access the following directory:
BIA_RCU_HOME/rcu/integration/biapps/schema
where BIA_RCU_HOME is the directory where you unzipped the Oracle BI Applications RCU installation package.
If you have the Oracle Business Intelligence Applications RCU CD-ROM, insert the CD-ROM into your computer and access the following directory:
/rcu/integration/biapps/schema
Ensure that the directory where you transfer or copy the dump files has global write access. RCU writes log files to this directory.
To create the Oracle BI Applications database schemas using the Oracle BI Applications RCU:
Do one of the following:
If you downloaded and extracted the Oracle Business Intelligence Applications RCU .zip file, access the bin directory in the BIA_RCU_HOME.
If you have the Oracle Business Intelligence Applications RCU CD-ROM, insert the CD-ROM into your computer and access the bin directory.
Start RCU:
UNIX:
./rcu
Windows:
rcu.bat
The Welcome screen opens.
In the Welcome screen, click Next.
In the Create Repository screen click Create, and then click Next.
In the Database Connection Details screen, specify the connection details for the database in which you want to store the schemas.
Specify the following database connection details:
Table 4-2 Specifying Database Connection Details for RCU
| Field Name | Action |
|---|---|
|
Database Type |
Click Oracle Database. Other database types are not supported in this release. |
|
Host Name |
Specify the fully qualified host name of the computer hosting the database. For example, |
|
Port |
Specify the number of the communication port for the database. 1521 is the default port number for Oracle Database. |
|
Service Name |
Specify the database account name or the Service Name for the database. For example, |
|
Username |
Specify the username for accessing the computer that hosts the database. For example, |
|
Password |
Specify the password for the username specified in the Username field. |
|
Role |
If this value is not SYS, then you must select SYS. The default value is selected automatically when you enter a username in the Username field. |
Click Next. The Checking Prerequisites screen opens.
After the prerequisite checks conclude with no errors, click OK to dismiss the screen and proceed to the Select Components screen.
In the Select Components screen, near the top of the screen, select Create a new Prefix. The default prefix is DEV. You can provide another prefix, if preferred.
RCU automatically creates schema names in the format prefix_schemaname. For example, if you enter the prefix DEV11G, RCU creates the Oracle Business Analytics Warehouse schema with the name DEV11G_DW. Make a note of these schema names and the prefix values from this screen.
Expand the Oracle BI Applications Schemas group, and then click the Oracle Data Warehouse Administration Console (DAC), and the Oracle Business Analytics Warehouse (DW) schemas only.
Do not select the Oracle Transactional BI (OTBI) schema.
Click Next. The Checking Prerequisites screen opens. After the prerequisite checks conclude with no errors, click OK to dismiss the screen and proceed to the Schema Passwords screen.
In the Schema Passwords screen, select Use same password for all schemas, and provide and confirm a password for the schemas.
Click Next to proceed to the Custom Variables screen.
In the Custom Variables screen, enter the locations of the dump files in the Value field for each schema. For example, if the dump files are located in a Linux directory named /tmp on the database computer, enter /tmp in the Value field.
Click Next to proceed to the Map Tablespaces screen.
In the Map Tablespaces screen, confirm the schema names. For more information, especially for tablespace recommendations, see Section 3.1, "Oracle-Specific Database Guidelines for Oracle Business Analytics Warehouse."
Click Next to create the tablespaces for the schemas. After the tablespaces are created with no errors, click OK to dismiss the screen and proceed to the Summary screen.
In the Summary screen, click Create. The Create screen opens and RCU creates the schemas. After the schemas are created with no errors, the Completion Summary screen opens.
In the Completion Summary screen, click Close.
Use the Sales Prediction Engine RCU to create data warehouse database objects (ODM tables, views, packages, ILS Processing tables, and so on) in the Oracle Business Analytics Warehouse. This is required if the Sales Prediction Engine module of Oracle Fusion Customer Relationship Management was deployed.
Before you create the data warehouse database objects, ensure that you have a supported Oracle Business Analytics Warehouse that contains the Oracle BI Applications schemas. See Section 4.3.2.1, "Creating Oracle BI Applications Schemas Using Oracle BI Applications RCU."
To create the Sales Prediction Engine schema with the Sales Prediction Engine RCU, see "Setting Up Sales Prediction Engine" in Oracle Fusion Applications Post-Install Guide.
Before continuing, you must apply seed data patches for Oracle BI Applications. For the list of required patches and instructions on how to apply them, see the Oracle BI Applications chapter in Oracle Fusion Middleware Release Notes.
To install and set up Informatica PowerCenter for an Oracle BI Applications environment, complete the following tasks, in order:
Read the installation considerations in Section 4.3.4.1, "Before Installing Informatica PowerCenter for Oracle BI Applications Environments"and the prerequisites in Section 4.3.4.3, "Prerequisites for Installing Informatica PowerCenter for Oracle BI Applications Environments.".
Install the Informatica PowerCenter software:
Note: If you have licensed Informatica PowerCenter separately from Oracle BI Applications, skip this step and continue with step 4.
Install Informatica PowerCenter Client Tools. See Section 4.3.4.4, "Installing Informatica PowerCenter Client Tools (Windows)."
Install Informatica PowerCenter Client Services. See Section 4.3.4.5, "Installing Informatica PowerCenter Services and Hotfix 11."
Install and configure database connectivity software. See Section 4.3.4.6, "Install and Configure Database Connectivity Software."
Create an Informatica PowerCenter Repository Service. See Section 4.3.4.7, "Creating the Informatica Repository Service."
Create an Informatica PowerCenter Integration Service. See Section 4.3.4.8, "Creating the Informatica Integration Service."
Load the prebuilt Informatica Repository that is required for Oracle BI Applications. See Section 4.3.4.9, "Restoring the Prebuilt Informatica Repository."
Set up the Informatica source files. See Section 4.3.4.10, "Copying Source Files to the Informatica PowerCenter Services Computer."
Set up Relaxed Code Page Validation. See Section 4.3.4.11, "Setting PowerCenter Integration Services Relaxed Code Page Validation."
Set up Integration Services Properties. See Section 4.3.4.12, "Setting PowerCenter Integration Services Custom Properties."
Create a Repository Administrator User in a native security domain. See Section 4.3.4.13, "Creating the Repository Administrator User in the Native Security Domain."
Set up the Informatica Domain and Repository. See Section 4.3.4.14, "Accessing Informatica Domain and Repository from Informatica Client Tools."
Before you install and configure Informatica PowerCenter for an Oracle BI Applications environment, consider the following:
Determine which computers will host Informatica PowerCenter Client Tools and Informatica PowerCenter Services. The PowerCenter Services can be installed on UNIX or Windows. The PowerCenter Client Tools must be installed on Windows.
DAC uses the Informatica pmrep and pmcmd command line programs to communicate with the Informatica Integration Service and the Repository Service. For these reasons, you must do one of the following:
Collocate the DAC Server with the PowerCenter Services and the DAC Client with the Informatica Client.
Make the Informatica binaries, domains.infa file, and the DAC Server available on shared network locations.
DAC produces parameters files that are consumed by Informatica. By default, the parameter files are produced in the following location:
DOMAIN_HOME\dac\Informatica\parameters
You must either share this location so that Informatica PowerCenter Services has read and write access, or configure an alternate shared location to which both the DAC Server and Informatica PowerCenter Services have read and write access.
You must meet all requirements and complete preinstallation tasks as described in Section 4.3.4.3, "Prerequisites for Installing Informatica PowerCenter for Oracle BI Applications Environments" and in the chapter "Before You Install" of the Informatica PowerCenter Installation Guide. For information on the location of the Informatica documentation, see Section 4.3.4.2, "Locations of Installation Files for Informatica PowerCenter and Hotfix 11."
When you install PowerCenter Services and Client Tools version 8.6.1 and Hotfix 11, use the Informatica PowerCenter installation documentation in conjunction with the steps provided in the following sections. This chapter summarizes the steps to install Informatica PowerCenter and assumes a single-computer installation for the PowerCenter Services components. For information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica, see Certification Document for Oracle BI Applications:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
The Informatica PowerCenter 8.6.1 and HotFix 11 installation files, license key, and user documentation are provided as zip files. These zip files are available for download in the Fusion Applications Media Pack on eDelivery.
For example, the following files are included as part of the Fusion Applications Media Pack for Linux x86 64-bit operating system:
infa_linux_x86-64_64bit_861_1of2.zip
infa_linux_x86-64_64bit_861_2of2.zip
The first zip file in each media pack (1of2.zip) includes the Server and Client install files. The second zip file (2of2.zip) includes the Informatica documentation, the license key, and HotFix 11 installation files.
Oracle BI Applications 11g Release (11.1.1) requires Informatica PowerCenter 8.6.1 with Hotfix 11. For information on where to obtain the installation files, see Section 4.3.4.2, "Locations of Installation Files for Informatica PowerCenter and Hotfix 11."
Note:
For information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica, see the Certification Document for Oracle BI Applications:http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
If you license Informatica PowerCenter separately and you do not have Informatica PowerCenter 8.6.1 and Hotfix 11, you must upgrade your Informatica PowerCenter license to 8.6.1 and Hotfix 11 before deploying Oracle BI Applications.
Also, please note Informatica PowerCenter Services runs on 32-bit or 64-bit platforms. For more information about these two platforms, see the Certification Document for Oracle BI Applications:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
This section explains how to install Informatica PowerCenter 8.6.1 Client Tools and Hotfix 11 for an Oracle BI Applications deployment. For detailed generic information about installing Informatica 8.6.1, refer to the Informatica PowerCenter Installation Guide. For the locations of the installation files for Informatica PowerCenter and Hotfix 11, see Section 4.3.4.2, "Locations of Installation Files for Informatica PowerCenter and Hotfix 11." For information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica, see the Certification Document for Oracle BI Applications:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
To install Informatica PowerCenter Client Tools on Windows:
Run the program install.bat from the root directory where you unzipped the PowerCenter Client Tools 8.6.1 install package.
Follow the instructions in the Informatica PowerCenter Client 8.6.1 installation wizard. For more information, see Chapter 4, "Client Installation" in Informatica PowerCenter Installation Guide.
Install Informatica PowerCenter Hotfix 11 by running install.bat from the root directory where you unzipped the hotfix package. Follow the prompts to complete the installation. For more information, see the Informatica PowerCenter Version 8.6.1 HotFix Release Notes.
This section explains how to install Informatica PowerCenter Services 8.6.1 and Hotfix 11 for an Oracle BI Applications deployment. For detailed generic information about installing Informatica 8.6.1, see Informatica PowerCenter Installation Guide. For the locations of the installation files for Informatica PowerCenter and Hotfix 11, see Section 4.3.4.2, "Locations of Installation Files for Informatica PowerCenter and Hotfix 11." For information about additional hotfixes or emergency bug fixes that may be required to support the current version of Informatica, see the Certification Document for Oracle BI Applications:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
Note:
If you have purchased the 'Informatica OEM PowerCenter ETL Server and PowerConnect Adapters' license from Oracle, use the Oracle_All_OS_Prod.key license key file. This file is located in the DVD root directory of the Informatica PowerCenter folder included in the Fusion Applications media pack on eDelivery.
On Windows, do not install Informatica in a directory that has a space in the directory name. For example, do not install in D:\Program Files\INFA. If you install into a directory with a space in the name, you will cause errors in DAC.
To install Informatica PowerCenter Services 8.6.1 and Hotfix 11:
Start the Informatica PowerCenter Services installer, depending on your operating system:
To start the installer on Windows, run the file install.bat from the root directory where you unzipped the PowerCenter Services 8.6.1 installation package.
To start the installer on UNIX or Linux, use a shell command line to run install.sh from the root directory where you untarred the PowerCenter Services 8.6.1 installation package.
On UNIX or Linux, select the option to use the GUI mode installation.
Follow the instructions on the Informatica PowerCenter Services installation wizard.
For more information, see Chapter 3, "PowerCenter Installation" in the Informatica PowerCenter Installation Guide.
Stop any Informatica services that are running.
Install the Informatica PowerCenter Hotfix 11 by running install.bat or install.sh from the root directory where you unzipped or untarred the hotfix package. Follow the prompts to complete the installation.
For more information, see the Informatica PowerCenter Version 8.6.1 HotFix Release Notes.
You must install and configure the appropriate database connectivity software, Oracle Database Client, on the computers that host the Informatica PowerCenter Integration Service and Repository Service.
The PowerCenter Integration Services requires connectivity to the Oracle Business Analytics Warehouse (target) database. The Integration Service uses native connectivity to access the Oracle Business Analytics Warehouse. This native connection is also used by Integration Services to connect to the Oracle BI Applications Configuration Manager tables, which reside in the prefix_DW schema.
The PowerCenter Repository Service requires native connectivity to communicate with the Informatica Repository database.
To install and configure the Oracle Database Client:
On the computer or computers that host the Integration Services and Repository Service, install the Oracle Database Client.
Refer to the following topics in the Informatica PowerCenter Configuration Guide:
For Integration Service or Repository Service installed on Windows computers, see the section entitled "Configuring Native Connectivity" in Chapter 10, "Connecting to Databases from Windows."
For Integration Service or Repository Service installed on Linux or UNIX computers, see the section entitled "Configuring Native Connectivity" in Chapter 11, "Connecting to Databases from UNIX."
Note:
You must configure the environmental variables on Linux or UNIX as described in the Informatica documentation.On the computer that hosts the Integration Service, create a tnsnames.ora entry for the prefix_DW schema. On the computer that will host the Repository Service, create a tnsnames.ora entry for the Informatica Repository.
For additional information about database connectivity for Integration Services and Repository Services, see the topic entitled "Install and Configure Database Client Software," in Chapter 2, "Before You Install," in the Informatica PowerCenter Installation Guide.
Follow the procedure in this section to create the Informatica Repository Service.
For detailed information about creating the Repository Service, see the topic titled, "Creating the Repository Service," in "Chapter 7: Creating and Configuring the Repository Service," in the Informatica PowerCenter Administrator Guide.
To create the Informatica Repository Service:
Open the Informatica PowerCenter Administration Console.
On the left side of the Administration Console, click Create, and then click Create Repository Service.
In the Create New Repository Service dialog box, specify the appropriate values for the required properties. For a description of the required properties, see "Creating the Repository Service," in Chapter 7, "Creating and Configuring the Repository Service," in the Informatica PowerCenter Administrator Guide.
In particular, note the following properties:
For the Code Page, select UTF-8 encoding of Unicode.
Note: The code page of the Repository Service cannot be changed once the Repository Service has been created.
For the Creation Mode, ensure you select Create New Repository Content.
Follow the procedure in this section to create the Informatica Integration Service.
For detailed information about creating the Integration Service, see the topic titled "Creating an Integration Service" in Chapter 9, "Creating and Configuring the Integration Service," in the Informatica PowerCenter Administrator Guide.
To create the Informatica Integration Service
Open the Informatica PowerCenter Administration Console.
On the left side of the Administration Console, click Create, and then click Create Integration Service.
In the Create New Integration Service dialog box, specify the appropriate values for the required properties.
For a description of the required properties, see the topic titled "Creating an Integration Service" in Chapter 9, "Creating and Configuring the Integration Service," in the Informatica PowerCenter Administrator Guide.
In particular, note the following properties:
Associated Repository Service: Select the Repository Service you created in Section 4.3.4.7, "Creating the Informatica Repository Service."
Data Movement Mode: Select Unicode.
During the Oracle BI Applications installation, an Informatica Repository file named Oracle_BI_DW_Base.rep is installed into the ORACLE_HOME directory.
To restore the prebuilt Informatica Repository:
In an English environment, follow the steps in Section 4.3.4.9.1, "Restoring the Prebuilt Informatica Repository for Environments in English"
In an non-English environment, follow the steps in Section 4.3.4.9.2, "Restoring the Prebuilt Informatica Repository on a Non-English Operating System"
You use the Restore option in Informatica PowerCenter Administration Console to load the prebuilt Oracle_BI_DW_Base repository.
To load the prebuilt Oracle_BI_DW_Base.rep repository into Informatica:
Copy the file ORACLE_HOME/biapps/admin/provisioning/dac/infabaseline/Oracle_BI_DW_Base.rep file on the installation computer to the following directory on the computer where Informatica PowerCenter Services is installed:
On Windows, copy the file to the INFA_HOME\server\infa_shared\Backup directory.
On UNIX or Linux, copy the file to INFA_HOME/server/infa_shared/Backup directory.
Note: for more information about Oracle home locations, see Section 4.2.3, "Summary of Home Directories"
In Informatica PowerCenter Administration Console, select the Repository Service that was created in the procedure in Section 4.3.4.7, "Creating the Informatica Repository Service"
In the General Properties area of the Properties tab, ensure the OperatingMode value is Exclusive.
To change the OperatingMode value, click Edit, and then select a new value from the drop-down list. Click OK to exit edit mode.
In the Actions menu at the top right-hand side, click Actions, and then click Delete Contents.
If prompted, enter the repository username and password (for example, Administrator\Administrator), and then click OK.
In the Actions menu at the top right-hand side, click Actions, then Repository Contents, then Restore.
At the Restore Contents for repository_name dialog, enter the repository username and password (for example, Administrator\Administrator), and then click OK.
Click Actions, and then click Restore Contents.
At the Restore Contents dialog, select Oracle_BI_DW_Base.rep from the Select Backup File drop-down list.
Select the Restore as New check box.
Click OK to start the restore process.
When the restore process is complete, click Close (or click Save first, to save the logging information).
When the restore is complete, you will see a "Success" message. The process typically takes from ten to twenty minutes.
When a repository is restored, the repository becomes a standalone repository. After restoring the repository, you need to promote it to a global repository.
For instructions, see the topic titled "Promoting a Local Repository to a Global Repository" in Chapter 8, "Managing the Repository," in Informatica PowerCenter Administrator Guide.
Change the OperatingMode value to Normal.
Go to the Properties tab.
In the General Properties area, click Edit.
Click the OperatingMode drop-down list, and click Normal.
Note:
If you do not set the Operating Mode to Normal, the Integration Service will not restart.If prompted, enter the repository username and password.
If Informatica PowerCenter Services is installed on a non-English version of the operating system, you must use the command line to restore the prebuilt Informatica Repository provided with Oracle BI Applications.
To restore the prebuilt Informatica Repository on a non-English operating system:
Copy the ORACLE_HOME/biapps/admin/provisioning/dac/infabaseline/Oracle_BI_DW_Base.rep file on the installation computer to the following directory on the computer where Informatica PowerCenter Services is installed:
On Windows copy the file to the INFA_HOME\server\infa_shared\Backup directory.
On UNIX or Linux copy the file to INFA_HOME/server/infa_shared/Backup directory.
Note:
For more information about Oracle home locations, see Section 4.2.3, "Summary of Home Directories"Open a command window.
Enter the following command to connect to the repository:
Pmrep connect -r Repository_Name -d Domain
Enter the following command to restore the repository:
PmRep restore -u Domain_User_Name -p Domain_User_Password -i Input_File_Name -n
where theInput_File_Name is the name of the prebuilt repository file.
You need to copy source files from the Oracle BI Applications installation directory to the Informatica directory on the Informatica PowerCenter Services computer.
Note: The following instructions assume the default Informatica directory locations for source files.
The default Informatica directory for source files is INFA_HOME\server\infa_shared\SrcFiles. You can confirm the source file directory for your environment by launching the PowerCenter Administration Console and going to the General Properties area of the Processes tab. The parameter name for the source file directory is $PMSourceFileDir.
Note: The value of the $PMSourceFileDir parameter must match the DAC system property called InformaticaParameterFileLocation. You will set this property later in the set up process, using the instructions in Section 4.3.14.1, "Setting DAC System Properties".
Before you start
After installation, the Source Files and other ETL-related files required for Informatica PowerCenter are located in the following ZIP file:
ORACLE_HOME\biapps\etl\biapps_etl.zip
Extract the files in biapps_etl.zip into the following location:
ORACLE_HOME\biapps\etl\biapps_etl\
You extract the following directory:
ORACLE_HOME\biapps\etl\biapps_etl\data_files\src_files
Copying the source files
To copy source files to Informatica PowerCenter Services:
Copy the source files as follows:
From:
ORACLE_HOME\biapps\etl\biapps_etl\data_files\src_files
To:
INFA_HOME\server\infa_shared\SrcFiles
Note:
If Informatica PowerCenter Services is installed on a UNIX or Linux computer, convert the target paths above from Windows to UNIX/Linux. For example, covert the Windows target path:From:
INFA_HOME\server\infa_shared\SrcFiles
To:
INFA_HOME/server/infa_shared/SrcFiles
PowerCenter Integration Services must be configured for relaxed code page validation. For more information, refer to section Understanding Globalization Relaxed Code Page Validation in Informatica Administrator Guide.
To configure Informatica PowerCenter Integration Services for relaxed code page validation:
Log in to Informatica Administrator.
Click the Integration Service.
Click the Properties tab.
In the Configuration Properties area, click Edit.
Deselect the ValidateDataCodePages check box.
Follow the procedure in this section to set PowerCenter Integration Services custom properties.
To set Informatica PowerCenter Integration Services Custom Properties:
In Informatica Administrator, select the Integration Service.
Click the Properties tab.
In the Custom Properties area, click Edit.
Use the New option to display the New Custom Property dialog, and add the following Custom Properties:
Click OK to save the details.
Ensure that the Integration Service and Repository Service that you created during the Informatica PowerCenter installation are running.
For DAC to access Informatica and perform tasks in pmcmd and pmrep command line programs, DAC must log in to Informatica as an Informatica Repository Administrator user. This user must be configured in the native security domain.
You must create such a Repository Administrator user, or, if your security policies permit, you can use the default Administrator user (whose privileges include Repository administration) for DAC connectivity to Informatica.
For more information on creating users and Informatica security domains, see Chapter 4, "Managing Users and Groups," in the Informatica PowerCenter Administrator Guide.
To create a Repository Administrator defined in the native security domain:
Log in to the PowerCenter Administration Console as Administrator.
Navigate to the Security page by clicking the Configure Security icon on the top-right corner of the page.
On the Security page, click Create User, or select an existing user defined in the native domain.
Note: Do not create this user in an LDAP domain or select an existing user from an LDAP domain.
On the Privileges tab of the new or existing user, click the appropriate Repository Service.
In the Edit Roles and Privileges page, expand the Repository Service, and under System-Defined Roles, select the Administrator role check box.
Click OK.
When you first log in to any of the Informatica PowerCenter Client tools (for example, Designer, Workflow Manager), you must specify the Informatica Domain that you created when you installed Informatica PowerCenter Server. For example, you might want to log in to Informatica PowerCenter Designer to check that the Oracle BI Applications Repository has been successfully loaded.
The following tasks describe how to use Informatica PowerCenter Designer to specify an Informatica Domain and Informatica Repository. However, you can use any of the Informatica PowerCenter Client tools.
To set up the Domain:
Start Informatica PowerCenter Designer.
Click Repository, and then Configure Domain, to display the Configure Domains dialog.
Click the Add a new Domain icon to display the Add Domain dialog.
Use the Add Domain dialog to specify the following:
Table 4-4 Add Domain dialog fields
| Field Name | What to enter |
|---|---|
|
Domain Name |
Specify the name of the domain that you created when you installed Informatica PowerCenter Services (for example, BIA_RS). |
|
Gateway Host |
Specify the hostname or IP address of the Informatica Server computer that hosts the Gateway node (for example, machineA). |
|
Gateway Port |
Specify the gateway port number. For example, 6001. |
Click OK.
When you specify a valid set of Domain details, the new domain is displayed in the Domains list, and any available Repositories are displayed in the Repositories list.
In the Repositories list, select the check box for the Repository that you want to use.
To set up the Repository:
Start Informatica PowerCenter Designer.
Click the Repository, and then click Add, to display the Add Repository dialog.
In the Repository field, type the name of the Repository Service that you created in Informatica Administration Console (for example, BIA_RS), and specify Administrator as the user name.
For more information about creating the Repository Service, see Section 4.3.4.7, "Creating the Informatica Repository Service."
Click OK, to save the details and to return to the Start Page.
In the Repositories tree, double-click the Repository that you specified in the Step 3 (for example, BIA_RS).
In the Connection Settings part of the Connect to Repository dialog, ensure that the Domain field displays the domain that you specified in the previous task.
Specify Administrator as the user name and password, and then click Connect.
You can now expand the repository in the Repositories list to display the contents.
The Oracle BI Administration Tool enables you to manage the metadata repository and is required for certain steps in the Oracle BI Applications set-up process. Typically, you install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer.
Before you install the Oracle BI Administration Tool, ensure that the computer where you intend to perform the installation meets the following requirements:
The computer is running a supported Microsoft Windows operating system.
The computer has network connectivity with the computer that hosts your Oracle BI server.
For the instructions and considerations for installing the Oracle BI Administration Tool, see "Installing and Uninstalling Oracle Business Intelligence Client Tools" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
During the Fusion Applications installation and provisioning process, the BI Domain is created. However, none of the Oracle BI Applications components (Configuration Manager, DAC Server, and Functional Setup Manager) are deployed in the WebLogic BI domain. Therefore, you must extend the WebLogic BI domain to include these components. You deploy these components in WebLogic using the following python configuration scripts:
The install_dwtools.py and configure_dwtools.py scripts, along with the other Oracle BI Applications scripts, can be found in ORACLE_HOME/dwtools/scripts. However, the version of the WebLogic Scripting Tool (wlst) that must be used can be found in ORACLE_HOME/common/bin.
ATG, a J2EE component used by Configuration Manager and Functional Setup Manager, is also deployed with the install_dwtools.py and configure_dwtools.py scripts.
Configuration Manager, Functional Setup Manager, and ATG are deployed to the WebLogic Administration Server. The DAC Server is deployed to the WebLogic Managed Server. To deploy DAC into a Managed Server in a different domain home from the Administration Server, or to deploy the DAC Server for high availability, see "Configuring Oracle Business Intelligence Applications" in Oracle Fusion Applications Enterprise Deployment Guide.
Note:
Only one DAC Server application can be run against the DAC repository at one time. Therefore, the DAC Server application should be deployed to only one Managed Server. If more than one DAC Server application is run against the DAC repository, the repository will be corrupted.For information about accessing the DAC Server through the WebLogic Server Administration Console, see Section 10.9, "Monitoring the DAC Server Using WebLogic Server" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
To extend the BI domain:
Stop the Administration Server.
Run install_dwtools.py using the following syntax:
WLST_PATH install_dwtools.py 'DOMAIN_HOME' 'INFA_HOME' 'INFA_DOMAIN_FILE' 'DW_DB_CONNECT' 'DW_DB_SCHEMA' 'MDS_DB_CONNECT' 'MDS_DB_SCHEMA' 'DAC_DB_CONNECT' 'DAC_DB_SCHEMA' 'DAC_TARGET'
where:
WLST_PATH is the path to WebLogic Scripting Tool.
DOMAIN_HOME is the location of the Oracle BI domain (for example,\MW_HOME\user_projects\domains\bifoundation_domain).
INFA_SERVER_HOME is the location of the user-specified Informatica installation directory on the computer that hosts Informatica PowerCenter Services (for example,\informatica\8.6.1\).
INFA_DOMAIN_FILE is the location and name of the Informatica domains fine infa.domain on the computer that hosts Informatica PowerCenter Services (for example,\informatica\8.6.1\domains.infa).
DW_DB_CONNECT is the connection string for the database that stores the DW schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, machine12345.company.com.example:1521:BIA11G.
DW_DB_SCHEMA is the name of the DW schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, you might have specified the name DEV11G_DW.
MDS_DB_URL is the connection string for the database that stores the MDS schema. This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.company.com.example:1521:BIA11G.
MDS_DB_SCHEMA is the name of the MDS schema that was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, DEV11G_MDS.
DAC_DB_URL is the connection string for the database that stores the DAC schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, machine12345.company.com.example:1521:BIA11G.
DAC_SCHEMA is the name of the DAC schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, you might have specified the name DEV11G_DAC.
DAC_TARGET is the name of the Manager Server into which the DAC Server is deployed.
For example:
/mw_home/Oracle_BI1/common/bin/wlst.sh install_dwtools.py '/mw_home/user_projects/domains/bifoundation_domain' '/informatica' '~/informatica.infa' 'jdbc:oracle:thin:@localhost:1521/orcl' 'DEV1_DW' 'jdbc:oracle:thin:@localhost:1521/orcl' 'DEV1_MDS' 'jdbc:oracle:thin:@localhost:1521/orcl' 'DEV1_DAC' 'bi_server1'
Note:
When you run the script, you are also prompted for passwords.Start the Administration Server.
Run configure_dwtools.py using the following syntax:
WLST_PATH configure_dwtools.py 'WL_USERNAME' 'ADMIN_HOST' 'ADMIN_PORT'
where:
WLST_PATH is the path to the WebLogic Scripting Tool.
WL_USERNAME is the WebLogic username
ADMIN_HOST is the computer that hosts the Administration Server
ADMIN_PORT is the port number for the Administration Server
For example:
/mw_home/Oracle_BI1/common/bin/wlst.sh configure_dwtools.py 'weblogic' 'localhost' '7001'
Note:
When you run the script, you are also prompted for passwords.Use the Oracle BI Applications configuration script (configure_rpd.py) to configure the following connection pools for Oracle BI Applications in the BI metadata repository file (OracleBIApps.rpd):
Oracle Business Analytics Warehouse data source connection pools:
Connection pool for the Oracle BI Application Configuration data source
Oracle DB InitBlock Initialization Connection Pool (uses the same values as those used for the HCM_OLTP connection)
In addition, the OLAPTBO repository static variable needs to be configured manually.
Note that the following repository files are provided on installation:
OracleBIApps.rpd - the full repository file containing all Oracle BI Applications and Oracle Transactional Business Intelligence projects
OracleBIAppsCRM.rpd - a partial repository file containing Oracle BI Applications and Oracle Transactional Business Intelligence projects for CRM modules
OracleBIAppsERP.rpd - a partial repository file containing Oracle BI Applications and Oracle Transactional Business Intelligence projects for ERP modules
The OracleBIApps.rpd file is configured during Fusion Applications installation and provisioning, and is deployed to the BI Instance (for example, BI_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository). The configure_rpd.py script used in this procedure configures the repository file deployed in the BI Instance. The configurations specific to Oracle BI Applications made by the configure_rpd.py script must be performed on the repository file that was configured during Fusion Applications installation and provisioning, namely OracleBIApps.rpd.
To configure connection pools in the Oracle BI repository file (OracleBIApps.rpd):
Access ORACLE_HOME/dwtools/scripts and run configure_rpd.py using the following syntax:
WLST_PATH configure_rpd.py 'DOMAIN_HOME' 'DW_DB_CONNECT' 'DW_DB_SCHEMA' 'BI_INSTANCE_HOME' 'ADMIN_HOST' 'ADMIN_PORT' 'WL_USERNAME'
where:
WLST_PATH is the path to the WebLogic Scripting Tool. Use the version of wlst that is found in ORACLE_HOME/common/bin.
DOMAIN_HOME is the location of the Oracle BI domain. For example,\MW_HOME\user_projects\domains\bifoundation_domain.
DW_DB_CONNECT is the connection string for the database that stores the DW schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, machine12345.company.com.example:1521:BIA11G.
DW_DB_SCHEMA is the name of the DW schema that you created when you performed the setup steps in Section 4.3.2, "Step 2: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, you might have specified the name DEV11G_DW.
BI_INSTANCE_HOME is the home of your BI instance.
ADMIN_HOST is the computer that hosts the Administration Server
ADMIN_PORT is the port number for the Administration Server
WL_USERNAME is the WebLogic username
For example:
/mw_home/Oracle_BI1/common/bin/wlst configure_rpd.py '/mw_home/user_projects/domains/bifoundation_domain' '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))' 'DEV1_DW' '/mw_home/instances/instance1' 'localhost' '7001' 'weblogic'
Note:
When you run the script, you are also prompted for passwords.The script sets the following static variables:
OLAP_USER is set to the value of the Oracle Business Analytics Warehouse table owner (prefix_DW schema).
OLAP_DSN is set to the connect string for the Oracle Business Analytics Warehouse.
CM_USER is set to the value of the Oracle Business Analytics Warehouse table owner (prefix_DW schema).
CM_DSN is set to the connect string for the Oracle Business Analytics Warehouse.
The script also sets the password of the prefix_DW schema on the Oracle Data Warehouse Connection Pool, the Oracle Data Warehouse Repository Initblocks Connection Pool, and the Connection Pool for the Oracle BI Applications Configuration data source. The Oracle DB InitBlock Initialization Connection Pool is configured to the same values as those for the HCM_OLTP connection.
Open the repository file OracleBIApps.rpd in the BI Administration Tool and, in Variable Manager, select the OLAPTBO static repository variable. Set the variable to the Oracle Business Analytics Warehouse table owner (prefix_DW schema).
Using OPMN, restart the BI Server.
You must grant users access to Oracle BI Applications Configuration Manager, Functional Setup Manager, and DAC.
Access to these applications are controlled through the following Duty Roles (also referred to in Oracle APM as Application Roles):
BI Applications Administrator Duty (BIA_ADMINISTRATOR_DUTY)
BI Applications Implementation Manager Duty (BIA_IMPLEMENTATION_MANAGER_DUTY)
BI Applications Functional Developer Duty (BIA_FUNCTIONAL_DEVELOPER_DUTY)
Grant users duty roles based on the activities that they need to perform. For example, a user who needs to perform administrator tasks should be granted the BI Applications Administrator duty role. Work with your security administer to grant duty roles to users.
Note:
Many tasks in this chapter involve DAC and Configuration Manager. The user who performs these tasks using these applications must possess the BI Applications Administrator Duty role.For more information, see Section 2.1.12, "Security Overview of Oracle BI Applications Configuration Manager and Functional Setup Manager" and Section 2.1.13, "About Permissions in DAC, Configuration Manager, and FSM Manager" in Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.
The Extract Transform and Load (ETL) process must be run by a user with appropriate data security privileges granted on the Fusion Application tables from which data is extracted into the Oracle Business Analytics Warehouse. The user named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges.
When configuring the FUSION_APPS_OBIA_BIEE_APPID user in a DAC database connection and Informatica connection, you must enter the password for this user. However, because the password is not known (as it is generated automatically during Fusion setup), you must first complete one of the following options with your security administrator:
Change the FUSION_APPS_OBIA_BIEE_APPID password using appropriate FMW tool (for example, Oracle Identity Management (OIM)). Make note of the user's credentials. These credentials will be used to configure connections in DAC and Informatica later in the set up process.
Create a new user and password and make this user a member of the group (enterprise role) FUSION_APPS_OBIA_BIEE_APPID. For example, create a new user OBIA_ETL_USER and password, and make the user a member of the group FUSION_APPS_OBIA_BIEE_APPID. Make note of the user's credentials. These credentials will be used to configure connections in DAC and Informatica later in the set up process.
For more information, see Section 2.1.10, "What is Required to Run the ETL Process?" in Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.
Work with your Web administrator to configure Oracle HTTP Server so that URLs for Configuration Manager, Functional Setup Manager, and DAC Server point to the virtual host and port for the BI domain. Ensure that you configure the same Oracle HTTP Server for Configuration Manager, Functional Setup Manager, and DAC Server.
To configure Oracle HTTP Server:
Access the directory APPTOP/instance/CommonDomain_webtier/config/OHS/ohs1/moduleconf
where APPTOP is the Application home folder.
Open the file FusionVirtualHost_bi.conf.
Under the #BIEE section, add the following entries for Oracle BI Applications Configuration Manager, Functional Setup Manager, and DAC Server:
Oracle BI Applications Configuration Manager entry:
<LocationMatch ^/biacm/>
SetHandler weblogic-handler
WeblogicCluster host:port
</LocationMatch>
where host is the fully-qualified domain name of the WebLogic host where Oracle BI Applications Configuration Manager is deployed and port is the Administration Server port.
Functional Setup Manager entry:
<LocationMatch ^/setup/>
SetHandler weblogic-handler
WeblogicCluster host:port
</LocationMatch>
where host is the fully-qualified domain name of the WebLogic host where Functional Setup Manager is deployed and port is the Administration Server port.
DAC Server entry:
<LocationMatch ^/dacserver/>
SetHandler weblogic-handler
WeblogicCluster host:port
</LocationMatch>
where host is the fully-qualified domain name of the WebLogic host where the DAC Server is deployed and port is the Managed Server port.
Restart Oracle HTTP Server by accessing the directory APPTOP/instance/CommonDomain_webtier/bin and running the following commands:
./opmnctl stopall
./opmnctl startall
Provide the URL for Oracle BI Applications Configuration Manager to your end users.
Oracle BI Applications Configuration Manager contains a link that launches Functional Setup Manager. Work with your Oracle BI Applications administrator and your Security Administrator to configure single sign-on (SSO) between Oracle BI Applications Configuration Manager and Functional Setup Manager using Oracle Access Manager. Without SSO configuration, no single sign-on capabilities are provided, however users with the appropriate Oracle BI Application duty roles can still access Oracle BI Applications Configuration Manager and Functional Setup Manager.
To configure SSO for Oracle BI Applications Configuration Manager and Functional Setup Manager using Oracle Access Manager:
In a supported Web browser, log in to Oracle Access Manager.
For example, using the following URL:
http://<host>:<port>/oamconsole/
where host is the host name and port is the port number for your Oracle Access Manager application.
Display the Policy Configuration tab.
Create a policy for Oracle BI Applications Configuration Manager, as follows:
In the Browse pane, navigate to Application Domains\bi.
Click the Resources node.
Use the Create option to display the Create Resource page.
Specify the following details:
Resource type: http
Host Identifier: OraFusionApp
Resource URL: /biacm*
Save the details.
Determine whether there is an existing policy for Functional Setup Manager (for example, there might be an existing policy for the Resource URL /setup* in the Application Domains\fs domain).
If there is an existing policy for Functional Setup Manager, then you can skip step 5 below and use this existing policy. If there is not an existing policy for Functional Setup Manager, then follow step 5 below to create a policy.
Create a policy for Functional Setup Manager, as follows:
In the left hand Browse pane, navigate to Application Domains\bi.
Expand the Resources node.
Use the Create option to display the Create Resource page.
Specify the following details:
Resource type: http
Host Identifier: OraFusionApp
Resource URL: /setup*
Save the details.
DAC administrators must install the DAC Client on the Windows-based computer where the Informatica PowerCenter Client Tools were installed. If Informatica PowerCenter Client Tools are not collocated on the computer, then the DAC Client must have access to the Informatica PowerCenter binaries and the domains.infa file on a shared network location.
For more information on the DAC Client requirements, see Section 2.2, "DAC Client Installation Requirements" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
To install the DAC Client using the Oracle BI Applications Client installer:
Download the Oracle BI Applications Client installer package from the Oracle Fusion Applications Media Pack on eDelivery.
Start the DAC Client installer by double-clicking the biapps_client_install.exe file. The installation wizard opens to the Introduction page.
In the Introduction screen, click Next to proceed. The Informatica Server Location page opens.
In the Informatica Server Location page, enter the location of the Informatica PowerCenter Server folder (that is, the INFA_HOME), or click Choose... to navigate to the folder location. For example, c:\Informatica\PowerCenter8.6.1.
Click Next to continue. The Informatica Domain File page opens.
In the Informatica Domain File page, enter the location of the Informatica PowerCenter domains file domains.infa, or click Choose... to navigate to the file. For example, c:\Informatica\PowerCenter8.6.1\domains.infa.
Click Next to continue. The Choose Install Folder page opens.
In the Choose Install Folder page, enter the absolute path for the folder where you want to install the DAC Client, or click Choose... to navigate to and specify the folder. For example, you might specify C:\BIA_11g_Clients.
The installation directory path can contain alphanumeric, underscore (_), hyphen (-) or dot (.) characters and must begin with an alphanumeric character.
The directory in which you install DAC is referred to as the Oracle Home location.
Click Next to continue. The Choose Shortcut Folder page opens.
In the Choose Shortcut Folder page, use the radio buttons to specify where you would like to create product icons on the Windows computer. For example, you might want to add a DAC Client icon to the Windows Start Menu.
Click Next to continue. The Pre-Installation Summary page opens.
In the Pre-Installation Summary page, verify your selections. To return to previous install options, click Previous.
To continue with the installation, click Install. The installation begins.
When the installation concludes, click Done.
To copy the DAC Authentication file to the computer that hosts the DAC Client:
The DAC Client uses an authentication file (cwallet.sso) to access the DAC Repository. The authentication file is automatically generated when the BI domain is extended to include the DAC Server by running the install_dwtools.py script in Section 4.3.6, "Step 6: Extend the BI Domain." The authentication file is saved by default to the following directory:
DOMAIN_HOME\conf-shared\security\repository
Copy the file cwallet.sso to the computer where the DAC Client is installed.
An administrator must distribute this authentication file to all DAC Client users who intend to access the DAC Repository. For more information about the authentication file, see Section 4.2, "About the DAC Authentication File" in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.
DAC Configuration Handled by the Oracle BI Applications Clients Installer
The Oracle BI Applications Clients installer performs the following configuration:
In the config.bat file, the DAC installer configures the JAVA_HOME and DAC_HOME variables.
In the dac_env.bat file, the DAC installer creates an environment variable named INFA_DOMAINS_FILE and sets the value to the directory path of the domans.infa file.
The DAC installer adds the directory path to Informatica PowerCenter binaries to the PATH environment variable.
Note:
If you reinstall or upgrade Informatica PowerCenter without reinstalling DAC, you need to manually set these environment variables.In Oracle BI Applications 11g Release (11.1.1), the DAC Server is an enterprise application deployed into the Managed Server of the BI Domain. The DAC Client is used to configure the URL of the DAC Server in the DAC Repository.
To configure the DAC Server URL:
Start the DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file. The Login dialog window opens.
In the Login dialog window, select the Configure.
In the Configuring dialog, select Create Connection, and then click Next.
Enter the appropriate connection information:
Name: Enter a unique name for the connection to the DAC repository.
Connection type: Choose Oracle (Thin).
Service Name: Enter the service name for the DAC Repository (prefix_DAC).
Database Host: Enter the name of the computer that hosts the DAC Repository database.
Database Port: Enter the port number for the database.
Click in the Authentication File field, and then do the following:
In the Authentication File dialog window, click Choose existing authentication file, and then click OK.
Navigate to the appropriate directory, select the cwallet.sso file that you copied from the DAC Server computer, and click OK.
In the Configuring dialog window, click Test Connection to confirm the connection works.
Click Apply.
Click Finish.
In the drop-down list of the Login dialog window, select the Connection that you created.
Enter any values in the User Name and Password fields, as the DAC repository does not contain any user names or passwords. A user account will be created with the user name and password you enter. This user account is automatically assigned the Administrator role.
Select DAC as the Authentication Type.
Click Login.
In the DAC Client, navigate to Tools menu, click DAC Server Management, and then click Repository Configuration.
In the Repository Configuration dialog window, enter the following information:
Mode: Web
URL: The URL for the DAC Server enterprise application deployed in WebLogic Server.
Click Save.
Note:
For all subsequent logins to the DAC Client, select the Connection and choose the FMW Authentication Type. Users will be authenticated against the LDAP system and must be granted the appropriate Oracle BI Applications duty role, as described in Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components."This section explains how to configure DAC integration settings. It contains the following topics:
This section describes how to set DAC System Properties to ensure proper integration between the DAC Client, the DAC Server, and Informatica.
To set DAC System Properties:
Start the DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file. The Login dialog window opens.
In the Login dialog window, select the Connection.
Enter the User Name and Password. This user must be granted the Oracle BI Applications Administrator Duty Role. See Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components."
From the Views menu, click Setup, and then click DAC System Properties.
Set the value for the InformaticaParameterFileLocation property.
DAC produces parameters files that are consumed by Informatica and writes them to the location specified by this property. By default, the parameter files are created in the following directory:
DOMAIN_HOME\dac\Informatica\parameters
You must either share this location so that Informatica PowerCenter Services has read and write access, or configure an alternate shared location to which both the DAC Server and Informatica PowerCenter Services have read and write access.
This section explains how to register the Informatica PowerCenter Integration Services and the Informatica PowerCenter Repository Service in DAC.
When you register Informatica Services in DAC, note the following:
You must register one or more Integration Services service.
You must register one Repository Service.
To register Informatica Services in DAC:
In DAC, navigate to the Setup view, and then click the Informatica Servers tab.
For the Informatica Integration Service that you want to register, do the following:
Modify the record with Name = INFORMATICA_DW_SERVER by entering the following information in the Edit subtab:
| Field | Enter or select |
|---|---|
| Name | Logical name for the Integration Service. |
| Type | Informatica |
| Service | Specify the name of the Integration Service you created when you installed Informatica. For example, you might have used Informatica Administration Console to create an Integration Service named 'Oracle_BIA_IS'.
Tip: To find out the name of the Integration Service, log into Informatica Administration Console and navigate to the Domain that you created, and note down the name of the Integration Service within that Domain. |
| Server Port | No longer used. |
| Domain | Informatica domain name. |
| Login | Informatica Repository user name that has appropriate privileges to execute workflows (for example, Administrator).
Note: DAC must log in to Informatica as an Informatica Repository Administrator user that is configured in the native security domain. See Section 4.3.4.13, "Creating the Repository Administrator User in the Native Security Domain." |
| Password | Informatica Repository user password. |
| Maximum Sessions | Maximum number of workflows that can be executed in parallel on the Informatica PowerCenter Integration Services service. If the number of sessions is zero or is not specified, the DAC Server assigns the default value of 10. Adjust this value based on the topology and configuration of your deployment. Allowing too many sessions can create excessive loads, which may result in failures. |
| Repository Name | Name of the Repository Service. For example, Oracle_BIA_RS. |
| Inactive | Indicates whether the PowerCenter Integration Services service will participate in the ETL process. |
Click Test Connection to ensure that the connection works.
Note: Integration Services must be running.
Click Save to save the details.
For the Informatica Repository Service you want to register, do the following:
Modify the record with Name = INFORMATICA_REP_SERVER by entering the following information in the Edit subtab:
| Field | Enter |
|---|---|
| Name | Logical name for the Repository Service. |
| Type | Repository. |
| Hostname | Repository Service host name or IP address. |
| Server Port | Informatica Gateway port number. For example, 6001. |
| Domain | (Read only) The Domain for the Hostname specified by the Hostname field. If the correct Domain is not displayed, click Refresh at the top of the Informatica Servers tab to refresh the field. |
| Login | Informatica Repository user name that has appropriate privileges to execute workflows (for example, Administrator). |
| Password | Informatica Repository user password (for example, Administrator). |
| Maximum Sessions | Maximum number of workflows that can be executed in parallel on the Informatica PowerCenter Integration Services service. If the number of sessions is zero or is not specified, the DAC Server assigns the default value of 10. |
| Repository Name | Name of the Repository Service. For example, Oracle_BIA_RS. |
| Inactive | Indicates whether the Repository Service will participate in the ETL process. |
Click Test Connection to ensure that the connection works.
Note: The Repository Service must be running.
Click Save to save the details.
Follow the procedure in this section to configure physical data source connections in DAC. You must configure the following data sources:
DataWarehouse - For the connection to the Oracle Business Analytics Warehouse.
BIACM - For the connection to Oracle BI Applications Configuration Manager.
FUSION_V1_FSCM - For the connection to the Oracle BI Server for the Fusion Applications FSCM domain.
FUSION_V1_CRM - For the connection to the Oracle BI Server for the Fusion Applications CRM domain.
FUSION_V1_HCM - For the connection to the Oracle BI Server for the Fusion Applications HCM domain.
Note:
You must configure connections for the Fusion Applications domains listed above, even if you have not deployed the associated applications.To configure physical data source connections in DAC:
Start the DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file. The Login dialog window opens.
In the Login dialog window, select the Connection.
Enter the User Name and Password. This user must be granted the Oracle BI Applications Administrator Duty Role. See Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components."
From the Views menu, click Setup, and then click Physical Data Sources. The Physical Data Sources tab displays pre-created records for the data sources listed above.
Note: In DAC, Data Source Number must be unique, even though this restriction is not enforced when a Data Source Number is specified in DAC Client.
Update the records for the following data sources and configure them as specified in the following table:
| Name | Type | Connection Type | Table Owner and Password |
|---|---|---|---|
| DataWarehouse | Warehouse | Oracle (Thin) | The table owner and password for the Oracle Business Analytics Warehouse. |
| BIACM | Source | Oracle (Thin) | The table owner and password for the Oracle Business Analytics Warehouse.
Note: The |
| FUSION_V1_FSCM | Source | BI Server | The user name and password for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL." |
| FUSION_V1_CRM | Source | BI Server | The user name and password for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL." |
| FUSION_V1_HCM | Source | BI Server | The user name and password for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL." |
Click Test Connection for each connection to ensure the connection works.
Click Save.
This section describes how to configure relational connections in Informatica, and contains the following topics:
Section 4.3.16.1, "Create an ODBC DSN to the Oracle BI Server"
Section 4.3.16.2, "Create Informatica Relational Connections"
The Informatica PowerCenter Integration Service connects to the Oracle BI Server (for access to the Oracle Fusion Application source system). Integration Service accesses the Oracle BI Server using the Oracle BI ODBC DSN. You must install and configure the Oracle BI ODBC DSN on the computer that hosts Integration Services.
The procedure for creating the ODBC DSN is specific to the operating system (Windows, Linux, or UNIX) of the computer that hosts Integration Services.
Procedure for Windows
To create an ODBC DSN to the Oracle BI Server:
On the computer that hosts Integration Services, open the Windows Control Panel by selecting Start > Settings > Control Panel, double-click Administrative Tools, and then double-click Data Sources (ODBC).
In the ODBC Data Source Administrator dialog, click the System DSN tab, and then click Add.
In the Create New Data Source dialog, select the driver Oracle BI Server 11g_OHid_number (where id_number is a number specific to an installed Oracle home), and then click Finish. The first page of the Oracle BI DSN Configuration wizard is displayed.
Note:
If the Oracle BI Server 11g driver is not installed on the computer, you can install the BI Administration Tool using the Oracle Business Intelligence Client installer. See Section 5.1, "Installing and Uninstalling Oracle Business Intelligence Client Tools" in Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.Type a name for the data source in the Name field. For example, Analytics Web ETL.
Note: Do not change the name of the centrally managed default DSN for Presentation Services and the Administration Tool.
Optionally, enter a description in the Description field.
In the Server field, select the computer that hosts the Oracle BI Server that will be used to run ETL.
If the server name does not appear in the list, then type the computer name in the Server field.
To connect to a set of clustered Oracle BI Servers through the Cluster Controllers, do the following:
Select Clustered DSN.
Enter information for the primary and secondary Cluster Controllers, as follows:
In the Primary Controller field, enter the name of the computer that is specified as the primary Cluster Controller. Then, enter the port number for the Primary Controller in the appropriate Port field.
If a secondary Cluster Controller has been set up, then type the name of the host where the Secondary Controller is running in the Secondary Controller field. Then, enter the port number for the Secondary Controller in the appropriate Port field.
You can find information about the Primary and Secondary Controller hosts and ports on the Availability tab of the Capacity Management page in Fusion Middleware Control.
To test the connection to the Cluster Controllers, click Test Cluster Connect.
If the test is not successful, then correct any errors identified in the message and test the connection again.
Note: Do not change the Primary Controller, Secondary Controller, and Port parameters of the centrally managed default DSN for Presentation Services.
Select Route Requests To Physical Layer to create a dedicated physical connection to the Oracle BI Server for clients using this DSN. All SELECT queries over this connection will be treated as SELECT_PHYSICAL queries.
SELECT_PHYSICAL queries directly query objects in the Physical layer of the metadata repository, bypassing the Presentation layer and the Business Model and Mapping layer.
Select Use Forward Only Cursor to change the ODBC cursor from its default scrollable mode to forward only.
Click Next. The second page of the Oracle BI DSN Configuration wizard is displayed.
Enter a port number for the Oracle BI Server in the Port field. This option is enabled when Clustered DSN has not been selected on the first page of the wizard.
You can find information about the Oracle BI Server port on the Availability tab of the Capacity Management page in Fusion Middleware Control.
Click Next. The third page of the Oracle BI DSN Configuration wizard is displayed.
Select Use Regional Settings when outputting dates and times. When this option is enabled, data in Date, Time, or DateTime format is displayed using Windows regional settings, rather than the default format for the Oracle BI Server. To see the Windows regional settings, open the Control Panel and double-click Regional and Language Options.
Click Finish to save the DSN configuration.
Procedure for Linux and UNIX
Note:
The Informatica Integration Services user account must have access to the shared Middleware Home for BI. Integration Services must be able to access the ODBC library files for the BI Server.To create an ODBC DSN to the Oracle BI Server:
On the computer that hosts the Integration Service, configure the Informatica ODBC.ini file (in INFA_HOME/ODBC5.2/ or INFA_HOME/ODBC6.0/) with an entry for the BI Server ODBC.
For a single BI Server, the ODBC.ini file entries should appear similar to the following:
[ODBC_DSN_NAME] Driver= BI_SERVER_ODBC_PATH Description=Oracle BI Server ServerMachine= BI_SERVER_HOST Repository= Catalog= UID= PWD= Port=PORT ForwardOnlyCursor=Yes SelectPhysical=Yes IsClusteredDSN=No Regional=Yes PrimaryCCSPort= SSL=No PrimaryCCS=
where:
ODBC_DSN_NAME is the name you are assigning to the data source. For example, Analytics Web ETL.
BI_SERVER_ODBC_PATH is the path to the ODBC library file for the BI Server. For example, ORACLE_BI_HOME/bifoundation/server/bin/libnqsodbc64.so.
BI_SERVER_HOST is the fully qualified name of the computer hosting the BI Server.
PORT is the port number of the BI Server. For example, 9703.
For a BI Server cluster, the ODBC.ini file entries should appear similar to the following:
[ODBC_DSN_NAME] Driver=BI_SERVER_ODBC_PATH Description=Oracle BI Server ServerMachine=BI_SERVER_HOST Repository= Catalog= UID= PWD= Port= ForwardOnlyCursor=Yes SelectPhysical=Yes IsClusteredDSN=Yes Regional=Yes PrimaryCCSPort=PORT_CLUSTER SSL=No PrimaryCCS=BI_SERVER_CLUSTER_CONTROLLER
where:
ODBC_DSN_NAME is the name you are assigning to the data source. For example, Analytics Web ETL.
BI_SERVER_ODBC_PATH is the path to the ODBC library file for the BI Server. For example, ORACLE_BI_HOME/bifoundation/server/bin/libnqsodbc64.so.
BI_SERVER_HOST is the fully qualified name of the computer hosting the BI Server.
PORT_CLUSTER is the port number of the primary controller for the BI Server cluster. For example, 9706.
BI_SERVER_CLUSTER_HOST is the name of the computer hosting the BI Server cluster controller.
Set Environmental Variables for Linux and UNIX, as follows (use shell commands as appropriate):
export TNS_ADMIN=/oracle/db_1/network/admin export ORACLE_HOME=/oracle/db_1/ export PATH=/oracle/db_1/bin:$PATH run bi-init.sh . ./bi-init.sh export PATH=.:/INFA/server/tomcat/bin:/INFA/server/bin:/INFA/java/ jre:/INFA/ODBC5.2/bin:$PATH export LD_LIBRARY_PATH=/oracle/db_1/lib:$LD_LIBRARY_PATH export LD_LIBRARY_PATH=/INFA/server/bin:/INFA/ODBC5.2/lib:/INFA/java/lib:/INFA/java/jre:$LD_LIBRARY_PATH export JRE_HOME=/INFA/java/jre export JAVA_HOME=/INFA/java/jre export ODBCINI=/INFA/ODBC5.2/odbc.ini export INFA_HOME=/INFA export INFA_DOMAINS_FILE=/INFA/domains.infa
Restart Integration Services from the Informatica Administration Console.
Before you configure relational connections in Informatica, ensure Repository Services and Integration Services are enabled and running.
To configure relational connections in Informatica:
In Informatica PowerCenter Workflow Manager, select Connections, then click Relational to display the Relational Connection Browser.
Create a Relational Connection of type Oracle for DataWarehouse with the following settings:
Name - DataWarehouse. The name must match the name of the physical data source connection in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Type - Oracle
User Name - Table owner for the Oracle Business Analytics Warehouse schema (prefix_DW).
Password - Table owner password
Connect String - The tnsnames.ora entry for the Oracle Business Analytics Warehouse. This is the tnsnames.ora entry from Section 4.3.4.6, "Install and Configure Database Connectivity Software."
Code Page - UTF-8 encoding of Unicode
Attributes - Enable the Enable Parallel Mode option.
Create a Relational Connection of type Oracle for BIACM with the following settings:
Name - BIACM. The name must match the name of the physical data source connection in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Type - Oracle
User Name - Table owner for the Oracle Business Analytics Warehouse schema (prefix_DW).
Password - Table owner password.
Connect String - The tnsnames.ora entry for the Oracle Business Analytics Warehouse. This is the tnsnames.ora entry from Section 4.3.4.6, "Install and Configure Database Connectivity Software."
Code Page - UTF-8 encoding of Unicode.
Attributes - Enable the Enable Parallel Mode option.
Create a Relational Connection of type ODBC for FUSION_V1_CRM with the following settings:
Name - FUSION_V1_CRM. The name must match the name of the physical data source connection in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Type - ODBC
User Name - The user name for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL."
Password - ETL user password.
Connect String - The BI Server ODBC DSN (for example, Analytics Web ETL) that was created on the computer that hosts the Integration Services. See Section 4.3.16.1, "Create an ODBC DSN to the Oracle BI Server."
Code Page - UTF-8 encoding of Unicode.
Create a Relational Connection of type ODBC for FUSION_V1_FSCM with the following settings:
Name - FUSION_V1_FSCM. The name must match the name of the physical data source connection in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Type - ODBC
User Name - The user name for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL."
Password - ETL user password.
Connect String - The BI Server ODBC DSN (for example, Analytics Web ETL) that was created on the computer that hosts the Integration Services. See Section 4.3.16.1, "Create an ODBC DSN to the Oracle BI Server."
Code Page - UTF-8 encoding of Unicode.
Create a Relational Connection of type ODBC for FUSION_V1_HCM with the following settings:
Name - FUSION_V1_HCM. The name must match the name of the physical data source connection in DAC. See Section 4.3.15, "Step 15: Configure Physical Data Source Connections in DAC."
Type - ODBC
User Name - The user name for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL."
Password - ETL user password.
Connect String - The BI Server ODBC DSN (for example, Analytics Web ETL) that was created on the computer that hosts the Integration Services. See Section 4.3.16.1, "Create an ODBC DSN to the Oracle BI Server."
Code Page - UTF-8 encoding of Unicode.
Note:
You must configure connections for the Fusion Applications domains listed above, even if you have not deployed the associated applications.For data movement mode Unicode to Unicode to work correctly, you must set the custom property SiebelUnicodeDB on Informatica Integration Services. Set the property in the following format:
user_OLTP@ConnectString_OLTP user_OLAP@ConnectString_OLAP.
To set SiebelUnicodeDB property in Informatica Integration Services:
Log in to Informatica Administration Console
Select the Integration Service.
In the Properties tab, scroll down to the Custom Properties area, and click Edit.
In the Name field, enter the following:
SiebelUnicodeDB
In the Value field, enter the following:
user_OLTP@ConnectString_OLTP user_OLAP@ConnectString_OLAP
where:
user_OLTP is the user name for the ETL user specified in Section 4.3.9, "Step 9: Create a User for ETL." It must match exactly the value you entered for the User Name field when creating the relational connection for the OLTP in Informatica Workflow Manager.
ConnectString_OLTP is the connect string for the BI Server ODBC DSN created in Section 4.3.16.1, "Create an ODBC DSN to the Oracle BI Server." It must match exactly the value you entered for the Connect String field when creating the relational connections for the OLTP (FUSION_V1_*) in Informatica Workflow Manager.
user_OLAP is the database user for the Oracle Business Analytics Warehouse database. It must match exactly the value you entered for the User Name field when creating the relational connection for the Data Warehouse in Informatica Workflow Manager.
ConnectString_OLAP is the connect string for the Oracle Business Analytics Warehouse database. It must match exactly the value you entered for the Connect String field when creating the relational connection for the Data Warehouse in Informatica Workflow Manager.
Note:
Ensure you enter a space between the values for ConnectString_OLTP and user_OLAP.
You must enter the user names and connection strings in the same case as you used for the relational connections in Informatica Workflow Manager.
This section provides instructions for enabling user currency preference settings for Oracle BI Applications. This section contains the following topics:
The Currency User Preference file used by Oracle BI Applications is userpref_currencies_OBIA.xml. The file instanceconfig.xml used by Oracle BI Presentation Services must point to this file. To do this, you modify the UserprefCurrenciesConfigFile parameter in instanceconfig.xml to point to userpref_currencies_OBIA.xml.Both instanceconfig.xml and userpref_currencies_OBIA.xml file are located in the following directory:
INSTANCE_HOME\config\OracleBIPresentationServicesComponent\coreapplication_obipsn
To enable user currency preference file for Oracle BI Applications:
Access the following directory on the Oracle BI instance:
INSTANCE_HOME\config\OracleBIPresentationServicesComponent\coreapplication_obips1
Open the file instanceconfig.xml for editing.
Modify the UserprefCurrenciesConfigFile parameter in instanceconfig.xml to point to userpref_currencies_OBIA.xml.
Save and close instanceconfig.xml.
Using OPMN, restart Presentation Services.
Oracle Business Intelligence is installed with a set of preferred currencies with pre-configured Preferred Currency Codes and Preferred Currency Names. You can use the default Currency Display Names, or you can specify new Currency Display Names as described in this section. You edit Preferred Currency Name values to change the currency labels that are displayed in all modules associated with BI dashboards. For example, you might want to change the 'Local Currency' label from 'Ledger Currency' to 'Local Currency'.
To edit a Currency Display Name:
Log in to Oracle BI Applications Configuration Manager as a user with the Business Intelligence Applications Administrator duty role.
For more information about how to log in and use Oracle BI Applications Configuration Manager, see Appendix A, "How to Start Oracle BI Applications Configuration Manager."
From the Tasks bar, click Manage Preferred Currencies to display the "Manage Preferred Currencies dialog".
Select a currency in the Preferred Currencies list. Selecting the currency displays the associated modules in the bottom table.
Click the value in the Preferred Currency Name column (or click the Edit icon) to display the Preferred Currency Name dialog.
In the Preferred Currency Name field, specify a currency name. This is the name that will appear for end users in the Currency drop-down list, located in Preferences tab of the My Accounts dialog window of Oracle Business Intelligence.
Click Save and Close.
By default, Document currency is excluded from the Currency drop-down list (located in the Preferences tab of the My Accounts dialog window of Oracle Business Intelligence). To include Document currency, you must remove a specific filter from all of the following security groups in the RPD:
OBIA_PROJECT_CURRENCY_PREFERENCES
OBIA_HCM_CURRENCY_PREFERENCES
OBIA_SCM_CURRENCY_PREFERENCES
OBIA_FINANCIAL_CURRENCY_PREFERENCES
OBIA_PROCUMENT_CURRENCY_PREFERENCES
OBIA_MARKETING_CURRENCY_PREFERENCES
OBIA_PARTNER_CURRENCY_PREFERENCES
OBIA_CRM_CURRENCY_PREFERENCES
OBIA_SALES_CURRENCY_PREFERENCES
To enable document currency:
Start the Oracle BI Administration Tool.
Click Manage, and then Identity.
In the Identity Manager dialog window, click BI Repository.
Click the Application Roles tab.
For each of the security groups in the RPD list above, do the following:
Double-click the security group.
Click Permission, and then click the Data Filters tab.
Remove the following filter in the data filter column:
AND "Core"."Fact - Preference List"."Currency Preference Code" <> 'Document Currency'
For example, the original filter:
"Core"."Fact - Preference List"."Module Code" = 'PROJECT_AN' AND "Core"."Fact - Preference List"."Currency Preference Flag" in ('W', 'B') AND "Core"."Fact - Preference List"."Currency Preference Code" <> 'Document Currency'
should become as follows after you remove the filter:
"Core"."Fact - Preference List"."Module Code" = 'PROJECT_AN' AND "Core"."Fact - Preference List"."Currency Preference Flag" in ('W', 'B')
Repeat steps for each of the remaining security groups.
Save the RPD:
Optionally, you may choose to trim the Oracle BI Applications repository file (RPD) to support the Offerings you have purchased. For information about optimizing the Oracle BI Applications repository file, see Appendix A, "Optimizing a Repository File (RPD) for Oracle BI Applications".
This section contains the following topics:
Register your Oracle Fusion Applications source system using Oracle BI Applications Configuration Manager. Specify a source system to match your Oracle Fusion Applications configuration.
To register a Source System:
Log in to Oracle BI Applications Configuration Manager as a user with the Business Intelligence Applications Administrator duty role.
For more information about how to log in and use Oracle BI Applications Configuration Manager, see Appendix A, "How to Start Oracle BI Applications Configuration Manager."
In Oracle BI Applications Configuration Manager, click the Define BI Applications Instance link to display the Define Business Intelligence Applications Instance dialog.
Display the Source Systems tab.
Specify a Source System as follows.
Click the Add icon to display the Register Source dialog.
Use the Register Source dialog to specify the following details:
| Element | Description |
|---|---|
| Source Instance Name | Specify a Source Instance name to identify the Fusion Applications source system. For example, 'Oracle Fusion Applications - Production'. The Source Instance name appears in the Configuration Manager screens that are available to functional developers. |
| Description | (Optional) Additional information to assist BI implementors and functional developers. |
| Data Source Number | A unique ID to identify data from the Oracle Fusion Applications Transactional Database. The Data Source Number entered here must match the DSN specified in the Physical connection in DAC for the Fusion Applications Source of type BI Server.
The default Data Source Number for Fusion Applications source is 200. Enter 200 unless you changed this value in DAC. Note: In DAC, Data Source Number must be unique, even though this restriction is not enforced when a Data Source Number is specified in DAC Client. |
| Select Fusion Applications | Select the Select check box for each application that is deployed in the Oracle Fusion Applications database instance.
For example, if you have all three Fusion Applications deployed in one Fusion Applications instance, select all three check boxes. |
Save the details.
Note:
When you register your source system in Configuration Manager, the appropriate setup seed data is enabled based on your Oracle Fusion Applications selections. For example,Using Oracle BI Applications Configuration Manager, enable the Oracle BI Applications Offerings that you have purchased.
To enable Oracle BI Applications Offerings for standardization:
Log in to Oracle BI Applications Configuration Manager as a user with the Business Intelligence Applications Administrator duty role.
For more information about how to log in and use Oracle BI Applications Configuration Manager, see Appendix A, "How to Start Oracle BI Applications Configuration Manager."
Click the Manage BI Applications link to display the Manage Business Intelligence Applications dialog.
Click the BI Application Offerings tab.
Offerings are not enabled by default. Click
Click the Enabled check box next to each Offering you want to enable. (By default, offerings are disabled.) Enabling Offerings enables the applicable setup seed data in Configuration Manager.
Note:
Enable only the Offerings that have been purchased so that you don't see data for other Offerings. You can enable additional Offerings as you purchase them.Click Save to save your changes.
To exit this screen, click Done.
Oracle BI Applications 11g Release (11.1.1) supports the load of data from the Fusion Applications source to the Oracle Business Analytics Warehouse in multiple languages.
In Oracle BI Applications Configuration Manager, you specify the language or languages in which data is extracted from the source and loaded into the Oracle Business Analytics Warehouse.
To specify the data warehouse languages:
Log in to Oracle BI Applications Configuration Manager as a user with the Business Intelligence Applications Administrator duty role.
For more information about how to log in and use Oracle BI Applications Configuration Manager, see Appendix A, "How to Start Oracle BI Applications Configuration Manager."
Click the Manage BI Applications link to display the Manage Business Intelligence Applications screen.
Click the Warehouse Languages tab.
Specify the languages from which data is to be extracted from the list of languages displayed in the table by selecting Installed from the Installed drop down. American English is the Installed language by default. All other languages are disabled.
Note:
When you mark a language as Installed, the Data Load Parameter LANGUAGE_LIST is populated internally with the list of selected languages. This parameter list is used during data extraction to extract data in the selected languages.Set the Base Language by selecting the Language record and clicking the Set Base Language icon in the table toolbar. By default, American English is the Base Language.
Note:
The base language is used to generate pseudo-translation records in the Oracle Business Analytics Warehouse for any languages missing in the Source system.Click Save to save your changes.
Source-specific data must be loaded to the Oracle BI Applications Configuration Manager tables. This enables Oracle BI Applications Configuration Manager to display the appropriate source-specific values as choices to functional developers in the functional setup user interfaces. The data from the Fusion Applications source is loaded to the Oracle BI Applications Configuration Manager tables using ETL routines.
Work with your ETL Administrator to complete this procedure.
To run domains ETL:
Start the DAC Client.
To start DAC Client, navigate to the \dac\ folder and double-click the startclient.bat.
At the Login dialog, select the appropriate Connection.
When prompted for a User Name and Password, enter a User Name with the appropriate permissions to access the Execute view in the DAC Client and to run ETL.
For more information about granting access to Oracle BI Applications Components, see Section 4.3.8, "Step 8: Grant User Access to Oracle BI Applications Components"
In the DAC Client, navigate to the Execute view, and display the Execution Plans tab.
Run the Execution Plan named 'Domains - Fusion 1.0'.
Oracle BI Applications is installed with a Role Catalog containing pre-configured Duty Roles that provide access to Oracle BI Applications dashboards and data. Each Duty Role is mapped to one or more Fusion Applications Enterprise Roles (also referred to as Job Roles). When you deploy Oracle BI Applications, you need to verify that the Duty Roles are mapped to the default Fusion Applications Enterprise Roles. When Fusion Applications is deployed, Duty Roles might have been removed from the Enterprise Role hierarchies, and therefore must be restored (or re-mapped) before you can deploy Oracle BI Applications. For details of Duty Roles that might be been removed from Role hierarchies, refer to section 'Oracle Business Intelligence Dashboards and Reports' in Oracle Fusion Applications Release Notes.
A list of required Enterprise Roles and Duty Roles for Oracle BI Applications is published on My Oracle Support (ID 1333454.1.) as a spreadsheet named 'Oracle Business Intelligence Applications Duty Role Assignments for Fusion Applications'.
For instructions on how to verify Duty Roles for Oracle BI Applications, see Appendix A, "Verifying Duty Roles required for Oracle BI Applications,".
After you complete the setup tasks described in this chapter, Oracle BI Applications is ready for functional setup, which is accomplished using Oracle BI Applications Configuration Manager and Functional Setup Manager. Provide the Oracle BI Applications Configuration Manager URL to your Implementation Managers and Functional Developers. To understand the process to functionally configure Oracle BI Applications, see Part II, "Functional Configuration for Oracle Business Intelligence Applications".
After functional setup is complete, your environment is ready for ETL and load of data into the Oracle Business Analytics Warehouse. Data Load is performed using DAC and Informatica PowerCenter. Furthermore, after Oracle BI Applications reports and dashboards have been tested and the data validated, the Oracle BI Applications System Administrator will need to inform the Fusion Applications Administrator to enable the appropriate embedded reports and dashboard regions in Fusion Applications. The ADR regions are enabled using Functional Setup Manager for Fusion Applications.
|
 Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|