3 Installing and Setting Up Oracle BI Applications

Follow these instructions for installing and setting up Oracle Business Intelligence Applications (Oracle BI Applications).

Topics:

Hardware Requirements

Here is some information regarding the hardware requirements for Oracle BI Applications.

  • Middleware host of 32 GB RAM and 64 bit Oracle Linux 7 X86.
  • Database host of 32 GB RAM and Oracle Linux 7 X86.
  • 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.
  • At least 5 GB free space for /tmp.

For additional information about hardware requirements for Oracle BI Enterprise Edition (Oracle BI EE) 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.

Install Oracle Database 19c in the database host. Oracle Database requires a compatible version of Java. Ensure that you install the correct version of Java as required by the database. In the database host, install Oracle Database 19.3 by following the database installation instructions. Ensure that you don’t select a container database.

Installing and Configuring Oracle BI Applications

Use these instructions to install and configure Oracle BI Applications.

Oracle BI Applications requires:
  • Oracle Fusion Middleware installer which includes the WebLogic Server 12c (12.2.1.3)
  • Oracle Business Intelligence Enterprise Edition ( 12.2.1.4)
  • Oracle Data Integrator ( 12.2.1.3)

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

Installing JDK

Install the recommended JDK version 1.8.

Refer to the JDK installation document for detailed instructions

Note:

Ensure that you remove any other version of Java present in the system before installing version 1.8 and install 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 version 1.8 as the default version of Java.

Installing Oracle Fusion Middleware (WebLogic Server)

Oracle BI Applications requires Oracle Fusion Middleware version 12.2.1.3.

  1. Download the Fusion Middleware Infrastructure Installer from the Oracle website.
  2. Copy the Fusion Middleware Infrastructure Installer to the middleware host and unzip it.
  3. With JAVA_HOME set, start the Oracle WebLogic Server install by this command: $JAVA_HOME/bin/java -jar fmw_12.2.1.3.0_infrastructure.jar
  4. Select the inventory location, such as /u01/biapps/installation/InvWLS and click OK.
  5. Select the Oracle Home location, such as /u01/biapps/Middleware/Oracle_home and click Next.

    Note:

    Don't select /home.
  6. Click Next until you complete the install steps.

Installing Oracle Business Intelligence

Install Oracle Business Intelligence version 12.2.1.4.

  1. Download the Linux X64 version of Oracle Business Intelligence from the Oracle website.
  2. Follow the Oracle Business Intelligence Enterprise Edition installation document. See Installing and Configuring Oracle Business Intelligence.

    Note:

    Ensure that you provide the same oracle_home location as mentioned while installing Oracle Fusion Middleware, like /u01/biapps/Middleware/Oracle_home.
  3. Select BI Platforms with or without samples.
  4. Don't run config.sh for the Oracle Business Intelligence Enterprise Edition configuration.

Creating Schemas Using Business Intelligence RCU

You must run the Business Intelligence repository creation utility (RCU) to create schemas for Oracle Business Intelligence Enterprise Edition.

The RCU is available with the Oracle Fusion Middleware distribution files.
  1. Start RCU using the command: $ ./ORACLE_HOME/oracle_common/bin/rcu.
    You see a sequence of dialogs. Follow the instructions provided on each of the dialogs to create the required schema.
  2. On the Welcome page, click Next.
  3. Under Create Repository, select System Load and Product Load, and then click Next.
  4. In the Database Connection Details dialog, enter your environment and system administrator details, and then click Next.

    Caution:

    Don't use database SID while creating schemas; you must use only service name. Also, don't provide SID even in the connection string.
    Description of GUID-9CE4949D-088E-4864-B4DB-169639F99F36-default.gif follows
    Description of the illustration GUID-9CE4949D-088E-4864-B4DB-169639F99F36-default.gif
  5. Wait for the RCU to complete checking the prerequisites and then click OK.
  6. In the Select Components dialog, provide a schema prefix (for example, DEV or PROD or any string without special characters), select the components that you want to install, and then click Next.

    Note:

    When you select Oracle Business Intelligence Platform, the RCU auto-selects other components like Common Infrastructure Services, Oracle Platform Security Services, Audit services, and Metadata Services.

    Don't select the ODI_REPO schema. This is created by the Oracle BI Applications RCU and is suffixed as BIA_ODI_REPO.

    Description of GUID-4EF73637-16F8-482A-BEB1-783B2121BD03-default.gif follows
    Description of the illustration GUID-4EF73637-16F8-482A-BEB1-783B2121BD03-default.gif
  7. Wait for the RCU to complete checking the prerequisites and then click OK.
  8. In the Schema Passwords dialog, specify the passwords for the schema users, and then click Next.

    Note:

    Not all special characters are allowed in the schema password. It can contain #, underscore but shouldn't contain $, parenthesis ( ), or @.
    Description of GUID-56D72507-8E65-4B8B-BBFA-AA9F73B3F376-default.gif follows
    Description of the illustration GUID-56D72507-8E65-4B8B-BBFA-AA9F73B3F376-default.gif
  9. In the Map Tablespaces dialog, view the default and temporary tablespaces for the components that you selected. If required, create or modify tablespaces using the Manage Tablespaces button. Click Next.
  10. In the Confirmation dialog, click OK to create any tablespaces that don't exist in the selected schemas.
  11. In the Creating Tablespaces dialog, wait for the RCU to complete creating the tablespaces, and then click OK.
  12. In the Summary dialog, click Create to generate BITECH schema components.

    When the schemas are created with no errors, you see the Completion Summary dialog.

  13. In the Completion Summary dialog, click Close.

    To create Oracle Business Intelligence schemas using the Oracle Business Intelligence RCU with a RAC database, see Creating BI Schemas Using RCU with a RAC Database.

Installing Oracle Data Integrator

You install Oracle Data Integrator using the Oracle Data Integrator installer.

  1. Download Oracle Data Integrator 12.2.1.3 from the Oracle website.
  2. Follow the installation document to complete the installation using the same oracle_home location as mentioned while installing Oracle Fusion Middleware, like /u01/biapps/Middleware/Oracle_home.
  3. Ensure that you select Enterprise Install.

Installing Oracle BI Applications

Install Oracle BI Applications using the installer.

  1. Download the installer (jar file) from the Oracle website.
    You see two jar files. Ensure your keep both the jar files in the same directory.
  2. Prepare a text file (known as response file) using the name biapps.resp with the contents seen in the sample response file:
    [ENGINE]
    #DO NOT CHANGE THIS.
    Response File Version=1.0.0.0.0
    [GENERIC]
    #provide oracle home location, where the product would be installed.
    ORACLE_HOME=/u01/biapps/Middleware/Oracle_Home
  3. Execute the installer using the command such as $ java -jar obia.12c.distribution-11.1.1.10.3-generic.jar -silent -responseFile /tmp/biapps.resp.

    Note:

    Ensure that the responseFile parameter value is an absolute file path and not a relative path. Use a command for the jar file which doesn’t have 2 in the filename of the responseFile.

Creating 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 under ORACLE_HOME/oracle_common/rcu/integration/biapps/schema.
  1. After installing Oracle Fusion Middleware Infrastructure, start the RCU from the ORACLE_HOME/oracle_common/bin directory using these commands:
    ORACLE_HOME/oracle_common/bin/rcu -compInfoXMLLocation
          ORACLE_HOME/oracle_common/rcu/config/ComponentInfo_biapps.xml -storageXMLLocation
          ORACLE_HOME/oracle_common/rcu/config/Storage_biapps.xml
    You see a sequence of dialogs. Follow the instructions provided on each dialog to create the required schema.
  2. On the Welcome page, click Next.
  3. Under Create Repository, select System Load and Product Load, and then click Next.
  4. In the Database Connection Details dialog, enter your database details and click Next. If your database is RAC, then enter the SCAN url.

    Caution:

    Don't use database SID while creating schemas; you must use only service name. Also, don't provide SID even in the connection string.
    Description of GUID-5ADA5BCE-180D-4E6C-AB7A-5EBE0D945D81-default.gif follows
    Description of the illustration GUID-5ADA5BCE-180D-4E6C-AB7A-5EBE0D945D81-default.gif

    Note:

    If you see a warning message that the database version is more recent, then click Ignore.
  5. Wait for the RCU to complete checking the prerequisites and then click OK.
  6. In the Select Components dialog, provide a schema prefix (for example, DEV or any string without special characters), select the components that you want to install, and then click Next.
  7. Wait for the RCU to complete checking the prerequisites and then click OK.

    If you see a warning message stating that the version of the database is more recent then the clock, then ignore the message.

    Description of GUID-7C9B3BF3-4C44-49F4-9F05-26ED48FC8541-default.gif follows
    Description of the illustration GUID-7C9B3BF3-4C44-49F4-9F05-26ED48FC8541-default.gif
  8. In the Schema Passwords dialog, specify the passwords for the schema users, and then click Next.

    Note:

    Not all special characters are allowed in the schema password. It can contain number sign # or underscore _, but shouldn't contain dollar sign $, parenthesis ( ) , or at sign @.
    Description of GUID-385ABE94-748E-462E-8D21-0813413BFBA3-default.gif follows
    Description of the illustration GUID-385ABE94-748E-462E-8D21-0813413BFBA3-default.gif
  9. In the Custom Variables dialog, enter the database dump location (/dbhost/dumps) for Oracle Data Integrator Master and Work repository and Oracle BI Applications components, and then click Next.

    For example, copy the dump location from the machine where you installed Oracle Fusion Middleware to the database host, if the dump location is different. If all the dump files are in the same location, then specify the same dump location three times. You need to provide only the /dump location; the file name isn't required.

    Description of GUID-E3A17949-8152-4307-88D7-10DF33156353-default.gif follows
    Description of the illustration GUID-E3A17949-8152-4307-88D7-10DF33156353-default.gif
  10. In the Map Tablespaces dialog, view the default and temporary tablespaces for the components that you had selected. If required, create or modify tablespaces using the Manage Tablespaces button after referring to the schema guidelines. Click Next.

    Note:

    Oracle BI Applications has one schema to support all higher releases of Oracle Fusion Applications. For example, the FA_11 schema supports Oracle Fusion Applications releases 11 and higher.
    Description of GUID-B14F540C-BC8D-4142-9954-3A1FC8474C95-default.gif follows
    Description of the illustration GUID-B14F540C-BC8D-4142-9954-3A1FC8474C95-default.gif
  11. In the Creating Tablespaces dialog that is automatically launched to create any tablespaces that don't exist in the selected schemas, click OK.
  12. In the Summary dialog, click Create to complete the operation.

    When the schemas are created with no errors, you see the Completion Summary dialog.

  13. In the Completion Summary dialog, click Close.

Setting the BIAPPS Schema User Password as Unlimited

Ensure that the database password for all BIAPPS schema users doesn’t expire. Resetting the database password may lead to failure in the BIAPPS components operations.

  1. Sign in to the database as sys user.
  2. Create a profile with password-related attributes set to unlimited using the following sql script:
    CREATE PROFILE BIAPPS
    LIMIT PASSWORD_LIFE_TIME UNLIMITED
    PASSWORD_GRACE_TIME UNLIMITED
    PASSWORD_REUSE_TIME UNLIMITED
    PASSWORD_REUSE_MAX UNLIMITED
    FAILED_LOGIN_ATTEMPTS UNLIMITED
    PASSWORD_VERIFY_FUNCTION NULL
    PASSWORD_LOCK_TIME UNLIMITED;
  3. Associate all the BIAPPS users with this profile by executing the following sql script for all the BIAPPS users:
    ALTER USER <BIAPPS_SCHEMA_USER> PROFILE BIAPPS;For example, ALTER USER BIAPPS_DW PROFILE BIAPPS;

Applying Middleware Patches

After the software-only install, you must apply patches on ORACLE HOME.

All patches are available in the same place from where you downloaded the Oracle BI Applications software.
  1. Copy the patches to a location, unzip them, and apply them using the instructions in the patch README file.
  2. Set ORACLE HOME as the parent of product home. For example, setenv ORACLE_HOME /u01/biapps/Middleware/Oracle_HOME.

    Note:

    Don't set it as =/u01/biapps/Middleware/Oracle_home/odi.
    Some patches require the latest OPatch software, hence you must upgrade OPatch to release 13.9.4.2. To upgrade OPatch, locate the opatch_generic.jar file in 13.9.4.2/opatch/opatch_generic.jar and apply it using the sample script:
    java -jar <path_to_opatch_generic.jar>/opatch_generic.jar -silent oracle_home=<OARCLE HOME PATH>
  3. Execute $ORACLE_HOME/OPatch/opatch apply <patch dir>.
  4. Run the $ORACLE_HOME/OPatch/opatch apply <patch dir>. command for all individual patches under the bi, odi, and adf directories.
  5. Go through each patch log and ensure that you see the “OPatch Succeeded” message.
  6. Execute $ORACLE_HOME/OPatch/opatch lsinventory, take output in a file, and verify that each patch number appears in that file as applied.

Editing Your Input File

The configuration script expects details about your environment. You must make a copy of 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.

Prior to editing your input.txt file, ensure that you've decided your configuration plan, such as:

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 the input.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.
Property Property Value
biprov.jdk_home.dir
Provide the JDK 1.8 directory, under which the bin folder must exist.
biprov.oracle_home.dir
Provide the absolute path where you'd install Oracle BI Applications, like /u01/installation/Middleware/Oracle_home. The configuration process creates a directory and you must ensure that the users have write permission on that path.
biprov.bi_domain.dir
Provide the absolute path where domain directory is to be created, like /u01/installation/Middleware/user_projects/domains/biadomain. The configuration process creates a directory and you must ensure that the users have write permission on that path.
biprov.bi_domain.name
Don't change the value, retain the value as biadomain.
biprov.db.jdbc.url
JDBC url of where the Oracle BI schemas are created.
biprov.db.schema.prefix
Schema prefix used during The Oracle BI RCU run.
biprov.db.schema.pwd
Password of the schema user.
biprov.odi.db.schema.prefix
Schema prefix for the ODI schema created using the RCU.
biprov.fa.admin.user
The administrator username for Oracle Weblogic Server. Choose any name without special characters.
biprov.fa.admin.pwd
Password of the Oracle Weblogic Server administrator.
biprov.wls.port
The administrator server port for Oracle Weblogic Server. Assign a unique value or retain the default value as 7001.
biprov.wls.managed.port
Oracle BI managed server port. Assign a unique value or retain the default value.
biprov.machine.name
Provide the name of the machine where installation is done.
biprov.node_manager.port
Provide the node manager port or retain the default value.
biprov.obiccs.port
Provide the cluster controller port or retain the default value.
biprov.obiccs.port.monitor
Provide a port or retain the default value.
biprov.obisch.port
Provide the scheduler service port or retain the default value.
biprov.obisch.port.script
Provide a port or retain the default value.
biprov.obisch.port.monitor
Provide a port or retain the default value.
biprov.obips.port
Provide the presentation service port or retain the default value.
biprov.obijh.port
Provide the java host port or retain the default value.
biprov.obis.port
Provide the Oracle BI server port or retain the default value.
biprov.obis.port.monitor
Provide a port or retain the default value.
biprov.bi.service.instance
Provide name for service instance or retain the default value.
biprov.odi.port
Provide port for ODI managed server or retain the default value.
biprov.odi.ssl.port
Keep blank (SSL not supported in Oracle BI Applications).
biprov.odi.is.ssl.configured
Keep as false (SSL not supported in Oracle BI Applications).
biprov.temp.dir
Provide a directory for temporary use or retain the default value of /tmp.
biprov.bi.cluster.name
Oracle BI cluser name or keep the default.
biprov.odi.user.name
Provide BIAppsAdminUser as the name. This user can access Oracle WebLogic Server, Oracle BI Enterprise Edition, Oracle Business Intelligence Applications Configuration Manager, and Oracle Data Integrator.
biprov.odi.console.user.pwd
Password for the BIAppsAdminUser.
biprov.odi.cluster.name
Provide the cluster name for the ODI managed server or retain the default value.
biprov.isRac
Provide the value as false (even for scan url).
[DW_DATABASE]
DW_DATABASE_CONNECTION_STRING
For the data warehouse schema, provide the connection string in the form host:port/service.
DW_DATABASE_SCHEMA_USER_NAME
The data warehouse schema username.
DW_DATABASE_SCHEMA_PASSWORD
Password for the data warehouse schema user.
DW_DATABASE_TYPE
Don’t change.
There are other schemas, like BIACOMP, ODI_REPOSITORY, MDS, and STB. You need to fill similar sections for those schemas. After that, depending upon 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].
Property Value for Embedded LDAP Value for External LDAP
biprov.ldap.type
Embedded External
biprov.ldap.external.user
Blank for embedded LDAP For OID LDAP, provide the username of the OID administrator, like orcladmin.
biprov.ldap.pwd
During config, reset the password of the embedded LDAP administrator to this value Provide the password for the external LDAP administrator whose username you provided. Ensure that the password has upper and lower case characters; for example, abcDEfg.
biprov.ldap.external.url
Blank The URL of external LDAP, like ldap://host.us.example.com:1234.
biprov.ldap.external.user_prefix
Blank cn=Users, dc=us, dc=oracle, dc=com.
biprov.ldap.external.group_prefix
Blank cn=Groups, dc=us, dc=oracle, dc=com.

Configuring Oracle BI Applications

After the input.txt file is ready, go to $ORACLE_HOME/bi/biapps/scripts directory and run the following command:

java –jar obia.config.jar <path of edited input.txt>/input.txt

Loading 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.
Ensure that the:
  • Database is up and running.
  • BIACOMP schema is available.
  • The C_RPD_MSGS, C_RPD_MSGS_REL, and C_RPD_MSGS_TL tables exist in the BIACOMP schema.
  1. In your middleware host, navigate to <ORACLE_HOME>/bi/nls.
  2. Copy the file rpd_translations.zip to the database host.
  3. In your database host, complete the following:
    1. Unzip the translations file rpd_translations.zip in your database host and navigate to the rpd_translations directory.
    2. Run the script:
      • For Linux/Unix:
        loadOtbiSeeddataSqlldr.sh thrice to load translations data into three tables using the following command:
        sh loadOtbiSeeddataSqlldr.sh <DB user name> <DB password> <db Connect String> <Control File> <Log
                Directory> <CSV File Location> <BI OH Path>
        For example:
        sh loadOtbiSeeddataSqlldr.sh BIAPPS_BIACOMP welcome1 dbhost.mycomany.com:1616/DBServiceName
                importcrpdmsgs.ctl /u01/logs c_rpd_msgs_delim.csv
              /scratch/19c/db/DB_Home
        sh loadOtbiSeeddataSqlldr.sh BIAPPS_BIACOMP welcome1 dbhost.mycomany.com:1616/DBServiceName
                rpd_translations/importcrpdmsgsrel.ctl /u01/logs c_rpd_msgs_rel_delim.csv
                /scratch/19c/db/DB_Home
         sh loadOtbiSeeddataSqlldr.sh BIAPPS_BIACOMP welcome1 dbhost.mycomany.com:1616/DBServiceName
                importcrpdmsgstl.ctl /u01/logs c_rpd_msgs_tl_delim.csv
                /scratch/19c/db/DB_Home
      • For Windows:
        <DB_OH>/bin/sqlldr <BIACOMP USER>/<BIACOMP password>@<dbtns> data=<path of file>\c_rpd_msgs_delim.csv control=<path of ctl>\importcrpdmsgs.ctl log=c:\temp\crpdmsgs.log
        <DB_OH>/bin/sqlldr <BIACOMP USER>/<BIACOMP password>@<dbtns> data=<path of file>\c_rpd_msgs_rel_delim.csv control=<path of ctl>\importcrpdmsgsrel.ctl log=c:\temp\crpdmsgsrel.log
        <DB_OH>/bin/sqlldr <BIACOMP USER>/<BIACOMP password>@<dbtns> data=<path of file>\c_rpd_msgs_tl_delim.csv control=<path of ctl>\importcrpdmsgstl.ctl log=c:\temp\crpdmsgstl.log
  4. After successfully running the script loadOtbiSeeddataSqlldr.sh, verify that the C_RPD_MSGS, C_RPD_MSGS_REL, and C_RPD_MSGS_TL tables have the translations data.

Configuring Oracle Data Integrator Studio

Oracle Data Integrator Studio (ODI Studio) is the interface that you use 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.

  1. 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 the DOMAIN_HOME/odi-client-config/external directory.
  2. Copy cwallet.sso and jps-config.jse.xml to ORACLE_HOME/odi/studio/bin.
  3. Copy DOMAIN_HOME/config/fmwconfig/System-jazn-data.xml to the ORACLE_HOME/odi/studio/bin directory.

Setting the JPS Config File Location

Use these instructions to set the location of the JPS Config file.

  1. Navigate to the ORACLE_HOME/odi/studio/bin directory.
  2. Open the odi.conf file in an editor.
  3. At the bottom of the file, add AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml.
  4. Save the file.

Starting Oracle Data Integrator Studio

Use these instructions to start ODI Studio.

  1. Navigate to the ORACLE_HOME/odi/studio directory.
  2. Enter the command for Linux ./odi.sh -clean -initialize.

Connecting to the Master Repository

Use these instructions to create an ODI Repository Login and connect to the master repository using the newly created login in Oracle Data Integrator.

  1. Sign in to ODI Studio, from the menu, select File, then select New.
  2. In the New Gallery dialog, select ODI under Categories in the left pane, select Create a New ODI Repository Login under Items in the right pane, and then click OK.
  3. In the Repository Connection Information dialog, provide the following details:
    1. In the Oracle Data Integrator Connection section, enter:
      • Login Name: Specify a custom login name.
      • User: Specify SUPERVISOR (all capital letters).
      • Password: Specify the supervisor password that you provided in the RCU Custom Variable dialog.
    2. In the Database Connection (Master Repository) section, enter:
      • User: Specify the schema user name for the Master repository. This must be prefix_BIA_ODIREPO as specified in the Select Components dialog in RCU.
      • Password: Specify the schema password for the Master repository. This must be the password that you specified in the Schema Passwords dialog in RCU.
      • Driver List: Select the appropriate driver for your database from the list of values.
      • URL: Specify the connection URL. Click on the magnifying glass icon for more information about the connection details for your driver.
    3. In the Work Repository section, select Master Repository Only.
    Repository Connection Information dialog
  4. Click Test to test the connection, and fix any errors. After the test is successful, click OK to create the connection.
  5. In the New Wallet Password dialog, specify and confirm a new wallet password.
    After you have successfully created a new login, you are returned to ODI Studio.
  6. In ODI Studio, under the Designer tab, select Connect to Repository and, when prompted, provide your new wallet password.
    After you provide your wallet password, you see the Oracle Data Integrator Login dialog.
  7. Provide the following information to log in:
    1. Select the name of the new login that you created from the list of values.
    2. Specify SUPERVISOR as the user name.
    3. Provide the password for the Supervisor user.
    After successfully signing into ODI, you see the ready-to-use ODI repository artifacts.Image displays the ready-to-use repository artifacts in ODI Studio.

Using 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.

The configuration flow is largely the same whether you're using a non-RAC database or a RAC database. The instructions to install Fusion Middleware infrastructure, Oracle Business Intelligence, creating Business Intelligence schemas, installing Oracle Data Integrator, and installing Oracle BI Applications are the same whether you're using a non-RAC database or a RAC database. For creating schemas using the Business Intelligence RCU when you've a RAC database, see Creating BI Schemas Using RCU with a RAC Database.

Note:

Oracle recommends that you use the SCAN URL for the RAC database. You can directly use the SCAN URL in the configuration.
  1. While editing the input file:
    1. Keep the value of biprov.isRAC parameter as False.
    2. Provide the SCAN URL for all the database schemas in the input file.
    3. Keep DATABASE_TYPE as Oracle Database.
  2. Run config to complete the process.

Using an External LDAP

If you choose to use an external LDAP for users, instead of using Oracle Weblogic’s embedded LDAP, then follow these steps.

Note:

Oracle BI Applications only supports Oracle Internet Directory.
Ensure that Oracle Internet Directory is installed and you're aware of the administrator username and password for Oracle Internet Directory. The administrator's password must include upper and lower case characters; for example, abcDEfg.
  1. In Oracle Directory Services Manager, click Data Browser.
  2. In the Data Tree, click dc=com, dc=oracle, dc=us, and then cn=users.
  3. Right-click cn=users and select Create.
  4. Enter the applicable details and click Apply.
    Oracle Idirectory Services Manager
  5. In the input.txt file, specify the details about the external Oracle Internet Directory and run config.

Configuring 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.

To configure high availability, you must review the install configuration step of the single node installation and complete a few additional steps. You may either choose to set up high availability manually or use the automated scripts. The high-level steps to set up high availability are:
  1. Install and configure Oracle BI Applications on Node1. Ensure all components are up and running.
  2. Install Oracle BI Applications on Node2. Perform software only installation including prerequisite patches and don't run config.
  3. Configure high availability for Oracle Business Intelligence.
  4. Configure high availability for Oracle Data Integrator.
  5. Configure DSN for high availability on Windows.
  6. Perform post-configure steps for high availability.
  7. Configue Oracle HTTP Server (OHS) for high availability.

Note:

You can perform steps 3 and 4 either manually or by using automated scripts.
Ensure the following prerequisites:
  1. The shared path is available for storage. For data sharing, you need a common mount point where both host can read/write (this isn't ORACLE_HOME).
  2. Node1 and Node2 hosts are reachable from each other. You must be able to ping the hosts from one another.
    1. The /etc/hosts file on each host must have entry of the other host.
    2. The IP address obtained with a ping command and the IP entry in the /etc/hosts file must be the same.
  3. In Node1, install JDK, Oracle Fusion Middleware Infrastructure (Oracle WebLogic Server), Oracle Business Intelligence Suite Enterprise Edition, Oracle Data Integrator, and Oracle BI Applications and complete the configuration. Node1 must be working as single node installation.
  4. The same path is used for the Oracle_Home on both nodes. For example, if ORACLE_HOME in node1 is /u01/middlware then node2 should also have ORACLE_HOME in /u01/middleware. But ORACLE_HOME mustn't be the common drive between these hosts.
  5. In Node2, complete a software-only installation of JDK, Oracle Fusion Middleware Infrastructure, Oracle Business Intelligence Suite Enterprise Edition, 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.

Configuring High Availability with Automated Scripts

Use these steps to configure high availability with automated scripts.

  1. Update your input.txt file available at <Oracle_Home>/bi/biapps/scripts/input.txt with these sample parameters:
    • biprov.ha.shared.dir=<HA_SHARED_PATH>
    • biprov.ha.node2.hostname=<NODE2_HOST_NAME>. For example, biprov.ha.shared.dir=/shared_mount/nfs_shared and biprov.ha.node2.hostname=node2.mycompany.com
  2. Execute the following script on node1 to clone machine and bi server and update global cache settings:
    <Oracle_Home>/bi/biapps/scripts/configure_HA_primary.sh <INPUT_TXT_FILE_PATH>.
  3. Execute the following script on node2 to create cloned biadomain and start nodemanager:
    <Oracle_Home>/bi/biapps/scripts/configure_HA_secondary.sh <INPUT_TXT_FILE_PATH>.
  4. Execute the following script on node1, to create ODI_server2 server and start all components:
    <Oracle_Home>/bi/biapps/scripts/configure_HA_primary_ODI.sh <INPUT_TXT_FILE_PATH>.
  5. Verify that all components are up and running. For example, $DOMAIN_HOME/bitools/bin/status.sh.

Configuring High Availability with Manual Steps

Use these steps to configure high availability manually.

Before you proceed, ensure that you've completed these steps:
  1. Install and configure Oracle BI Applications on Node1. Ensure all components are up and running.
  2. Install Oracle BI Applications on Node2. Don't run config. You must perform the software-only install.

For Oracle Business Intelligence high availability steps, see the Oracle Support document "OBIEE 12c: Quick Reference How To Cluster | Scale-out OBIEE 12c Including Examples" (Doc ID 2101898.1) 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).

  1. On Node 1, complete the following steps:

    Note:

    Be sure install and config is completed in node1, and node1 is up and running.
    1. Export the $ORACLE_HOME and $DOMAIN_HOME environment variables. For example, export ORACLE_HOME=/u01/Middleware/Oracle_Home and export DOMAIN_HOME=/u01/user_projects/domains/biadomain.
    2. Open a shell session in node 1 and stop all components using the stop.sh command.
    3. Navigate to the $DOMAIN_HOME/config/fmwconfig/bienv/core directory.
    4. Make a backup of the bi-environment.xml file and edit it to change the Singleton Data Directory (SDD). Ensure that the new SDD points to a shared directory that can be accessed by both nodes of the cluster. Your mount point or share must persist through reboots;. For example, /shared_mount/nfs_shared/bidata.
    5. Copy the bidata directory to the new SDD location. For example,
      cd <DOMAIN_HOME> 
      cp -R bidata /shared_mount/nfs_shared/bidata
      .
    6. Start all components on node 1 using the start.sh command.
    7. Set up the global cache using the sample command Create directory /shared_mount/nfs_shared/cache.
      1. Sign in to Oracle Enterprise Manager Fusion Middleware Control.
      2. Click Target Navigation, expand Business Intelligence, select biinstance, click the Configuration tab, and then the Performance subtab.
      3. Click Lock & Edit available under Lock icon and provide the global cache path and size.
      4. Click Apply button and then Activate Changes available under the Lock icon.
    8. Start all components to make sure that the changes are done correctly using the start.sh command.
    9. Stop all components on the node1 using the stop.sh command.
    10. Create BI machine and BI server for node2 using the clone command: $DOMAIN_HOME/bitools/bin/clone_bi_machine.sh -m <NODE2_HOST_NAME> <NODE2_HOST_NAME> <HA_SHARED_PATH>/node2_clone.jar
  2. On Node 2, complete the following steps:

    Note:

    Oracle BI Applications is installed on Node2 but config isn't yet executed.
    1. Create the domain directory, as it exists in the node. Use the same directory and naming structure such as mkdir -p /u01/user_projects/domains/biadomain. Ensure that the DOMAIN_HOME in both nodes specifies the same path name.
    2. Export the $ORACLE_HOME and $DOMAIN_HOME environment variables.
    3. Unpack the domain by using the template jar that you created using the $ORACLE_HOME/oracle_common/common/bin/unpack.sh -template=<HA_SHARED_PATH>/node2_clone.jar -domain=$DOMAIN_HOME command.
    4. Start the Node Manager using the $DOMAIN_HOME/bin/startNodeManager.sh command.
  3. On Node 1 complete the following steps:
    1. Start the components AdminServer, bi_server1, ODI_server1, obis1, obips1, obiccs1, obijh1, obisch1, and bi_server2 using the $DOMAIN_HOME/bitools/bin/start.sh -i "AdminServer,bi_server1,ODI_server1,obis1,obips1,obiccs1,obijh1,obisch1,bi_server2" command.
    2. Start the components obis2, obips2, obiccs2, obijh2, and obisch2 using the $DOMAIN_HOME/bitools/bin/start.sh -i "obis2,obips2,obiccs2,obijh2,obisch2" command.

      If you're configuring high availability in Windows, then you must create and configure DSN. Refer to the DSN Creation section to complete those steps and then continue to configuring ODI for high availability.

Configuring High Availability for ODI

Use these steps to configure high availability for ODI.

  1. On Node 1 complete the following steps:
    1. Create ODI_server2 and assign it to the machine and cluster using these wlst commands:
      $ORACLE_HOME/oracle_common/common/bin/wlst.sh
      
      connect('<WLS_USER>', '<WLS_USER_PASSWORD>', '<WLS_ADMIN_SERVER_HOST>:<WLS_ADMIN_SERVER_PORT>')
      edit()
      startEdit()
      cd('/')
      cmo.createServer("ODI_server2")
      cd('/Servers/' + "ODI_server2")
      cmo.setListenAddress(<node2_host_name>)
      cmo.setListenPort(<node2_odi_port>)
      activate()
      
      Bring down all components by executing stop.sh and then connect to wlst in offline mode using:
      $ORACLE_HOME/oracle_common/common/bin/wlst.sh
      readDomain(<DOMAIN_HOME>)
      assign('Server', 'ODI_server2', 'Machine', <node2_host_name>)
      assign('Server', 'ODI_server2', 'Cluster', <odi_cluster_name>)
      cd('/Server/ODI_server2')
      set('ListenPort', int("<node2_odi_port>"))
      updateDomain()
      closeDomain()
      .
    2. Start all components using the $DOMAIN_HOME/bitools/bin/start.sh command.
    3. Verify that all components are up and running using the $DOMAIN_HOME/bitools/bin/status.sh command.

Configuring Oracle HTTP Server for High Availability

Use these steps to configure Oracle HTTP server (OHS) for high availability.

Install and configure the latest available supported version of Oracle HTTP Server on a separate machine. After installing and configuring OHS, configure the Oracle BI Applications URL in OHS.
  1. Stop OHS using the command:
    cd /u02/installation/OHS/Oracle_Home/user_projects/domains/ohs_domain/bin ./stopComponent.sh ohs1
  2. Add URL mappings for odiconsole, oraclediagent, analytics and biacm using this command:
    cd /u02/installation/OHS/Oracle_Home/user_projects/domains/ohs_domain/config/fmwconfig/components/OHS/instances/ohs1
    Add this content to the mod-wl_ohs.conf file:
    #odi agent
    
    <Location /oraclediagent>
    WebLogicCluster <node1_host>:<odi1_port>,<node2_host>:<odi2_port>
    SetHandler weblogic-handler
    </Location>
    
    # ODI Console
    <Location /odiconsole>
    WebLogicCluster <node1_host>:<odi1_port>,<node2_host>:<odi2_port>
    SetHandler weblogic-handler
    </Location>
    
    # analytics
    <Location /analytics>
    WebLogicCluster <node1_host>:<bi_server1_port>,<node2_host>:<bi_server2_port>
    SetHandler weblogic-handler
    </Location>
    
    # biacm
    <Location /biacm>
    WebLogicCluster <node1_host>:<bi_server1_port>,<node2_host>:<bi_server2_port>
    SetHandler weblogic-handler
    </Location>
    
  3. Start OHS using the command:
    cd /u02/installation/OHS/Oracle_Home/user_projects/domains/ohs_domain/bin ./startComponent.sh ohs1
  4. Verify that all the URLs configured above are working fine. For example:
    • http://ohshost:7777/oraclediagent/
    • http://ohshost:7777/odiconsole
    • http://ohshost:7777/analytics
    • http://ohshost:7777/biacm
  5. Bring down one set of Oracle Business Intelligence and Oracle Data Integrator servers and check if the URLs are redirecting to the Oracle Business Intelligence and Oracle Data Integrator instances that are running.

Configure DSN for High Availability on Windows

For cluster DSN configuration, you must create the "AnalyticsWeb_Cluster" DSN under System DSN on Node 1 and Node 2.

  1. In the Name field, enter AnalyticsWeb_Cluster, and select Oracle BI Server as driver for Node 1 and Oracle BI Server-Oracle-Home for Node 2.
  2. After AnalyticsWeb_Cluster is created successfully, update instanceconfig.xml on both Node 1 and Node 2 using these instructions:
    1. Edit DOMAIN_HOME/config/fmwconfig/biconfig/OBIPS/instanceconfig.xml.
    2. Replace <DSN>AnalyticsWeb</DSN> with <DSN>AnalyticsWeb_cluster</DSN>.
    3. Save the file.
  3. On Node 2, create the additional data sources opss_datasource and biplatform_datasource using these instructions:
    1. Navigate to Control Panel, click All Control Panel Items, click Administrative Tools, and then double-click Data Sources (ODBC) (64-bit). You see the ODBC Data Source Administrator (64-bit) dialog. ODBC Data Source Administrator (64-bit) dialog
    2. Click the System DSN tab and then click Add.
    3. In the Create New Data Source dialog, from the list of the available drivers, select Oracle 8.0 Oracle Wire Protocol, and click Finish.Create New Data Source dialog
    You see the ODBC Oracle Wire Protocol Setup dialog.

    add image

    ODBC Oracle Wire Protocol Setup dialog
  4. Enter the data source name as opss_datasource and enter the description as Oracle 8.0 Oracle Wire Protocol. Similarly create
  5. Under Standard Connection, enter your host, port number, and service name, and then click OK.
  6. Follow step 4 and 5 to create data source biplatform_datasource.
  7. Create odbc.ini using the sample and copy to DOMAIN_HOME/config/fmwconfig/bienv/core/.

    Sample odbc.ini file

    [ODBC]
    Trace=0
    TraceFile=C:/Middleware/user_projects/domains/biadomain/odbctrace.out
    TraceDll=C:/Middleware/Oracle_Home/oracle_common/../bi/modules/oracle.bi.datadirect.odbc/8.0.2/lib/ARtrc28.so
    InstallDir=C:/Middleware/Oracle_Home/oracle_common/../bi/modules/oracle.bi.datadirect.odbc/8.0.2
    UseCursorLib=0
    IANAAppCodePage=4
    
    [ODBC Data Sources]
    AnalyticsWeb_Cluster=Oracle BI Server
    opss_datasource=Oracle 8.0 Oracle Wire Protocol
    biplatform_datasource=Oracle 8.0 Oracle Wire Protocol
    [AnalyticsWeb_Cluster]
    Description=Oracle BI Server
    UID=
    PWD=
    Catalog=
    SelectPhysical=
    Repository=
    ForwardOnlyCursor=
    CentrallyManaged=Yes
    SSL=No
    Driver=C:/Middleware/Oracle_Home/oracle_common/../bi/bifoundation/server/bin/libnqsodbc64.so
    IsClusteredDSN=Yes
    Regional=No
    
    [opss_datasource]
    HostName=<your database host name>
    EncryptionLevel=1
    PortNumber=<your port number>
    Driver=C:/Middleware/Oracle_Home/oracle_common/../bi/modules/oracle.bi.datadirect.odbc/8.0.2/lib/ARora28.so
    EnableNcharSupport=1
    DataIntegrityLevel=1
    ServiceName=<your service name>
    Description=Oracle 8.0 Oracle Wire Protocol
    
    [biplatform_datasource]
    HostName=<your database host name>
    EncryptionLevel=1
    PortNumber=<your port number>
    Driver=C:/Middleware/Oracle_Home/oracle_common/../bi/modules/oracle.bi.datadirect.odbc/8.0.2/lib/ARora28.so
    EnableNcharSupport=1
    DataIntegrityLevel=1
    ServiceName=<your service name>
    Description=Oracle 8.0 Oracle Wire Protocol
  8. In the odbc.ini file, update the database host name, port number, and service name and paths (trace and driver) as per your environment.

Performing Post-Configure Steps for High Availability

Perform these steps after configuring Oracle BI Applications for high availability.

  1. Log in to the Admin console in node1 and perform the following steps:
    1. Navigate to Environment and then Servers.
    2. Click Admin Server and then click the General tab.
    3. Click Lock & Edit.
    4. Update Listen Address field with the admin server host.
    5. If default port is other than the default listen port, then update the Listen Port field with the appropriate port number.
    6. Click Save and then click Activate Change.
  2. Open Oracle Data Integrator (ODI) Studio or ODI Console. Go to Topology, click Physical Architecture, click Agents, and then click OracleDIAgent.
  3. In Agent, update the Oracle HTTP server (OHS) hostname and port.
  4. Create a network file system that is available in both hosts, such as filer2. Ensure that path /filer2/HAShared is available in both hosts.
  5. Give write permission to the location to all, for example, chmod -R 777 /filer2/HAShared.
  6. In node2, go to <ORACLE_HOME>/bi/biapps/etl and unzip biapps_etl.zip in the same location.
  7. Edit the following parameters in the BIAPPSConfig.properties file available at <DOMAIN_HOME>/config/fmwconfig/biinstances/coreapplication/BIAPPSConfig.properties in both nodes:
    • ODI_SERVER_PORT=<OHS_PORT>
    • ODI_SERVER_HOST=<OHS_HOST>
  8. Complete the functional setup and register the source in BIACM.
  9. After registering the source in BIACM, note the data source number of that source (DSN). In the following steps, examples are given for DSN 215 and SHARED_LOCATION refers to /filer2/HAShared.
  10. Once the source is registered, compare the folders in node2 with those of node1 and create the missing folders in node2. These folders may be missing in node2:
    1. <DOMAIN_HOME>/biapps/logs/etl
    2. <DOMAIN_HOME>/biapps/logs/healthcheck/log
    3. <DOMAIN_HOME>/biapps/logs/process
    4. <DOMAIN_HOME>/biapps/shared/healthcheck/report
  11. Update the location of the source files for the physical schema of BIAPPS_DW_FILE data server in ODI Studio:
    1. Log into ODI Studio. Navigate to Topology Manager, click Technology, and then click File.
    2. Expand the BIAPPS_DW_FILE data server and double-click to open the physical schema.
    3. In the Definition pane, for the Directory (Schema) and Directory (Work Schema) properties, specify the shared location where you copied the source files. Update the shared location in ODI Studio for the following by clicking Topology, then Technologies, and then File for:
      • BIAPPS_DW_FILE
      • BIAPPS_DW_LOG_FILE
      • BIAPPS_DW_SHARED_FILE
      • EXT_STORAGE_FUSION_11_0__215
      • BIAPPS_DW_FILE - Copy all the files/folders from ORACLE_HOME/bi/biapps/etl/data_files/src_files/BIA_11 to SHARED_LOCATION/BIA_11.
      • BIAPPS_DW_LOG_FILE - Copy all the files/folders from DOMAIN_HOME/biapps/logs to SHARED_LOCATION/logs.
      • BIAPPS_DW_SHARED_FILE - Copy all the files/folders from DOMAIN_HOME/biapps/shared to SHARED_LOCATION/shared.
      • EXT_STORAGE_FUSION_11_0_215 - Source registration may happen in any of the physical nodes. Hence, you must look into DOMAIN_HOME of node1 and node2 to locate the folders mentioned in the following instructions:

        Copy all the files/folders from DOMAIN_HOME/biapps/shared/215/ReplStg to SHARED_LOCATION/shared/215/ReplStg.

        Copy all the files/folders from DOMAIN_HOME/biapps/shared/215/download to SHARED_LOCATION/shared/215/download.

        Copy all the files/folders from DOMAIN_HOME/biapps/shared/215/srcFiles to SHARED_LOCATION/shared/215/srcFiles.

        Copy all the files/folders from DOMAIN_HOME/biapps/shared/215/upload to SHARED_LOCATION/shared/215/upload.

Creating BI Schemas Using RCU with a RAC Database

Follow these steps for a successful configuration while creating Oracle Business Intelligence schemas with the Oracle Business Intelligence RCU with a RAC database:

  1. Install Oracle Fusion Middleware Infrastructure and Oracle Business Intelligence as described in Installing Oracle Fusion Middleware (WebLogic Server) and Installing Oracle Business Intelligence.
    Don't run Oracle Data Integrator and Oracle BI Applications yet.
  2. Launch the RCU from $ORACLE_HOME/oracle_common/bin/rcu and select the System Load and Product Load option.
  3. Provide the VIP or SCAN host of the RAC database with sys login details and click Next. Ensure that you select the Connection Parameters option and don't select the Connection String option.
  4. Provide the prefix for the schemas, select all components, and then click Next.
  5. View all the schemas to be created and click Next.
  6. Verify the schema names, ensure that the schema password contains no special characters including the underscore, and click Next until completion.
    You see all the schemas with data created in the database.
  7. Verify that the <Schema_Prefix>_STB.COMPONENT_SCHEMA_INFO table is populated with applicable details.
  8. Run the installers for Oracle Data Integrator and Oracle BI Applications and create the BIAPPS schema using the RCU.

Uninstalling Oracle BI Applications

Use the following steps to uninstall Oracle BI Applications.

  1. Stop all running Oracle WebLogic services using this command: $DOMAIN_HOME/bitools/bin/stop.sh.
  2. Drop all schemas by following these steps:
    1. Run the RCU by entering ./ORACLE_HOME/oracle_common/bin/rcu.
    2. Select Drop Schema for each schema to drop and exit.
    3. Invoke RCU again using the command:
      ORACLE_HOME/oracle_common/bin/rcu  –compInfoXMLLocation
            ORACLE_HOME/oracle_common/rcu/config/ComponentInfo_biapps.xml  –storageXMLLocation
            ORACLE_HOME/oracle_common/rcu/config/Storage_biapps.xml
    4. Select Drop Schema and select all the BIAPPS schemas to drop.

    Note:

    Ensure that you drop the schemas using the RCU; don't use any other SQL command.
  3. Manually remove your Domain home directory.
    For example, if your Domain home directory is /u01/biapps/Middleware/user_projects, then use the command
    cd /u01/biapps/Middleware
    rm -rf user_projects
    .
  4. Manually remove your Application home directory.
    If there is another user_project directory within Oracle_home like /u01/biapps/Middleware/Oracle_Home/user_projects, then delete that using the following command:
    cd /u01/biapps/Middleware/Oracle_Home
    rm -rf user_projects
    .
  5. Remove the domain_registry.xml file in your Oracle home using the command cd /scratch/user/installation/Middleware/Oracle_Home rm -rf domain_registry.xml.
  6. Restart your system.
  7. If you're trying to reconfigure, then keep ORACLE_HOME intact, create all schemas again, and then run the configure step.
  8. If you're planning to complete the uninstallation process, then you need to remove the Oracle home directory and inventory folder that you provided while installing Oracle BI Applications.