This chapter provides instructions for installing and setting up 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"
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 Oracle Data Integrator, 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.
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, go to the Oracle Fusion Middleware Supported System Configurations page athttp://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html and see System Requirements and Supported Platforms.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 installing Oracle Business Intelligence Enterprise Edition.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 Oracle Data Integrator also require JDK and JRockit. For the supported versions, 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. 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).
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.8.1, you must select the following four options:
Business Intelligence Enterprise Edition.
Business Intelligence Publisher.
Real-Time Decisions.
Essbase Suite.
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 release 11.1.1.8.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.
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), and locate the section titled "Upgrade Installer," under the section "Obtaining the Installation Program."
Oracle BI Applications requires an installation of Oracle Data Integrator 11g. For the specific version of Oracle Data Integrator that is 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.
For detailed information on installing Oracle Data Integrator, see Oracle Fusion Middleware Installation Guide for Oracle Data Integrator.
Note the following points:
On the Oracle Data Integrator installer Welcome screen, ignore the message regarding creation of the Oracle Data Integrator Repository. You will create the Oracle Data Integrator 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 Oracle Data Integrator 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 Oracle Data Integrator 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, "How to Start the BI and Oracle Data Integrator Managed Servers"
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 the following points:
For this release of Oracle BI Applications, the following components are supported only on Oracle Database Enterprise Edition:
Business Analytics Warehouse
BI Applications Components Repository.
Oracle Data Integrator Repository for BI Applications
For 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 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
Oracle Data Integrator 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, machine12345.example.com |
| 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 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 the following options:
| Schema Option | Default Schema Owner |
|---|---|
| Oracle Business Analytics Warehouse | <prefix>_DW (required for all deployments). |
| Oracle Business Applications Components | <prefix>_BIACOMP (required for all deployments).
When you select the BI Applications Components Repository (BIACOMP), RCU will create an additional schema, named BIACM_IO. Do not modify or delete this schema. It is required for metadata access by the different Oracle BI Applications components. |
| Oracle Data Integrator Master and Work Repository | <prefix>_BIA_ODIREPO (required for all deployments). |
Click Next to display the Schema Passwords screen.
On the Schema Passwords screen, specify and confirm a password for the schemas, then click Next to proceed to the Custom Variables screen.
Note:
The RCU uses .dmp files to create the required schemas. Before you perform the action in the Custom Variables screen, you must copy the .dmp files for each schema to a directory with global write access on the appropriate database server host machine. (RCU writes log files to this directory). The .dmp files are located in BIA_RCU_HOME\rcu\integration\biapps\schema.In the Value field 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 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.8.1 media pack. Oracle BI EE patches from Bundle Patch 131017 are included and will be applied to Oracle BI EE 11.1.1.7.0.
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.
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.
The BI Administration Tool has to be patched to BI 131017 as follows: If you have applied the BI EE Bundle Patch 131017 as part of the procedure 3.3.4 Applying Platform Patches, or if you had applied Bundle Patch 13107 earlier but had not applied the patch to your BI Administration Tool instances, then you must patch BI Administration Tool as part of this procedure.
If you have applied a Bundle Patch version higher than 131017, then you must ensure that BI Administration Tool has been appropriately patched.
The BI EE Client Installer executable is delivered in patch p17463403_111170_Generic. This patch is available in
- PATCH_ROOT_DIR\biappsshiphome\generic or
- PATCH_ROOT_DIR/biappsshiphome/generic. For the location of your PATCH_ROOT_DIR, see Section 3.3.4 Applying Platform Patches.
System administrators must provide the BI EE Client Installer executable to developers who have installed BI Administration Tool on Windows machines. On Windows machines where BI Administration Tool has been installed:
Run biee_client_install_x64.exe obtained on unzip of the patch zip file.
Select 'Modify an existing instance'.
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'.
To apply platform patches:
Shut down WebLogic Administration Server, Managed Server, and Node Manager. Shut down BI processes using Oracle Process Manager and Notification Server (OPMN).
Download "Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications" and "Oracle Fusion Middleware Platform Patches for Oracle Business Intelligence Applications for <OS> from the Oracle Business Intelligence Applications 11.1.1.8.1 media pack on Oracle Software Delivery Cloud. Download all parts.
Extract all .zip files into the same Patch Home directory, as follows:
Extract the contents of the 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. |
| 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:
For example, for the 7-Zip tool:
|
| 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 the following command from <BI_Oracle_Home>/perl/bin:
$ perl <BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl <BI_Oracle_Home>/biapps/tools/bin/apply_patches_import.txt
For example:
<BI_Oracle_Home>/perl/bin/perl <BI_Oracle_Home>/biapps/tools/bin/APPLY_PATCHES.pl <BI_Oracle_Home>/biapps/tools/bin/apply_patches_import.txt
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
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.
Make sure that the Dynamic Monitoring Service patch 16569379 is applied to your BI system.
The Dynamic Monitoring Service patch 16569379 is included the FMW Patches for BI Applications 11.1.1.8.1 under PATCH_HOME/patches/biappsshiphome/<OS folder>, and is applied when the Patch Application Script (APPLY_PATCHES.pl) is run.
This section provides instructions for updating the ATGLite data in the BIACOMP schema.
To update ATGLite:
Run the following command:
java -jar biappsrepositoryutil.jar upgradeATG <mandatory parameters>
Where the mandatory parameters are as follows:
| Parameter | Description |
|---|---|
| bi.oracle.home | Full path of the Oracle BI home. |
| work.dir | Working directory to be used for the run.
Log files will be created for each run and saved in this directory. The naming convention for the SQL log file is atgUpgradeSQLYYYY-MM_DD_HH_MM.log. Log files will be available only if they are not empty. |
| db.conn.sid.url | Connection to the database that hosts the BIACOMP schema. The format is host:port:SID.
For example: host.domain:1521:orcl. If you are using Oracle Database 12c pluggable database (PDB), then use the format host:port/ServiceName. For example, host:port/orcl.mycompany.com. |
| biacomp.user | BIACOMP schema owner. |
| biacomp.password | BIACOMP schema owner's password. |
| atg.db.seed.url | URL used to connect to the BIACOMP schema. (The ATG user is the BIACOMP schema owner.) The format is host:port/ServiceName. For example: host:port/orcl.mycompany.com. |
| db.sys.user | Database system user name. |
| db.sys.password | Database system user password.
Note: If this parameter is not passed in the command line, then the tool will request the password at runtime. |
java -jar biappsrepositoryutil.jar upgradeATG bi.oracle.home=scratch/MiddleWareHome/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=BIAPPS_BIACOMP biacomp.password=password db.conn.sid.url=<host>:<database port>:<SID> atg.db.seed.url=<host>:<database port>/<ServiceName> db.sys.user=sysuser db.sys.password=password
This section provides instructions for updating the FSM data in the BIACOMP schema.
To update FSM:
Run the following command:
java -jar biappsrepositoryutil.jar upgradeFSM <mandatory parameters>
Where the mandatory parameters are as follows:
| Parameter | Description |
|---|---|
| bi.oracle.home | Full path of the Oracle BI home. |
| work.dir | Working directory to be used for the run.
Log files will be created for each run and saved in this directory. The naming convention for the SQL log file is fsmUpgradeSQLYYYY-MM_DD_HH_MM.log. Log files will be available only if they are not empty. |
| db.conn.sid.url | Connection to the database that hosts the BIACOMP schema. The format is host:port:SID.
For example: host.domain:1521:orcl. If you are using Oracle Database 12c pluggable database (PDB), then use the format host:port/ServiceName. For example, host:port/orcl.mycompany.com. |
| biacomp.user | BIACOMP schema owner. |
| biacomp.password | BIACOMP schema owner's password. |
| fsm.db.seed.url | URL used to connect to the BIACOMP schema. (The FSM user is the BIACOMP user.) The format is host:port/ServiceName. For example: host:port/orcl.mycompany. |
| db.sys.user | Database system user name. |
| db.sys.password | Database system user password.
Note: If this parameter is not passed in the command line, then the tool will request the password at runtime. |
java -jar biappsrepositoryutil.jar upgradeFSM bi.oracle.home=scratch/MiddleWareHome/Oracle_BI1/ work.dir=scratch/workfolder biacomp.user=BIAPPS_BIACOMP biacomp.password=password db.conn.sid.url=<host>:<database port>:<SID> fsm.db.seed.url=<host>:<database port>/<ServiceName> db.sys.user=sysuser db.sys.password=password
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 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 <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.
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 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 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 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.
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.
Note that 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.
ODI Studio is a desktop client that enables you to design and manage the ODI Repository. ODI Studio is typically installed on developer machines. The supported operating systems for ODI Studio are Windows 32-bit and 64-bit and Linux 32-bit.
To install ODI Studio, perform the following procedures:
You install ODI Studio using the Oracle Data Integrator 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 Oracle Data Integrator 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 ODI Studio patch is available in PATCH_ROOT_DIR\odi\generic or PATCH_ROOT_DIR/odi/generic. For an explanation of the PATCH_ROOT_DIR, see Section 3.3.4, "Applying Platform Patches."
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: If you installed ODI Studio on the BI Domain host machine, you do not have to apply the patch.
During installation of Oracle BI Applications, source files are installed in the BI_Oracle_Home/biapps/etl directory. These files are used during the ETL process and will be configured by functional developers. You must copy these files to a location that ODI Agent deployed in WebLogic Server can access but that is outside of the Oracle Home directory; otherwise, when the Oracle BI Applications environment is upgraded or patched, these files will be overwritten.
To copy source files:
Navigate to the BI_Oracle_Home/biapps/etl directory.
Copy all files under the BI_Oracle_Home/biapps/etl directory into a location that ODI Agent deployed in WebLogic Server can access but is outside of the Oracle Home directory.
Note the following 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.
The next step in the installation and setup process is to perform the system setup tasks in Chapter 4, "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.