| Oracle® Fusion Middleware Installation Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7) Part Number E35981-04 |
|
|
PDF · Mobi · ePub |
| Oracle® Fusion Middleware Installation Guide for Oracle Business Intelligence Applications 11g Release 1 (11.1.1.7) Part Number E35981-04 |
|
|
PDF · Mobi · ePub |
This chapter provides instructions for installing and performing post-installation setup tasks for Oracle BI Applications.
This chapter contains the following main topics:
Section 3.2, "Installing Prerequisites for Oracle BI Applications"
Section 3.3, "Installing and Configuring Oracle BI Applications"
Section 3.4, "Performing Post-Installation System Set Up Tasks"
The hardware requirements for Oracle BI Applications are as follows:
10-12 GB of free memory and 10 GB Swap Space for run-time requirements.
35 GB free disk space and 10 GB Swap Space to run the Business Analytics Applications Suite installer. This disk space will be released after the installer finishes.
For additional information about hardware requirements for Oracle BI EE and ODI, see Oracle Fusion Middleware System Requirements and Specifications at http://docs.oracle.com/html/E18558_01/fusion_requirements.htm.
This section provides information about the components you must install before you install Oracle BI Applications.
Note:
For the specific versions of the prerequisite products supported for this release of Oracle BI Applications, see "System Requirements and Supported Platforms," at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
Note:
When you run the Oracle Business Intelligence 11g installer, you can select either the Software Only Install or Enterprise Install option. If you select the Software Only Install option, then you must install WebLogic Server 10.3.6 before running the Oracle BI EE installer. If you select the Enterprise Install option, WebLogic Server 10.3.5 is automatically installed. You must then upgrade to WebLogic Server 10.3.6 after the Oracle BI Applications installation is complete.
This section contains the following topics:
The Business Analytics Applications Suite installer, which you run to install Oracle BI Applications, requires JDK version 1.6.0_35 or higher or JRockit version 6u37 R28.2.5 or higher.
Oracle BI EE, WebLogic Server, and ODI also require JDK and JRockit. For the supported versions, see Oracle Fusion Middleware System Requirements and Specifications at http://docs.oracle.com/html/E18558_01/fusion_requirements.htm. Make sure the version of JDK or JRockit you install meets the requirements for all products.
Note: You must use the 64-bit version of JDK or JRockit to install on 64-bit machines. On Windows, the location of the JDK must be on the same drive as the installers.
Oracle BI Applications requires WebLogic Server 11g Release 1 (10.3.6).
If you choose to install Oracle Business Intelligence Enterprise Edition (Oracle BI EE) using the Software Only Install option, then you must install WebLogic Server 10.3.6 by following the instructions in Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1 (10.3.6).
If you choose to install Oracle BI EE using the Enterprise Install option, then you do not have to perform this step, because WebLogic Server 10.3.5 is automatically installed. However, you must upgrade to WebLogic Server 10.3.6 after the Oracle BI Applications installation is complete. For instructions on upgrading WebLogic Server, see Oracle Fusion Middleware Upgrade Guide for Oracle WebLogic Server 11g Release 1 (10.3.6).
For instructions on installing WebLogic Server 10.3.6, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server 11g Release 1 (10.3.6).
Before installing Oracle Business Intelligence Enterprise Edition, you must run the Fusion Middleware Repository Creation Utility (RCU) to create the necessary schemas. In the Select Components screen of the RCU, make sure you select the options to install the following schemas:
Metadata Services (appears under AS Common Schemas)
Make a note of the Metadata Services schema owner name and password. You will need these values when you run the configApps.bat or configApps.sh file to set up Oracle BI Applications.
Business Intelligence Platform (appears under Oracle Business Intelligence)
Caution:
Do not select the option to install the Oracle Data Integrator schema. You will install an Oracle BI Applications-specific ODI schema when you run the Business Analytics Applications Suite RCU.
For instructions on running the Fusion Middleware RCU, see Oracle Business Intelligence Suite Enterprise Edition Installation and Upgrade Guide.
Oracle BI Applications requires an installation of Oracle Business Intelligence Enterprise Edition 11g deployed on WebLogic Server 10.3.6. WebLogic Server 10.3.5 is not supported.
When you run the Oracle Business Intelligence 11g installer, you can select either the Software Only Install or Enterprise Install option. If you select the Software Only Install option, then you must install WebLogic Server 10.3.6 before running the Oracle BI EE installer. If you select the Enterprise Install option, WebLogic Server 10.3.5 is automatically installed. You must then upgrade to WebLogic Server 10.3.6 after the Oracle BI Applications installation is complete.
For instructions on installing WebLogic Server, see Oracle Fusion Middleware Installation Guide for Oracle WebLogic Server.
For instructions on installing Oracle BI EE, see Oracle Business Intelligence Suite Enterprise Edition Installation and Upgrade Guide.
Note the following points:
Oracle BI EE must be deployed on WebLogic. Websphere is not supported for Oracle BI Applications.
The BI Domain should not be extended or scaled out before running the Business Analytics Applications Suite installer.
Installing Oracle BI EE using the Simple Install mode is not supported.
Installing Oracle BI EE on Windows 32-bit and Linux 32-bit is not supported for Oracle BI Applications.
If you are installing Oracle BI EE in Enterprise Install mode, on the Configure Components screen, for Oracle BI Applications 11.1.1.7.1, you must select the following four options:
Business Intelligence Enterprise Edition.
Business Intelligence Publisher (will be automatically selected).
Real-Time Decisions.
Essbase Suite.
Oracle BI Applications requires an installation of ODI 11g. For the specific version of ODI that is supported for this release of Oracle BI Applications, see "System Requirements and Supported Platforms," at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
For detailed informations on installing ODI, see Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.
Note the following points:
On the ODI installer Welcome screen, ignore the message regarding creation of the ODI Repository. You will create the ODI Repository for Oracle BI Applications later when you run the Business Analytics Applications Suite RCU.
On the Select Installation Type screen, select all the components under Java EE Installation, that is, Java EE Agent, ODI Console, and Public Web Service.
On the Select Installation Type screen, if you also choose to install ODI Studio, then you must also select the ODI SDK option.
On the Specify Installation Locations screen, enter the Middleware Home where Oracle BI EE is installed. Note: The installation of ODI in other locations is not supported for BI Applications.
If you chose to install ODI Studio, then on the Repository Configuration screen, you must select the Skip Repository Configuration option.
The ODI installer is a generic installer. To launch the installer, use one of the following commands:
| Platform | Command |
|---|---|
|
Windows |
setup.exe -jreLoc <location of jdk or jrockit> For example: setup.exe -jreLoc C:\jdk Note: For information about the JDK or JRockit requirements, see Section 3.2.1, "Installing JDK or JRockit." |
|
UNIX and Linux |
./runInstaller -jreLoc <location of jdk or jrockit> |
This section provides instructions for installing and configuring Oracle BI Applications.
You must perform the following procedures in the order as they appear:
Section 3.3.1, "Creating Database Instances for Schemas and Repositories"
Section 3.3.2, "Creating Schemas Using Business Analytics Applications Suite RCU"
Section 3.3.8, "Installing ODI Studio and Load Plan Generator Plug-In"
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 Business Analytics Warehouse is supported only on Oracle Database.
The Oracle BI Applications Components Repository and ODI Repository for BI Applications are supported only on Oracle Database. For the specific versions of Oracle Database supported for this release of Oracle BI Applications, see "System Requirements and Supported Platforms," at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
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.1.1, "Guidelines for Oracle Business Analytics Warehouse Databases," for information about database requirements for the Business Analytics Warehouse.
You need to run the Business Analytics Applications Suite RCU to create schemas for the following components:
Oracle Business Analytics Warehouse
Oracle Business Applications Components
ODI Repository for Oracle 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 connections, 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.
On the Value field in 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.
Run the Business Analytics Applications Suite installer to install Oracle BI Applications. This installer runs in software only mode.You must run the Business Analytics Applications Suite installer on the machine where you ran the Oracle BI EE installer. All files are installed to disk in the Oracle Home for BI directory. Note that you will perform post-installation steps to configure Oracle BI Applications in a later procedure.
Prerequisite to Running the Business Analytics Applications Suite Installer
Make sure you have met the following prerequisites before you run the Business Analytics Applications Suite installer:
The installer is a generic installer and requires JDK or JRockit to be installed. See Section 3.2.1, "Installing JDK or JRockit," for more information.
35 GB free disk space is required to run the Business Analytics Applications Suite installer. This disk space will be released after the installer finishes.
To run the Business Analytics Applications Suite installer:
Launch the Business Analytics Applications Suite installer by entering the following:
The Business Analytics Applications Suite installer displays the Welcome screen.
| Platform | Command |
|---|---|
|
Windows |
In a command prompt: setup.exe -jreLoc <Drive:\...\jdk or jrockit location> Where For example: setup.exe -jreLoc C:\jdk |
|
UNIX and Linux |
./runInstaller -jreLoc <jdk or jrockit location> |
Note: If you are running the installer on a Linux machine that does not have the file /etc/oraInst.loc, the Specify Inventory Location screen will display. For information about this screen, see Section B.1, "Specify Inventory Location."
Click Next to display the Prerequisite Checks screen.
This screen analyzes the host computer to ensure that specific operating system prerequisites have been met. If any of the prerequisite checks fail, then an error message appears in the bottom portion of the screen. Fix the error and click Retry to try again. If you want to ignore the error or warning messages and continue with the installation, click Continue. Click Abort to stop prerequisite checking for all components.
Click Next to display the Specify Installation Location screen.
In the Specify Installation Location screen, specify the details of the Oracle BI EE installation.
| Field | Action |
|---|---|
|
Oracle Middleware Home |
Specify the path to the directory for an existing Oracle Middleware home where Oracle BI EE has been installed. If you do not know the location of the directory, click Browse to locate the directory on your system. |
|
Oracle Home Directory |
Specify the Oracle Home for BI, for example, Oracle_BI1. Do not specify any other Oracle home or choose to create a new one. The Oracle Home for BI directory is where the software binary files for Oracle BI Applications and Operational Planning Applications will be installed. |
If you are installing on a Windows operating system, make sure that the directory paths are valid and do not contain double back-slashes (\\).
Click Next to display the Summary screen.
In the Summary screen, review the summary information, and click Next to start the installation.
The installer installs the Oracle BI Applications folders and files in the Oracle Home for BI directory.
Note:
Even when the progress bar on the installer reports 100% complete, you must wait until the Finish button is displayed.
Click Finish.
You must apply Fusion Middleware platform patches. The patches are available for download as part of the Oracle Business Intelligence Applications 11.1.1.7.1 media pack. You will run a script to apply the patches. The script is a Perl script and is available in <BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl.
Note:
When installing and running the Perl script, note the following:
For installations on Windows, the perl script uses the WinZip utility to extract the contents of the individual patches. If WinZip is not installed on the machine, then you must use install 7-zip and update the script to use it as follows:
Download and install 7-zip in C:\Program Files.
Open the APPLY_PATCHES.pl file using a text editor.
Modify the following lines in the download_patch routine.
From:
$DOWNLOAD_EXE = "\"C:${DIRSEP}Program Files${DIRSEP}WinZip${DIRSEP}wzunzip.exe\" -ybc -d";
$cmd = "$DOWNLOAD_EXE $_[0] $PATCHES_HOME";
To:
$DOWNLOAD_EXE = "\"C:${DIRSEP}Program Files${DIRSEP}7-Zip${DIRSEP}7z.exe\"";
$cmd = "$DOWNLOAD_EXE x $_[0] -o$PATCHES_HOME";
Save and close the file.
The Perl script you will run to apply the patches requires a parameter input file (apply_patches_import.txt). In this procedure, before you run the Perl script, you will update the parameter input file to reflect the appropriate directory paths.
To apply platform patches:
If Oracle BI EE was installed in Enterprise Install mode, then shut down WebLogic Administration Server, Managed Server, and Node Manager. Shut down BI processes using Oracle Process Manager and Notification Server (OPMN).
If you installed Oracle BI EE in Software Only mode, then skip this step.
Download "Oracle Fusion Middleware Platform Patches for Oracle Business Analytics Applications Suite" from the Oracle Business Intelligence Applications 11.1.1.7.1 media pack on Oracle Software Delivery Cloud, as follows:
Download the following three parts from the Oracle Business Intelligence Applications 11.1.1.7.1 Media Pack and unzip them into the same directory location:
Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 1 of 2)
Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications (Part 2 of 2)
Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for <OS>
Extract the ZIP file or files into a Patch Home directory, as follows:
Extract the contents of the three downloaded zip files containing the patches into the same directory, for example, C:\patches or PATCH_HOME/patches.
Note: The directory structure of the extracted contents is not patches4fa/dist/ps6rc3. The patches are contained in folders: biappsshiphome, odi, weblogic and oracle_common. You do not have to unzip the individual patches.
Update the parameter input file (apply_patches_import.txt) to reflect the paths as specified in the text file:
Create a writable directory where logs and temporary patch files will be stored. In the apply_patches_import.txt file, you will set the WORKDIR= variable to point to the path for this directory.
Open apply_patches_import.txt, which is located in the <BI_Oracle_Home>/biapps/tools/bin directory.
Specify the following directory paths:
| Directory | Path |
|---|---|
|
JAVA_HOME |
Path of the JDK you installed for your platform. |
|
INVENTORY_LOC |
Path of the Oracle\Inventory directory. For example: C:\Program Files\Oracle\Inventory. |
|
ORACLE_HOME |
Path of the Oracle Home for BI directory. |
|
MW_HOME |
Path of the Oracle Middleware Home directory. |
|
COMMON_ORACLE_HOME |
Path of the oracle_common directory, which is under the Middleware Home directory. |
|
WL_HOME |
Path of the Oracle WebLogic Server Home directory. |
|
ODI_HOME |
Path of the ODI Home directory. |
|
WORKDIR |
Path of a writable directory where logs and temporary patch files are stored. |
|
PATCH_ROOT_DIR |
Path of the patch directory. For example: C:\patches or, PATCH_HOME/patches |
Run the following command to apply the patch:
$ perl APPLY_PATCHES.pl <PARAM_INPUT_FILE_PATH>
For example:
perl <BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl <BI_Oracle_Home>/biapps/tools/bin/apply_patches_import.txt
Note: This script can be run from any location if Perl is set in the path variable. If Perl is not set in the path variable, run the script from the following location:
<ORACLE_HOME>/perl/bin>
Confirm that all patches have been applied successfully by reviewing the following log files in the directory specified by WORDIR:
final_patching_report.log (summary of patch application)
biappshiphome_generic_patches.log
biappshiphome_<OS specific>_patches.log
odi_generic_patches.log
oracle_common_generic_patches.log
weblogic_patching.log
Note: The WebLogic Server patches are for WebLogic Server 10.3.6. Therefore, if you have WebLogic Server 10.3.5 installed, the patches will not be installed in your environment, and you will not see the weblogic_patching.log file. Also, the final patching report will show the WebLogic Server patches have failed. You can ignore the WebLogic Server patch failures.
If Oracle BI EE was installed in Enterprise Install Mode, then start WLS Admin Server, Managed Server and Node Manager. Start the BI processes using OPMN.
If you installed Oracle BI EE in Software Only mode, then skip this step.
You configure the BI Domain by running the config.bat or config.sh file. You need to perform this procedure if you installed Oracle BI EE in Software Only Install mode.
Note: If you installed Oracle BI EE in Enterprise Install mode, you do not have to perform this procedure. The BI Domain was configured as part of Section 3.2.4, "Installing Oracle Business Intelligence Enterprise Edition 11g."
The config.bat and config.sh files are located in <BI_Oracle_Home>/bin.
When running the config.bat file (or config.sh on Linux/UNIX), do the following:
On the Create or Scale Out BI System screen, select Create New BI System.
For information about the options in this screen, see Section A.4, "Create, Scale Out, or Extend BI System," in Oracle Business Intelligence Suite Enterprise Edition Installation and Upgrade Guide.
On the Configure Components screen, for Oracle BI Applications V11.1.1.7.1, you must select the following four options:
Business Intelligence Enterprise Edition.
Business Intelligence Publisher (will be automatically selected).
Real-Time Decisions.
Essbase Suite.
Note: Do not scale out the BI Domain.
You run the configApps.bat or configApps.sh file to extend the BI Domain to deploy Oracle BI Applications and to configure the components.
During this phase, the following key configurations occur:
Oracle BI Applications Configuration Manager, Functional Setup Manager, ODI Java EE Agent, ODI Console, and Load Plan Generator are deployed into WebLogic Server.
Component wiring is performed.
A BI Applications Administrator User (with full access to Configuration Manager and access to ODI with the Supervisor role) is created in WebLogic Server embedded LDAP.
The ODI Repository for BI Applications is configured and set to use external authentication (authentication against the WebLogic Server embedded LDAP).
The configApps.bat and configApps.sh files are located in <BI_Oracle_Home>/bin.
To configure components by running the configApps.bat or configApps.sh file:
Before running the configApps process, ensure that WLS Admin Server, Node Manager, and BI Services are running.
Start the configuration utility from the bin directory in the BI_Oracle_Home (default folder name is Oracle_BI1), based on the operating system:
UNIX commands:
cd BI_Oracle_Home/bin
./configApps.sh
Windows commands:
cd BI_Oracle_Home\bin
configApps.bat
On the Welcome screen, click Next.
On the Prerequisite Checks screen, after the prerequisite checks conclude with no errors, click Next.
If an error message appears, fix the error and then click Retry to run the prerequisite check again (recommended). Repeat this until all prerequisite checks conclude with no errors. To stop the configuration process while you fix a prerequisite error, click Abort. To ignore an error or warning message, and continue with the configuration process, click Continue (not recommended).
Note:
The configuration might not function normally if you continue without resolving the issue that caused an error or warning message during the prerequisite checks.
On the Extend BI Domain screen, specify the following:
| Field | Description |
|---|---|
|
Host Name |
The host name of the computer on which the WebLogic Server domain exists. This field is read-only. |
|
Port |
Specify the port number over which the WebLogic Server domain communicates. The default is 7001. |
|
User Name |
Specify the user name for logging into the WebLogic Server. |
|
User Password |
Specify the password for logging into the WebLogic Server. |
Click Next.
The Specify Installation Location screen displays the following information.
| Field | Description |
|---|---|
|
Middleware Home |
Specify the path to the directory for an existing Oracle Middleware Home where Oracle BI EE has been installed. The value in this field is read-only. |
|
Oracle Home |
The Oracle Home for BI, which is the location where Oracle BI EE, Oracle BI Applications, and Operational Planning Applications files are installed. The value in this field is read-only. |
|
WebLogic Server Home |
The directory name for the WebLogic Server. The value in this field is read-only and is the host name you specified in the Middleware Home field. |
|
Domain Home |
The home directory for the domain associated with the Oracle Business Intelligence system. The value in this field is read-only. |
|
Instance Home |
The path to the Oracle Instance directory. The installer installs component configuration files and runtime processes in the Oracle Instance directory. Runtime components write to this directory only. The directory that you identify for the Oracle Instance can be located anywhere on your system, and does not need to be inside the Oracle Middleware Home. The value in this field is read-only. |
|
Instance Name |
The name of the Oracle Business Intelligence instance. By default, the location is based on the value in the Instance Home field. This directory is commonly referred to as ORACLE_INSTANCE. The value in this field is read-only. |
Click Next.
On the Configure Components screen, to deploy Oracle BI Applications, select BI Application Components.
Note: Do not select the Indirect Spend Planning option. This option is not supported.
Click Next.
On the RPD Encryption Password screen, specify the following:
| Field | Description |
|---|---|
|
RPD Password |
Specify the password used to encrypt the RPD. |
|
Confirm RPD Password |
Confirm the password used to encrypt the RPD. |
Click Next.
On the BI Applications Administrator User screen, specify the following:
| Field | Description |
|---|---|
|
Username |
Specify a user name for the Oracle BI Applications Administrator. Note: Do not enter "Administrator," "Admin," "Sadmin," or "Supervisor" in upper case, lower case, or mixed case letters. These user names are reserved. Also, do not use the WebLogic Server administrator user name. |
|
Password |
Specify a password for the Oracle BI Applications Administrator. |
|
Confirm Password |
Confirm the password. |
Note these credentials because this user will be used to perform system setups and is the user that is used for communications between the Oracle BI Applications Configuration Manager and ODI. This user has full access privileges in Configuration Manager and access to ODI with the Supervisor role.
Click Next.
On the MDS Schema screen, specify the following:
| Field | Description |
|---|---|
|
Database Type |
The type of database that hosts the MDS schema. The only supported database type is Oracle. |
|
Connect String |
The connect string used to access the MDS schema. |
|
MDS Schema Username |
The schema name for the MDS schema. |
|
MDS Schema Password |
The password for the MDS schema. |
Note: The values for user name and password must match the values you entered when you ran the Fusion Middleware RCU in Section 3.2.3, "Running Fusion Middleware RCU."
Click Next.
On the BI Applications Components Repository Schema screen, specify the following:
| Field | Description |
|---|---|
|
Database Type |
Select the type of database that hosts the Oracle BI Applications Components Repository schema. The only supported database type is Oracle. |
|
Connect String |
Specify the connect string used to access the Oracle BI Applications Components Repository schema. Use the format: host:port:service_name |
|
BIA Components Repository Schema Username |
Specify the schema name for the Oracle BI Applications Components Repository schema. |
|
BIA Components Repository Schema Password |
Specify the password for the Oracle BI Applications Components Repository schema. |
Click Next.
On the Business Analytics Warehouse Schema screen, specify the following:
| Field | Description |
|---|---|
|
Database Type |
Specify the type of database that hosts the Business Analytics Warehouse schema. The only supported database type is Oracle. |
|
Connect String |
Specify the connect string used to access the Business Analytics Warehouse schema. Use the format: host:port:service_name |
|
Business Analytics Warehouse Schema Username |
Specify the schema name for the Business Analytics Warehouse schema. |
|
Business Analytics Warehouse Schema Password |
Specify the password for the Business Analytics Warehouse schema. |
Click Next.
On the BI Applications ODI Repository Schema screen, specify the following:
| Field | Description |
|---|---|
|
Database Type |
Specify the type of database that hosts the ODI Repository schema. The only supported database type is Oracle. |
|
Connect String |
Specify the connect string used to access the ODI Repository schema. Use the format: host:port:service_name |
|
ODI Repository Schema Username |
Specify the schema name for the ODI Repository schema. The default name is <prefix>_BIA_ODIREPO. This is the repository you created when you ran the Business Analytics Applications Suite RCU. |
|
ODI Repository Schema Password |
Specify the password for the ODI Repository schema. |
Click Next.
On the Configure Ports screen, specify the following:
| Field | Description |
|---|---|
|
Auto Port Configuration |
Select this option if you want Oracle Business Analytics Applications Suite installer to configure the ports for you. |
|
Specify Ports Using Configuration File |
Select this option to use a configuration file to configure the ports. Optionally, click Browse to specify a configuration file location. Click View/Edit File to view or edit the file. A sample configuration file named staticport.ini is provided. The file is stored in the Disk1\stage\Response directory of the Business Analytics Applications Suite installer. You can edit this file to specify the configuration settings for your environment. |
On the Summary screen, click Save to save the settings for this configuration in a response file (optional), and then click Configure to start the configuration process.
On the Configuration Progress screen, you can monitor the progress of the software configuration and respond to errors, if any occur.
If a configuration task fails, an error message appears. To retry the task, click Retry. To continue with the next task, click Continue (not recommended). To stop the installation and configuration process entirely, click Abort.
After the configuration concludes without any errors, click Next.
On the Complete screen, click Save to save the settings for this installation in a response file (optional), and then click Finish to exit the Oracle Business Intelligence Configuration Assistant.
Oracle BI Applications requires WebLogic Server 10.3.6. If you installed Oracle BI EE in Enterprise Install mode, then WebLogic Server 10.3.5 was automatically installed. You must now upgrade to WebLogic Server 10.3.6. The WebLogic Upgrade Installer allows you to upgrade to WebLogic Server 10.3.6. The Upgrade Installer is available on My Oracle Support (https://support.oracle.com). For instructions on downloading the Upgrade Installer and upgrading to WebLogic 10.3.6, see Oracle Fusion Middleware Getting Started With Installation for Oracle WebLogic Server 11g Release 1 (10.3.6) > Obtaining the Installation Program > Upgrade Installer.
ODI Studio with the Oracle BI Applications Load Plan Generator Plug-in 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.
To install ODI Studio and the Load Plan Generator Plug-in, 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.
The Oracle BI Applications Load Plan Generator Plug-in is delivered as a ZIP file containing a set of jar files and a Readme file with instructions on how and where to deploy the jar files. System administrators must provide the ZIP file to developers as needed. The ZIP file is installed in the Oracle Home for BI directory, at <BI_Oracle_Home>/clients/biappsclients/odi/OBIA_LPG_Plugin.zip.
Follow the instructions in the Readme file to extract the ZIP file and deploy the jar files.
This section contains information about the post-installation patches that you must apply.
To apply the post-installation Patches:
Apply the ATGLite Patch, as described in Section 3.3.9.1, "Applying the ATGLite Patch".
Apply the client-side Patch 16629917 to ODI Studio, as described in Section 3.3.9.2, "Applying Patch 16629917 to ODI Studio".
Apply the client-side Patch 16492220 to BI Clients, as described in Section 3.3.9.3, "Applying Patch 16492220 to BI Clients".
The patches are available in the directory in which you extracted the Fusion Middleware Patches in step Section 3.3.4, "Applying Platform Patches." in the PATCH_ROOT_DIR, for example, C:\patches or PATCH_HOME/patches.
Note: This sub-step is part of Section 3.3.9, "Applying Post-Installation Patches."
ATGLite is a J2EE component used by Oracle BI Applications Configuration Manager and Functional Setup Manager.The binaries for ATGLite Patch 16239380 are applied when the Fusion Middleware platform patches are applied in Section 3.3.4, "Applying Platform Patches." However, schema update and seed data updates are not applied and must be performed by running scripts. ATGLite Patch 16239380 updates tables and seed data in the BI Applications Components Repository Schema (BIACOMP).
To apply the ATGLite Patch:
Stop all the services related to Business Intelligence components.
Note: Use Fusion Middleware Control to stop Oracle BI EE components. For more information, see 'Using Fusion Middleware Control to Start and Stop Oracle Business Intelligence System Components and Java Components" in Oracle Business Intelligence Suite Enterprise Edition System Administrator's Guide.
Update the BIACOMP schema:
Oracle recommends that you perform the steps below by starting a fresh Xterm, such as Xterm1, because the ORACLE_HOME used is the Oracle RDBMS client.
Identify the client install of Oracle RDBMS. Set the environment to execute SQLPlus from this client installation. The most common variables are ORACLE_HOME, PATH LD_LIBRARY_PATH, TWO_TASK and ORACLE_SID.
Verify that you can connect to the BIACOMP schema database as
sqlplus system/<password>
sqlplus <BIACOMP_user>/<password>
Execute the following:
sqlplus <schema_BIACOMP>/<password_DW>@<db> @<BI ORACLE_HOME>/sdf/DW/ATGPF/sql/fndtbs_11170_upg.sql
Apply seed data updates:
Note: This step applies to Linux and UNIX installations only. For Windows installations, the script required for this process is not currently available. Oracle Fusion Middleware Release Notes for Oracle Business Intelligence Applications will be updated when a Windows-specific script is available.
Without the application of the seed data updates, BI Applications Configuration Manager and Functional Setup Manager continue to function without loss of functionality.
Oracle recommends that you perform the steps below by starting a fresh Xterm, such as Xterm1, because the ORACLE_HOME used is the ORACLE_HOME for BI.
Identify the BI_ORACLE_HOME.
This is the directory under MW_HOME that holds Oracle BI EE and Oracle BI Applications code. For example:
/scratch/shiphomeInstall/mwhome_110116_1002/Oracle_BI1
Set ORACLE_HOME to BI_ORACLE_HOME. For example:
ORACLE_HOME /scratch/shiphomeInstall/mwhome_110116_1002/Oracle_BI1
or
export ORACLE_HOME=/scratch/shiphomeInstall/mwhome_110116_1002/Oracle_BI1
Execute the post script using the following command. You must specify the arguments in the same order as they appear:
cd <patch_dir>/16239380/custom/linux
sh post apply 16239380 <database host>:<database port>:<database_sid>
<BIACOMP schema> <BIACOMP password>
Note: Where <patch dir> is /work/patches/biappsshiphome/generic where '/work' directory is the Work directory specified in step Section 3.3.4, "Applying Platform Patches."
For example:
sh post apply 16239380 dbhost.example.com:1521:orcl DEV_BIACOMP BIACOMP_db_password
Start the WebLogic Server using Fusion Middleware Control, and restart BI Services.
If you receive the following error, ignore it:
1) SEVERE: java.io.FileNotFoundException: /slot/XXXXXXX/oracle/ora6464/mw_home_standalone/patches/XXXXXXXX/custom/scripts/./config/jps-config.xml (No such file or directory) 2) INFO: MDS-00013: no metadata found for metadata object "/META-INF/connections.xml"
Note: This sub-step is part of Section 3.3.9, "Applying Post-Installation Patches."
Patch 16629917 is available in PATCH_ROOT_DIR\odi\generic or PATCH_ROOT_DIR/odi/generic.
System administrators must provide this patch to developers who have installed ODI Studio on their machines.
Follow the instructions in the Patch Readme to apply the patch on ODI Studio.
Note: This sub-step is part of Section 3.3.9, "Applying Post-Installation Patches."
Patch 16492220 is available in PATCH_ROOT_DIR\biappsshiphome\generic or PATCH_ROOT_DIR/biappsshiphome/generic.
System administrators must provide this patch to developers who have installed BI Clients (BI Administration Tool or BI Catalog Manager) on Windows machines.
Note: If BI Clients have not been installed then provide the biee_client_install_x64.exe executable file in the patch to developers to install the BI Clients. Run biee_client_install_x64.exe obtained on unzip of the patch zip file. Select "Install a new instance"
On Windows machines where BI Clients have been installed:
Run biee_client_install_x64.exe obtained on unzip of the patch zip file. Select "Modify an existing instance".
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 for BI 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 for BI 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.
This section contains the following topics:
Section 3.4.1, "Setting the Business Analytics Warehouse Connection in ODI"
Section 3.4.2, "Registering Source Systems and Propagating Connection Details to ODI"
Section 3.4.4, "Editing Preferred Currency Display Names and Enabling Document Currency"
Section 3.4.5, "Setting Languages for Data Load into the Business Analytics Warehouse"
Section 3.4.7, "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 directory where you copied source files to in Section 3.3.10, "Copying Source Files," 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. Note: This user was created during the Section 3.3.6, "Configuring Oracle BI Applications."
In the navigation pane, select the Define Business Intelligence Applications Instance link, which appears under System Setups.
The Source Systems tab is displayed.
Click the Add icon.
The Register Source dialog is displayed.
To register the source in Configuration Manager, specify the following properties:
| Property | Description |
|---|---|
|
Product Line |
Select the source instance product line. |
|
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 |
(For PeopleSoft Enterprise sources only.) In the Data Server Details window, select the appropriate data server for the source instance. |
Click Next. The Register Source in Oracle Data Integrator Topology page is active.
To register the source in ODI, do the following:
Select Global from the Context drop-down list.
The Global value is required because the Oracle BI Applications interfaces are designed to use this value.
In the Technology: Oracle tab, specify the following properties:
| Property | Description |
|---|---|
|
ODI Data Server Name |
Specify a name for the transactional OLTP database (source database). This ODI Data Server Name must be unique across all ODI data servers in the ODI Repository. |
|
JDBC Driver |
The name of the JDBC driver for the transactional OLTP database (source database) connection. Oracle recommends that you use the default value. |
|
JDBC URL |
Specify the JDBC URL for the transactional OLTP database (source database) connection. The format for the URL is the following:
|
|
Database Username |
Specify the database username for the transactional OLTP database (source database). |
|
Database Password |
Specify the password for the transactional OLTP database (source database). |
|
Test |
Use this button to test the connection to the transactional OLTP database (source database). |
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 resides. |
|
Path To File |
Specify the directory where you copied the source files in Section 3.3.10, "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, if your source system is Oracle EBS 12.1.1, the directory path would be: <source file home>/biapps/etl/data_ files/src_files/EBS_12_1_1 |
|
Array Fetch Size |
The number of rows requested by ODI on each communication with the data server. Note: This column may 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 may be hidden. To view this column, click View, Columns, Show All. |
|
JDBC Driver |
Oracle recommends that you use the default value. Note: This column may be hidden. To view this column, click View, Columns, Show All. |
|
JDBC URL |
Oracle recommends that you use the default value. Note: This column may 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, 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 pre-configured 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 Section 10.2 'Using Fusion Middleware Control to Upload a Repository and Set the Oracle BI Presentation Catalog Location' in Oracle Business Intelligence Suite Enterprise Edition System Administrator's Guide.
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.
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.4.2, "Registering Source Systems and Propagating Connection Details to ODI," including registering the source in the Register Source in Oracle Data Integrator Topology page, as described in step 5 in the procedure.
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 may 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.
Note: On installation the Oracle BI Applications system is configured to use WebLogic Server embedded LDAP for authentication.
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 Fusion Middleware Security Guide for Oracle Business Intelligence Applications.
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 security guide.
Oracle BI Applications release 11.1.1.7.1 delivers a full RPD file with projects for all the BI Applications modules and for Operational Planning Applications. This full RPD is deployed to the BI Server. You can trim the RPD so that it includes only the projects that are relevant to your deployment. Although optional, trimming the RPD makes the BI Server startup process faster and also makes patching quicker.
The steps for trimming the RPD depend on the status of your deployment:
If the RPD has not been customized for your deployment: Extract the projects for the products that your organization has purchased. You do not need to perform a merge. See section Section 3.4.8.1, "Extracting Projects From Full RPD," for instructions.
If the RPD has been customized for your deployment: Extract the applicable projects from the full (delivered) RPD for release 11.1.1.7.1, and, additionally, merge that RPD with your customized release 11.1.1.7.1 RPD. See Section 3.4.8.1, "Extracting Projects From Full RPD," and Section 3.4.8.2, "Merging Repositories," for instructions.
Follow this procedure to extract projects from the full RPD. The end result of this process is a trimmed RPD.
To extract from the RPD the projects for the products you have purchased:
Open a Command window on the computer where the BI Administration Tool is installed.
If you installed Oracle BI EE on Windows, then run bi-init.cmd to launch a Command prompt that is initialized to your Oracle instance. This utility is located in:
<MiddlewareHome>\instances\instance<n>\bifoundation\OracleBIApplication\coreapplication\setup
If you installed the BI Administration Tool using the BI Client installer, then run bi_init.bat to launch a Command prompt that is initialized your Oracle instance. This file is located in:
<Oracle BI Home>\oraclebi\orahome\bifoundation\server\bin
In a Command prompt window, run ExtractProjects, as described below:
If you installed Oracle BI EE on Windows, ExtractProjects.exe is located in <Oracle Home for BI>\bifoundation\server\bin.
If you installed BI Administration Tool using the BI Client installer, ExtractProjects.exe is located in <Oracle BI Home>\oraclebi\orahome\bifoundation\server\bin.
Run one of the following commands:
For extracting a single project:
ExtractProjects -B input_rpd -O output_rpd -I "project_name"
For extracting multiple projects:
ExtractProjects -B input_rpd -O output_rpd -I "project_name1" -I "project_name2"-I "project_name3" (and so on)
where:
input_rpd is the name and path of the full (delivered) release 11.1.1.7.1 RPD and from which you want to extract the project or projects (for example, OracleBIApps.rpd).
output_rpd is the name and path of the RPD you want to create with the extracted projects (for example, OracleBIAppsTrimmed.rpd).
project_name is the name of the RPD project you want to extract.
You will be prompted to enter the encryption password for the RPD (input_rpd ).
The list of projects in the 11.1.1.7.1 RPD includes the following:
Financial Analytics Fusion Edition
Human Resources Analytics Fusion Edition
Marketing Analytics Fusion Edition
Partner Analytics Fusion Edition
Project Analytics Fusion Edition
Sales Analytics Fusion Edition
Supply Chain and Order Management Analytics Fusion Edition
Student Information Analytics
Service Analytics
Price Analytics
Manufacturing Analytics
Operational Planning
DataLineage_Project
Note: The RPD contains projects in addition to those listed above. These projects are included for future content delivery and upgrade support. To determine the BI Applications available in this release, see "System Requirements and Supported Platforms," for Oracle BI Applications release 11.1.1.7.1 at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html.
Save and rename the trimmed RPD. Make sure the name identifies this RPD as one that has been trimmed, for example, OracleBIAppsTrimmed.rpd.
Follow this procedure only if you have customized the RPD and are subsequently trimming the RPD.
To merge repositories:
In the Oracle BI Administration Tool, open in offline mode the trimmed Oracle BI RPD that you created in the procedure Section 3.4.8.1, "Extracting Projects From Full RPD," for example, OracleBIAppsTrimmed.rpd.
On the menu bar, click File, and then click Merge.
In the Select Original Repository dialog box, select the repository OracleBIApps.rpd, which is the full RPD.
Enter the password for the original repository, and then click OK.
Click Select for the Modified Repository field. The Select Modified Repository dialog box opens.
The Select Modified Repository dialog opens.
Select the repository that contains the customizations you made to the RPD file, for example, OracleBIAppsCustom.rpd.
Click Open, and enter the password for the previously customized RPD file, and then click OK.
In the Decision drop-down list, select the action you want to take regarding the repository change, or accept the default action.
To locate subsequent rows with empty Decision fields, click the Decision header cell. After all rows have a value in the Decision field, the Merge button becomes enabled.
Click Merge.
A message appears after the merge concludes successfully.
On the menu bar, click File, and then click Save As. Save the current repository using a new name, such as OracleBIAppsFinal.rpd.
After the system setups are complete, your environment is ready for functional configuration and, subsequently, data loads.
For instructions on performing functional configuration, see Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
For information about performing ETL processes, see Oracle Fusion Middleware ETL Guide for Oracle Business Intelligence Applications.
For information about administering and customizing Oracle BI Applications, see Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Applications.
For information about how security is implemented in Oracle BI Applications, see Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Applications.
|
 Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|