Skip Headers
Oracle® Fusion Middleware Installation and Configuration Guide for Oracle Business Intelligence Applications
11g Release 1 (11.1.1)
Part Number E16814-05
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us
Go to previous page
Previous		 Go to next page
Next
PDF · Mobi · ePub

3 Setting Up Oracle Business Intelligence Applications

This chapter explains how to install and deploy Oracle BI Applications into a single BI domain with the WebLogic Administration Server and Managed Server in the same domain home, after exiting Oracle Fusion Applications Provisioning.

Note:

For information about deploying Oracle BI Applications components for high availability, see "Configuring Oracle Business Intelligence Applications" in Oracle Fusion Applications Enterprise Deployment Guide.

This chapter contains the following sections:

3.1 Roadmap for Installing, Setting Up, and Upgrading Oracle BI Applications

Do one of the following:

3.1.1 High-level Tasks for Setting Up Oracle BI Applications

To install and set up Oracle BI Applications, you must complete the following tasks, in order. Each high-level task breaks down into a list of detailed steps.

Tip: Before you begin, obtain the BI repository and BI Domain details from the team that installed Oracle Fusion Applications, as described in Section 3.2, "Before You Set Up Oracle BI Applications.".

  1. Create databases for Oracle Business Analytics Warehouse, DAC Repository, Informatica Domain, and Informatica Repository, as described in Section 3.4.1, "Setup Step: Create Required Databases."

  2. Create the following schemas using RCU:

  3. Apply all required Oracle BI Applications patches for this release, as described in Section 3.4.3, "Setup Step: Apply Patches.".

  4. Install and configure Informatica PowerCenter Client tools, as described in Section 3.4.4, "Setup Step: Installing Informatica PowerCenter Client Tools (Windows).".

  5. Create a user for running ETL, as described in Section 3.4.5, "Setup Step: Create a User for ETL."

  6. Grant user access to Oracle BI Applications components, as described in Section 3.4.6, "Setup Step: Grant User Access to Oracle BI Applications Components."

  7. Install DAC Client on a Windows-based machine where the Informatica PowerCenter Client Tools are installed, as described in Section 3.4.7, "Setup Step: Install and Set Up DAC Client."

  8. Install and configure Oracle BI Applications components, as follows:

  9. Create an ODBC DSN to BI Server, as described in Section 3.4.10, "Setup Step: Create an ODBC DSN to the Oracle BI Server.".

  10. Start or re-start the following components:

  11. (For UNIX environments) Validate the Oracle BI Applications component configuration as described in Section 3.4.12, "Setup Step: Validate the Oracle BI Applications Component Configuration".

  12. Set up Informatica Client tools to access the Informatica Domain and Repository, as described in Section 3.4.13, "Setup Step: Accessing the Informatica Domain and Repository from Informatica Client Tools".

  13. Install the Oracle BI Administration Tool, as described in Section 3.4.14, "Setup Step: Install Oracle BI Administration Tool."

  14. Restore the 'full' metadata repository for Oracle BI Applications, as described in Section 3.4.15, "Restore the BI Metadata Repository File for Oracle BI Applications."

  15. Configure Oracle HTTP Server, as described in Section 3.4.16, "Setup Step: Configure Oracle HTTP Server."

  16. Configure single sign-on (SSO) for Oracle BI Applications Configuration Manager and Functional Setup Manager, as described in Section 3.4.17, "Setup Step: Configure SSO and Portlet Provider for Oracle BI Applications Configuration Manager and Functional Setup Manager."

  17. Use Oracle BI Applications Configuration Manager to do the following:

    1. Enable Offerings that you have purchased, as described in Section 3.4.18, "Setup Step: Enable Offerings for Deployment."

    2. Set languages for data load, as described in Section 3.4.19, "Setup Step: Set Languages for Data Load."

    3. Edit Preferred Currency Display Names, as described in Section 3.4.20, "Setup Step: Editing Preferred Currency Display Names."

  18. Enable the Document Currency, as described in Section 3.4.21, "Setup Step: Enable Document Currency."

  19. Run Domains ETL, as described in Section 3.4.22, "Setup Step: Run Domains ETL."

  20. Verify that Duty Roles Exist for Oracle BI Applications, as described in Section 3.4.23, "Setup Step: Verifying Duty Roles required for Oracle BI Applications."

Next Steps

After you complete the setup tasks described above, Oracle BI Applications is ready for functional configuration, which is accomplished using Oracle BI Applications Configuration Manager and Functional Setup Manager. To enable functional configuration, you must 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 configuration is complete, your environment is ready for ETL and data-load into 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 (ADR) regions in Fusion Applications. The ADR regions are enabled using Functional Setup Manager for Fusion Applications.

3.2 Before You Set Up Oracle BI Applications

Before You Begin

Before you can begin to set up Oracle Business Intelligence Applications, you need to obtain the following three values from the team who installed Oracle Fusion Applications:

Obtaining the Oracle BI Repository and Host Name

Two Oracle Fusion Applications provisioning screens impact Oracle Business Intelligence Applications. Before you complete the setup tasks for Oracle Business Intelligence Applications, consult with the team who installed Oracle Fusion Applications to obtain the values for Host and RPD password.

Obtaining the Location of the Oracle BI Domain

At the conclusion of the Oracle Fusion Applications provisioning process for Oracle Business Intelligence, the following entities are available:

The resulting environment is referred to as the "Business Intelligence domain" or "BI Domain." Consult with the team who installed Oracle Fusion Applications for the location of the BI Domain.

The following default values are used:

Before you set up Oracle BI Applications, do the following:

After you complete the tasks listed above, proceed to Section 3.4, "Tasks for Setting Up Oracle BI Applications" for detailed instructions on how to set up Oracle BI Applications.

3.3 Overview of Setting Up Oracle BI Applications

This section provides an overview for setting up Oracle BI Applications, and includes the following topics:

3.3.1 About Setting Up Oracle BI Applications

Oracle Business Intelligence Enterprise Edition is installed and provisioned as part of the Fusion Applications installation 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 machine that hosts the BI Domain.

Warehouse Component Deployment Assistant (WCA) is a script that you use to install and configure a number of components for Oracle BI Applications in UNIX environments. For example, WCA installs Informatica PowerCenter Services, and configures a Repository Service and an Integration Service. For a complete list of components that are configured by WCA, see Section A.6, "About Warehouse Component Deployment Assistant (WCA)."

WCA is not supported on Windows environments, therefore you must configure components manually by following the steps in Section 3.4.9, "Setup Step: Manually Configure Oracle BI Applications Components in a Windows Environment.".

The following Oracle Business Intelligence provisioning 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 BI metadata repository file (OracleBIApps.rpd) is trimmed during BI Provisioning to contain only those RPD projects for Transactional Business Intelligence and Oracle BI Applications that are relevant for the installed Fusion Applications Offerings.

  • 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 (or Duty Roles) required by Oracle BI Applications and Oracle Fusion Transactional Business Intelligence are provisioned.

During the Fusion Applications installation, the software components of Oracle BI Applications are installed in the Business Intelligence Oracle Home but are not deployed. This chapter describes how to deploy Oracle BI Applications by installing and setting up the Oracle BI Applications components.

3.3.2 About the Components in an Oracle BI Applications Environment

The following figure shows the main tools and components that you set up in an Oracle BI Applications environment:

Figure 3-1 Tools and Components in an Oracle Business Intelligence Applications Environment

Client Tools and Components

Tools

  • Informatica PowerCenter Client tools - third-party Informatica PowerCenter Client tools that you use to set up the Informatica platform, and make ETL customizations if required. For example, Informatica PowerCenter Administrator, Informatica PowerCenter Designer.

  • Oracle BI Applications Configuration Manager - a Web application used to perform system setup, and manage functional setup data.

  • Functional Setup Manager (FSM) - a Web application leveraged by Oracle BI Applications Configuration Manager that is used to configure Oracle BI Applications 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 (that is, RPD files).

  • Warehouse Component Deployment Assistant (WCA) - a tool that you use during Oracle BI Applications setup, which configures a number of components for Oracle BI Applications. For example, for DAC, Informatica PowerCenter, and Oracle BI Applications Configuration Manager. For a complete list of components that are configured by WCA, see Section A.6, "About Warehouse Component Deployment Assistant (WCA)."

  • Fusion Middleware Control - a Web application that enables you to manage system components by performing tasks such as monitoring status, starting and stopping processes, scaling out, resolving issues, and configuring components.

Components

  • Informatica PowerCenter Services - third-party Informatica PowerCenter server that is used to perform ETL. Informatica PowerCenter Services is managed by Informatica Administrator, which is a Web application .

  • Informatica Repository - prebuilt ETL logic for each BI Application.

  • Functional Setup Data - Functional Configuration choices made in Functional Setup Manager and Oracle BI Applications 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.

  • Metadata Repository - RPD file that stores the BI metadata.

  • BI Presentation Services Catalog - prebuilt reports and dashboards, common files for Oracle Transactional Intelligence and Oracle BI Applications.

  • Oracle Business Analytics Warehouse - the target database into which source system data is loaded (sometimes referred to generically as the data warehouse).

  • DAC Repository - stores the metadata that represents Oracle Business Analytics 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).

3.3.3 Summary of Home Directories

The following table defines the main Home directories for the components in an Oracle BI Applications deployment:

Table 3-1 Summary of Home Directories for Oracle BI Applications

Home Directory Description

DOMAIN_HOME

Location of the Oracle WebLogic BI Domain (for example, /instance/domains/<hostname>/BIDomain).

INFA_HOME

Location of the user-specified Informatica installation directory on the machine that hosts Informatica PowerCenter (for example,\informatica\91\).

MW_HOME

Location of the Oracle Fusion Middleware home (for example,\FMW_11g\). It includes the WebLogic home and one or more Oracle homes.

ORACLE_HOME (for Oracle Business Intelligence)

This is the root directory of Oracle Business Intelligence. For example, the Oracle home for Oracle Business Intelligence is typically MW_HOME/Oracle_BI1.

ORACLE_INSTANCE

Location of the Oracle Instance home (for example, MW_HOME\Oracle_BI1\instances\instance1).

3.4 Tasks for Setting Up Oracle BI Applications

This section provides detailed tasks for setting up Oracle BI Applications.

Note: You must perform the tasks in this section in the sequence described in Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Before you complete the tasks described in this section, you must ensure that your environment meets the prerequisites and that you understand the recommendations described in Section 3.2, "Before You Set Up Oracle BI Applications."

3.4.1 Setup Step: Create Required Databases

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up 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 that 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 2.4, "Code Page and Data Movement Requirements."

For the database that hosts Oracle Business Analytics Warehouse, perform the following additional steps:

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 Oracle Software Delivery Cloud. See Section A.7.3, "Locations of Installation Files for Informatica PowerCenter and Hotfix 2."

3.4.2 Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

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. For information about creating the Sales Prediction Engine RCU, see Section 3.4.2.2, "Creating Data Warehouse Objects with the Oracle Sales Prediction Engine RCU".

3.4.2.1 Creating Oracle BI Applications Schemas Using Oracle BI Applications 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.

The Oracle BI Applications RCU zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS - either Linux or Window>. (The Fusion Applications software repository is obtained when you download and unzip the Oracle Fusion Applications 11g parts available in the Oracle Fusion Applications Media Pack on the Oracle Software Delivery Cloud.) Extract this zip file into a folder, for example, BIA_RCU_HOME.

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 3.4.1, "Setup Step: Create Required Databases." 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

  • 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.

Pre-requisites

Before you create Oracle BI Applications schemas using the Oracle BI Applications RCU, you must do the following:

  • 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;

  • Before running the Oracle BI Applications RCU to create database schemas, you must transfer the following dump files (.dmp) to a directory with global write access (RCU writes log files to this directory) on the machine that hosts your database):

    • obia.dmp

      This file is required for Oracle Business Analytics Warehouse, and includes the Oracle BI Applications Configuration Manager repository and the Oracle Functional Setup Manager repository.

    • dac.dmp

      This file is required for Oracle Business Intelligence Data Warehouse Administration Console, and 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.

To create the Oracle BI Applications database schemas using the Oracle BI Applications RCU:

  1. Access the bin directory in the BIA_RCU_HOME.

  2. Start RCU, as follows:

    • UNIX:

      ./rcu

    • Windows:

      rcu.bat

    The Welcome screen opens.

  3. In the Welcome screen, click Next.

  4. In the Create Repository screen click Create, and then click Next.

  5. 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 3-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 machine hosting the database. For example, machine12345.example.com.

    Port

    Specify the number of the communication port for the database. 1521 is the default port number for Oracle Databases.

    Service Name

    Specify the database account name or the Service Name for the database. For example, BIA11G.

    Username

    Specify the username for accessing the machine that hosts the database. For example, SYS.

    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.

  6. After the prerequisite checks conclude with no errors, click OK to dismiss the screen and proceed to the Select Components screen.

  7. 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.

  8. Expand the Oracle BI Applications Schemas group, and then select the Oracle Data Warehouse Administration Console (DAC), and the Oracle Business Analytics Warehouse (DW) schemas only.

    Note: Do not select the Oracle Transactional BI (OTBI) schema.

  9. 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.

  10. In the Schema Passwords screen, specify and confirm a password for the schemas.

    Note: It is not necessary to select the Use same password for all schemas option.

    Click Next to proceed to the Custom Variables screen.

  11. 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 machine, enter /tmp in the Value field.

    Click Next to proceed to the Map Tablespaces screen.

  12. In the Map Tablespaces screen, confirm the schema names. For more information, especially for tablespace recommendations, see Section 2.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.

  13. 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.

  14. In the Completion Summary screen, click Close.

3.4.2.2 Creating Data Warehouse Objects with the Oracle Sales Prediction Engine RCU

Use the Sales Prediction Engine RCU to create data warehouse database objects (ODM tables, views, packages, ILS Processing tables, and so on) in Oracle Business Analytics Warehouse. This is required if the Sales Prediction Engine module of Oracle Fusion Customer Relationship Management was deployed.

Before you create Oracle Business Analytics Warehouse database objects, ensure that you have a supported Oracle Business Analytics Warehouse that contains the Oracle BI Applications schemas. See Section 3.4.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, follow the steps in "Setting Up Sales Prediction Engine" in the Customer Relationship Management chapter of Oracle Fusion Applications Post-Install Guide.

3.4.3 Setup Step: Apply Patches

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Before the ATGLite and FSM patches are applied, you must download and apply the following patches from the My Oracle Support > Patches and Updates area:

  • 13969226 - DAC 11.1.1.6.2 CUMULATIVE PATCH 2.

    Note: Before you apply the first patch 13969226, you must shut down the Weblogic Server.

  • 14016865 - biappsinst patch 4 biappsshiphome_11.1.1.6.2.

Notes:

  • Apply the above patches using the patch instructions in the readme files.

Then, you must use the Oracle BI Applications Upgrade Tool to apply the following patches for Functional Setup Manager and ATGLite. The Oracle BI Applications Upgrade Tool is a command line utility that is available in the following Oracle Home for BI location:

ORACLE_HOME/biapps/tools/lib/biappsrepositoryutil.jar

Run the Oracle BI Applications Upgrade Tool, as follows:

Note: You must perform the steps in the order specified below. That is, you must upgrade the ATGLite component before upgrading the FSM component.

  1. Navigate to the directory ORACLE_HOME/biapps/tools/lib.

  2. Use the Oracle BI Applications Upgrade Tool to upgrade the ATGLite component using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=<ORACLE_HOME> atg.repo.user=<DW_SCHEMA_USER> atg.repo.password=<DW_SCHEMA_PASSWORD> db.conn.sid.url=<DBHOSTNAME:DB_PORT:DBSID> dw.user=<DW_SCHEMA_USER> dw.password=<DB_SCHEMA_PASSWORD> atg.db.seed.url=<DBHOSTNAME:DBPORT/DB_SERVICENAME> db.sys.user=sys db.sys.password=<DB_SYS_PASSWORD>

    For example:

    java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=/scratch/aime/work/mw5376/Oracle_BI1/ atg.repo.user=fusion_DW atg.repo.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dw.user=fusion_DW dw.password=welcome1 atg.db.seed.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1

  3. Use the Oracle BI Applications Upgrade Tool to upgrade the schema and seed data for the FSM component using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=<ORACLE_HOME> fsm.repo.user=<DW_SCHEMA_USER> fsm.repo.password=<DW_SCHEMA_PASSWORD> db.conn.sid.url=<DBHOSTNAME:DB_PORT:DB_SID> dw.user=<DW_SCHEMA_USER> dw.password=<DW_SCHEMA_PASSWORD> fsm.db.seed.url=<DBHOSTNAME:DBPORT/DB_SERVICENAME> db.sys.user=sys db.sys.password=<DB_SYS_PASSWORD>

    For example:

    java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=/scratch/aime/work/mw5376/Oracle_BI1/ fsm.repo.user=fusion_DW fsm.repo.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dw.user=fusion_DW dw.password=welcome1 fsm.db.seed.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1

3.4.4 Setup Step: Installing Informatica PowerCenter Client Tools (Windows)

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

This section explains how to install Informatica PowerCenter V9.1 Client Tools and Hotfix 2 for an Oracle BI Applications deployment. For detailed generic information about installing Informatica V9.1, refer to the Informatica PowerCenter Installation Guide.

Note: Informatica PowerCenter Services is installed using WCA for Linux and UNIX (for more information, see Section 3.4.8, "Setup Step: Configure Oracle BI Applications components using Warehouse Component Deployment Assistant (WCA) in a UNIX Environment."). For Windows, Informatica PowerCenter must be installed by running the Informatica installer manually (for more information, see Section 3.4.9, "Setup Step: Manually Configure Oracle BI Applications Components in a Windows Environment.").

You must install Informatica PowerCenter Client Tools on the same Windows machine as the DAC Client.

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:

  1. Run the program install.bat from the root directory where you unzipped the PowerCenter Client Tools V9.1 install package.

    For information about the location of the Informatica installation files, see Section A.7.3, "Locations of Installation Files for Informatica PowerCenter and Hotfix 2.".

  2. Follow the instructions in the Informatica PowerCenter Client 9.1 installation wizard. For more information, see Chapter 4, "Client Installation" in Informatica PowerCenter Installation Guide.

  3. Install Informatica PowerCenter Hotfix 2 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 9.1 HotFix Release Notes.

3.4.5 Setup Step: Create a User for ETL

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI 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 Oracle Business Analytics Warehouse. For this purpose, the Group named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges (by default, this Group is mapped to the Duty Role named OBIA_EXTRACT_TRANSFORM_LOAD_DUTY).

To create a user for ETL:

  1. Use Oracle Identity Management (or an appropriate security tool) to create a new user and password.

    For example, you might create a new user named OBIA_ETL_USER.

  2. Make the user a member of the Group FUSION_APPS_OBIA_BIEE_APPID.

    For example, you might assign the user OBIA_ETL_USER to the group FUSION_APPS_OBIA_BIEE_APPID.

  3. Make a note of the user credentials.

    These credentials are used to configure connections in DAC and Informatica later in the setup process.

3.4.6 Setup Step: Grant User Access to Oracle BI Applications Components

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

You must grant users access to Oracle BI Applications Configuration Manager, Functional Setup Manager, and DAC. Access to these applications is controlled through the following Duty Roles (Duty Roles are also referred to as Application Roles in Oracle APM):

  • 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)

Examples of Setting Up Users For Oracle BI Applications

To set up security, you map User to Enterprise Role to Duty Role.

For example:

  • In a small deployment, you might set up one user with an Enterprise Role named 'BIA_Admin_Role', which you map to the BI Applications Administrator Duty (that is, BIA_ADMINISTRATOR_DUTY). A user with the BIA_Admin_Role privileges can then access Oracle BI Applications components with required functionality.

  • In a large deployment, you might set up the following users:

    • To manage the functional configuration, you set up one user with an Enterprise Role named 'BIA_Admin_Role', which you map to the BI Applications Administrator Duty (that is, BIA_ADMINISTRATOR_DUTY).

    • To set up an implementation project and assign tasks to functional developers, you set up two users with an Enterprise Role named 'BIA_Implementation_Manager_Role', which you map to the BI Applications Implementation Manager Duty (that is, BIA_IMPLEMENTATION_MANAGER_DUTY).

    • To perform the Tasks for functional configuration in FSM, you set up ten users with an Enterprise Role named 'BIA_Functional_Developer_Role', which you map to the BI Applications Functional Developer Duty (that is, the BIA_FUNCTIONAL_DEVELOPER_DUTY).

Work with your security administer to grant Duty Roles to appropriate Fusion Applications Enterprise Roles (also known as Job Roles). For example, you might use LDAP tools and Oracle Authorization Policy Manager to set up appropriate Users and Enterprise Roles, and map these to the default Duty Roles specified above.

For more detailed information about security privileges required for Oracle BI Applications components, see Section 2.1.10 'Security Overview of Oracle BI Applications Configuration Manager and Functional Setup Manager' in Oracle Fusion Middleware Reference Guide for Oracle Business Intelligence Applications.

Note:

Many tasks in this chapter involve DAC and Oracle BI Applications Configuration Manager. The user who performs these tasks using these applications must possess the BI Applications Administrator Duty role.

3.4.7 Setup Step: Install and Set Up DAC Client

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

To install and set up DAC Client, do the following:

For information about the DAC Client installer, see Section 3.4.7.4, "About DAC Configuration Handled by the Oracle BI Applications Client Installer".

3.4.7.1 How to Install DAC Client

DAC administrators must install DAC Client on the Windows-based machine where the Informatica PowerCenter Client Tools were installed. If Informatica PowerCenter Client Tools are not collocated on the machine, then DAC Client must have access to the Informatica PowerCenter binaries and the domains.infa file on a shared network location.

You can obtain the Oracle BI Applications Client Installer executable from one of the following locations:

- On Windows, in the folder <Install Repository>\biappsshiphome\shiphome.

- On Linux and UNIX, in the folder <Install Repository>/biappsshiphome/dist/stage/clients/biappsclients.

For more information on 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:

  1. Start DAC Client installer by double-clicking the biapps_client_install.exe file.

    The installation wizard opens to the Introduction page.

  2. In the Introduction screen, click Next to proceed. The Informatica Server Location page opens.

  3. 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\PowerCenter9.1.

    Click Next to continue. The Informatica Domain File page opens.

  4. 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\PowerCenter9.1\domains.infa.

    Click Next to continue. The Choose Install Folder page opens.

  5. In the Choose Install Folder page, enter the absolute path for the folder where you want to install 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.

  6. In the Choose Shortcut Folder page, use the radio buttons to specify where you would like to create product icons on the Windows machine. 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.

  7. 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.

  8. When the installation is complete, click Done.

3.4.7.2 How to copy the DAC Authentication File to the DAC Client Machine

DAC Client uses an authentication file (cwallet.sso) to access the DAC Repository. The authentication file is automatically generated when WCA extends the BI domain to include the DAC Server (as described in Section 3.4.8, "Setup Step: Configure Oracle BI Applications components using Warehouse Component Deployment Assistant (WCA) in a UNIX Environment"). The authentication file is saved by default to the following directory:

DOMAIN_HOME\dac\conf-shared\security\repository

Copy the file cwallet.sso to the machine where 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.

3.4.7.3 How to log into DAC Client for the first time

To log into DAC Client for the first time:

  1. Start the DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file.

    The Login dialog opens.

  2. In the Login dialog, select Configure.

  3. In the Configuring dialog, select Create Connection, and then click Next.

  4. Enter the appropriate connection information:

    • Name: Specify a short unique name for the connection to the DAC repository.

      This name is displayed in the list of connections available at the DAC login dialog.

    • Connection type: Choose Oracle (Thin).

    • Service Name: Enter the service name for the DAC Repository (for example, XE).

    • Database Host: Enter the name of the computer that hosts the DAC Repository database.

    • Database Port: Enter the port number for the database.

  5. Click in the Authentication File field, and then do the following:

    1. In the Authentication File dialog, click Choose existing authentication file, and then click OK.

    2. Navigate to the appropriate directory, select the cwallet.sso file that you copied from the DAC Server computer, and click OK.

    3. In the Configuring dialog, click Test Connection to confirm the connection works.

    4. Click Apply.

    5. Click Finish.

  6. In the Connection field of the Login dialog, select the Connection that you created.

  7. Use the User name and Password fields to specify the credentials of a user that has been granted the role 'BI Applications Administrator Duty'.

    Note: Users are set up with appropriate roles in step Section 3.4.6, "Setup Step: Grant User Access to Oracle BI Applications Components".

  8. In the Authentication Type field, choose FMW, then click Login.

3.4.7.4 About DAC Configuration Handled by the Oracle BI Applications Client 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.

3.4.8 Setup Step: Configure Oracle BI Applications components using Warehouse Component Deployment Assistant (WCA) in a UNIX Environment

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Warehouse Component Deployment Assistant (WCA) is a script that you use to install and configure a number of components for Oracle BI Applications in UNIX environments. For example, WCA installs Informatica PowerCenter Services, and configures a Repository Service and an Integration Service. For a complete list of components that are configured by WCA, see Section A.6, "About Warehouse Component Deployment Assistant (WCA)."

Note: WCA is not supported on Windows environments, therefore you must manually configure Oracle BI Applications components, as described in Section 3.4.9, "Setup Step: Manually Configure Oracle BI Applications Components in a Windows Environment.".

To configure Oracle BI Applications components using WCA:

  1. Set the following environment variables for WCA:

    #Env Variable Setting in .cshrc file [Profile file of linux user] related to WCA. For example : 
setenv WCA_HOME "/scratch/aime/work/APPTOP/fusionapps/bi/dwtools/scripts/wca" 
setenv ANT_HOME /scratch/aime/work/APPTOP/fusionapps/modules/org.apache.ant_1.7.1  
setenv PATH "${ANT_HOME}/bin:${PATH}" 
setenv JAVA_HOME /scratch/aime/work/APPTOP/fusionapps/jdk6

  2. Configure WebLogic Server so that it does not prompt for an Administrator password when starting up or shutting down, as follows:

    1. Create a file 'boot.properties' with the WebLogic Server Administrator's username password and store the file in $DOMAIN_HOME/servers/[server_name]/security.

    2. Add the following parameters to the boot.properties file:

      username=<Superuser with Admin role such as WebLogic>
password=<password of user>

    3. Repeat steps 2.a and 2.b for Admin Server and all Managed Servers.

      For example, you might create the following files:

      MW_HOME/user_projects/domains/bifoundation_domain/servers/AdminServer/security/boot.properties.

      MW_HOME/user_projects/domains/bifoundation_domain/servers/bi_server1/security/boot.properties.

    For more information about setting up a boot.properties file, see the topic 'Boot Identity Files' in the chapter 'Starting and Stopping Servers, in Oracle Fusion Middleware Managing Server Startup and Shutdown for Oracle WebLogic Server. or locate this topic in WebLogic Server Administration Console Online Help.

  3. Shutdown BI domain WebLogic Admin server, managed server, and OPMN services.

    Note: Node Manager should be running (or 'up').

  4. Specify configuration values for the other parameters in the wca_params.properties file.

    You must specify a value for all parameters that are not installed with a default value, and make sure that default values are correct. For example:

    Note: If you have set the value of CONFIGURE_INFA to 'y', then you must specify appropriate values for the Informatica-related configuration values.

    ...
#This parameter represents the Informatica Installation home directory.
#Supported Values: Give the absolute path to Informatica Installation home directory
INFA_HOME=/scratch/aime/work/Informatica/PowerCenter9.1
 
#This parameter represents host name of the machine where Informatica is installed
INFA_PCS_HOST=localhost

#This parameter represents the Informatica Domain User Name that is created when Informatica is installed.
#Supported Values: The domain user name provided when Informatica is installed.
#We can also use the default user provided by Informatica: Administrator
INFA_DOM_USER=Administrator
 
...

    Tip: For a full list of parameters that must be set, refer to the file wca_params.properties. Use the inline parameter descriptions marked with # for guidance on the value that is required.

  5. Using a text editor, edit the file <BI_Oracle_Home>/dwtools/wca/wca_passwords.properties and specify a password for each component.

    Note: If you have set the value of CONFIGURE_INFA to 'y', then you must specify appropriate passwords for the Informatica-related components.

    ...
INFA_DOM_PASSWRD=admin
DW_DB_PASSWRD=biacm
DW_ETL_USER_PASSWRD=abc
INFA_DOM_DB_PASSWRD=password 
INFA_REP_DB_PASSWRD=password
INFA_REP_PASSWRD=Administrator
DAC_DB_PASSWRD=biacm
MDS_DB_PASSWRD=fusion_mds
WL_PASSWRD=fusionfa1
RPD_ENCRYPTION_PASSWRD=welcome1
...

    Note:

    To maintain security, Oracle recommends that after you have completed configuration with WCA, you remove the passwords from the passwords.properties file.

  6. Start WCA with the values specified in the properties files, by executing the following command:

    <MW_HOME>\Oracle_BI1\dwtools\scripts\wca\ant

    Use the on screen progress report and associated log files to determine whether all components were configured correctly. If all components were configured correctly, the message 'BUILD SUCCESSFUL' is displayed on screen and in the log file.

    This screenshot is described in surrounding text.

    If WCA fails to configure an Oracle BI Applications component, then the WCA script is stopped, an error message is displayed on screen, and an ERR file is created.

    If WCA fails to configure an Oracle BI Applications component, then when the WCA script stops, do the following:

    1. Attempt to correct the fault that is reported.

      Use the log files created by WCA in the wca\logs folder to diagnose the error and attempt to correct the fault that is reported. Log files are named with a timestamp.

    2. Re-start WCA.

    Note:

    If WCA cannot configure a component, you must manually configure that component, as described in "Diagnosing WCA Errors" below, then re-start WCA. If you manually configure a component and want to re-start WCA, then you must change the ERR extension to a SUCC extension for the appropriate error file. For example:

    1. WCA reports an error creating the Informatica repository, and creates the file create_Repository_service.err.

    2. If you cannot resolve this error to enable WCA to create the Informatica repository, then you manually create the Informatica repository as described in Section 3.5.1, "Setup Step: Creating the Informatica Repository Service.".

    3. You rename the file create_Repository_service.err to create_Repository_service.succ, then re-start WCA.

      If you do not rename this file, then the WCA script will stop when it detects the create_Repository_service.err file.

    Note: Do no delete other ERR files or SUCC files created by WCA.

  7. (Optional) Remove the passwords from the passwords.properties file.

    Note:

    To maintain security, Oracle recommends that after you have completed configuration with WCA, you remove the passwords from the passwords.properties file.

Diagnosing WCA Errors

Table 3-3, "Diagnosing WCA Errors" below explains how to manually rectify WCA configuration errors. For example, if WCA fails to create an Informatica PowerCenter Repository Service, then you must analyze and attempt to fix the problem reported in the WCA log. If you cannot fix the problem, then you must create a Repository Service manually using Informatica Administrator, as specified in the Action Required If You Cannot Resolve The Error column.

Log files are available under MW_HOME/ORACLE_BI_HOME/dwtools/scripts/wca/logs. The file wca_<timestamp>.log should be used to for debugging failures that happen during WCA script execution.

If an error cannot be fixed, use the manual task in the Action Required If You Cannot Resolve The Error column to configure the component.

Table 3-3 Diagnosing WCA Errors

WCA Configuration Error Action Required If You Cannot Resolve The Error

Failure to create Informatica PowerCenter Repository Service.

Manually create the Informatica PowerCenter Repository Service, by following the steps in Section 3.5.1, "Setup Step: Creating the Informatica Repository Service.".

Error files:

create_Repository_service.err.

Failure to create Informatica PowerCenter Integration Service.

Manually create the Informatica PowerCenter Integration Service, by following the steps in Section 3.5.3, "Setup Step: Creating the Informatica Integration Service.".

Error files:

create_integration_service.err

create_integration_service.succ

Failure to restore the Informatica PowerCenter Repository .

Manually restore the Informatica PowerCenter Repository, by following the steps in Section 3.5.2, "Setup Step: Restoring the Prebuilt Informatica Repository.".

Error files:

restoreInfaRep_restoreInfaRep.err

restoreInfaRep_changeOpModeToNormal.err

Failure to copy source files to the Informatica PowerCenter machine.

Manually copy source files to the Informatica PowerCenter machine, by following the steps in Section 3.5.4, "Setup Step: Copying Source Files to the Informatica PowerCenter Services machine.".

Error files:

copySrcFile_copyZipFile.err

copySrcFile_unzipCopiedZipFile.err

Failure to configure Informatica PowerCenter Properties.

Manually configure Informatica PowerCenter properties, by following the steps in:

Section 3.5.5, "Setup Step: Setting PowerCenter Integration Services Relaxed Code Page Validation."

Section 3.5.6, "Setup Step: Setting PowerCenter Integration Services Custom Properties."

Failure to create a repository Administrator user.

Manually create a repository Administrator user, by following the steps in Section 3.5.7, "Setup Step: Creating the Repository Administrator User in the Native Security Domain.".

Error files:

creuser_creRepAdminUser.err

creuser_assignRepAdminRole.err

Failure to create Informatica Relational Connections.

Manually create Informatica Relational Connections, by following the steps in Section 3.5.11, "Setup Step: Configuring Relational Connections in Informatica.".

Error files:

creconn_connToRepInAuthenticatedMode.err

creconn_creDWConn.err

creconn_creBIACMConn.err

creconn_creFV1CRMConn.err

creconn_creFV1HCMConn.err

creconn_creFV1FSCMConn.err

Failure to create DAC Integration Settings.

Manually create DAC integration settings, by following the steps in Section 3.5.10, "Setup Step: Configuring Physical Data Source Connections in DAC." and Section 3.5.15, "Setup Step: Configure DAC Integration Settings.".

Error files:

configure_DAC.err

Failure to register Source Systems.

Manually register Source Systems, by following the steps in Section 3.5.14, "Setup Step: Registering Source Systems.".

Error files:

registerSrcInCm.err

Failure to extend the BI Domain.

Manually extend the BI Domain, by following the steps 1 and 2 in Section 3.5.8, "Setup Step: Extending the BI Domain.".

Error files:

Extending_BI_Domain.err

If WCA fails to extend the BI Domain and generates the error message '[ERROR]: The Weblogic Admin Server Failed to Start', then do the following:

1. Determine whether the WebLogic Admin Server is running. If WebLogic Admin Server is not running, manually start Admin Server.

2. Re-start WCA.

Failure to configure the BI Domain.

Manually configure the BI Domain, by following the steps 3 and 4 in Section 3.5.8, "Setup Step: Extending the BI Domain.".

Error files:

Configuring_BI_Domain.err

Failure to configure RPD connection pools.

Manually configure RPD connection pools, by following the steps in Section 3.5.9, "Setup Step: Configuring the Oracle BI Connection Pools.".

Error files:

Configure_Connection_Pools.err

Failure to enable currencies.

Manually enable currencies, by following the steps in Section 3.5.13, "Setup Step: Enabling User Currency Preference Settings.".

Error files:

Enable_User_Currencies.err

3.4.9 Setup Step: Manually Configure Oracle BI Applications Components in a Windows Environment

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

If you are deploying Oracle BI Applications in a Windows environment (that is, not supported by WCA), then you must perform the following tasks manually:

Note: If you are deploying Oracle BI Applications in a UNIX or Linux environment, then you use WCA to install and configure Oracle BI Applications components automatically. For more information, see Section 3.4.8, "Setup Step: Configure Oracle BI Applications components using Warehouse Component Deployment Assistant (WCA) in a UNIX Environment."

  1. Install Informatica PowerCenter Services V9.1 HotFix 2, as described in Section A.7, "Manual Installation and Set Up For Informatica PowerCenter Services.".

  2. Create the Informatica Repository Service, as described in Section 3.5.1, "Setup Step: Creating the Informatica Repository Service.".

  3. Restore the Pre-built Informatica Repository, as described in Section 3.5.2, "Setup Step: Restoring the Prebuilt Informatica Repository.".

  4. Create the Informatica Integration Service, as described in Section 3.5.3, "Setup Step: Creating the Informatica Integration Service.".

  5. Transfer the Informatica source files, as described in Section 3.5.4, "Setup Step: Copying Source Files to the Informatica PowerCenter Services machine.".

  6. Set the Integration Services relaxed code page validation value, as described in Section 3.5.5, "Setup Step: Setting PowerCenter Integration Services Relaxed Code Page Validation.".

  7. Set the Informatica Repository custom properties, as described in Section 3.5.6, "Setup Step: Setting PowerCenter Integration Services Custom Properties.".

  8. Create the Repository Administrator User, as described in Section 3.5.7, "Setup Step: Creating the Repository Administrator User in the Native Security Domain.".

  9. Extend the BI Domain, as described in Section 3.5.8, "Setup Step: Extending the BI Domain.".

  10. Configure the Oracle BI Connection Pools, as described in Section 3.5.9, "Setup Step: Configuring the Oracle BI Connection Pools.".

  11. Configure the Physical Data Source Connections in DAC, as described in Section 3.5.10, "Setup Step: Configuring Physical Data Source Connections in DAC.".

  12. Configure the Relational Connections in Informatica, as described in Section 3.5.11, "Setup Step: Configuring Relational Connections in Informatica.".

  13. Set the SiebelUnicodeDB Property in Informatica Integration Services, as described in Section 3.5.12, "Setup Step: Setting the SiebelUnicodeDB Property in Informatica Integration Services.".

  14. Enable User Currency Preference Settings, as described in Section 3.5.13, "Setup Step: Enabling User Currency Preference Settings.".

  15. Register Source Systems in Oracle BI Applications Configuration Manager, as described in Section 3.5.14, "Setup Step: Registering Source Systems.".

  16. Configure DAC Integration Settings, as described in Section 3.5.15, "Setup Step: Configure DAC Integration Settings.".

3.4.10 Setup Step: Create an ODBC DSN to the Oracle BI Server

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

The Informatica PowerCenter Integration Service connects to the Oracle BI Server (for access to the Oracle Fusion Applications source system). The Integration Service accesses the Oracle BI Server using the Oracle BI ODBC Data Source Name (DSN). You must install and configure the Oracle BI ODBC DSN on the machine that hosts Informatica PowerCenter Services.

Note: For Linux and UNIX machines this step cannot be performed until Informatica PowerCenter Services has been installed.

The procedure for creating the ODBC DSN is specific to the operating system (Windows, Linux, or UNIX) of the machine that hosts Informatica PowerCenter Services.

Procedure for Windows

To create an ODBC DSN to the Oracle BI Server:

  1. On the machine that hosts Informatica PowerCenter Services, display the ODBC Data Source Administrator dialog.

    For example, open the Windows Control Panel, select Administrative Tools, and then select Data Sources (ODBC).

  2. Display the System DSN tab, and then click Add to display the Create New Data Source dialog.

  3. Select the driver Oracle BI Server <id_number> (where id_number is a number specific to an installed Oracle home, for example '1'), 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 machine, then you can install the BI Administration Tool using the Oracle Business Intelligence Client installer. For more information about installing Oracle Business Intelligence Client Tools, see Section 3.4.14, "Setup Step: Install Oracle BI Administration Tool".

  4. Type a name for the data source in the Name field. For example, AnalyticsWeb.

    Note: Do not change the name of the centrally managed default DSN for Presentation Services and the Administration Tool.

  5. In the Server field, select the machine 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 machine name in the Server field.

  6. To connect to a set of clustered Oracle BI Servers through the Cluster Controllers, do the following:

    1. Select Clustered DSN.

    2. Enter information for the primary and secondary Cluster Controllers, as follows:

      • In the Primary Controller field, enter the name of the machine 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.

    3. 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.

  7. 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.

  8. Select Use Forward Only Cursor to change the ODBC cursor from its default scrollable mode to forward only.

  9. Click Next to display the second page of the wizard.

  10. Use the Login ID and Password fields to specify credentials for the Oracle BI Server (for example, weblogic, welcome1).

  11. 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.

  12. Click Next to display the third page of the wizard.

  13. 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.

  14. Click Finish to save the DSN configuration.

Procedure for Linux and UNIX

Note:

The Integration Service user account must have access to the shared Middleware Home for BI. The Integration Service must be able to access the ODBC library files for the BI Server.

To create an ODBC DSN to the Oracle BI Server:

  1. On the machine 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 machine 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 machine 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 machine hosting the BI Server cluster controller.

  2. Set the following Environment Variables for Linux and UNIX:

    • INFA_HOME

    • INFA_DOMAINS_FILE

    • JAVA_HOME

    • JRE_HOME

    • LD_LIBRARY_PATH

    • ODBCINI

    • ORACLE_HOME

    • PATH

    • TNS_ADMIN

    For example, (use appropriate shell commands for your platform):

    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

  3. In Informatica Administrator, restart the Integration Service (that is, choose Disable, then Enable).

3.4.11 Setup Step: Start DAC Server

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

To start DAC Server, do the following:

1. Navigate to the DAC domain home, for example, /instance/domains/<Domain Host>/BIDomain/dac.

2. Execute the automationUtils.sh cmdCredentials command with the cwallet.sso file and the administrator username for WebLogic Server Administrator Console. For example:

/instance/domains/<Domain Host>/BIDomain/dac/conf/security/repository/cwallet.sso FAadmin

Note: When prompted for a password, specify the administrator password for WebLogic Server Administrator Console.

3. Start the DAC Server. For example:

sh dacCmdLine.sh StartServer

3.4.12 Setup Step: Validate the Oracle BI Applications Component Configuration

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

To validate the Oracle BI Applications component configuration, do the following:

  1. In a shell, run bi-init.sh or bi-init.cmd.

  2. In the same shell, set all environment variables that are suggested for running Domains ETL.

  3. Navigate to the folder <WCA_HOME>/validations/.

  4. In the same shell, execute the ValidateWCA.py script, for example:

    $BI_ORACLE_HOME/common/bin/wlst.sh <WCA_HOME>/validations/ValidateWCA.py

Notes:

Before you execute the ValidateWCA.py script, you must do the following:

  • Make sure that the DAC server is in the 'Active' state in Managed Server.

  • Make sure that DAC Client can connect to the DAC Server.

  • Assign the execute permission to the wca/validations/validateDAC.sh script.

The ValidateWCA.py script produces a Web report containing an analysis of the configuration of each component, with a 'Details' link to more detail for each component. For example:

Client Tools and Components

Note: If you are deploying Oracle BI Applications in a Windows environment (that is, not supported by WCA), then to use the ValidateWCA.py script you must manually edit the wca_parameter.properties file to specify values for all components that you have manually configured. For example, if you manually created the Informatica PowerCenter Repository Service and Integration Service, then you must manually set values for the INFA_RS_NAME and INFA_IS_NAME parameters that match the service names that you used.

3.4.13 Setup Step: Accessing the Informatica Domain and Repository from Informatica Client Tools

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

When you first log into any of the Informatica PowerCenter Client tools (for example, Designer, Workflow Manager), you must specify the Informatica Domain and Repository that you want to use.

Note: The following tasks describe how to use Informatica PowerCenter Designer to specify an Informatica PowerCenter Domain and Informatica PowerCenter Repository. However, you can use any of the Informatica PowerCenter Client tools.

To set up the Informatica Domain:

  1. Start Informatica PowerCenter Designer.

  2. Click Repository, and then Configure Domain, to display the Configure Domains dialog.

    This screenshot is described in surrounding text.

  3. Click the Add a new Domain icon to display the Add Domain dialog.

    This screenshot is described in surrounding text.

  4. Use the Add Domain dialog to specify the following:

    Table 3-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. The default domain name is 'Domain_<HOSTNAME>'. For example, if the hostname of the Informatica PowerCenter Services machine is abc.us.oracle.com, then the domain name is Domain_abc.

    Gateway Host

    Specify the hostname or IP address of the Informatica Server machine that hosts the Gateway node (for example, machineA).

    Gateway Port

    Specify the gateway port number. For example, 6001.

  5. 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.

  6. In the Repositories list, select the check box for the Repository that you want to use.

    This screenshot is described in surrounding text.

To set up the Informatica Repository:

  1. Start Informatica PowerCenter Designer.

  2. Select the Repository, and then click Add, to display the Add Repository dialog.

    This screenshot is described in surrounding text.

  3. In the Repository field, type the name of the Repository Service that was created by the WCA script or created manually (for example, BIA_RS), and specify Administrator as the user name.

  4. Click OK, to save the details and to return to the Start Page.

  5. In the Repositories tree, double-click the Repository that you specified in the Step 3 (for example, BIA_RS).

    This screenshot is described in surrounding text.

  6. 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.

  7. Specify Administrator as the user name and password, and then click Connect.

    This screenshot is described in surrounding text.

  8. You can now expand the repository in the Repositories list to display the contents.

    This screenshot is described in surrounding text.

3.4.14 Setup Step: Install Oracle BI Administration Tool

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

The Oracle BI Administration Tool enables you to manage the metadata repository and is required in the Oracle BI Applications set-up process. If the Oracle BI Administration Tool has not been installed, then you must install it on a Windows machine.

You install Oracle BI Administration Tool using the Oracle Business Intelligence Enterprise Edition Plus Client Installer. The Installer executable is named biee_client_install.exe and this file is available in the installed BI Middleware Home, in bi/clients/biserver.

Before you install the Oracle BI Administration Tool, ensure that the machine where you intend to perform the installation meets the following requirements:

  • The machine is running a supported Microsoft Windows operating system.

  • The machine has network connectivity with the machine 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.

3.4.15 Restore the BI Metadata Repository File for Oracle BI Applications

The BI metadata repository is trimmed during the BI Provisioning phase in a Fusion Applications installation to contain only RPD projects for Oracle Fusion Transactional Business Intelligence (OTBI). Oracle BI Applications requires a full (that is, untrimmed) RPD for ETL. To deploy Oracle BI Applications, you must restore the Golden RPD and merge it with updates and customizations in the Runtime RPD.

Note:

The trimmed BI metadata repository is referred to as the Runtime RPD, and is located in:

BI_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository\OracleBIApps.rpd

The full (that is, untrimmed) BI metadata repository is referred to as the Golden RPD, and is located in:

BI_ORACLE_HOME/biapps/admin/provisioning/OracleBIServerComponent/OracleBIApps.rpd

To restore the BI Metadata Repository file for Oracle BI Applications:

  1. Create an appropriate directory structure, as described in Section 3.4.15.2, "Create Directories and Copy In the RPD Files".

  2. Open the Runtime RPD and obtain the list of Projects, as described in Section 3.4.15.3, "Open the Runtime RPD and Obtain a List of Projects".

  3. Extract the Project metadata from the Golden RPD, as described in Section 3.4.15.4, "Extract the Trimmed Metadata from the Golden RPD".

  4. Equalize the Runtime RPD and the Golden RPD, as described in Section 3.4.15.5, "Equalize the Runtime RPD and the Golden RPD".

  5. Create a patch for the new RPD, as described in Section 3.4.15.6, "Create a Patch for the New RPD".

  6. Apply the patch containing the new RPD, as described in Section 3.4.15.7, "Apply the Patch for the New RPD".

  7. Upload the new RPD, as described in Section 3.4.15.8, "Upload the New RPD".

3.4.15.1 Before you start

Before you start, you need the following:

  • a copy of the Runtime RPD.

  • the password for the Runtime RPD (to obtain the password, go to the LDAP's Credential Store, and navigate to cn=oracle.bi.system, cn=CredentialStore, cn=FusionDomain, cn=JPSContext, cn=FAPolicies, and obtain the password).

  • a copy of the Golden RPD.

  • the password for the Golden RPD (the default is Admin123).

3.4.15.2 Create Directories and Copy In the RPD Files

Create the following directory structure and set up the RPD files.

  1. Create the following directories:

    Work\

    Work\GoldenRPD

    Work\RuntimeRPD

    Work\ExtractRPD

    Work\Patch

    Work\RestoredRPD

    Work\EqualizeRPD

  2. Copy the Golden RPD and the Runtime RPD to the corresponding folders:

    1. Copy the Golden RPD (OracleBIApps.rpd) to the \Work\GoldenRPD directory and rename it GoldenRPD.rpd.

      Note: The Golden RPD is located in the following location:

      BI_ORACLE_HOME/biapps/admin/provisioning/OracleBIServerComponent/OracleBIApps.rpd

    2. Copy the Runtime RPD (OracleBIApps.rpd) to the \Work\RuntimeRPD directory, and rename it RuntimeRPD.rpd.

      Note: The Runtime RPD is located in the following location:

      BI_INSTANCE\bifoundation\OracleBIServerComponent\coreapplication_obis1\repository

3.4.15.3 Open the Runtime RPD and Obtain a List of Projects

  1. In Oracle BI Administration Tool, open the Runtime RPD in Offline mode.

    For example, open C:\Work\RuntimeRPD\RuntimeRPD.rpd.

  2. From the menu, choose Manage, then Projects, to display the Projects Manager dialog.

  3. Note down or copy into a file the project names in this list, using the high/low case letters and spaces exactly as displayed.

    For example, "Fusion Incentive Compensation Transactional Analysis", "Fusion Marketing Transactional Analysis". You will use this list of project names in the next task.

3.4.15.4 Extract the Trimmed Metadata from the Golden RPD

  1. Open a command prompt.

  2. Navigate to the bin directory of the Oracle BI Administration Tool installation, and open the bi_init.bat file.

    For example, C:\_CLIENT_INSTALL_DIR_\oraclebi\orahome\bifoundation\server\bin\bi_init.bat.

  3. Edit the bi_init.bat file, and copy into memory the sections where the environment variables are being set.

    For example, copy the following commands:

    set ORACLE_HOME=C:\RUP3\oraclebi\orahomeset ORACLE_INSTANCE=C:\RUP3\oraclebi\orainstset ORACLE_BI_APPLICATION=coreapplication

  4. In the command prompt, execute the environment commands by pasting in the commands from Step 3 and pressing Enter.

  5. In the command prompt, execute the extractprojects command using the following parameters and values:

    -B <Path>\GoldenRPD.rpd

    -O <Path>\ExtractRPD.rpd

    -I "Project 1" -I "Project 2" -I "Project <n>"

    Note: You must specify the Project names that you obtained in Section 3.4.15.3, "Open the Runtime RPD and Obtain a List of Projects".

    -P Password of the Golden RPD.

    Note: The -I 'Project Name' command must be repeated for each project.

    For example, C:\RUP3\oraclebi\orahome\bifoundation\server\bin>extractprojects.exe -B C:\Work\GoldenRPD\GoldenRPD.rpd -O C:\Work\ExtractRPD\ExtractRPD.rpd -P Admin123 -I "Fusion Incentive Compensation Transactional Analysis" -I "Fusion Marketing Transactional Analysis" -I "Fusion Partner Transactional Analysis" -I "Fusion Sales Transactional Analysis" -I "Marketing Analytics Fusion Edition" -I "Partner Analytics Fusion Edition" -I "Sales Analytics Fusion Edition"

    The output from the extractprojects command is an RPD named ExtractRPD.rpd that will be referred to as the Extract RPD. The Extract RPD contains the same set of projects as the Runtime RPD.

3.4.15.5 Equalize the Runtime RPD and the Golden RPD

  1. In a command project, execute the equalizerpd command using the following parameters and values:

    -C <Path>\ExtractRPD.rpd-B Password of the Extract RPD-F <Path>\RuntimeRPD.rpd-E Password of the Runtime RPD-O <Path>\EqualizeRPD.rpdFor example: C:\RUP3\oraclebi\orahome\bifoundation\server\bin>equalizerpds.exe -C C:\Work\ExtractRPD\ExtractRPD.rpd -B Admin123 -F C:\Work\RuntimeRPD\RuntimeRPD.rpd -E welcome1 -O C:\Work\EqualizeRPD\EqualizedRPD.rpd

    The output from the equalizerpd command is an RPD named EqualizeRPD.rpd that will be referred to as the Equalized RPD. This Equalized RPD contains the merged metadata from the Runtime RPD and the Golden RPD.

3.4.15.6 Create a Patch for the New RPD

The patch being created is a diff between the Equalized RPD and the Extracted RPD, this patch will contain the all the configuration and customization changes that have been made.

  1. In Oracle BI Administration Tool, open the Equalized RPD.

  2. Choose File, then Compare, to display the Compare repositories dialog.

  3. From the Compare repositories dialog, open the Extract RPD as the Original Repository.

  4. When prompted, specify the Golden RPD (that is, Admin123) password to open the Extract RPD.

    The Oracle BI Administration Tool analyzes the RPDs and displays a list of differences.

  5. Click Create Patch to display Create Patch dialog, and specify a patch file name and location (for example: C:\Work\Patch\patch.xml).

  6. Click Save.

3.4.15.7 Apply the Patch for the New RPD

  1. Apply the patch obtained from the previous task using the biserverxmlexec command with the following commands and parameters:

    -P Password of GoldenRPD

    -I Path_Name\File_Name of the Patch.xml file

    -S Password of the RuntimeRPD

    -B <Path>\GoldenRPD.rpd

    -O <Path>\RestoreRPD.rpd

    Note: RestoreRPD.rpd referred here is the name of the Restored RPD

    For example: C:\RUP3\oraclebi\orahome\bifoundation\server\bin>biserverxmlexec.exe -P Admin123 -I C:\Work\Patch\patch.xml -S welcome1 -B C:\Work\GoldenRPD\GoldenRPD.rpd -O C:\Work\RestoreRPD\RestoreRPD.rpd

3.4.15.8 Upload the New RPD

  1. Use Oracle Fusion Middleware Control to upload the new RPD.

    Tip: In Oracle Fusion Middleware Control, use the Upload BI Server Repository area on the Business Intelligence\coreapplication\Deployment\Repository tab.

    For detailed instructions on how to upload an RPD file, see Section 10.2 'Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location' in Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

3.4.16 Setup Step: Configure Oracle HTTP Server

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Work with your Web administrator to configure Oracle HTTP Server so that URLs for Oracle BI Applications 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 Oracle BI Applications Configuration Manager, Functional Setup Manager, and DAC Server.

To configure Oracle HTTP Server:

  1. Access the directory APPTOP/instance/CommonDomain_webtier/config/OHS/ohs1/moduleconf

    where APPTOP is the Application home folder.

  2. Open the file FusionVirtualHost_bi.conf.

  3. 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.

    Note: For each LocationMatch entry, make sure that you have a space character between the value (for example, DACServer) and the closing '>' character.

  4. Restart Oracle HTTP Server by accessing the directory APPTOP/instance/CommonDomain_webtier/bin and running the following commands:

    ./opmnctl stopall

    ./opmnctl startall

  5. Provide the URL for Oracle BI Applications Configuration Manager to your end users.

3.4.17 Setup Step: Configure SSO and Portlet Provider for Oracle BI Applications Configuration Manager and Functional Setup Manager

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

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 Oracle BI Applications and FSM, do the following:

  1. Configure SSO as described in Section 3.4.17.1, "How to configure SSO for Oracle BI Applications Configuration Manager and FSM".

  2. Configure Portlet Provider as described in Section 3.4.17.2, "How to configure Portlet Provider for Oracle BI Applications Configuration Manager and FSM".

3.4.17.1 How to configure SSO for Oracle BI Applications Configuration Manager and FSM

To configure SSO for Oracle BI Applications Configuration Manager and Functional Setup Manager using Oracle Access Manager:

  1. In a supported Web browser, login 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.

  2. Display the Policy Configuration tab.

    This screenshot is described in surrounding text.

  3. Create a policy for Oracle BI Applications Configuration Manager, as follows:

    1. In the Browse pane, navigate to Application Domains\bi.

    2. Double-click the Resources node, to display the bi Resources page.

      This screenshot is described in surrounding text.

    3. Use the New Resource option to display the Create Resource page.

    4. Specify the following details:

      Resource type: http

      Host Identifier: OraFusionApp

      Resource URL: /biacm/.../*

      This screenshot is described in surrounding text.

    5. Save the details.

  4. 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.

  5. Create a policy for Functional Setup Manager, as follows:

    1. In the left hand Browse pane, navigate to Application Domains\bi.

    2. Double-click the Resources node, to display the bi Resources page.

    3. Use the New Resource option to display the Create Resource page.

    4. Specify the following details:

      Resource type: http

      Host Identifier: OraFusionApp

      Resource URL: /setup/.../*

      This screenshot is described in surrounding text.

    5. Save the details.

3.4.17.2 How to configure Portlet Provider for Oracle BI Applications Configuration Manager and FSM

To configure Portlet Provider for Oracle BI Applications Configuration Manager and Functional Setup Manager using Oracle Access Manager:

  1. In a supported Web browser, login 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.

  2. Display the Policy Configuration tab.

    This screenshot is described in surrounding text.

  3. Create a policy for Oracle BI Applications Configuration Manager, as follows:

    1. In the Browse pane, navigate to Application Domains\bi.

    2. Select the Resources node.

      This screenshot is described in surrounding text.

    3. Use the New Resource option to display the Create Resource page.

    4. Specify the following details:

      Resource type: http

      Host Identifier: OraFusionApp

      Resource URL: /setup/portlets/…/*

      Protection Level: Excluded

      This screenshot is described in surrounding text.

    5. Save the details.

3.4.18 Setup Step: Enable Offerings for Deployment

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Use Oracle BI Applications Configuration Manager to enable the Oracle BI Applications Offerings that you have purchased.

To enable Oracle BI Applications Offerings for deployment:

  1. Login 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 Section A.2, "How to Start Oracle BI Applications Configuration Manager"

  2. Select the Manage BI Applications link to display the Manage Business Intelligence Applications dialog.

  3. Display the BI Application Offerings tab.

  4. Select the Enabled check box next to each Offering you want to deploy.

    Enabling Offerings enables the applicable setup seed data in Oracle BI Applications Configuration Manager.

    Note:

    Enable only the Offerings that have been purchased so that you do not display data for other Offerings. You can enable additional Offerings as you purchase them.

  5. Click Save to save your changes.

  6. To exit this screen, click Done.

3.4.19 Setup Step: Set Languages for Data Load

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

Oracle BI Applications 11g Release 1 (11.1.1) loads data from a Fusion Applications source to 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 Oracle Business Analytics Warehouse.

To specify Oracle Business Analytics Warehouse languages:

  1. Login 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."

  2. Select the Manage BI Applications link to display the Manage Business Intelligence Applications screen.

  3. Display the Warehouse Languages tab.

  4. 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 default installed language. 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.

  5. 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 Oracle Business Analytics Warehouse for any languages missing in the Source system.

  6. Click Save to save your changes.

3.4.20 Setup Step: Editing Preferred Currency Display Names

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

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:

  1. Login 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 Section A.2, "How to Start Oracle BI Applications Configuration Manager"

  2. From the Tasks bar, click Manage Preferred Currencies to display the "Manage Preferred Currencies dialog".

  3. Select a currency in the Preferred Currencies list. Selecting the currency displays the associated modules in the bottom table.

  4. Click the value in the Preferred Currency Name column (or click the Edit icon) to display the Preferred Currency Name dialog.

  5. 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 of Oracle Business Intelligence.

  6. Click Save and Close.

3.4.21 Setup Step: Enable Document Currency

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

By default, Document currency is excluded from the Currency drop-down list (located in the Preferences tab of the My Accounts dialog 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:

  1. Start the Oracle BI Administration Tool.

  2. Click Manage, and then Identity.

  3. In the Identity Manager dialog, click BI Repository.

  4. Display the Application Roles tab.

  5. For each of the security groups in the RPD list above, do the following:

    1. Double-click the security group.

    2. Click Permission, and then display the Data Filters tab.

    3. 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')

    4. Repeat steps for each of the remaining security groups.

  6. Save the RPD:

3.4.22 Setup Step: Run Domains ETL

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

This task loads source-specific data into 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 FSM. The data from the Fusion Applications source is loaded into the Oracle BI Applications Configuration Manager tables using ETL routines.

Work with your ETL Administrator to complete this procedure.

Note: Before you run ETL Execution Plans, make sure that you have set the environment variables as specified in Section A.7.2, "Before Installing Informatica PowerCenter for Oracle BI Applications Environments.".

To run domains ETL:

  1. Start DAC Client.

    To start DAC Client, navigate to the \dac\ folder and execute the file startclient.bat.

  2. At the Login dialog, select an appropriate Connection.

  3. When prompted for a User Name and Password, enter a User Name with the appropriate permissions to access the Execute view in DAC Client and to run ETL.

    For more information about granting access to Oracle BI Applications Components, see Section 3.4.6, "Setup Step: Grant User Access to Oracle BI Applications Components"

  4. In DAC Client, navigate to the Execute view, and display the Execution Plans tab.

  5. Run the Execution Plan named 'Domains - Fusion 1.0'.

    This screenshot is described in surrounding text.

3.4.23 Setup Step: Verifying Duty Roles required for Oracle BI Applications

This task is performed as part of Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications".

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, "How to Verify Duty Roles required for Oracle BI Applications,".

3.5 Platform-Specific and Topology-Specific Setup Steps

This section contains setup steps that are specific to Windows environments, or setup steps that apply only to a specific topology (for example, when Informatica Services or DAC Server are not installed on the BI Domain machine). Always use Section 3.1.1, "High-level Tasks for Setting Up Oracle BI Applications" for guidance on the appropriate tasks for your deployment.

This section contains the following tasks:

3.5.1 Setup Step: Creating the Informatica Repository Service

Follow this procedure to create the Informatica Repository Service.

Note: Before you log into Informatica Administrator, make sure that the Informatica service is running. To start the Informatica Service, use the Start Informatica Services program. On Windows, you can also use the Windows Services dialog to start the 'Informatica 9.1.0' service. On UNIX, use the infaservice [startup | shutdown] command.

For detailed information about creating a Repository Service, refer to the Informatica documentation.

To create the Informatica Repository Service:

  1. Open Informatica Administrator and display the Domain tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Domain Navigator, select the root Domain, then click Actions, then New, then PowerCenter Repository Service, to display the New PowerCenter Repository Service wizard.

  3. Use the 'Specify the properties for this new PowerCenter Repository Service' dialog to specify a Name (for example, BIA_RS), Location, License, and Node, then click Next.

  4. Use the 'Specify the database properties for this new PowerCenter Repository Service' dialog to specify a Database Type, Username, Password, Connection String, and Code Page.

    Notes:

    • The Username and Password are for the database account that you created for the Informatica repository

    • If you specify the wrong code page, you cannot correct this later. If the code page is incorrect, then you must create a new Repository Service.

  5. In the 'Specify the creation options for the new PowerCenter Repository Service' area, select the 'No content exists under specified connection string. Create new content' radio button. For detailed information about creating a Repository Service, refer to the Informatica documentation.

  6. Click Finish.

3.5.2 Setup Step: Restoring the Prebuilt Informatica Repository

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:

3.5.2.1 Restoring the Prebuilt Informatica Repository for Environments in English

You use the Restore option in Informatica Administrator to load the prebuilt Oracle_BI_DW_Base repository.

To load the prebuilt Oracle_BI_DW_Base.rep repository into Informatica:

  1. Copy the file ORACLE_HOME/biapps/admin/provisioning/dac/infabaseline/Oracle_BI_DW_Base.rep file on the installation machine to the following directory on the machine 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 3.3.3, "Summary of Home Directories"

  2. In Informatica Administrator, select the Repository Service.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  3. In the General Properties area of the Properties tab, make sure 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.

  4. In the Actions menu at the top right-hand side, choose Actions, then Repository Contents, then Delete.

  5. At the Delete Contents for <repository name> dialog box, enter the repository username and password (for example, Administrator\Administrator), then click OK.

  6. In the Actions menu at the top right-hand side, choose Actions, then Repository Contents, then Restore.

  7. At the Restore Contents for <repository name> dialog, enter the repository username and password (for example, Administrator\Administrator), then click OK.

  8. Choose Actions, then Repository Contents, then Restore.

  9. At the Restore Contents dialog, select Oracle_BI_DW_Base.rep from the Select Backup File drop-down list.

  10. Select the Restore as New check box.

  11. Click OK to start the restore process.

  12. When the restore process is complete, click Close (or click Save first to save the logging information).

    When the restore is complete (the process typically takes approximately ten to twenty minutes depending on repository size and network speed), you will see a 'Success' message.

  13. When a repository is restored, the repository becomes a standalone repository. After restoring the repository, you need to promote it to a global repository.

  14. Change the OperatingMode value to Normal.

    To change the Operating Mode, display the Properties tab, in the General Properties area, click Edit, then click the OperatingMode drop-down list, and select Normal.

    Note: If you do not set the Operating Mode to Normal, then the Integration Service will not restart.

  15. If prompted, enter the repository username and password.

3.5.2.2 Restoring the Prebuilt Informatica Repository on a Non-English Operating System

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:

  1. Copy the ORACLE_HOME/biapps/admin/provisioning/dac/infabaseline/Oracle_BI_DW_Base.rep file on the installation machine to the following directory on the machine 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 3.3.3, "Summary of Home Directories"

  2. Open a command window.

  3. Enter the following command to connect to the repository:

    Pmrep connect -r Repository_Name -d Domain

  4. 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.

3.5.3 Setup Step: Creating the Informatica Integration Service

Follow this procedure to create the Informatica Integration Service.

Note: Before you begin, make sure that you have set up the environment variables for Informatica PowerCenter, as described in Section A.7.4, "Installing Informatica PowerCenter Services and Hotfix 2.".

For detailed information about creating an Integration Service, refer to the Informatica documentation.

To create the Informatica Integration Service

  1. Open Informatica Administrator and display the Domain tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Domain Navigator, select the root Domain, then click Actions, the New, then PowerCenter Integration Service, to display the New PowerCenter Integration Service wizard.

  3. Use the 'Specify the properties for this new PowerCenter Integration Service' dialog to specify a Name (for example, BIA_IS), Location, License, and Node, then click Next.

  4. Use the 'Specify the PowerCenter Integration Service and its login credentials' dialog to select the Repository Service that you created in a previous step, and specify the repository username and password (for example, Administrator\Administrator).

  5. In the 'Select the data movement mode' area, select the appropriate Code Page setting from the Data Movement Mode drop down list.

  6. Click Finish.

    The Integration Service will only start if the Repository Service is operating with the Operating Mode set to 'Normal'.

3.5.4 Setup Step: Copying Source Files to the Informatica PowerCenter Services machine

You need to copy source files from the Oracle BI Applications installation directory to the Informatica directory on the Informatica PowerCenter Services machine.

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 3.5.15.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:

  1. 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 machine, 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

3.5.5 Setup Step: Setting PowerCenter Integration Services Relaxed Code Page Validation

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:

  1. Open Informatica Administrator and display the Domain tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Domain Navigator pane, select the Integration Service.

  3. Display the Properties page.

  4. In the Configuration Properties area, click Edit to display the Edit Configuration Properties page.

  5. Clear the ValidateDataCodePages check box.

3.5.6 Setup Step: Setting PowerCenter Integration Services Custom Properties

Follow this procedure to set PowerCenter Integration Services custom properties.

To set Informatica PowerCenter Integration Services Custom Properties:

  1. Open Informatica Administrator and display the Domain tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Domain Navigator pane, select the Integration Service.

  3. Display the Properties page.

  4. In the Custom Properties area, click Edit to display the Edit Custom Properties page.

  5. Use the New option to display the New Custom Property dialog, and add the following Custom Properties:

    • Table 3-5 Custom Properties for Informatica PowerCenter Integration Services

      Custom Properties Name Custom Properties Value Notes

      overrideMpltVarWithMapVar

      Yes

      Enables Informatica to evaluate parameters within mapplets.

  6. Click OK to save the details.

  7. Ensure that the Integration Service and Repository Service that you created during the Informatica PowerCenter installation are running.

3.5.7 Setup Step: Creating the Repository Administrator User in the Native Security Domain

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, then 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, refer to the Informatica documentation.

To use the default Administrator user in the native security domain:

  1. Open Informatica Administrator and display the Security tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Users area, expand the Native directory and select Administrator.

    Note: Do not select an existing user from an LDAP domain.

  3. Display the Privileges tab, and use the make sure that the correct Domain and Repository Service are selected.

    This screenshot is described in surrounding text.

  4. Click OK.

To create a new Repository Administrator defined in the native security domain:

  1. Open Informatica Administrator and display the Security tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Users area, click Actions, then Create User to display the Create User dialog.

    Note: Do not create this user in an LDAP domain.

  3. Use the Create User dialog to specify the user details, then click OK.

  4. In the Users area, select the new user, display the Privileges tab, then click Edit to display the Edit Roles and Privileges dialog.

  5. Use the Roles tab and Privileges tab to select the appropriate Domain and Repository Service.

    This screenshot is described in surrounding text.

  6. Click OK.

3.5.8 Setup Step: Extending the BI Domain

During the Fusion Applications installation and provisioning process, the BI Domain is created. However, none of the Oracle BI Applications components (Oracle BI Applications 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:

  • install_dwtools.py

  • configure_dwtools.py

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.

The install_dwtools.py and configure_dwtools.py scripts also deploy ATG, which is a J2EE component used by Oracle BI Applications Configuration Manager and Functional Setup Manager.

Oracle BI Applications 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:

  1. Stop the Administration Server.

  2. 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, /instance/domains/<hostname>/BIDomain).

    • INFA_HOME is the location of the user-specified Informatica installation directory on the machine that hosts Informatica PowerCenter Services (for example,\informatica\9.1\).

    • INFA_DOMAIN_FILE is the location and name of the Informatica domains fine infa.domain on the machine 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 3.4.2, "Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, machine12345.example.com:1521/BIA11G_DW.

    • DW_DB_SCHEMA is the name of the DW schema that you created when you performed the setup steps in Section 3.4.2, "Setup Step: 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 Oracle BI EE platform MDS schema (that is, not the Fusion Applications schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, machine12345.example.com:1521/BIA11G_MDS.

    • MDS_DB_SCHEMA is the name of the Oracle BI EE platform MDS schema (that is, not the Fusion Applications MDS schema). This schema was created during the provisioning of Oracle Business Intelligence, as part of the Oracle Fusion Applications installation process. For example, BIA11G_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 3.4.2, "Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, machine12345.example.com:1521/BIA11G_DAC.

    • DAC_SCHEMA is the name of the DAC schema that you created when you performed the setup steps in Section 3.4.2, "Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example, you might have specified the name BIA11G_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' 'BIA11G_DW' 'jdbc:oracle:thin:@localhost:1521/orcl' 'BIA11G_MDS' 'jdbc:oracle:thin:@localhost:1521/orcl' 'BIA11G_DAC' 'bi_server1'

    Note:

    When you run the script, you are also prompted for passwords.

  3. Start the Administration Server.

  4. 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 machine 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.

3.5.9 Setup Step: Configuring the Oracle BI Connection Pools

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:

  • Oracle Business Analytics Warehouse data source connection pools:

    • Oracle Data Warehouse Connection Pool

    • Oracle Data Warehouse Repository InitBlock Connection Pool

  • Connection pool for Oracle BI Applications Configuration Manager

  • 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 Fusion Transactional Business Intelligence projects

  • OracleBIAppsCRM.rpd - a partial repository file containing Oracle BI Applications and Oracle Fusion Transactional Business Intelligence projects for CRM modules

  • OracleBIAppsERP.rpd - a partial repository file containing Oracle BI Applications and Oracle Fusion 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):

  1. 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 3.4.2, "Setup Step: Create Schemas and Data Warehouse Objects for Oracle BI Applications". For example:

      (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=localhost)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=orcl)))

    • DW_DB_SCHEMA is the name of the DW schema that you created when you performed the setup steps in Section 3.4.2, "Setup Step: 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 machine 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 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 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 Oracle BI Applications Configuration Manager. The Oracle DB InitBlock Initialization Connection Pool is configured to the same values as those for the HCM_OLTP connection.

  2. 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).

  3. Using OPMN, restart the BI Server.

3.5.10 Setup Step: Configuring Physical Data Source Connections in DAC

Follow this procedure to configure physical data source connections in DAC. You must configure the following data sources:

  • DataWarehouse - For the connection to Oracle Business Analytics Warehouse.

  • BIACM - For the connection to Oracle BI Applications Configuration Manager.

  • FUSION_V1 - For connection to the Oracle BI Server for the Fusion Application domains.

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:

  1. Start DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file. The Login dialog opens.

  2. In the Login dialog, select the Connection.

  3. Enter the User Name and Password. This user must be granted the Oracle BI Applications Administrator Duty Role. See Section 3.4.6, "Setup Step: Grant User Access to Oracle BI Applications Components"

  4. 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.

  5. 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 Oracle Business Analytics Warehouse.

    BIACM

    Source

    Oracle (Thin)

    The table owner and password for Oracle Business Analytics Warehouse.

    Note: The prefix_DW schema contains the Oracle BI Applications Configuration Manager tables.

    FUSION_V1

    Source

    BI Server

    The user name and password for the ETL user specified in Section 3.4.5, "Setup Step: Create a User for ETL"

  6. Click Test Connection for each connection to ensure the connection works.

  7. Click Save.

3.5.11 Setup Step: Configuring Relational Connections in Informatica

This section describes how to configure relational connections in Informatica.

Note: Unicode to Unicode is the only supported configuration mode for Oracle Business Intelligence Applications 11g Release (11.1.1).

Before you configure relational connections in Informatica, ensure that Repository Services and Integration Services are enabled and running.

To configure relational connections in Informatica:

  1. In Informatica PowerCenter Workflow Manager, select Connections, then Relational, to display the Relational Connection Browser.

  2. Create a Relational Connection of type Oracle for DataWarehouse with the following settings:

  3. Create a Relational Connection of type Oracle for BIACM with the following settings:

  4. Create a Relational Connection of type ODBC for FUSION_V1 with the following settings:

Note:

You must configure connections for the Fusion Applications domains listed above, even if you have not deployed the associated applications.

3.5.12 Setup Step: Setting the SiebelUnicodeDB Property in Informatica Integration Services

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:

  1. Open Informatica Administrator and display the Domain tab.

    For information about how to access Informatica Administrator, see Section A.1, "How to Log Into Informatica Administrator".

  2. In the Domain Navigator pane, select the Integration Service.

  3. In the Properties tab, scroll down to the Custom Properties area, and click Edit.

  4. In the Name field, enter the following:

    SiebelUnicodeDB

  5. In the Value field, enter connect strings for the OLTP and OLAP data sources in the following format:

    user_OLTP@ConnectString_OLTP user_OLAP@ConnectString_OLAP

    where:

    • user_OLTP is the user name for the ETL user specified in Section 3.4.5, "Setup Step: 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 3.4.10, "Setup Step: 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 Oracle Business Analytics Warehouse. It must match exactly the value you entered for the User Name field when creating the relational connection for Oracle Business Analytics 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 Oracle Business Analytics Warehouse in Informatica Workflow Manager.

    Note:

    • Ensure that you enter a space between the values for ConnectString_OLTP and user_OLAP. For example:

      oltp@db204007.host.com olap@db204008.host.com

    • You must enter the user names and connection strings in the same upper and lower case letters as you used for the relational connections in Informatica Workflow Manager.

3.5.13 Setup Step: Enabling User Currency Preference Settings

This section provides instructions for enabling user currency preference settings for Oracle BI Applications. This section contains the following topics:

3.5.13.1 Enabling the Currency User Preference File for Oracle BI Applications

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

To enable user currency preference file for Oracle BI Applications:

  1. Access the following directory on the Oracle BI instance:

    INSTANCE_HOME\config\OracleBIPresentationServicesComponent

  2. Open the file instanceconfig.xml for editing.

  3. Modify the UserprefCurrenciesConfigFile parameter in instanceconfig.xml to point to userpref_currencies_OBIA.xml.

  4. Save and close instanceconfig.xml.

  5. Using OPMN, restart Presentation Services.

3.5.14 Setup Step: Registering Source Systems

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:

  1. 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."

  2. Select the Define BI Applications Instance link to display the Define Business Intelligence Applications Instance dialog.

  3. Display the Source Systems tab.

  4. Specify a Source System as follows.

    1. Click the Add icon to display the Register Source dialog.

    2. 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 Oracle BI Applications 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.

    3. Save the details.

    Note:

    When you register your source system in Oracle BI Applications Configuration Manager, the appropriate setup seed data is enabled based on your Oracle Fusion Applications selections. For example,

3.5.15 Setup Step: Configure DAC Integration Settings

This section explains how to configure DAC integration settings. It contains the following topics:

3.5.15.1 Setting DAC System Properties

This section describes how to set DAC System Properties to ensure proper integration between DAC Client, the DAC Server, and Informatica.

To set DAC System Properties:

  1. Start DAC Client by navigating to the \dac directory and double-clicking the startclient.bat file. The Login dialog opens.

  2. In the Login dialog, select the Connection.

  3. Enter the User Name and Password for a user with the Oracle BI Applications Administrator Duty Role.

    For more information about assigning the Oracle BI Applications Administrator Duty Role, see Section 3.4.6, "Setup Step: Grant User Access to Oracle BI Applications Components".

  4. From the Views menu, click Setup, and then click DAC System Properties.

  5. 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.

3.5.15.2 Registering Informatica Services in DAC

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:

  1. In DAC, navigate to the Setup view, and then display the Informatica Servers tab.

  2. For the Informatica Integration Service that you want to register, do the following:

    1. 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 that was created manually or was created by the WCA script (for example, BIA_IS).

      Tip: To find out the name of the Integration Service, log into Informatica Administrator 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 3.5.7, "Setup Step: 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.

    2. Click Test Connection to ensure that the connection works.

      Note: Integration Services must be running.

    3. Click Save to save the details.

  3. For the Informatica Repository Service you want to register, do the following:

    1. 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.

      Specify the name of the Repository Service that was created manually or was created by the WCA script (for example, BIA_RS).

      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, BIA_RS.

      Inactive

      Indicates whether the Repository Service will participate in the ETL process.

    2. Click Test Connection to ensure that the connection works.

      Note: The Repository Service must be running.

    3. Click Save to save the details.

3.6 Upgrading Oracle BI Applications

This section explains how to upgrade Oracle BI Applications from Version 11.1.1.6.0 to Version 11.1.1.6.2. Before you start the upgrade process, Oracle recommends that you read Section 3.6.1, "Overview to Upgrading Oracle BI Applications". Then, follow the detailed upgrade tasks in Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

This section contains the following topics:

Pre-requisites

It is assumed that you currently have Fusion Applications 11.1.3 with Oracle BI Applications 11.1.1.6.0 deployed, and that you want to upgrade to Fusion Applications 11.1.4 with Oracle BI Applications 11.1.1.6.2. Before you upgrade Oracle BI Applications, you must perform the Fusion Applications Install and Provisioning for the 11.1.4 release. The BI Install and Provisioning phase upgrades the following components:

Oracle BI Applications Release 11.1.1.6.2 includes the new Oracle BI Applications Upgrade Tool, which upgrades the schema and metadata for DAC, Oracle BI Configuration Manager and FSM, and ATGLite. The Upgrade Tool also upgrades the schema for Oracle Business Analytics Warehouse (via DAC).

3.6.1 Overview to Upgrading Oracle BI Applications

The section provides an overview of the upgrade process.

3.6.1.1 About Oracle BI Applications Platform binary upgrades

The following components are upgraded:

  • Oracle BI Applications Configuration Manager, Functional Setup Manager and the DAC Server. The .ear files for these components are upgraded to 11.1.1.6.2 as part of the Fusion Applications Install and Provisioning process. When the WebLogic Server for the BI Domain is restarted, the new ear files are deployed.

  • Informatica PowerCenter platform. Oracle BI Applications Release 11.1.1.6.2 requires Informatica PowerCenter Version 9.1 HotFix 2. When you upgrade to Informatica PowerCenter Version 9.1 HotFix 2, you might need to re-configure some integration settings (for more details, see Section 3.6.2.4, "Upgrade Task: Upgrade the Informatica PowerCenter Platform to 9.1 HotFix 2").

  • DAC Client. You must install DAC Client version 11.1.1.6.2 (for more details, see Section 3.6.2.2, "Upgrade Task: Install DAC Client 11.1.1.6.2.").

3.6.1.2 About Oracle BI Applications Component Repositories - Schema Upgrades and Seed Data Updates

The following components are upgraded:

  • Oracle Business Intelligence Data Warehouse Administration Console (DAC) Repository. The DAC Repository must be upgraded to version 11.1.1.6.2. This upgrade is performed using the Oracle BI Applications Upgrade Tool.

  • Informatica Repository. The Informatica Repository must be upgraded to version 11.1.1.6.2. This upgrade is performed using the Informatica repository upgrade capabilities.

  • Oracle BI Applications Configuration Manager and Functional Setup Manager Repositories. Schema upgrades and seed data updates for Oracle BI Applications Configuration Manager and Functional Setup Manager and ATGLite are performed using the Oracle BI Applications Upgrade Tool.

  • RPD Message Strings. RPD Message Strings are updated using the Oracle BI Applications Upgrade Tool.

  • Oracle Business Analytics Warehouse. The Oracle Business Analytics Warehouse schema is upgraded to version 11.1.1.6.2 using the Oracle BI Applications Upgrade Tool, which in turn will use DAC to perform the upgrade.

After the Oracle Business Analytics Warehouse schema is upgraded, you must re-load the data in Oracle Business Analytics Warehouse by running a Full Load to populate data (for more details, see Section 3.6.2.7, "Upgrade Task: Reload Oracle Business Analytics Warehouse").

3.6.1.3 About Other Components and Metadata Upgrades

The following components are upgraded:

  • Security Application Policies.

    Oracle BI Applications Security Policies should be applied if you have upgraded your Fusion Applications from 11g Release 1, Update 1 to 11g Release 1, Update 2 and are now upgrading to 11g Release 4 and have not applied the BI Application Security Policies as described in Fusion Applications Release Notes for 11g Release 1, Update 2 on My Oracle Support: Oracle Fusion Applications Release Notes, 11g Release 1, Update 2 (11.1.3.0.0) [ID 1439014.1] > Section 4.3.8.1 Upgrading Security Application Policies for Oracle Business Intelligence Applications and Oracle Fusion Transactional Business Intelligence. If this step was not completed earlier, you must perform this step as a pre-requisite (see Step 1 in Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications").

  • Oracle BI Metadata Repository (RPD) and Presentation Catalog. The Oracle BI Metadata Repository (RPD) and Presentation Catalog are upgraded to version 11.1.1.6.2 as the last step by BI provisioning during FA Install and Provisioning. No manual step is required.

3.6.2 High Level Tasks for Upgrading Oracle BI Applications

To upgrade Oracle BI Applications, you must complete the following tasks, in order. Each high-level task breaks down into a list of detailed steps.

Note: Before you start, make sure that the Fusion Applications Install and Provisioning phase for the Release 11.1.4 release has been completed. For more information about the Install and Provisioning phase, or the upgrade process in general, see Section 3.6.1, "Overview to Upgrading Oracle BI Applications".

  1. If you have upgraded Fusion Applications from 11g Release 1, Update 1 to 11g Release 1, Update 2 and are now upgrading to 11g Release 4 and have not applied the BI Application Security Policies, then you must do this now. If you have applied the BI Application Security Policies, then you can skip this step.

    Applying the BI Application Security Policies is described in Fusion Applications Release Notes for 11g Release 1, Update 2 on My Oracle Support: Oracle Fusion Applications Release Notes, 11g Release 1, Update 2 (11.1.3.0.0) [ID 1439014.1] > Section 4.3.8.1 Upgrading Security Application Policies for Oracle Business Intelligence Applications and Oracle Fusion Transactional Business Intelligence.

  2. Install the required patches, as described in Section 3.6.2.1, "Install the Required Patches".

  3. Install DAC Client 11.1.1.6.2, as described in Section 3.6.2.2, "Upgrade Task: Install DAC Client 11.1.1.6.2.".

  4. Use the BI Applications Upgrade Tool to upgrade multiple components, as described in Section 3.6.2.3, "Upgrade Task: Run the BI Applications Upgrade Tool".

  5. Upgrade the Informatica PowerCenter Platform to Version 9.1 HotFix 2, as described in Section 3.6.2.4, "Upgrade Task: Upgrade the Informatica PowerCenter Platform to 9.1 HotFix 2".

  6. Upgrade the Informatica Repository, as described in Section 3.6.2.5, "Upgrade Task: Upgrade the Informatica Repository".

  7. Configure DAC and Informatica integration settings, as described in Section 3.6.2.6, "Upgrade Task: Configure DAC and Informatica integration settings".

  8. Reload Oracle Business Analytics Warehouse (including Domains ETL execution), as described in Section 3.6.2.6, "Upgrade Task: Configure DAC and Informatica integration settings".

3.6.2.1 Install the Required Patches

Download and install the following patches from the My Oracle Support\Patches and Updates area:

  • 13969226 - DAC 11.1.1.6.2 CUMULATIVE PATCH 2.

    Note:

    Before you apply this patch, you must shut down the Weblogic Server.

  • 13954196 - dac upgrade patch file missing in the installed location for rup3 upgrade.

  • 14016865 - biappsinst patch 4 biappsshiphome_11.1.1.6.2.

3.6.2.2 Upgrade Task: Install DAC Client 11.1.1.6.2.

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

You must install the DAC Client 11.1.1.6.2 on all machines where DAC Client 11.1.1.6.0 was installed.

  1. Obtain the Oracle BI Applications Client Installer executable from one of the following locations:

    - On Windows, in the folder <Install Repository>\biappsshiphome\shiphome.

    - On Linux and UNIX, in the folder <Install Repository>/biappsshiphome/dist/stage/clients/biappsclients.

  2. For each DAC Client machine, install DAC Client as described in Section 3.4.7, "Setup Step: Install and Set Up DAC Client", including copying the authentication file and logging in for first time.

  3. Copy the DAWSystem.jar from the patch 13969226 DAC 11.1.1.6.2 CUMULATIVE PATCH 2 to the DAC Client installation. This file is available in the patch in the files/dac path inside the patch directory.

3.6.2.3 Upgrade Task: Run the BI Applications Upgrade Tool

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

You use the Oracle BI Applications Upgrade Tool to upgrade schema and seed data for the following components:

  • The DAC Schema and metadata.

  • The schema for Oracle Business Analytics Warehouse.

  • The schema and seed data for Oracle BI Applications Configuration Manager, FSM, and ATGLite.

  • The RPD Message Strings.

The Oracle BI Applications Upgrade Tool is a command line utility that is available in the following Oracle Home for BI location:

ORACLE_HOME/biapps/tools/lib/biappsrepositoryutil.jar

3.6.2.3.1 Update the Schema Version Registry Entry Update

Perform the following step if you initially deployed BI Applications with Fusion Applications V1 or with Fusion Applications RUP1.

Note: You do not need to perform this step if you initially deployed BI Applications with Fusion Applications RUP2.

If your BI Applications system has been upgraded to 11.1.1.6.0 (RUP2) from either 11.1.1.5.1 (v1) or 11.1.1.5.2 (RUP1), then the schema version registry needs to be updated to 11.1.1.6.0 for the Business Analytics Warehouse and DAC schemas. The BI Applications Upgrade Tool make use of these entries to locate the upgrade artifacts.

To update the schema version registry:

  1. Connect to Business Analytics Warehouse (DW_) and DAC repository (DAC_) Database(s).

  2. Execute following queries:

    update  schema_version_registry set version  ='11.1.1.6.0' where owner = '<DW_USER_NAME>' and  mr_name ='DW' ; 
update  schema_version_registry set version  ='11.1.1.6.0' where owner = '<DAC_USER_NAME>' and  mr_name ='DAC'  ; 
Replace the following values in above queries:
DAC_USER_NAME - DAC Repository schema user name 
DW_USER_NAME - DW Repository schema user name  
e.g. update  schema_version_registry set version  ='11.1.1.6.0' where owner = 'fusion_DW' and  mr_name ='DW' ;
3.6.2.3.2 Upgrade ATGLite, FSM, and Oracle BI Applications Configuration Manager Components

Run the Oracle BI Applications Upgrade Tool, as follows:

Note: You must perform the steps in the order specified below.

  1. Navigate to the directory ORACLE_HOME/biapps/tools/lib.

  2. Use the Oracle BI Applications Upgrade Tool to upgrade the DAC Schema and metadata using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeDAC bi.oracle.home=<ORACLE_HOME> dac.repo.user=<DAC_Schema_User> dac.repo.password=<DAC_Schema_Password> dac.conn.url=<dbhost:dbport/db_servicename> db.sys.user=sys db.sys.password=<DB_SYS_PASSWORD> db.conn.sid.url=<dbhost:dbport:dbsid>

    For example:

    java -jar biappsrepositoryutil.jar upgradeDAC bi.oracle.home=/scratch/aime/work/mw3837/Oracle_BI1 dac.repo.user=FUSION_DAC dac.repo.password=welcome1 dac.conn.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb

  3. Use the Oracle BI Applications Upgrade Tool to upgrade the Oracle Business Analytics Warehouse schema using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeDW bi.oracle.home=<ORACLE_HOME> dw.user=<DW_Schema_User> dw.password=<DW_Schema_Password> dw.conn.url=<dbhost:dbport/db_servicename> db.sys.user=sys db.sys.password=<DB_SYS_Password> db.conn.sid.url=<dbhost:dbport:dbsid>dac.repo.password=<DAC_Schema_Password> dac.conn.url=<dbhost:dbport/db_servicename> dac.repo.user=<DAC_Schema_User>

    For example:

    java -jar biappsrepositoryutil.jar upgradeDW bi.oracle.home=/scratch/aime/work/mw3837/Oracle_BI1 dw.user=FUSION_DW dw.password=welcome1 dw.conn.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dac.repo.password=welcome1 dac.conn.url=machine.company.com:1521/exampledb.company.com dac.repo.user=FUSION_DAC

    Notes:

    As part of the schema upgrade for the Oracle Business Analytics Warehouse from version 11.1.1.6.0 to 11.1.1.6.2, DAC generates a file named upgrade-questionable.sql. This file is located in the <Domain_Home>\dac\conf\sqlgen\sql\oracle directory. DAC will not automatically execute this script. You must execute it manually after review by your DBA with corrections made where necessary.

    The upgrade-questionable.sql file for the 11.1.1.6.0 to 11.1.1.6.2 schema upgrade contains the following:

    ALTER TABLE W_PARTY_ORG_DS RENAME COLUMN X_CUSTOM TO X_CUSTOM_OLD ; 
ALTER TABLE W_PARTY_ORG_DS ADD X_CUSTOM VARCHAR2(10 CHAR) ; 
UPDATE W_PARTY_ORG_DS SET X_CUSTOM = X_CUSTOM_OLD ;
ALTER TABLE W_PARTY_ORG_DS DROP COLUMN X_CUSTOM_OLD ;)

    For more information about DAC and the upgrade-questionable.sql files that it generates, see 'About the Upgrade Schema SQL Scripts' in User's Guide for Oracle Business Intelligence Data Warehouse Administration Console.

  4. Use the Oracle BI Applications Upgrade Tool to upgrade the ATGLite component using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=<ORACLE_HOME> atg.repo.user=<DW_SCHEMA_USER> atg.repo.password=<DW_SCHEMA_PASSWORD> db.conn.sid.url=<DBHOSTNAME:DB_PORT:DBSID> dw.user=<DW_SCHEMA_USER> dw.password=<DB_SCHEMA_PASSWORD> atg.db.seed.url=<DBHOSTNAME:DBPORT/DB_SERVICENAME> db.sys.user=sys db.sys.password=<DB_SYS_PASSWORD>

    For example:

    java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=/scratch/aime/work/mw5376/Oracle_BI1/ atg.repo.user=fusion_DW atg.repo.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dw.user=fusion_DW dw.password=welcome1 atg.db.seed.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1

  5. Use the Oracle BI Applications Upgrade Tool to upgrade the schema and seed data for the FSM component using the following command syntax:

    java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=<ORACLE_HOME> fsm.repo.user=<DW_SCHEMA_USER> fsm.repo.password=<DW_SCHEMA_PASSWORD> db.conn.sid.url=<DBHOSTNAME:DB_PORT:DB_SID> dw.user=<DW_SCHEMA_USER> dw.password=<DW_SCHEMA_PASSWORD> fsm.db.seed.url=<DBHOSTNAME:DBPORT/DB_SERVICENAME> db.sys.user=sys db.sys.password=<DB_SYS_PASSWORD>

    For example:

    java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=/scratch/aime/work/mw5376/Oracle_BI1/ fsm.repo.user=fusion_DW fsm.repo.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dw.user=fusion_DW dw.password=welcome1 fsm.db.seed.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1

  6. Use the Oracle BI Applications Upgrade Tool to upgrade the schema and seed data for the Configuration Manager component and the RPD Message Strings using the command below syntax:

    java -jar biappsrepositoryutil.jar upgradeBIACM  bi.oracle.home=<ORACLE_HOME> biacm.repo.user=<DW_SChema_User> biacm.repo.password=<DW_Schema_Password> db.conn.sid.url=<dbhost:dbport:dbsid> dw.user=<DW_Schema_User> dw.password=<DW_Schema_Password> biacm.db.seed.url=<dbhost:dbport/db_servicename> db.sys.user=sys db.sys.password=<DB_SYS_Password>

    For example:

    java -jar biappsrepositoryutil.jar upgradeBIACM  bi.oracle.home=/scratch/aime/work/mw9523/Oracle_BI1/ biacm.repo.user=FUSION_DW biacm.repo.password=welcome1 db.conn.sid.url=machine.company.com:1521:exampledb dw.user=FUSION_DW dw.password=welcome1 biacm.db.seed.url=machine.company.com:1521/exampledb.company.com db.sys.user=sys db.sys.password=welcome1

Notes:

After running the Upgrade Tool for the ATGLite and FSM component upgrades, the following messages may be seen in the ATG and FSM log files. These messages should be ignored.

SEVERE : File and folder require for running seed data change(cleanup-atg.sql) in ATG does not exist at expected location.
SEVERE : File and folder require for running seed data change(fsm-task.xml) in FSM does not exist at expected location.
SEVERE : File and folder require for running seed data change(cleanup-fsm.sql) in FSM does not exist at expected location.

In addition, the ATG log may show errors due to SQL Keywords such as the '/'character:

6.2/from11.1.1.6.0/schema/oracle/atg/upgrade.sql'Line Number: 868 2012-04-12 07:17:19.017 rcu:Extracting Statement from File Name: /scratch/aime/work/mw8793/Oracle_BI1/biapps/admin/provisioning/update/11.1.1.

These errors should be ignored.

3.6.2.4 Upgrade Task: Upgrade the Informatica PowerCenter Platform to 9.1 HotFix 2

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

The Informatica PowerCenter 9.1 and Hotfix 2 installation files, license key, and user documentation, are provided as zip files in the Fusion Applications software repository. These zip files are located in the following folder:

<Fusion Applications Install Repository>\installers\PowerCenter

The PowerCenter folder contains the following files:

  • OS-Specific Server install file - 910HF2_Server_Installer_<OS.zip or tar>.

  • 910HF2_Client_Installer_win32-x86.zip

  • Infa91Docs.zip

  • License Key

Upgrade Informatica PowerCenter Platform:

  1. Review Chapter 1 'Upgrade Overview' in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.1 HotFix 2 to understand the upgrade process and the upgrade tasks you will need to perform. This guide is available with the documentation set for Informatica 9.1 HotFix 2 with file name PC_910HF2_Upgrade85x86x_en.pdf.

  2. Follow the steps documented in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.0.1 HotFix 2 to upgrade your Informatica PowerCenter 8.6.1 environment to Informatica PowerCenter 9.1 HotFix 2. You must upgrade Informatica PowerCenter Services and all instances of Informatica PowerCenter Client Tools.

    1. Upgrade the Informatica domain and server files by running the Informatica PowerCenter 9.1 HotFix 2 installer. Refer to Chapter 2: 'Before You Upgrade the Domain and Server Files' and Chapter 3: 'Domain and Server Files Upgrade' in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.1 HotFix 2.

    2. Upgrade the application services. Refer to Chapter 4: 'Before You Upgrade the Application Services' and Chapter 5: 'Application Service Upgrade' in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.1 HotFix 2.

    3. Upgrade PowerCenter Client Tools by running the Informatica PowerCenter Client Tools 9.1 HotFix 2 installer. Refer to Chapter 6: 'Informatica Client Upgrade' in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.1 HotFix 2.

    4. Perform the post upgrade tasks that are documented in Chapter 7: 'After You Upgrade' in the Upgrade Guide for PowerCenter 8.5.x and 8.6.x for Informatica Version 9.1 HotFix 2.

      On Windows, Oracle Business Intelligence Data Warehouse Administration Console (DAC) requires Informatica to be installed in a directory structure without a space in the folder name For example, Informatica should not be installed in a folder named C:\Program Files\Informatica.

    5. Configure the $PMRootDir property: launch Informatica Administrator, select the Integration Service from the Navigator, click the Processes tab, click Edit, and enter the appropriate value for $PMRootDir.

      Note: When using the Informatica PowerCenter installation wizard in upgrade mode, the property $PMRootDir might not be updated to the upgraded service version installation directory for Informatica PowerCenter 9.1 HotFix 2.

  3. Copy the sources files for Oracle BI Applications to Informatica PowerCenter Services, as follows:

    1. 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

    2. Copy the source files as follows:

      From:

      ORACLE_HOME\biapps\etl\biapps_etl\data_files\src_files

      To:

      INFA_HOME\server\infa_shared\SrcFiles

    For more information about copying the source files, refer to Section 3.5.4, "Setup Step: Copying Source Files to the Informatica PowerCenter Services machine".

3.6.2.5 Upgrade Task: Upgrade the Informatica Repository

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

To upgrade the Informatica Repository with content for 11.1.1.6.2:

  1. Back up (or make a copy of) your current Informatica Repository.

    1. In Informatica Administrator, select the Repository Service for your 11.1.1.6.0 Informatica Repository.

    2. On the Domain tab Actions menu, select Repository Contents > Back Up.

    3. Enter the user name and password. (The Security Domain field appears when the PowerCenter domain contains an LDAP security domain. If necessary, enter the Security Domain.)

    4. Enter a file name, for example bia_111160, and description for the repository backup file.

    5. Choose to skip or back up workflow and session logs, deployment group history, and MX data. You might want to skip these operations to increase performance when you restore the repository. Then click OK.

      The results of the backup operation appear in the activity log.

  2. Copy the file Oracle_BI_DW_Base.rep from the BI ORACLE_HOME/biapps/admin/provisioning/dac/infabaseline directory 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\Backupdirectory.

    • On UNIX or Linux, copy the file to INFA_HOME/server/infa_shared/Backupdirectory.

  3. Create an empty schema to host the Informatica Repository for 11.1.1.6.2. You cannot use the same schema as used for the Informatica Repository for 11.1.1.6.0.

  4. Use Informatica Administrator to create a new Repository Service (for example, named BIA_RS_111162).

    For Database user, Database password and Connect string, enter the values for the new schema created in Step 3. Also, for the Creation Mode, ensure you select Create New Repository Content.

    For detailed steps, see Section "Setup Step: Creating the Informatica Repository Service" in the Installation and Configuration Guide for Oracle Business Intelligence Applications. <* Doc for 11.1.1.6.2 still in progress>.

  5. In Informatica Administrator, use the Repository Service that you created in step 4 (for example, named BIA_RS_11116) to restore the Oracle_BI_DW_Base.rep repository into the new empty schema.

    To do this, see Section "Setup Step: Restoring the Prebuilt Informatica Repository" in the Installation and Configuration Guide for Oracle Business Intelligence Applications for 11.1.1.6.2. <* Doc for 11.1.1.6.2 still in progress>

  6. Launch the Informatica PowerCenter Repository Manager, and connect to both your previous (11.1.1.6.0) and newly created (11.1.1.6.2) Informatica repositories.

  7. In your 11.1.1.6.0 Repository, make sure that all customizations that you have made are in a 'Custom' folder, then delete the following folders: SDE_FUSION_VI_Adaptor, SDE_UNIVERSAL, SILOS and PLP. Note: Do not delete your Custom folder.

  8. Copy the SDE_FUSION_VI_Adaptor, SDE_UNIVERSAL, SILOS and PLP folders from the 11.1.1.6.2 Repository (BIA_RS_111162) into your 11.1.1.6.0 Repository.

    This action updates your Repository with version 11.1.1.6.2 content. You will use this repository to run ETL in Oracle BI Applications 11.1.1.6.2. The Repository Service named BIA_RS_111162 that was created in Step 4 and the Informatica Repository for 11.1.1.6.2 restored in step 5 are no longer required.

3.6.2.6 Upgrade Task: Configure DAC and Informatica integration settings

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

In DAC, the Physical Data Sources connection to the BI Server has changed. The data source named FUSION_V1 must be configured to point to the BI Server. In Version 11.1.1.6.2, the connections FUSION_V1_FSCM, FUSION_V1_HCM, FUSION_V1_CRM are obsolete.

To configure the Physical Data Source to the BI Server in DAC:

  1. In DAC Client, from the Views menu, click Setup, and then click Physical Data Sources.

  2. Update the record for the FUSION_V1 data source as follows:

    Name: FUSION_V1

    Type: Source

    Connection Type: BI Server

    Table Owner and Password: The user name and password for the ETL user specified.

    The Relational Connections of type ODBC for FUSION_V1_CRM, FUSION_V1_FSCM, and FUSION_V1_HCM must be replaced with a Relational Connection of Type ODBC for FUSION_V1. To do this:

    1. In Informatica PowerCenter Workflow Manager, select Connections, then click Relational to display the Relational Connection Browser.

    2. Create a Relational Connection of type ODBC for FUSION_V1 with the following settings:

      Name - FUSION_V1

      Type - ODBC

      User Name - The user name for the ETL user.

      Password - ETL user password.

      Connect String - The BI Server ODBC DSN that was created on the computer that hosts the Integration Services.

      Code Page - UTF-8 encoding of Unicode.

3.6.2.7 Upgrade Task: Reload Oracle Business Analytics Warehouse

This task is performed as part of Section 3.6.2, "High Level Tasks for Upgrading Oracle BI Applications".

You must reload Oracle Business Analytics Warehouse using the Execution Plan named 'Domains - Fusion 1.0. Before you reload the data, you use the Reset option in DAC to truncate tables and delete refresh dates. This allows you to perform a full load of data into Oracle Business Analytics Warehouse.

To reload Oracle Business Analytics Warehouse:

  1. In DAC Client, on the Tools menu, select ETL Management, then Reset Data Warehouse.

    The Reset Data Warehouse dialog is displayed and prompts you to confirm that you want to reset the data warehouse.

  2. Enter the confirmation text in the text box, then click Yes.

  3. Run Domains ETL - In DAC Client, navigate to the Execute view, and display the Execution Plans tab.

  4. Select the Execution Plan named 'Domains - Fusion 1.0'.

  5. On the Connectivity Parameters sub-tab, set the DB_Connection_OLTP parameter for the 'Domains - Fusion 1.0' execution plan to use the FUSION_V1 connection.

  6. Run the Execution Plan named 'Domains - Fusion 1.0'.

    Note: Make sure that all Execution Plans use the FUSION_V1 connection for the DBConnection_OLTP connectivity parameter.

    When DAC has completed running the Execution Plan, verify the data in Oracle Business Analytics Warehouse.

  7. Load data into the Business Analytics Warehouse by running Execution Plans.

    All Execution plans should use the FUSION_V1 connection for the DBConnection_OLTP connectivity parameter.

Go to previous page
Previous		 Go to next page
Next
Go to Documentation Home
Home		 Go to Book List
Book List		 Go to Table of Contents
Contents		 Go to Index
Index		 Go to Feedback page
Contact Us