| Oracle® Business Intelligence Applications Installation Guide 11g Release 1 (11.1.1.8.0) E49132-01 |
|
|
PDF · Mobi · ePub |
| Oracle® Business Intelligence Applications Installation Guide 11g Release 1 (11.1.1.8.0) E49132-01 |
|
|
PDF · Mobi · ePub |
This chapter provides instructions for setting up Oracle BI Applications after exiting Oracle Fusion Applications provisioning. It covers setting up Oracle BI Applications in a single BI domain with the WebLogic Administration Server and Managed Server in the same domain home.
This chapter contains the following sections:
Section 3.1, "Overview of Setting Up Oracle BI Applications"
Section 3.2, "Prerequisites for Setting Up Oracle BI Applications"
This section provides an overview of setting up Oracle BI Applications. It includes the following topics:
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.
During the Fusion Applications installation, the software components of Oracle BI Applications are installed in the Business Intelligence Oracle Home but are not set up.
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 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 applications pillars
SQL Bypass connections FSCM_OLTP, CRM_OLTP, HCM_OLTP, and FBI_OLTP
Static Variables
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). |
|
ODI_HOME |
Location of the ODI home directory. |
|
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). |
Before you begin setting up Oracle BI Applications, do the following:
Review Oracle Fusion Middleware System Requirements and Specifications and ensure your environment meets the minimum requirements:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html
Also review the Certification Matrix for Oracle BI Applications:
http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html
Install Oracle BI Applications using the Oracle Fusion Applications installation and provisioning process. See Oracle Fusion Applications Installation Guide.
Read Chapter 2, "Preinstallation and Deployment Requirements for Oracle BI Applications."
Obtain the following component passwords from the team who installed Oracle Fusion Applications:
RPD password. In the Installation Location dialog in the Oracle Fusion Applications provisioning wizard, an RPD password was entered to access the Oracle BI repository. Oracle Fusion Applications provisioning creates this password and makes it available so that Oracle BI Applications can access the metadata in the repository in the Oracle Fusion Applications environment
Host name. In the Oracle Business Intelligence Configuration dialog, the Host where the Oracle Business Intelligence product was to be installed was entered.
Location of Oracle BI domain. At the conclusion of the Oracle Fusion Applications provisioning process for Oracle Business Intelligence, the following entities are available:
WebLogic domain
Oracle BI Web application (J2EE) components
Oracle BI Server and BI Presentation Services (deployed on the machine that hosts the domain)
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:
Admin Server port - 10201
Managed Server port - 10217
WLS Admin user - FAadmin
This section provides detailed tasks for setting up Oracle BI Applications.
Section 3.3.1, "Downloading Critical Oracle BI Applications Patches"
Section 3.3.2, "Creating Database Instances for Schemas and Repositories"
Section 3.3.3, "Creating Schemas Using Business Analytics Applications Suite RCU"
Section 3.3.13, "Installing ODI Studio and Configuring User Access"
Oracle BI Applications release 11.1.1.8.0 requires the following critical patches.
Oracle BI Applications RCU
The Oracle BI Applications RCU (also referred to as the Business Analytics Applications RCU) .zip file for this release is provided as a patch. This patch must be downloaded from My Oracle Support.
ODI Patch
Download the latest ODI patch available for Fusion Applications Release 8 from My Oracle Support.
For details about the patch numbers, see Oracle Business Intelligence Applications Release Notes.
You will apply the patches later in the Oracle BI Applications setup process.
Before you run the Business Analytics Applications Suite RCU and installer, you must create database instances to hold the following:
Business Analytics Warehouse schema.
Oracle BI Applications Components Repository (for Configuration Manager and Functional Setup Manager).
ODI Repository for Oracle BI Applications (includes Master and Work repositories).
Note the following points:
For this release of Oracle BI Applications, the following components are supported only on Oracle Database Enterprise Edition:
Business Analytics Warehouse
BI Applications Components Repository.
ODI Repository for BI Applications
For the specific version of Oracle Database Enterprise Edition supported for this release of Oracle BI Applications, see the Certification Matrix for Oracle BI Applications at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
The Oracle Database Enterprise Edition must be configured with UNICODE.
The Business Analytics Warehouse, BI Applications Components Repository, and ODI Repository can be installed on different database servers.
The ODI Master and Work repositories are installed into the same schema.
Review Section 2.2.1, "Guidelines for Oracle Business Analytics Warehouse Databases," for information about database requirements for the Business Analytics Warehouse.
The Oracle BI Applications RCU for this release is provided as a patch. This patch must be downloaded from My Oracle Support. If you did not download the RCU .zip file as instructed in Section 3.3.1, "Downloading Critical Oracle BI Applications Patches," download it now. See Oracle Business Intelligence Applications Release Notes for the patch number that contains the RCU .zip file.
Note: An Oracle BI Applications RCU .zip file named rcuHomeBIApps.zip is located in the Fusion Applications software repository under installers/biapps_rcu/<OS>. Do not use this RCU .zip file.
You run the Business Analytics Applications Suite RCU to create schemas for the following components:
Business Analytics Warehouse
Oracle BI Applications Components
ODI Repository for BI Applications
Before you run the Business Analytics Applications Suite RCU, note the following points:
On Windows machines, make sure that you unzip the downloaded RCU .zip file into a directory that does not have spaces in the directory path.
The RCU uses .dmp files to create the required schemas. You must copy the .dmp files for each schema to a directory with global write access on the appropriate database server machines. (RCU writes log files to this directory.) The .dmp files are located in BIA_RCU_HOME/rcu/integration/biapps/schema.
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, with the SYSDBA role selected).
If you are creating schemas on different databases, then you will need to run RCU multiple times, once for each database connection, because the database connections are different for the different database servers.
To create the Oracle BI Applications schemas using the Business Analytics Applications Suite RCU:
Access the bin directory in the BIA_RCU_HOME.
Start RCU, as follows:
UNIX:
./rcu
Windows:
rcu.bat
On the Welcome screen, click Next.
On the Create Repository screen, select Create, and then click Next.
On the Database Connection Details screen, specify the connection details for the database in which you want to store the schemas. Note that you must possess the DBA privilege and be logged in as SYSDBA (for example, as user SYS).
Specify the following database connection details:
| Field Name | Action |
|---|---|
|
Database Type |
Select 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, |
|
Port |
Specify the port number over which the database communicates. The default port number for an Oracle database is 1521. |
|
Service Name |
Specify the service name for the database. Typically, the service name is the same as the global database name. |
|
Username |
Specify the user name for the database. The default user name is SYS. The user must have DBA or SYSDBA privileges. |
|
Password |
Specify the password for the username specified in the Username field. |
|
Role |
Select |
Click Next to display the Select Components screen.
On the Select Components screen, near the top of the dialog, select Create a new Prefix.
The default prefix is DEV. You can change the prefix.
RCU automatically creates the schema owner (schema name) in the format prefix_schemaname.
Select the following options:
| Schema Option | Default Schema Owner |
|---|---|
|
Oracle Business Analytics Warehouse |
<prefix>_DW (required for all deployments). |
|
Oracle Business Applications Components |
<prefix>_BIACOMP (required for all deployments). When you select the BI Applications Components Repository (BIACOMP), RCU will create an additional schema named BIACM_IO. Do not modify or delete this schema. It is required for metadata access by the different Oracle BI Applications components. |
|
Oracle Data Integrator Master and Work Repository |
<prefix>_BIA_ODIREPO (required for all deployments). |
Click Next to display the Schema Passwords screen.
On the Schema Passwords screen, specify and confirm a password for the schemas, then click Next to proceed to the Custom Variables screen.
Note:
The RCU uses .dmp files to create the required schemas. Before you perform the action in the Custom Variables screen, you must copy the .dmp files for each schema to a directory with global write access on the appropriate database server host machine. (RCU writes log files to this directory). The .dmp files are located in BIA_RCU_HOME\rcu\integration\biapps\schema.
In the Value field of the Custom Variables screen, for each schema enter the directory path of the folder on the database server that contains the .dmp file.
Note: Do not include the name of the .dmp file in the directory path.
Click Next to proceed to the Map Tablespaces screen.
The Map Tablespaces screen displays the default and temporary tablespaces for the schemas. On this screen, do the following:
Leave the default values for Default Tablespace and Temp Tablespace for each schema.
Set the temporary tablespace size for the data warehouse tablespaces according to the values in the table below:
- Click Manage Tablespaces.
- In the left-side navigation panel, select the appropriate tablespace name.
- In the main window, select the tablespace name under the Datafiles heading.
- Click the Edit icon to display the Datafile dialog.
- In the Edit Datafile dialog, set the temporary tablespace size according to the table below:
| Tablespace | Value |
|---|---|
|
<prefix>_DW_DATA |
Size: 20 GB Maximum Size: Unlimited Leave the remaining default values. |
|
<prefix>_DW_IDX |
Size: 5 GB Maximum Size: Unlimited Leave the remaining default values. |
|
<prefix>_DW_STG |
Size: 10 GB Maximum Size: Unlimited Leave the remaining default values. |
|
<prefix>_DW_TEMP |
Size: 15 GB Maximum Size: Unlimited Leave the remaining default values. |
Click OK to exit the Edit Datafile dialog. Then, click Next in the Map Tablespaces screen, and click OK in the message dialog to create the tablespaces for the schemas.
On the Summary screen, click Create to start the schema creation process.
When the schemas are created with no errors, the Completion Summary screen is displayed.
On the Completion Summary screen, click Close.
If your organization has deployed the Sales Prediction Engine module of Oracle Fusion Customer Relationship Management, you must also create Oracle Business Analytics Warehouse database objects (ODM tables, views, packages, ILS Processing tables, and so on) using the Sales Prediction Engine RCU. For instructions on creating the Sales Prediction Engine schema with the Sales Prediction Engine RCU, see Oracle Fusion Applications Installation Guide.
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. For more information, see Section 3.3.2, "Creating Database Instances for Schemas and Repositories."
This section provides instructions for updating the ATGLite data in the BIACOMP schema.
To update ATGLite:
Run the following command:
java -jar biappsrepositoryutil.jar upgradeATG <mandatory parameters>
Where the mandatory parameters are as follows:
| Parameter | Description |
|---|---|
|
bi.oracle.home |
Full path of the Oracle BI home. |
|
work.dir |
Working directory to be used for the run. Log files will be created for each run and saved in this directory. The naming convention for the SQL log file is atgUpgradeSQLYYYY-MM_DD_HH_MM.log. Log files will be available only if they are not empty. |
|
db.conn.sid.url |
Connection to the database that hosts the BIACOMP schema. The format is host:port:SID. For example: host.domain:1521:orcl. |
|
biacomp.user |
BIACOMP schema owner. |
|
biacomp.password |
BIACOMP schema owner's password. |
|
atg.db.seed.url |
URL used to connect to the BIACOMP schema. (The ATG user is the BIACOMP schema owner.) The format is host:port/ServiceName. For example: host.domain:1521/orcl.domain. |
|
db.sys.user |
Database system user name. |
|
db.sys.password |
Database system user password. Note: If this parameter is not passed in the command line, then the tool will request the password at runtime. |
java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=scratch/MiddleWareHome/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=BIAPPS_BIACOMP biacomp.password=password db.conn.sid.url=<host>:<database port>:<SID> atg.db.seed.url=<host>:<database port>/<ServiceName> db.sys.user=sysuser db.sys.password=password
This section provides instructions for updating the FSM data in the BIACOMP schema.
To update FSM:
Run the following command:
java -jar biappsrepositoryutil.jar upgradeFSM <mandatory parameters>
Where the mandatory parameters are as follows:
| Parameter | Description |
|---|---|
|
bi.oracle.home |
Full path of the Oracle BI home. |
|
work.dir |
Working directory to be used for the run. Log files will be created for each run and saved in this directory. The naming convention for the SQL log file is fsmUpgradeSQLYYYY-MM_DD_HH_MM.log. Log files will be available only if they are not empty. |
|
db.conn.sid.url |
Connection to the database that hosts the BIACOMP schema. The format is host:port:SID. For example: host.domain:1521:orcl. |
|
biacomp.user |
BIACOMP schema owner. |
|
biacomp.password |
BIACOMP schema owner's password. |
|
fsm.db.seed.url |
URL used to connect to the BIACOMP schema. (The FSM user is the Business Analytics Warehouse schema owner.) The format is host:port/ServiceName. For example: host.domain:1521/orcl.domain. |
|
db.sys.user |
Database system user name. |
|
db.sys.password |
Database system user password. Note: If this parameter is not passed in the command line, then the tool will request the password at runtime. |
java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=scratch/MiddleWareHome/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=BIAPPS_BIACOMP biacomp.password=password db.conn.sid.url=<host>:<database port>:<SID> fsm.db.seed.url=<host>:<database port>/<ServiceName> db.sys.user=sysuser db.sys.password=password
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 instructions on 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 Enterprise Edition.
The ETL process must be run by a user with appropriate data security privileges granted on the Fusion Applications tables from which data is extracted into Oracle Business Analytics Warehouse. For this purpose, the enterprise role named FUSION_APPS_OBIA_BIEE_APPID is provisioned during install with the appropriate ETL security privileges.
Work with your security administrator to complete the steps below.
To create a user for ETL:
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.
Make the user a member of the Enterprise Role FUSION_APPS_OBIA_BIEE_APPID.
Make a note of the user credentials.
Follow the instructions below to extend the BI domain.
To extend the BI domain:
Using a text editor, create a response file with the parameters shown below. Enter the appropriate values for the parameters, and name the file response.rsp.
#DO NOT CHANGE THIS Response File Version=1.0.0.0.0 [GENERIC] MW_HOME=<MW_HOME> ORACLE_HOME=<ORACLE_HOME> WEBLOGIC_HOME=<WL_HOME> ADMIN_USER_NAME=<ADMIN_USER> ADMIN_PASSWORD=<ADMIN_PWD> WLS_SINGLE_SERVER_INSTALL=false #Make sure following flag value is true for extend DWskip_rpd__setup=true DATABASE_CONNECTION_STRING_MDS=<DATABASE_CONNECTION_STRING_MDS> DATABASE_SCHEMA_USER_NAME_MDS=<MDS_USERNAME> DATABASE_SCHEMA_PASSWORD_MDS=<MDS_PASSWORD> DATABASE_TYPE_MDS=Oracle Database DOMAIN_HOSTNAME=<DOMAIN_HOST> DOMAIN_PORT=<DOMAIN_PORT> AUTOMATIC_PORT_DETECT=<AUTOMATIC_PORT_DETECT> STATICPORT INI FILE LOCATION=<STATICPORT_INI_FILE_LOCATION> DW_DATABASE_CONNECTION_STRING=<DW_DATABASE_CONNECTION_STRING> DW_DATABASE_SCHEMA_USER_NAME=<DW_DATABASE_SCHEMA_USER_NAME> DW_DATABASE_SCHEMA_PASSWORD=<DW_DATABASE_SCHEMA_PASSWORD> DW_DATABASE_TYPE=Oracle Database BIACOMP_DATABASE_CONNECTION_STRING=<BIACOMP_DATABASE_CONNECTION_STRING> BIACOMP_DATABASE_SCHEMA_USER_NAME=<BIACOMP_DATABASE_SCHEMA_USER_NAME> BIACOMP_DATABASE_SCHEMA_PASSWORD=<BIACOMP_DATABASE_SCHEMA_PASSWORD> BIACOMP_DATABASE_TYPE=Oracle Database ODI_REPOSITORY_DATABASE_CONNECTION_STRING=<ODI_REPOSITORY_DATABASE_CONNECTION_STRING> ODI_REPOSITORY_DATABASE_SCHEMA_USER_NAME=<ODI_REPOSITORY_DATABASE_SCHEMA_USER_NAME> ODI_REPOSITORY_DATABASE_SCHEMA_PASSWORD=<ODI_REPOSITORY_DATABASE_SCHEMA_PASSWORD ODI_REPOSITORY_DATABASE_TYPE=Oracle Database #ODI_USER_NAME is referred as "BI Applications Administrator User" in config screen ODI_USER_NAME=<ODI_USER_NAME> ODI_USER_PASSWORD=<ODI_USER_PASSWORD> ODI_USER_CONFIRM_PASSWORD=<ODI_USER_CONFIRM_PASSWORD> #Following section is only needed when ODI is configured with External LDAP CONFIGURE_ODI_EXTERNAL_LDAP=true # LDAP URL - ldap://<host>:<port> LDAP_URL=<LDAP_URL> LDAP_USER=<LDAP_USER> LDAP_PASSWORD=<LDAP_PASSWORD> LDAP_USERBASE_PREFIX=<LDAP_USERBASE_PREFIX> LDAP_GROUPBASE_PREFIX=<LDAP_GROUPBASE_PREFIX> [SYSTEM] [APPLICATIONS] CONFIGURE_OBIACM=true CONFIGURE_ODI=true [RELATIONSHIPS]
Execute the following command:
| Platform | Command |
|---|---|
|
Windows |
Oracle_home\bin\configAppsInFAWithDW.bat ./response.rsp |
|
UNIX and Linux |
Oracle_home/bin/configAppsInFAWithDW.sh <path_to_response_file> |
Oracle BI Applications requires the BI and ODI Managed Servers (bi_server1 and odi_server1) to be started using Node Manager. This is required so that parameters, memory, and JVM arguments are appropriately set. If you do not start the BI and ODI Managed Servers, functionality loss and memory issues can occur in Oracle BI Applications Configuration Manager, Functional Setup Manager, and ODI.
To ensure that the BI and ODI Managed Servers are started using Node Manager, start them using the WebLogic Administration Console user interface. Do not start the BI and ODI Managed Servers using the Managed Server start scripts.
Work with your Web administrator to configure Oracle HTTP Server so that URLs for Oracle BI Applications Configuration Manager and Functional Setup Manager (FSM) 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 and FSM.
To configure Oracle HTTP Server:
Access the directory APPTOP/instance/CommonDomain_webtier/config/OHS/ohs1/moduleconf
where APPTOP is the Application home folder.
Open the file FusionVirtualHost_bi.conf.
Under the #BIEE section, add the following entries for Oracle BI Applications Configuration Manager and FSM:
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.
FSM entry:
<LocationMatch ^/setup >
SetHandler weblogic-handler
WeblogicCluster host:port
</LocationMatch>
where host is the fully-qualified domain name of the WebLogic host where FSM is deployed and port is the Administration Server port.
Note: For each LocationMatch entry, make sure that you have a space character between the value and the closing '>' character.
Restart Oracle HTTP Server by accessing the directory APPTOP/instance/CommonDomain_webtier/bin and running the following commands:
./opmnctl stopall
./opmnctl startall
Provide the URL for Oracle BI Applications Configuration Manager to your end users.
Oracle BI Applications Configuration Manager contains a link that launches Functional Setup Manager (FSM). Work with your Oracle BI Applications administrator and your security administrator to configure single sign-on (SSO) between Oracle BI Applications Configuration Manager and FSM 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 FSM.
To configure Oracle BI Applications and FSM, do the following:
Configure SSO as described in Section 3.3.12.1, "How to configure SSO for Oracle BI Applications Configuration Manager and FSM".
Configure Portlet Provider as described in Section 3.3.12.2, "How to configure Portlet Provider for Oracle BI Applications Configuration Manager and FSM".
To configure SSO for Oracle BI Applications Configuration Manager and FSM using Oracle Access Manager:
In a supported Web browser, log in to Oracle Access Manager, using the following URL:
http://<host>:<port>/oamconsole/
Where host is the host name and port is the port number for your Oracle Access Manager application.
Display the Policy Configuration tab.
Create a policy for Oracle BI Applications Configuration Manager, as follows:
In the Browse pane, navigate to Application Domains\bi.
Double-click the Resources node, to display the BI Resources page.
Use the New Resource option to display the Create Resource page.
Specify the following details:
Resource type: http
Host Identifier: OraFusionApp
Resource URL: /biacm/.../*
Save the details.
Determine whether there is an existing policy for FSM. 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 FSM, then you can skip step 5 below and use this existing policy. If there is not an existing policy for FSM, then follow step 5 below to create a policy.
Create a policy for FSM, as follows:
In the left hand Browse pane, navigate to Application Domains\bi.
Double-click the Resources node, to display the bi Resources page.
Use the New Resource option to display the Create Resource page.
Specify the following details:
Resource type: http
Host Identifier: OraFusionApp
Resource URL: /setup/.../*
Save the details.
To configure Portlet Provider for Oracle BI Applications Configuration Manager and FSM using Oracle Access Manager:
In a supported Web browser, login to Oracle Access Manager, using the following URL:
http://<host>:<port>/oamconsole/
Where host is the host name and port is the port number for your Oracle Access Manager application.
Display the Policy Configuration tab.
Create a policy for Oracle BI Applications Configuration Manager, as follows:
In the Browse pane, navigate to Application Domains\bi.
Select the Resources node.
Use the New Resource option to display the Create Resource page.
Specify the following details:
Resource type: http
Host Identifier: OraFusionApp
Resource URL: /setup/portlets/…/*
Protection Level: Excluded
Save the details.
ODI Studio is typically installed on developer machines. The supported operating systems for ODI Studio are Windows 32-bit and 64-bit and Linux 32-bit.
ODI Studio is a desktop client that enables you to design and manage the ODI Repository.
Perform the following procedures in the order they appear:
You install ODI Studio using the ODI installer.
Note the following points:
On the Select Installation Type screen, you must select Developer Installation as the installation type and both options under Developer Installation, that is, ODI Studio (with local agent) and ODI SDK.
On the Repository Configuration screen, you must select the Skip Repository Configuration option.
For instructions on installing ODI Studio, see Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.
The ODI Repository is configured for external authentication against WebLogic Server's embedded LDAP server. ODI Studio must be configured to use the appropriate security files for authentication. You must perform these steps on all installations of ODI Studio.
Note: You must perform these steps even if ODI Studio has been installed on the machine where Oracle Home for BI resides.
To configure user access for ODI Studio:
Copy cwallet.sso and jps-config-jse.xml from:
<MW_Home>/user_projects/domains/bifoundation_domain/odi-client-config/embedded
To:
<ODI_Home>/oracledi/client/odi/bin
Edit <ODI_Home>/oracledi/client/odi/bin/odi.conf by updating the JPS configuration file name as follows:
AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml
If you do not successfully complete these steps, you will receive the following error message: "ODI-10188: Error while login from OPSS../jps-config.xml (No such file or directory) ."
Perform steps 1 and 2 on all instances of ODI Studio.
Note: You must perform these steps even if ODI Studio has been installed on the machine where Oracle Home for BI resides.
If the BI Applications Administrator password or any ODI users' passwords were changed, administrators need to regenerate security files and redistribute the files to all instances of ODI Studio.
To regenerate security files:
Execute the wlst.sh script:
ORACLE_HOME/common/bin/wlst.sh <MW_Home>/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py embedded --ADMIN_USER_NAME <Administrator> --DOMAIN_HOSTNAME <Hostname> --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH <MW Home>/user_projects/domains/bifoundation_domain
Where ADMIN_USER_NAME is the WebLogic Server administrator user.
The updated JPS configuration file and credential wallet are created at location:
<MW_Home>/user_projects/domains/bifoundation_domain/odi-client-config/embedded
Copy these updated files to <ODI_Home>/oracledi/client/odi/bin on all ODI Studio instances.
Make sure that the odi.conf file is edited correctly, as described in step 2 in the previous procedure for configuring user access for ODI Studio.
The odi.conf file is located in <ODI_Home>/oracledi/client/odi/bin.
You need to apply the latest ODI patch for Fusion Applications to ODI Agent and ODI Console in the BI Domain and to all instances of ODI Studio. This patch is available on My Oracle Support. See Oracle Business Intelligence Applications Release Notes for the patch number. For instructions on applying the patch, see the readme file that accompanies the patch.
If you did not download the ODI patch as instructed in Section 3.3.1, "Downloading Critical Oracle BI Applications Patches," download it now and apply it.
During installation of Oracle BI Applications, source files are installed in the BI_Oracle_Home/biapps/etl directory. These files are used during the ETL process and will be configured by functional developers. You must copy these files to a location that ODI Agent deployed in WebLogic Server can access but that is outside of the Oracle Home directory; otherwise, when the Oracle BI Applications environment is upgraded or patched, these files will be overwritten.
To copy source files:
Navigate to the BI_Oracle_Home/biapps/etl directory.
Copy all files under the BI_Oracle_Home/biapps/etl directory into a location that ODI Agent deployed in WebLogic Server can access but is outside of the Oracle Home directory.
Avoid copying the files to a location with a long directory path.
Note: Depending on your deployment, there may be files in the BI_Oracle_Home/biapps/etl directory that you will not use.
You must perform the system setups in this section to complete integration of the Oracle BI Applications components and to ready the system for functional configurations and data loads. Perform the tasks in the order they appear:
Section 3.3.16.1, "Setting the Business Analytics Warehouse Connection in ODI"
Section 3.3.16.2, "Registering Source Systems and Propagating Connection Details to ODI"
Section 3.3.16.4, "Editing Preferred Currency Display Names and Enabling Document Currency"
Section 3.3.16.5, "Setting Languages for Data Load into the Business Analytics Warehouse"
Section 3.3.16.6, "Restoring the BI Metadata Repository File for Oracle BI Applications"
Section 3.3.16.9, "Granting Users Access to Configuration Manager, FSM and ODI"
Use ODI Studio to set the connection properties in the ODI Repository of the physical schema associated with the 'BIAPPS_DW_FILE' physical server.
To set the Business Analytics Warehouse physical schema connection in ODI:
Log into ODI Studio using the BI Applications Administrator credentials.
In the navigation pane, go to Topology, and expand Technologies, and then expand File.
Double-click BIAPPS_DW_FILE.
In the Definition pane, for the Directory (Schema) and Directory (Work Schema) properties, specify the src_files directory and include the subfolders data_files/src_files/BIA_11.
For example:
<source file home>/biapps/etl/data_files/src_files/BIA_11
Follow this procedure to register a source system and propagate the connection details to ODI.
To register a source system:
Launch Oracle BI Applications Configuration Manager using the URL http://<host>.<port>/biacm, and log in as the BI Applications Administrator user.
In Oracle BI Applications Configuration Manager, select the Define Business Intelligence Applications Instance link, which appears under System Setups on the Tasks pane.
The Source Systems tab is displayed.
Click the Add icon.
The Register Source dialog is displayed.
Specify the following properties:
| Property | Description |
|---|---|
|
Product Line |
Select Oracle Fusion. |
|
Product Line Version |
Select the version number of the source instance product line. |
|
Source Instance Name |
Specify a name for the source instance. This is the name given by the BI Applications System Administrator to a transactional system that serves as a source of data for BI Applications data load. The source instance is important because functional setup tasks and the setting of values for objects such as parameters and domain maps are performed in relation to a source instance. |
|
Description |
(Optional) Enter additional information about the source instance. |
|
Data Source Number |
Enter a unique number to identify the source instance. The Data Source Number value specifies a data source so that the data can be identified in the Oracle Business Analytics Warehouse. Each source instance must have a unique Data Source Number. |
|
Data Server Details |
A read-only list of data servers is displayed. |
Click Next to display the Register Source in Oracle Data Integrator Topology page.
To register the source in ODI, do the following:
Select Global from the Context drop-down list.
In the Technology: Oracle BI tab, specify the following properties:
| Property | Description |
|---|---|
|
ODI Data Server Name |
Specify a name for the ODI Data Server that indicates Fusion Applications is the source of data. This name must be unique across all ODI data servers in the ODI Repository. |
|
JDBC Driver |
This property indicates the name of the JDBC driver for the Oracle BI Server. For example: Oracle recommends that you use the default value. Note: Data from the Fusion Applications transactional system is retrieved from the Oracle BI Server. |
|
JDBC URL |
Specify the JDBC URL for the Oracle BI Server. The format for the URL is the following:
|
|
Database Username |
Specify the user name of the ETL user. This is the user created in Section 3.3.8, "Creating a User for ETL." |
|
Database Password |
Specify the password for the ETL user. |
|
Test |
Use this button to test the connection to the Oracle BI Server. |
In the Technology: File System tab, specify the following properties:
| Property | Description |
|---|---|
|
ODI Data Server Name |
Specify a name for the file system data server. This ODI Data Server Name must be unique across all ODI data servers in the ODI Repository. |
|
Host Name |
Specify the name of the host machine where the file system (source files used for ETL) resides. This is the machine to which you copied the source files in the procedure Section 3.3.15, "Copying Source Files." |
|
Path To File |
Specify the directory where you copied the source files in Section 3.3.15, "Copying Source Files." The directory path must include the appropriate source-specific folder for your environment. The source-specific folders are located in /biapps/etl/data_files/src_files. For example: |
|
Array Fetch Size |
The number of rows requested by ODI on each communication with the data server. Note: This column might be hidden. To view this column, click View, Columns, Show All. |
|
Batch Update Size |
The number of rows in a single INSERT command. Note: This column might be hidden. To view this column, click View, Columns, Show All. |
|
JDBC Driver |
Oracle recommends that you use the default value. Note: This column might be hidden. To view this column, click View, Columns, Show All. |
|
JDBC URL |
Oracle recommends that you use the default value. Note: This column might be hidden. To view this column, click View, Columns, Show All. |
Click Save and Close.
This information is passed to ODI where the connections are created.
Note:
The connection details are not propagated to the ODI Repository until you have entered and saved the information on both the Register Source in Configuration Manager page and the Register Source in Oracle Data Integrator Topology page.
Use Oracle BI Applications Configuration Manager to enable the Oracle BI Applications offerings that you have purchased and are deploying. The setup data relating to offerings is made visible in Configuration Manager when you enable the offering.
By default, if you have multiple source instances and you enable an offering, then the offering is enabled for all source instances. If an offering will not source from all source instances, then you can disable the source instances from which the offering will not source. For example, suppose you have two source instances, Oracle EBS and PeopleSoft, and you are deploying Financial Analytics. If Financial Analytics will only source from PeopleSoft, then you would disable the Oracle EBS source instance for the Financial Analytics offering.
To enable Oracle BI Applications offerings for deployment:
Log in to Oracle BI Applications Configuration Manager as the BI Applications Administrator user.
Select the Manage BI Applications link to display the Manage Business Intelligence Applications dialog.
Select the BI Application Offerings tab.
Select the Enabled check box next to each offering you want to deploy.
Enabling an offering makes the setup data associated with that offering available in Configuration Manager.
Click Save to save your changes.
To exit this dialog, click Done.
To disable a source instance from which an offering will not source:
Go to the Business Intelligence Application Offerings and Associated Sources tab.
Expand the appropriate offering.
Deselect the Enabled check box for the source you want to disable.
Click Save.
Oracle Business Intelligence is installed with a set of preferred currencies with preconfigured preferred currency names and preferred currency codes. Preferred currency names are used on Oracle Business Intelligence dashboards in the Currency drop-down on the My Account dialog\Preferences tab for a user logged into Oracle Business Intelligence.
You can use the Manage Preferred Currencies dialog to edit the default currency display names. 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 currency display names:
Login to Oracle BI Applications Configuration Manager as the BI Applications Administrator user.
From the Tasks bar, click Manage Preferred Currencies to display the Manage Preferred Currencies dialog.
Select a currency in the Preferred Currencies list. Selecting the currency displays the associated modules in the bottom table.
Click the value in the Preferred Currency Name column (or click the Edit icon) to display the Preferred Currency Name dialog.
In the Preferred Currency Name field, specify a currency name. This is the name that will appear for end users in the Currency drop-down list, located in Preferences tab of the My Accounts dialog of Oracle Business Intelligence.
Click Save and Close.
By default, document currency is excluded from the Currency drop-down list (located in the Preferences tab of the My Accounts dialog in Oracle Business Intelligence). To include Document currency in the Currency drop-down list, you must remove a specific filter from all of the following security groups in the BI metadata repository (RPD):
OBIA_PROJECT_CURRENCY_PREFERENCES
OBIA_HCM_CURRENCY_PREFERENCES
OBIA_SCM_CURRENCY_PREFERENCES
OBIA_FINANCIAL_CURRENCY_PREFERENCES
OBIA_MFG_CURRENCY_PRFERENCES
OBIA_PROCUREMENT_CURRENCY_PREFERENCES
OBIA_MARKETING_CURRENCY_PREFERENCES
OBIA_PARTNER_CURRENCY_PREFERENCES
OBIA_CRM_CURRENCY_PREFERENCES
OBIA_SALES_CURRENCY_PREFERENCES
Note: The security groups listed above are displayed in Oracle BI Administration Tool on the Application Roles tab on the Identity Manager dialog.
To enable document currencies:
In Oracle BI Administration Tool, click Manage, then Identity, to display the Identity Manager dialog.
In the Identity Manager dialog, click BI Repository.
Display the Application Roles tab.
For each of the security groups in the RPD list above, do the following:
Double-click the security group to display the Application Role - <Name> dialog.
Click Permissions, and then display the Data Filters tab.
In the Data Filter column, remove the following filter:
AND "Core"."Fact - Preference List"."Currency Preference Code" <> 'Document Currency'
For example, the filter before editing:
"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'
For example, the filter after editing:
"Core"."Fact - Preference List"."Module Code" = 'PROJECT_AN' AND "Core"."Fact - Preference List"."Currency Preference Flag" in ('W', 'B')
Save the changes.
If you edited the metadata repository in Offline mode, then you must use Oracle Fusion Middleware Control to upload the RPD file.
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 the section "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.
Oracle BI Applications supports data loads in multiple languages. You specify the languages for data loads in Oracle BI Applications Configuration Manager.
To specify Oracle Business Analytics Warehouse languages:
Log in to Oracle BI Applications Configuration Manager as a user with the Business Intelligence Applications Administrator duty role.
Select the Manage BI Applications link to display the Manage Business Intelligence Applications dialog.
Display the Warehouse Languages tab.
Specify the languages from which data is to be extracted from the list of languages displayed in the table by selecting Installed from the Installed drop down. American English is the 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.
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.
Click Save to save your changes.
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 perform the following tasks:
Section 3.3.16.6.2, "Create Directories and Copy in the RPD Files".
Section 3.3.16.6.3, "Open the Runtime RPD and Obtain a List of Projects".
Section 3.3.16.6.4, "Extract the Trimmed Metadata from the Golden RPD".
Section 3.3.16.6.5, "Equalize the Runtime RPD and the Golden RPD".
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).
Create the following directory structure and set up the RPD files.
Create the following directories:
Work\
Work\GoldenRPD
Work\RuntimeRPD
Work\ExtractRPD
Work\Patch
Work\RestoredRPD
Work\EqualizeRPD
Copy the Golden RPD and the Runtime RPD to the corresponding folders:
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
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
In Oracle BI Administration Tool, open the Runtime RPD in Offline mode.
For example, open C:\Work\RuntimeRPD\RuntimeRPD.rpd.
From the menu, choose Manage, then Projects, to display the Projects Manager dialog.
Note down or copy into a file the project names in this list, using the upper and lower 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.
Open a command prompt.
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.
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\orahome set ORACLE_INSTANCE=C:\RUP3\oraclebi\orainst set ORACLE_BI_APPLICATION=coreapplication
In the command prompt, execute the environment commands by pasting in the commands from Step 3 and pressing Enter.
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.3.16.6.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.
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.
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.
In Oracle BI Administration Tool, open the Equalized RPD.
Choose File, then Compare, to display the Compare repositories dialog.
From the Compare repositories dialog, open the Extract RPD as the Original Repository.
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.
Click Create Patch to display Create Patch dialog, and specify a patch file name and location (for example: C:\Work\Patch\patch.xml).
Click Save.
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
Use Oracle Fusion Middleware Control to upload the new RPD.
For example, if you specified the output file in the previous task as '-O C:\Work\RestoreRPD\RestoreRPD.rpd', then you upload RestoreRPD.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 the section "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.
Before you run the domains load plan, you must complete the mapping of externally conformed domains using the Manage Externally Conformed Domains page in Oracle BI Applications Configuration Manager. For instructions on completing this procedure, see Oracle Business Intelligence Applications Release Notes.
You must define, generate, and run a domains load plan to load source-specific data into Oracle BI Applications Configuration Manager tables. This enables Configuration Manager to display the appropriate source-specific values as choices in drop-down lists for setup objects.
Note: Before you perform this step you must have completed the procedure Section 3.3.16.2, "Registering Source Systems and Propagating Connection Details to ODI."
To define, generate and run the domains load plan:
Define the domains load plan:
In the Tasks pane of Oracle BI Applications Configuration Manager, select Manage Load Plans, which appears under the Load Plans Administration heading.
The Manage Load Plans page is displayed.
In the Load Plans toolbar, click the Add icon.
The Create Load Plan page is displayed.
On the first page of the Create Load Plan series, specify the following information:
| Field | Description |
|---|---|
|
Name |
Enter a unique name for the load plan. |
|
Description |
(Optional) Enter additional information about the load plan. |
|
Load Plan Type |
Select Domain-only Extract and Load (SDE and SIL). |
|
Source Instances |
Select a source instance. If you do not select an instance, then all instances are selected by default. |
Click Next.
The second page of the Create Load Plan series is displayed.
In the Available Fact Groups tab, select the fact groups you want to include in the domains load plan definition.
Note that fact groups might belong to a hierarchy of fact groups. You can select only the top level parent fact group and not a child fact group.
A load plan must contain at least one fact group. Multiple fact groups may be selected from one or more data sources.
Click Save. A submenu is displayed with the following options:
Click Save to save the load plan. After a load plan is saved, it is displayed in the Load Plans master list.
Click Save and Generate Load Plan to save the load plan and immediately generate it.
Note that the generation process in Oracle BI Applications Configuration Manager propagates the load plan properties to the ODI Repository, where the load plan is built
If you did not generate the load plan upon saving in the previous step, then generate it by doing the following:
In the Load Plans master list, select the domains load plan you defined in step 1.
In the Load Plans toolbar, click the Generate icon.
The Generation Status column indicates the progress of the generation process. The process must complete successfully before you can move on to the next step. Click the Refresh icon to refresh the display.
Run the domains load plan by selecting it in the master list, and clicking the Execute icon on the toolbar.
Work with your security administrator to grant users access to Oracle BI Applications Configuration Manager, Functional Setup Manager, and ODI.
Access to Configuration Manager and Functional Setup Manager is controlled through the following duty roles.
BI Applications Administrator Duty
BI Applications Functional Developer Duty
BI Applications Implementation Manager Duty
Load Plan Operator Duty
Load Plan Administrator Duty
The security administrator must grant the appropriate duty roles to a user based on the user's job responsibilities. For information on the Configuration Manager and Functional Setup Manager screens that each duty role has access to, see Oracle Business Intelligence Applications Security Guide.
The BI Applications administrator, load plan operator, and load plan administrator users will require appropriate access to ODI. In addition to these users being created in the LDAP system, you must create these users in the ODI Repository and grant them the Supervisor profile or an appropriate ODI profile. The BI Applications administrator must be granted the Supervisor role in ODI. Work with your security administrator to grant the duty roles.
For more information about managing security in ODI, see Oracle Fusion Middleware Developer's Guide for Oracle Data Integrator.
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 learn about the functional configuration process for Oracle BI Applications, see Oracle Business Intelligence Applications Configuration Guide.
Furthermore, after Oracle BI Applications analyses 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 analyses and dashboard (ADR) regions in Fusion Applications. The ADR regions are enabled using Functional Setup Manager for Fusion Applications.
|
 Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|