Installing and Configuring Oracle BI Applications

Use these instructions to install and configure Oracle BI Applications.

You must perform the following procedures in the order they are listed:

Database Instances for Schemas and Repositories

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)
Oracle Data Integrator Repository for Oracle BI Applications (includes Master and Work repositories)

Note these 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
- Oracle Data Integrator Repository for BI Applications
To identify the specific version of Oracle Database Enterprise Edition supported for this release of Oracle BI Applications, go to the Oracle Fusion Middleware Supported System Configurations page at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html and see System Requirements and Supported Platforms.
The Oracle Database Enterprise Edition must be configured with UNICODE.
The Business Analytics Warehouse, BI Applications Components Repository, and Oracle Data Integrator Repository can be installed on different database servers.
The Oracle Data Integrator Master and Work repositories are installed into the same schema.
Review Guidelines for Setting Up Oracle Business Analytics Warehouse Databases for information about database requirements for the Business Analytics Warehouse.

Creating Schemas Using Business Analytics Applications Suite RCU

You must run the Business Analytics Applications Suite RCU to create schemas for Oracle Business Analytics Warehouse, Oracle Business Applications Components, and Oracle Data Integrator Repository for Oracle BI Applications.

Before you run the Business Analytics Applications Suite RCU, note these points:

On Windows systems, 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 servers. (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 these 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 system hosting the database. For example, `host12345.example.com`
Port	Sphostecify 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 SYSDBA.

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

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. (RCU writes log files to this directory). The .dmp files are located in BIA_RCU_HOME\rcu\integration\biapps\schema.
In 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.

Don't include the name of the .dmp file in the directory path.

Click Next to proceed to the Map Tablespaces screen.

On the Map Tablespaces screen, which displays the default and temporary tablespaces for the schemas:

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 this table:

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.

Installing Oracle BI Applications Using the Business Analytics Applications Suite Installer

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 system 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:

The installer is a generic installer and requires JDK or JRockit to be installed. See JDK or JRocket Installation.
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.

Launch the Business Analytics Applications Suite installer using the command for your operating system.

The Business Analytics Applications Suite installer displays the Welcome screen.

Platform Command

Platform	Command
Windows	In a command prompt: `setup.exe -jreLoc <Drive:\...\jdk or jrockit location>` Where `jdk or jrockit location` is the directory that contains the bin folder. For example: `setup.exe -jreLoc C:\jdk`
UNIX and Linux	`./runInstaller -jreLoc <jdk or jrockit location>`

Windows

In a command prompt:

setup.exe -jreLoc <Drive:\...\jdk or jrockit location>

Where jdk or jrockit location is the directory that contains the bin folder.

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 system that does not have the file /etc/oraInst.loc, the Specify Inventory Location screen displays.

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 will be installed.

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 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.
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, wait until the Finish button is displayed.
Click Finish.

Applying Platform Patches

Apply the appropriate platform patches during the installation process.

Apply these patches to complete your installation:

Fusion Middleware bundle patch OBIEE 11g 11.1.1.7.150120
Oracle BI EE Client installer patch 19190111 (included in the Oracle Business Intelligence Applications 11.1.1.9.2 media pack).
If installing Fusion Middleware on Windows, install patch 18600348, which you can obtain at http://aru.us.oracle.com:8080/ARU/ViewPatchRequest/process_form?aru=18600348

You can apply the patches in any order.

Applying the Fusion Middleware Platform Patch

Apply the Fusion Middleware Platform patch.

Download Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for your operating system from the Oracle Business Intelligence Applications 11.1.1.9.2 media pack on Oracle Software Delivery Cloud.

Download all parts.
Extract all .zip files into the same Patch Home directory.

Extract the contents of the downloaded .zip files containing the patches into the same directory, for example, C:\patches or PATCH_HOME/patches. 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 don't 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 ORACLE_HOME/biapps/tools/bin directory (use backslashes for Windows).

Specify these 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.
WINDOWS_UNZIP_TOOL_EXE	If the platform is Windows, then specify an unzip tool EXE file with the complete path. The supported unzip tools are Winzip command line and 7-Zip command line. For example, for the Winzip tool: `c:{PathSep}Program Files{PathSep}WinZip{PathSep}wzunzip.exe` For example, for the 7-Zip tool: `c:{PathSep}Program Files{PathSep}7-Zip{PathSep}7z.exe`
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`

To apply the patch, run this command from ORACLE_HOME/perl/bin.
```
$ perl ORACLE_HOME/biapps/tools/bin/APPLY_PATCHES.pl ORACLE_HOME/biapps/tools/bin/apply_patches_import.txt
```
In case you run into issues during the applying patches procedure, for example, APPLY_PATCHES.pl and you are unable to identify the patches directory path on some windows platform, then you can manually apply the patches. For example, after all the patches in the zip file are unzipped to C:\work\patching\patches directory, use the following commands:
- C:\work\mw333\Oracle_BI1\OPatch\opatch napply C:\work\patching\patches\biappsshiphome\generic -silent -oh C:\work\mw333\Oracle_BI1 -jdk C:\work\mw333\Oracle_BI1\jdk > C:\work\patching\biappshiphome_generic_patches.log
- C:\work\mw333\Oracle_BI1\OPatch\opatch napply C:\work\patching\patches\biappsshiphome\win64 -silent -oh C:\work\mw333\Oracle_BI1 -jdk C:\work\mw333\Oracle_BI1\jdk > C:\work\patching\biappshiphome_win64_patches.log
- C:\work\mw333\oracle_common\OPatch\opatch napply C:\work\patching\patches\oracle_common\generic -silent -oh C:\work\mw333\oracle_common -jdk C:\work\mw333\Oracle_BI1\jdk > C:\work\patching\oracle_common_generic_patches.log
- C:\work\mw333\Oracle_ODI1\OPatch\opatch napply C:\work\patching\patches\odi\generic -silent -oh C:\work\mw333\Oracle_ODI1 -jdk C:\work\mw333\Oracle_BI1\jdk > C:\work\patching\odi_generic_patches.log
On other platforms, replace win64 and command path with the corresponding ones. Your patch directory structure should look similar to the following image:

Description of illustration biain_exdirstr.gif

To manually apply Weblogic patches, use the following command:
- C:\work\mw333\Oracle_BI1\jdk\bin\java -jar C:\work\patching\suwrapper\bsu-wrapper.jar -prod_dir=C:\work\mw333\wlserver_10.3 -install -patchlist=JEJW,LJVB,EAS7,TN4A,KPFJ,RJNF,2GH7,W3Q6,FKGW,6AEJ,IHFB -bsu_home=C:\work\mw333\utils\bsu -meta=C:\work\patching\suwrapper\suw_metadata.txt -verbose > C:\work\patching\weblogic_patching.log
Ensure that you place the Weblogic patch files from all .zip in the directory structure as seen in the following image:

Description of illustration biain_exdirstrwl.gif
Confirm that all patches have been applied successfully by reviewing these 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
Start WLS Administration Server, Node Manager, and BI Managed Server.

You must start the BI Managed Server using WLS Admin Console. Start the BI processes using OPMN.

Applying the BI EE Client Installer Patch

Apply the Oracle BI EE Client installer patch 19190111 (included in the Oracle Business Intelligence Applications 11.1.1.9.2 media pack) on Windows system where the BI Administration Tool has been installed.

System administrators must provide the BI EE Client Installer executable to developers who have installed the BI Administration Tool on Windows systems.

Obtain the patch file, then unzip it to a folder.
Change directories to PATCH_ROOT_DIR\biappsshiphome\generic.
Run biee_client_install_x64.exe.
Select an instance.
- Select Modify an existing instance if you have an existing installation of the Admin Client.
- Select Install a new instance for new installations.

Updating ATGLite

Use these instructions to update the ATGLite data in the BIACOMP schema.

Upgrade ATGLite schemas from 11.1.1.7.0 to 11.1.1.7.3 before configuring BI Applications.

Launch the Patch Set Assistant from ORACLE_HOME/bin.
Click Next in the Welcome screen.
On the Select Component page, select ATGPF Lite, which selects the child option, ATGLITE schema, then click Next.
On the Prerequisites page, select Database backup completed and Database version is certified by Oracle for Fusion Middleware upgrade, then click Next.
On the FSM Schema page, follow the instructions at the top of the page to enter the details for the database containing the FSM schema, then click Next.
Verify that the examination process is successful, then click Next.
View the Upgrade Summary, then click Upgrade.
Review the information on the Upgrade Success page, then click Close.

Updating FSM

Use these instructions to update the FSM data in the BIACOMP schema.

Upgrade FSM schemas from 11.1.1.7.0 to 11.1.1.7.3 before configuring BI Applications.

Launch the Patch Set Assistant from ORACLE_HOME/bin.
Click Next in the Welcome screen.
On the Select Component page, select Oracle Fusion Functional Setup Manager Lite, which selects the child option, FSM schema, then click Next.
On the Prerequisites page, select Database backup completed and Database version is certified by Oracle for Fusion Middleware upgrade, then click Next.
On the FSM Schema page, follow the instructions at the top of the page to enter the details for the database containing the FSM schema, then click Next.
Verify that the examination process is successful, then click Next.
View the Upgrade Summary, then click Upgrade.
Review the information on the Upgrade Success page, then click Close.

Oracle Business Intelligence Configuration

You configure the BI Domain by running the config.bat or config.sh file.

The config.bat and config.sh files are located in ORACLE_HOME/bin.

When running the script, do these tasks:

On the Create or Scale Out BI System screen, select Create New BI System.
On the Configure Components screen, for Oracle BI Applications, you must select the following four options:
- Business Intelligence Enterprise Edition.
- Business Intelligence Publisher (will be automatically selected).
- Real-Time Decisions.
- Essbase Suite.

Note:

Don't scale out the BI Domain.

Configuring Oracle BI Applications

You'll need to 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, these 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 Oracle Data Integrator Repository for Oracle BI Applications is configured and set to use external authentication (that is, authentication against the WebLogic Server embedded LDAP).

The configApps.bat and configApps.sh files are located in ORACLE_HOME/bin.

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 Oracle home (default folder name is Oracle_BI1), based on the operating system:

UNIX commands:

cd ORACLE_HOME/bin

./configApps.sh

Windows commands:

cd 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 these details:

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 this information:

Field	Description
Middleware Home	Specify the path to the directory for an existing Oracle Middleware Home where Oracle BI EE has been installed. This field is read-only.
Oracle Home	The Oracle Home for BI, which is the location where Oracle BI EE, and Oracle BI Applications files are installed. 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. 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. 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.

Click Next.
On the RPD Encryption Password screen, specify these details:

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.

Field	Description
RPD Password	Specify the password used to encrypt the RPD.
Confirm RPD Password	Confirm the password used to encrypt the RPD.

On the BI Applications Administrator User screen, specify these details:

Field	Description
Username	Specify a user name for the Oracle BI Applications Administrator. 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 Oracle Data Integrator. This user has full access privileges in Configuration Manager and access to Oracle Data Integrator with the Supervisor role.

Click Next.

On the MDS Schema screen, specify these details:

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 Running Fusion Middleware RCU.

Click Next.

On the BI Applications Components Repository Schema screen, specify these details:

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 these details:

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 these details:

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 these details:

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.

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.

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.

How to Start the BI and Oracle Data Integrator Managed Servers

Oracle BI Applications requires the BI and Oracle Data Integrator 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 Oracle Data Integrator Managed Servers, functionality loss and memory issues can occur in Oracle BI Applications Configuration Manager, Functional Setup Manager, and Oracle Data Integrator.

To ensure that the BI and Oracle Data Integrator Managed Servers are started using Node Manager, start them using the WebLogic Administration Console user interface. Do not start the BI and Oracle Data Integrator Managed Servers using the Managed Server start scripts.

Installing ODI Studio

You can design and manage the ODI Repository by using the ODI Studio desktop client. ODI Studio is typically installed on developer systems. The supported operating systems for ODI Studio are Windows 32-bit and 64-bit and Linux 32-bit.

Installing ODI Studio

You install ODI Studio using the Oracle Data Integrator installer.

Note these points:

On the Select Installation Type screen, 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, select the Skip Repository Configuration option.

For instructions on installing ODI Studio, see Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.

Configuring User Access for ODI Studio

The Oracle Data Integrator Repository is configured for external authentication against the WebLogic Server 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:
```
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 system where Oracle Home for BI resides.

Regenerating the Security Files

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.

About Applying the ODI Studio Patch

The ODI Studio patch is available in PATCH_ROOT_DIR/odi/generic.

For an explanation of the PATCH_ROOT_DIR, see Applying Platform Patches.

System administrators must provide this patch to developers who have installed ODI Studio on their systems. Follow the instructions in the Patch Readme to apply the patch on ODI Studio.

Note:

If you installed ODI Studio on the BI Domain host machine, you don't have to apply the patch.

Copying Source Files

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.

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.
Note these points:
- Avoid copying the files to a location with a long directory path.
- Do not put the files under the ODI Home directory.
- Depending on your deployment, there may be files in the BI_Oracle_Home/biapps/etl directory that you will not use.

Next Steps After Installation — System Setup

The next steps in the installation and setup process are to perform the system setup tasks and configure BI Applications–ODI Authentication to external (OID).

See Performing Post-Installation System Setup Tasks . These tasks are required to complete integration of the Oracle BI Applications components and to ready the system for functional configurations and data loads.

Steps to Configure BI Applications–ODI Authentication to External (OID)

Oracle Business Intelligence uses the Oracle WebLogic Server LDAP directory for authentication by default. The BI Applications installation on the BI EE platform requires the use of the embedded Weblogic LDAP. Once BI Applications has been installed and set up, you can be configured it to use an external LDAP for authentication.

Prerequisite: BI Applications 11.1.1.9.1+ has been installed into the BI Domain where the default Weblogic embedded LDAP is used for authentication.

Note:

The BI Applications installation will fail if an external LDAP system is being used. If you have configured the BI system for use with an external LDAP (for example, Oracle Internet Directory), then you must re-configure to use the default Weblogic embedded LDAP before you perform the BI Applications installation

To configure the BI system including BI Applications to use an external authenticator:

Configure the Business Intelligence system to use an external LDAP for authentication.
See: Chapter 3 Using Alternative Authentication Providers, Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition 11g Release 1 (11.1.1)
Create the BI Applications Administrator and BIAppsSystemUser users in the external LDAP system.

In the external LDAP, create the BI Applications Administrator user. This user will be granted the BI Applications Administrator Duty and will be added to the ODI Repository with Supervisor privileges during script execution in step 4 below. This user will have full access to BI Applications Configuration Manager and to ODI Console and the ODI Repository. In the external LDAP, create a user with name “BIAppsSystemUser”(this is case sensitive) and make sure uid attribute in OID is updated with the same name. This user credentials will be used by the ODI Java EE Agent deployed in Weblogic to connect to the ODI Repository. This user will also be created in the ODI repository with SUPERVISOR privileges during script execution in step 4 below
Update the oracle.biapps.system credential map to include the BIAppsSystemUser user.
Run wlst.sh from MW_HOME/oracle_common/common/bin folder:
```
connect('<ADMIN_USER_NAME>', '<ADMIN_PASSWORD>', 't3://<host>:<port>')
updateCred(map='oracle.biapps.system', key='system.user', user='BIAppsSystemUser', password='<Password_forBIAppsSystemUser>',
desc="Credential")
```
where: <Password_forBIAppsSystemUser> is the password entered for the BIAppsSystemUser in step 2 above
Run switch_odiToExternalAuth.py script.
This script will associate the BI Applications Administrator Duty to the BI Applications Administrator user and will add the BI Applications Administrator and BIAppsSystemUser users to the ODI repository with Supervisor privileges. ODI will be configured to use the external LDAP for authentication.

Run the following command from MW_HOME/oracle_common/common/bin folder:
```
./wlst.sh <ORACLE_HOME>/bifoundation/install/switch_odiToExternalAuth.py -- ADMIN_USER_NAME <ADMIN_USER> --DOMAIN_HOSTNAME <DOMAIN_HOST> -- DOMAIN_PORT <DOMAIN_PORT> --DOMAIN_HOME_PATH <FULL_DOMAIN_PATH> -- ODI_HOME_PATH <FULL_ODI_HOME_PATH> --ODI_DB_CONN_STRING jdbc:oracle:thin:@<ODI_DB_CONN_STRING> --ODI_DB_SCHEMA_USER <ODI_SCHEMA_USER> --ODI_CONSOLE_USER_NAME <ODI_CONSOLE_USER> -- OID_USER <OID_USER> --LDAP_URL <LDAP_URL> --USERBASE_PREFIX <USERBASE_PREFIX_IN_OID> --GROUPBASE_PREFIX <GROUPBASE_PREFIX_IN_OID>
```
Where the ODI_CONSOLE_USER is the BI Applications Administrator user.

Restart the ODI Managed Server using Weblogic Administration Console.

Configure ODI Studio Security files.

The ODI Repository is configured for external authentication against your external LDAP server. ODI Studio must be configured to use the appropriate security files for authentication. The security files have to be regenerated for login to ODI Studio to be successful.

Run the following command from BI_ORACLE_HOME/common/bin folder in order to generate the ODI client security artifacts.

Note:

Do not run wlst from any other location.

./wlst.sh <MW_HOME>/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py external -- ADMIN_USER_NAME <Administrator> --DOMAIN_HOSTNAME <Hostname> --DOMAIN_PORT <Domain Port, e.g. 7001> --DOMAIN_HOME_PATH <Domain Home Path, e.g. MW Home>/user_projects/domains/bifoundation_domain> --OID_USER cn=orcladmin --LDAP_URL <ldap://host:port> --USERBASE_PREFIX <User base where users will be searched, e.g., cn=users,dc=us,dc=oracle,dc=com> --GROUPBASE_PREFIX <user group, e.g., cn=groups,dc=us,dc=oracle,dc=com>
Where:
the ‘external’ parameter is used to configure to the external LDAP system.
--ADMIN_USER_NAME : Weblogic Administrator user Name 
--DOMAIN_HOSTNAME : BI Domain host name 
--DOMAIN_PORT: BI Domain port 
--DOMAIN_HOME_PATH : BI Domain home path 
--OID_USER: OID user, e.g. cn=orcladmin
--LDAP_URL: external ldap url; format: ldap://host:port 
--USERBASE_PREFIX : user base prefix; where users will be searched; e.g. cn=users,dc=us,dc=oracle,dc=com
--GROUPBASE_PREFIX : user group prefix; e.g. cn=groups,dc=us,dc=oracle,dc=com

Example: ./wlst.sh /scratch/mw6826/Oracle_BI1/bifoundation/install/createJPSArtifactsODI.py external --ADMIN_USER_NAME Administrator --DOMAIN_HOSTNAME slc01apw.us.oracle.com --DOMAIN_PORT 7001 --DOMAIN_HOME_PATH /scratch/mw6826/user_projects/domains/bifoundation_domain --OID_USER cn=orcladmin -- LDAP_URL ldap://scl14405.us.oracle.com:3060 --USERBASE_PREFIX cn=users,dc=us,dc=oracle,dc=com --GROUPBASE_PREFIX cn=groups,dc=us,dc=oracle,dc=com

Copy the jps-config-jse.xmlfile and cwallet.sso files from DOMAIN_HOME_PATH/odi-client-config/external to ODI_Home/oracledi/client/odi/bin on all machines where ODI Studio clients have been installed.
Open the ODI_Home/oracledi/client/odi/bin/odi.conf file for editing.

Edit the line starting with AddVMOption -Doracle.security.jps.config to point to the jps- config-jse.xml file and location as follows:
```
AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml
```
(where jps-config-jse.xml and cwallet.sso have been copied to the ODI_Home/oracledi/client/odi/bin directory).