3 Installing and Setting Up Oracle BI Applications
Topics:
Hardware Requirements
Regarding the hardware and performance requirements for Oracle BI Applications, refer to the Oracle BI Applications certification matrix on Oracle Technology Network.
For additional information about hardware requirements for Oracle Analytics Server and Oracle Data Integrator (ODI), see Oracle Fusion Middleware Supported System Configurations on Oracle Technology Network.
Installation Prerequisites for Oracle BI Applications
You must install certain components before you can install Oracle BI Applications.
Prior to installing an Oracle database, refer to the Oracle BI Applications certification matrix on Oracle Technology Network for the certified Oracle databases. While installing the database, ensure that you don’t select a container database.
If you're planning to use Oracle Autonomous Transaction Processing (ATP), then you must also configure Oracle Autonomous Datawarehouse (ADW). On ATP, create the BI platform schema, ODI schema, and BI_COMP schema. Create rest of the schemas such as DW and SDS on ADW.
Install and Configure Oracle BI Applications
Use these instructions to install and configure Oracle BI Applications.
- Oracle Fusion Middleware which includes the Oracle WebLogic Server 12c (12.2.1.4)
- Oracle Analytics Server
Refer to the Oracle BI Applications certification matrix on Oracle Technology Network for the supported version of Oracle Analytics Server.
- Oracle Data Integrator (12.2.1.4)
You must perform the following procedures in the order they are listed:
- Install JDK
- Install Oracle Fusion Middleware Infrastructure (WebLogic Server)
- Install Oracle Analytics Server
- Create Schemas Using RCU
- Install Oracle Data Integrator
- Install Oracle BI Applications
- Create Schemas for Oracle BI Applications
- Apply Mandatory Patches
- Configure Oracle Analytics Server
- Edit Your Input File
- Configure Oracle BI Applications
- Load Translation Data
- Configure Oracle Data Integrator Studio
- Use a RAC Database
- Use an External LDAP
- Configure Oracle BI Applications for High Availability
- Configure SSL
Install JDK
To install the recommended JDK version, refer to the Oracle BI Applications certification matrix on Oracle Technology Network.
Note:
Ensure that you remove any other version of Java present in the system before installing JDK on your local machine and not in any NFS path.You may set JAVA_HOME
as the environment variable for further use. You may set JAVA_HOME as the environment variable for further use. Add $JAVA_HOME/bin
in your PATH variable. You may use /usr/sbin/alternatives --config java
to configure the recommended version as the default version of Java.
Install Oracle Fusion Middleware Infrastructure (WebLogic Server)
Oracle BI Applications requires Oracle Fusion Middleware Infrastructure 12.2.1.4.
- Download the Oracle Fusion Middleware Infrastructure Installer. See the Download page for Oracle Business Intelligence Applications.
- For Linux systems, review the general UNIX operating system requirements, and verify the locale and open file limit settings as described in Oracle® Fusion Middleware System Requirements and Specifications 12c (12.2.1.4.0). Oracle recommends a high value for ulimit. A low value of open file limit and the number of processes limit can cause installation failure. As the root user, do the following:
- Copy the Oracle Fusion Middleware Infrastructure Installer to the middleware host and unzip it.
- Set
JAVA_HOME
, and then start the Oracle WebLogic Server installation by using this command:$JAVA_HOME/bin/java -jar fmw_12.2.1.4.0_infrastructure.jar
- Select the inventory location, such as
/scratch/biapps/installation/InvWLS
and clickOK
. - Select the Oracle Home location, such as
/scratch/biapps/Oracle/Middleware/ORACLE_HOME
and click Next. - Click Next until you complete the install steps.
Create Schemas Using RCU
You must run the repository creation utility (RCU) to create schemas for Oracle Analytics Server.
Note:
Ensure that the password is the same for all Oracle Fusion Middleware schemas such as the MDS, BIPLATFORM, STB, OPSS, IAU, and WLS schemas. Not all special characters are allowed in the schema password. It can contain #, underscore but shouldn't contain $, parenthesis ( ), or @. A database service might enforce special characters, so use only underscore. The password you provide in RCU can't be changed by SQL commands.To create the BI schema on Oracle ATP, see Create BI Schema on Oracle ATP Database.
To create the BI schema, perform the following steps.
Install Oracle Data Integrator
Install Oracle Data Integrator using the Oracle Data Integrator installer.
Create Schemas for Oracle BI Applications
You must create and load the Oracle BI Applications schemas in the database using the Repository Creation Utility (RCU).
- Make a directory in the database host and provide read/write permission to all files in that directory. For example:
- mkdir /dbhost/dumps
- chmod 777 /dbhost/dumps
- Copy three dump files from the middleware host to the database host folder
/dbhost/dumps
. These dumps are available underORACLE_HOME/oracle_common/rcu/integration/biapps/schema
.
To create the BIApps schema on Oracle Autonomous Transaction Processing (ATP), see Create BIApps Schema on Oracle Autonomous Transaction Processing (ATP).
Create BIApps Schema on Oracle Autonomous Transaction Processing (ATP)
Run the repository creation utility (RCU) to create the BIApps schema on Oracle Autonomous Transaction Processing (ATP).
Note:
Oracle Autonomous Transaction Processing (ATP) database provides various services consumer groups. Oracle recommends to always use “TP” ATP service name while running RCU and configuring Oracle BI Applications.- Upload the obia.dmp, obia_comp.dmp, obia_odi.dmp, and obia_partitions.dmp files to Object Storage.
- Create the ATP credentials.
- Copy the dump files from Object Storage to the data pump directory.
For example,
BEGIN DBMS_CLOUD.GET_OBJECT( credential_name => '<ATP CREDENTIAL NAME>', object_uri => '<bucket URL>/Dump_file_Name', directory_name => 'data_pump_dir'); END;
- Run the following SQL query on Oracle Autonomous Transaction Processing (ATP) or Oracle Autonomous Database (ADB), and note down the location name of the dump file in ATP.
SELECT * FROM dba_directories WHERE directory_name='DATA_PUMP_DIR';
Note the value of dpdump in your environment.
Description of the illustration schema_adw_dumpfilelocation.png - When you run RCU in silent mode, note that when you enter the connection string in the response file, there's a space after
description=
in the wallet's tnsnames.ora file:biaoas2023_tp = (description= (retry_count=20)
Remove the space after
description=
so that connection string is:biaoas2023_tp = (description=(retry_count=20)
Set the BIAPPS Schema User Password as Unlimited
Oracle recommends that you ensure that the database password for all BIAPPS
schema users doesn’t expire. Resetting the database password might lead to failure in the BIAPPS
components operations.
Upgrade OPatch
Upgrade Opatch to the latest release on the ORACLE_HOME location where you installed Oracle Fusion Middleware Infrastructure.
Apply Mandatory Patches
After the software-only install, you must apply patches on the ORACLE_HOME
location where you installed Oracle Fusion Middleware Infrastructure 12.2.1.4.
Configure Oracle Analytics Server
Use Configuration Assistant to configure Oracle Analytics Server.
Edit Your Input File
The configuration script expects details about your environment. You must copy the ORACLE_HOME/bi/biapps/scripts/input.txt
file to a location and edit the input.txt
file to update the properties for your environment.
input.txt
file, ensure that you've decided your configuration plan, such as:
- If you're going to use RAC database, then see Use a RAC Database.
- If you're using embedded LDAP or planning to use Oracle Internet Directory LDAP. See Use an External LDAP.
Based on your choices, you need to modify the properties in your input.txt
file. Ensure that you don't delete or comment out any of the properties.
Note:
Ensure that you edit theinput.txt
file only in Linux using the Visual Editor (Vi Editor). Don't edit the file in the Windows machine and copy to Linux. Editing in Windows causes the configuration to fail. For Windows, use the file path separator as \\ or / . For example, biprov.oracle_home.dir=c:\\Oracle\\Middleware\\Oracle_Home or biprov.oracle_home.dir=c:/Oracle/Middleware/Oracle_Home. All the paths in input.txt should use the same format.
Property | Property Value |
---|---|
|
Provide the JDK directory, under which the bin folder must exist. |
|
Provide the absolute path where you'd install Oracle BI Applications, such as /u01/installation/Middleware/Oracle_home . The configuration process creates a directory and you must ensure that the users have write permission on that path.
|
|
Provide the schema prefix used during the Oracle Analytics Server RCU run. |
|
Provide the schema prefix for the ODI schema created using the RCU. |
|
Provide the administrator username for Oracle Weblogic Server. Choose any name without special characters. |
|
Provide the password of the Oracle Weblogic Server administrator. |
|
Provide port for ODI managed server or retain the default value. |
|
Keep blank (SSL not supported in Oracle BI Applications). |
|
Keep as false (SSL not supported in Oracle BI Applications). |
|
Provide username of Oracle BI Applications administrator. This user can access Oracle WebLogic Server, Oracle Analytics Server, Oracle Business Intelligence Applications Configuration Manager, and Oracle Data Integrator. |
|
Provide the password for the Oracle BI Applications administrator. Don't include special characters. |
|
Provide the cluster name for the ODI managed server or retain the default value. |
|
Provide the value as false (even for scan URL). |
|
Provide the connection string in host:port/service format for the data warehouse schema. |
|
Provide the data warehouse schema username. |
|
Provide the password for the data warehouse schema user. |
|
Don’t change the value. |
|
Keep blank. |
|
Provide a password for the LDAP administrator and note the value for future reference. The password of the embedded LDAP administrator is reset to this value. |
|
Keep blank. |
|
Keep blank. |
|
Keep blank. |
|
Ensure that the value is set to False to disable the autonomous data warehouse configuration. In case you're planning to configure the autonomous data warehouse, refer to Configure Oracle BI Applications with Oracle Autonomous Data Warehouse. |
There are other schemas, like BIACOMP, ODI_REPOSITORY, MDS, and STB. You need to fill similar sections for those schemas. After that, depending on which source you want to use, enable the appropriate SDS schemas. For example, if you're using Oracle Fusion source, then fill in the [FUSION11_SDS_DATABASE] section. For Oracle E Business Suite source, fill in [EBS122_SDS_DATABASE].
Note:
For Oracle Autonomous Transaction Processing (ATP), add the database connection string in the following format:ODI_REPOSITORY_DATABASE_CONNECTION_STRING=<ATP service name from tnsnames.ora>?TNS_ADMIN=<ATP wallet extract folder>
For example in Windows, ODI_REPOSITORY_DATABASE_CONNECTION_STRING=biaatp_tp?TNS_ADMIN=C:\\biapps\\instantclient_19_14\\network\\admin\\atp_wallet
For example in Linux, ODI_REPOSITORY_DATABASE_CONNECTION_STRING=biaatp_tp?TNS_ADMIN=/scratch/instantclient_19_14/network/admin/atp_wallet
Use the same format for all the applicable schemas that you've created on ATP.
Configure Oracle BI Applications
Use Java archive obia.config.jar to configure Oracle BI Applications.
Note:
If you want to configure Oracle BI Applications on Oracle Autonomous Data Warehouse, see Configure Oracle BI Applications with Oracle Autonomous Data Warehouse.Note:
In Windows, to run the Java archive (obia.config.jar), launch the command prompt in Administrators Mode.Configure Oracle BI Applications with Oracle Autonomous Data Warehouse
Connect Oracle BI Applications to Oracle Autonomous Data Warehouse to access the data warehouse schemas.
My Oracle Support provides detailed instructions for obtaining the latest patches, applying the patches, and provisioning. See My Oracle Support note Doc ID 2808444.1 for instructions and details of the patch set.
Update $ORACLE_HOME/bi/biapps/scripts/input.txt, along with the [GENERIC] and [DATABASE] sections, and update these parameters:
biprov.adw.env=<If new configuration run with ADW, then TRUE Else FALSE>
biprov.wallet.location=<Unzipped ADW wallet location>
adw.wallet.trustStorePassword=<ADW wallet password>
instant.client.location=<Unzipped Instant client path>adw.service.name=<Service name, Refer to tnsnames.ora file in your wallet. Ex: biapps_low>
adw.admin.user=<ADW admin user Ex: ADMIN>
adw.admin.pwd=<ADW admin password>
adw.default.cred.user=<Credential Name. Default text: BIAPPS_ADW_AUTO_CREDENTIAL.>adw.default.user.name=<OCI User name. Open the Profile menu () from OCI console and fetch User name.
Ex:oracle/first.lastname@oracle.com>
adw.auth.token=<Generate an Authentication Token. This token is required for importing
dump from Object storage>
REMAP_SCHEMA=<BIAPPS_DW:ADW schema name for DW Ex: BIAPPS_DW:ADW_DW>
DUMP_FILE=<default_credential:<Pre-authenticated Request URL of the
Bucket>/obia.dmp Ex: default_credential:https://Server
Name/p/77Eo_TV2rtL/n/biappsdev/b/BIAPPSD_BUCKET/o/obia.dmp>
Make sure that the ADW wallet extracted folder contains all the files such as cwallet.sso, tnsnames.ora, and sqlnet.ora.
In the [DATABASE] section, update the database connection string for all schemas in the following format:
DW_DATABASE_CONNECTION_STRING=<ADW service name from tnsnames.ora>? TNS_ADMIN=<ADW wallet extract folder>
Note:
Autonomous data warehouse provides various services consumer groups. Oracle recommends to always use “LOW” ADW service name while configuring Oracle BI Applications.For example, DW_DATABASE_CONNECTION_STRING=biappsd3_low?TNS_ADMIN=/scratch/wallet
- biappsd3_low is the ADW service name from the tnsnames.ora file. Check your service name.
- /scratch/wallet is the folder where you have extracted the ADW wallet zip and it contains files such as cwallet.sso, tnsnames.ora, and sqlnet.ora .
Also, update the required SDS schema details.
Use the following commands to run the configuration:
Note:
In Windows, to run the Java archive (obia.config.jar), launch the command prompt in Administrators Mode.cd $ORACLE_HOME/bi/biapps/scripts/
java -jar obia.config.jar input.txt
Load Translation Data
Load translation data into the BIACOMP
schema of Oracle BI Applications.
Note:
You must complete all the steps listed in Installing and Setting Up Oracle BI Applications without any errors prior to loading the translation data.If you want to load translation data on ATP, see Load Translation Data on Oracle Autonomous Transaction Processing (ATP).
Ensure that the:- Database is up and running.
BIACOMP
schema is available.- The
C_RPD_MSGS
,C_RPD_MSGS_REL
, andC_RPD_MSGS_TL
tables exist in theBIACOMP
schema.
Load Translation Data on Oracle Autonomous Transaction Processing (ATP)
Load translation data into the BIACOMP schema of Oracle BI Applications.
Configure Oracle Data Integrator Studio
Use Oracle Data Integrator Studio (ODI Studio) to manage and configure Oracle Data Integrator (ODI).
ODI Studio is installed as part of the standalone or enterprise option under the specified ORACLE_HOME
directory. ODI Studio provides four graphical navigators for managing ODI artifacts: Designer, Operator, Topology, and Security. ODI Studio can also directly execute jobs on demand, and you can use it for development and testing.
Configuring Authentication
Use these instructions to configure authentication.
- If you're using embedded LDAP, then go to
DOMAIN_HOME/odi-client-config/embedded
directory. In case you're using Oracle Internet Directory as LDAP, then browse theDOMAIN_HOME/odi-client-config/external
directory. - Copy
cwallet.sso
andjps-config.jse.xml
toORACLE_HOME/odi/studio/bin
. - Copy
DOMAIN_HOME/config/fmwconfig/System-jazn-data.xml
to theORACLE_HOME/odi/studio/bin
directory.
Setting the JPS Config File Location
Use these instructions to set the location of the JPS Config
file.
Starting Oracle Data Integrator Studio
Use these instructions to start ODI Studio.
- Navigate to the
ORACLE_HOME/odi/studio
directory. - Enter the command for Linux
./odi.sh -clean -initialize
.
Use a RAC Database
If you're planning to use a real application cluster (RAC) database to configure Oracle BI Applications, then follow these additional steps.
Note:
Oracle recommends that you use the SCAN URL for the RAC database. You can directly use the SCAN URL in the configuration.Use an External LDAP
Instead of using Oracle Weblogic’s embedded LDAP, you can use Oracle Internet Directory as an external LDAP for users.
Note:
Oracle BI Applications only supports Oracle Internet Directory.If you want to configure Oracle BI Applications with Oracle Internet Directory, first configure Oracle BI Applications to use embedded LDAP, and then see the instructions in My Oracle Support Doc ID 2818769.1 to switch from embedded LDAP to Oracle Internet Directory.
Configure Oracle BI Applications for High Availability
You can configure Oracle BI Applications in high availability mode or horizontal scale-out mode. Two physical hosts support in domain and both installs have Oracle WebLogic Server running. The Oracle HTTP server is the load balancer.
- Install and configure Oracle BI Applications on Node1. Ensure all components are up and running.
- Install Oracle BI Applications on Node2. Perform software only installation including prerequisite patches and don't run config.
- Configure high availability for Oracle Analytics Server.
- Configure high availability for Oracle Data Integrator.
- Configure DSN for high availability on Windows.
- Perform post-configure steps for high availability.
- Configue Oracle HTTP Server (OHS) for high availability.
Note:
You can perform steps 3 and 4 either manually or by using automated scripts.
Machine or host name longer than 32 characters isn't supported. Specify a shorter name.
- Set up shared files and directories. For data sharing, you need a common mount point where both host can read/write (this isn't ORACLE_HOME). See Set Up Shared Files and Directories.
- Node1 and Node2 hosts are reachable from each other. You must be able to ping the hosts from one another.
- The
/etc/hosts
file on each host must have entry of the other host. - The IP address obtained with a ping command and the IP entry in the
/etc/hosts
file must be the same.
- The
- In Node1, install JDK, Oracle Fusion Middleware Infrastructure (Oracle WebLogic Server), Oracle Analytics Server, Oracle Data Integrator, and Oracle BI Applications and complete the configuration. Node1 must be working as single node installation.
- The same path is used for the Oracle_Home on both nodes. For example, if ORACLE_HOME in node1 is
/u01/middleware
then node2 should also have ORACLE_HOME in/u01/middleware
. But ORACLE_HOME mustn't be the common drive between these hosts. See Add New Computers. - In Node2, complete a software-only installation of JDK, Oracle Fusion Middleware Infrastructure, Oracle Analytics Server, Oracle Data Integrator and Oracle BI Applications. Don't run configuration step in Node2. Node2 has the same path of ORACLE_HOME from root as Node1 has.
Configure High Availability with Automated Scripts
Use these steps to configure high availability with automated scripts.
Configuring High Availability with Manual Steps
Use these steps to configure high availability manually.
- Install and configure Oracle BI Applications on Node1. Ensure all components are up and running.
- Install Oracle BI Applications on Node2. Don't run config. You must perform the software-only install.
For Oracle Analytics Server high availability steps, see About Scaling Oracle Analytics Server and for Oracle Data Integrator high availability steps, see the Oracle Support document "How To Create And Deploy a High Availability ODI 12c Java EE Agent to a Cluster on WebLogic Server" (Doc ID 1676176.1).
Configuring Oracle HTTP Server for High Availability
Use these steps to configure Oracle HTTP server (OHS) for high availability.