Installing and Setting Up Oracle BI Applications

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

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 BI Applications requires:

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

To install the recommended JDK version, refer to the Oracle BI Applications certification matrix on Oracle Technology Network.

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 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 from the Download page for Oracle Fusion Middleware Software.
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:
1. Edit the /etc/security/limits.conf file and save the following values.
```
* hard nofile 999999
* soft nofile 999999
* soft nproc 131072
* hard nproc 131072
* soft core unlimited
* hard core unlimited
```
  The nofile values represent the open file limit; the nproc values represent the number of processes limit.
2. Edit the /etc/sysctl.conf file and add following line to change the number of file descriptors.
  fs.file-max = 26815744
3. Run the following command to apply the view the settings.
  sysctl -p
4. Run the following command to verify if the value of fs.file-max is set to 26815744.
  cat /proc/sys/fs/file-max
5. Run the following command to view the PAM limits.
  sudo vi /etc/pam.d/common-session
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 click OK.
Select the Oracle Home location, such as /scratch/biapps/Oracle/Middleware/ORACLE_HOME and click Next.
Click Next until you complete the install steps.

Install Oracle Analytics Server

Install Oracle Analytics Server.

Download Oracle Analytics Server from the Download page for Oracle Analytics Server.

Refer to the Oracle BI Applications certification matrix in the in the Oracle Fusion Middleware Supported System Configurations page for the supported version of Oracle Analytics Server.
Copy the Oracle Analytics Server Installer zip file to the middleware host, and unzip the file.
Install Oracle Analytics Server. See instructions in Installing the Oracle Analytics Server Software.
Make sure you've set JAVA_HOME, and then run the following command to start Oracle WebLogic Server:

For Linux: $JAVA_HOME/bin/java -jar Oracle_Analytics_Server_Linux_version-no.jar

For Windows: $JAVA_HOME/bin/java -jar Oracle_Analytics_Server_Windows_version-no.jar

Where Oracle_Analytics_Server_Linux_version-no is the name of the Oracle Analytics Server jar file downloaded from edelivery.
Select the same ORACLE_HOME location as provided for Oracle Fusion Middleware Infrastructure, for example, /scratch/biapps/Oracle/Middleware/ORACLE_HOME.
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.

The RCU is available with the Oracle Fusion Middleware distribution files.

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.

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.
On the Welcome page, click Next.
Under Create Repository, select System Load and Product Load, and then click Next.

Description of the illustration 103-schemas-rcu-step3.gif
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 the illustration 103-schemas-rcu-step4.gif
Wait for the RCU to complete checking the prerequisites and then click OK.

Description of the illustration 103-schemas-biapps-step5.gif
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 the illustration 103_schemas-rcu-step6.gif
Wait for the RCU to complete checking the prerequisites and then click OK.

Description of the illustration 103-schemas-rcu-step7.gif
In the Schema Passwords dialog, specify the passwords for the schema users, and then click Next.

Description of the illustration 103-schemas-rcu-step8.gif
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.

Description of the illustration 103-schemas-rcu-step10.gif
In the Confirmation dialog, click OK to create any tablespaces that don't exist in the selected schemas.

Description of the illustration 103-schemas-rcu-step11.gif
In the Creating Tablespaces dialog, wait for the RCU to complete creating the tablespaces, and then click OK.

Description of the illustration 103-schemas-rcu-step12.gif
In the Summary dialog, click Create to generate BITECH schema components.

Description of the illustration 103-schemas-rcu-step13.gif

When the schemas are created with no errors, you see the Completion Summary dialog.
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.

Install Oracle Data Integrator

Install Oracle Data Integrator using the Oracle Data Integrator installer.

Download Oracle Data Integrator 12.2.1.4 from the Oracle Data Integrator Downloads page.
Copy the Oracle Data Integrator 12.2.1.4 zip file to the middleware host, and unzip the file.
Make sure you have set JAVA_HOME, and then run the following command to start Oracle WebLogic Server:
$JAVA_HOME/bin/java -jar fmw_12.2.1.4.0_odi.jar
Select the same ORACLE_HOME location as provided for Oracle Fusion Middleware Infrastructure, for example, /scratch/biapps/Oracle/Middleware/ORACLE_HOME.
Make sure you select Enterprise Install.
Click Next until you complete the install steps.

Install Oracle BI Applications

Install Oracle BI Applications 11.1.1.10.3 PS4 using the installer.

Download the installer (jar file) from the Oracle Business Intelligence Applications Downloads page.
You see two jar files. Ensure your keep both the jar files in the same directory.

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=/scratch/biapps/Oracle/Middleware/ORACLE_HOME

Run the installer:
$ java -jar obia.12c.distribution-11.1.1.10.PS4-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.

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 under ORACLE_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).

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.
On the Welcome page, click Next.
Under Create Repository, select System Load and Product Load, and then click Next.

Description of the illustration 103-schemas-biapps-step3.gif
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 the illustration 103-schemas-biapps-step4.gif

Note:
If you see a warning message that the database version is more recent, then click Ignore.
Wait for the RCU to complete checking the prerequisites and then click OK.

Description of the illustration 103-schemas-biapps-step5.gif
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.

Description of the illustration 103-schemas-biapps-step6.gif
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 the illustration 103-schemas-biapps-step7.gif
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 the illustration 103-schemas-biapps-step8.gif
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 the illustration 103-schemas-biapps-step9.gif
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 the illustration 103_pb1_create_schemas_biapps_step10.gif
In the Creating Tablespaces dialog that is automatically launched to create any tablespaces that don't exist in the selected schemas, click OK.

Description of the illustration 103-schemas-biapps-step11.gif
In the Summary dialog, click Create to complete the operation.

Description of the illustration 103_pb1_create_schemas_biapps_step12.gif

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

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.

Before you run the RCU, perform these tasks:

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)

Perform these steps to create the BIApps schema on Oracle Autonomous Transaction Processing (ATP).

Set the TNS_ADMIN environment variable to map it to the directory where the tnsnames.ora file is available.
For example, in Linux,
```
export TNS_ADMIN=/scratch/wallet
```
Where /scratch/wallet is the ATP wallet extract folder.

Start RCU using the command:

ORACLE_HOME/oracle_common/bin/rcu -compInfoXMLLocation /scratch/user/installation/Middleware/Oracle_Home/oracle_common/rcu/config/ComponentInfo_biapps_adw.xml -storageXMLLocation /scratch/user/installation/Middleware/Oracle_Home/oracle_common/rcu/config/Storage_biapps.xml

Note:

The name of the component info XML file must be ComponentInfo_biapps_adw.xml.

On the Welcome page, click Next.
Under Create Repository, select System Load and Product Load, and then click Next.
Open the /scratch/wallet/tnsnames.ora file, get the connection string description for your desired service name, and enter the value for Connect String.
Enter Username and Password, and then click Next.
Ignore the Connection String Format alert, and then click OK.
Enter the schema prefix name, select only ODI and BIACOMP as components, and then click Next.
It might take some time to navigate to the next page.
Description of the illustration schema_adw_select_components.png
Enter the schema passwords, and then click Next.
In the Custom Variables page, enter value as "dpdump" or the value of dpdump in your environment.
In the Map Tablespaces page, click Next.
It might take some time to navigate to the next page.
In the Summary page, click Create.

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.

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;

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;

Upgrade OPatch

Upgrade Opatch to the latest release on the ORACLE_HOME location where you installed Oracle Fusion Middleware Infrastructure.

Download the latest patches from the same location where you downloaded the Oracle BI Applications software, save the latest patches to a location, and unzip them.
Set ORACLE_HOME as the parent of product home.
For example, setenv ORACLE_HOME /scratch/biapps/Middleware/ORACLE_HOME PATH
Locate the opatch_generic.jar file in the folder where you have unzipped the latest patch, and apply it.

For example, java -jar path_to_opatch_generic.jar/opatch_generic.jar -silent oracle_home=ORACLE_HOME PATH

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.

All patches are available in the same place from where you downloaded the Oracle BI Applications software.

Copy the patches to a location, unzip them, and apply them using the instructions in the patch README file.
Set ORACLE_HOME as the parent of product home.

For example, setenv ORACLE_HOME/scratch/biapps/Middleware/ORACLE_HOME

Don't set it as /scratch/biapps/Middleware/Oracle_home/odi.
Run the $ORACLE_HOME/OPatch/opatch apply <patch dir> command for all individual mandatory patches available in all the sub directories.
Verify each patch log and ensure that you see the “OPatch Succeeded” message.
Run the $ORACLE_HOME/OPatch/opatch lsinventory command, take output in a file, and verify that each patch number appears in that file as applied.

Configure Oracle Analytics Server

Use Configuration Assistant to configure Oracle Analytics Server.

Oracle recommends to follow About Oracle Analytics Server Installation.

In Windows, make sure that the machine name doesn't include an underscore character (_). If you edit the machine name to remove the underscore character, reboot the machine before you run Configuration Assistant.

Read and follow the step-by-step instructions in Configure Oracle Analytics Server Domain Using Configuration Assistant.
Note:
In Windows, when you configure the Oracle Analytics Server domain, provide the ATP connect string in the format below. Use "\\" as the path separater.
```
CONNECT_STRING=midtier_biplatform?TNS_ADMIN=<ATP_WALLET_HOME>
```
For example, CONNECT_STRING=biaoas2023_tp?TNS_ADMIN=C:\\biapps\\instantclient_19_14\\network\\admin\\atp_wallet
Verify the WebLogic servers.
Run these commands, and make sure that all the components are in RUNNING state.
1. cd DOMAIN_HOME/bitools/bin
2. ./status.sh

Run the datamodel command and verify that Oracle Analytics Server works.

After you configure Oracle Analytics Server, run the datamodel.sh (linux) or datamodel.cmd (Windows) command.

Change the directory to DOMAN_HOME/bitools/bin.

Run the following command:

./datamodel.sh listconnectionpool -SI <Service Instance> -U <WebLogic User> -S <Host Name> -N <BI Server Port> -V true

For example: ./datamodel.sh listconnectionpool -SI < biainstance > -U <weblogic> -S <localhost> -N <8003> -V true

Output example:

Post listconnectionpool REST with url: http://localhost:8003/bi-lcm/v1/si/biainstance/rpd/listconnectionpool
{
    "Title":"List Connection Pools",
    "Conn-Pool-Info":[
        {
            "uid":"c0000000-c929-1508-ac27-0ae4a1690000",
            "connPool":"DUMMY_CP",
            "parentName":"\"DUMMY\"",
            "user":"admin1",
            "password":"706F87F7847C7A8EFED6E3F0AB261ADE 7C2E35213306F12832914CBE7A9DD95561D771DED06484112B1FC6F27B6D0D58",
            "dataSource":"testDb",
            "appServerName":"AppServer1",
            "externalizedConnection":""
        }
    ],
    "Variables-In-Conn-Pool":[
    ]
}

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.

Prior to editing your 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 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. 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
`biprov.jdk_home.dir`	Provide the JDK directory, under which the bin folder must exist.
`biprov.oracle_home.dir`	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.
`biprov.db.schema.prefix`	Provide the schema prefix used during the Oracle Analytics Server RCU run.
`biprov.odi.db.schema.prefix`	Provide the schema prefix for the ODI schema created using the RCU.
`biprov.fa.admin.user`	Provide the administrator username for Oracle Weblogic Server. Choose any name without special characters.
`biprov.fa.admin.pwd`	Provide the password of the Oracle Weblogic Server administrator.
`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.odi.user.name`	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.
`biprov.odi.console.user.pwd`	Provide the password for the Oracle BI Applications administrator. Don't include special characters.
`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`	Provide the connection string in host:port/service format for the data warehouse schema.
`DW_DATABASE_SCHEMA_USER_NAME`	Provide the data warehouse schema username.
`DW_DATABASE_SCHEMA_PASSWORD`	Provide the password for the data warehouse schema user.
`DW_DATABASE_TYPE`	Don’t change the value.
`biprov.ldap.external.user`	Keep blank.
`biprov.ldap.pwd`	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.
`biprov.ldap.external.url`	Keep blank.
`biprov.ldap.external.user_prefix`	Keep blank.
`biprov.ldap.external.group_prefix`	Keep blank.
`biprov.adw.env`	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.

Edit the input.txt file.
After the input.txt file is ready, in the $ORACLE_HOME/bi/biapps/scripts directory, run the following command:
```
java –jar obia.config.jar <path of edited input.txt>/input.txt
```

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, and C_RPD_MSGS_TL tables exist in the BIACOMP schema.

In your middleware host, navigate to <ORACLE_HOME>/bi/nls.
Copy the file rpd_translations.zip to the database host.

In your database host, complete the following:

Unzip the translations file rpd_translations.zip in your database host and navigate to the rpd_translations directory.

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> <Oracle DB Home Path>

For example:

sh loadOtbiSeeddataSqlldr.sh BIAPPS_BIACOMP welcome1 dbhost.mycomany.com:1616/DBServiceName
        importcrpdmsgs.ctl /u01/logs c_rpd_msgs_delim.csv
      /scratch/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/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/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

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.

Load Translation Data on Oracle Autonomous Transaction Processing (ATP)

Load translation data into the BIACOMP schema of Oracle BI Applications.

Before you load translation data into the BIACOMP schema of Oracle BI Applications, make sure that:
- The database is up and running.
- The BIACOMP schema is available.
- The C_RPD_MSGS, C_RPD_MSGS_REL, and C_RPD_MSGS_TL tables exist in the BIACOMP schema.
- The steps listed in Install and Configure Oracle BI Applications are completed without any errors.
In your middleware host, navigate to <ORACLE_HOME>/bi/nls.

Unzip the rpd_translations.zip translations file in your OCI compute machine and navigate to the rpd_translations directory.

Run the script:

For Linux/Unix, run the loadOtbiSeeddataSqlldr.sh script thrice to load translations data into three tables using the following command:

sh loadOtbiSeeddataSqlldr.sh <DB user name> <DB password> 
<atp_service_name> <Control File> <Log Directory> 
<CSV File Location> <Instant Client loc>

For example:

<rpd translation unzip path>/rpd_translations/loadOtbiSeeddataSqlldr.sh DEV_BIACOMP <DB password> biaatp_tp <rpd translation unzip path>/rpd_translations/importcrpdmsgs.ctl /u01/biapps/log_msgs <rpd translation unzip path>/rpd_translations/c_rpd_msgs_delim.csv /u01/biapps/instantclient_21_4

<rpd translation unzip path>/rpd_translations/loadOtbiSeeddataSqlldr.sh DEV_BIACOMP <DB password> biaatp_tp <rpd translation unzip path>/rpd_translations/importcrpdmsgsrel.ctl /u01/biapps/log_msgs_rel <rpd translation unzip path>/rpd_translations/c_rpd_msgs_rel_delim.csv /u01/biapps/instantclient_21_4

<rpd translation unzip path>/rpd_translations/loadOtbiSeeddataSqlldr.sh DEV_BIACOMP <DB password> biaatp_tp <rpd translation unzip path>/rpd_translations/importcrpdmsgstl.ctl /u01/biapps/log_msgs_tl <rpd translation unzip path>/rpd_translations/c_rpd_msgs_tl_delim.csv /u01/biapps/instantclient_21_4

For Windows:

<DB_OH>/bin/sqlldr <BIACOMP USER>/<BIACOMP password>@<atp_service_name> 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>@<atp_service_name> 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>@<atp_service_name> data=<path of file>\c_rpd_msgs_rel_delim.csv control=<path of ctl>\importcrpdmsgsrel.ctl log=c:\temp\crpdmsgstl.log

After you successfully run the loadOtbiSeeddataSqlldr.sh script, verify that the C_RPD_MSGS, C_RPD_MSGS_REL, and C_RPD_MSGS_TL tables have the translations data.

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

Navigate to the ORACLE_HOME/odi/studio/bin directory.
Open the odi.conf file in an editor.

At the bottom of the file, add the following:

AddVMOption -Doracle.security.jps.config=./jps-config-jse.xml
AddVMOption -Dexclude.technology.refresh.seeded.objects=true

Save the 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.

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.

Sign in to ODI Studio, from the menu, select File, then select New.
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.
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 a user who has supervisor privileges. For example, user specified as biprov.odi.user.name in the input.txt file.
  - Password: Specify the password for the user you entered in the User field.
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.
Description of the illustration repository_connection_info.png
Click Test to test the connection, and fix any errors. After the test is successful, click OK to create the connection.
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.
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.
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 a user who has supervisor privileges.
3. Provide the password for the user who has supervisor privileges.
After successfully signing into ODI, you see the ready-to-use ODI repository artifacts.

Regenerating the Security Files

Administrator must regenerate the security files and redistribute the files to all instances of ODI Studio if there’s a change in the password of Oracle BI Applications administrator or any Oracle Data Integrator user.

Execute the wlst.sh script.

ORACLE_HOME/oracle_common/common/bin/wlst.sh ORACLE_HOME/bi/biapps/scripts/createJPSArtifactsODI.py embedded --ADMIN_USER_NAME <WebLogic Server Admin User> --DOMAIN_HOSTNAME <Hostname> --DOMAIN_PORT <WebLogic Port> --DOMAIN_HOME_PATH DOMAIN_HOME

The updated JPS configuration file and credential wallet are created in the DOMAIN_HOME/odi-client-config/embedded directory.

On all the ODI Studio instances, copy the updated JPS configuration file and the credential wallet files from the DOMAIN_HOME/odi-client-config/embedded directory to the ORACLE_HOME/odi/studio/bin directory.
Make sure that the odi.conf file is edited correctly to configure user access for ODI Studio.

The odi.conf file is located in the ORACLE_HOME/odi/studio/bin directory.

See Setting the JPS Config File Location.

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.

The configuration flow is largely the same whether you're using a non-RAC database or a RAC database. The instructions to install Oracle Fusion Middleware Infrastructure, Oracle Business Intelligence, creating Oracle 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 Oracle 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.

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.
Run config to complete the process.

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.

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:

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.

Ensure the following prerequisites:

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

Update your input.txt file available at <Oracle_Home>/bi/biapps/scripts/input.txt with these sample parameters:
- biprov.ha.bi_domain.dir=<DOMAIN_HOME>
- 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
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>.
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>.
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>.
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:

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

On Node 1, complete the following steps to change the Singleton Data Directory (SDD). See Change the Singleton Data Directory (SDD).
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|cmd [-m <new computer name>] <listen address> <Jar file>
  For example:
  ORACLE_HOME/user_projects/domains/bi/bitools/bin/clone_bi_machine.sh example.com /oracle/nfs_shared/clone/demobi2.jar
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 command: ORACLE_HOME/oracle_common/common/bin/unpack.sh -template=[location of copied jar file from primary computer] –domain=DOMAIN_HOME -nodemanager_type=PerDomainNodeManager
  For example:
```
Oracle_Home/oracle_common/common/bin/unpack.sh -template=/refresh/home/oracle/nfs_shared/clone/demobi2.jar -domain=/../../Oracle_Home/user_projects/domains/bi -nodemanager_type=PerDomainNodeManager
```
4. On the new computer, start the Node Manager and Managed Server to create the config.xml file.
  For example:
  Oracle_Home/user_projects/domains/bi/bin/startNodeManager.sh
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.
3. Re-synchronize the data source on the new computer.
  On the new computer, run the following script:
  DOMAIN_HOME/bitools/bin/sync_midtier_db.sh
4. On the primary computer, start the new system components for the new computer:
  Change directory to DOMAIN_HOME/bitools/bin/.
  
  Enter:
  ./start.sh -i obis2,obips2,obiccs2,obijh2,obisch2
  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.

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.
4. Use Fusion Middleware Control to view system component availability. See Use Fusion Middleware Control to View System Component Availability.
5. Use the Administration Console to view managed server availability. See Use the Administration Console to View Managed Server Availability.

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.

Stop OHS using the command:
cd /u02/installation/OHS/Oracle_Home/user_projects/domains/ohs_domain/bin ./stopComponent.sh ohs1

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>

#bi-security-login
<Location /bi-security-login>
WebLogicCluster <node1_host>:<bi_server1_port>,<node2_host>:<bi_server2_port>
SetHandler weblogic-handler
</Location>

Start OHS using the command:
cd /u02/installation/OHS/Oracle_Home/user_projects/domains/ohs_domain/bin ./startComponent.sh ohs1
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
Bring down one set of Oracle Analytics Server and Oracle Data Integrator servers and check if the URLs are redirecting to the Oracle Analytics Server and Oracle Data Integrator instances that are running.

Performing Post-Configure Steps for High Availability

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

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.
Open Oracle Data Integrator (ODI) Studio or ODI Console. Go to Topology, click Physical Architecture, click Agents, and then click OracleDIAgent.
In Agent, update the Oracle HTTP server (OHS) hostname and port.
Create a network file system that is available in both hosts, such as filer2. Ensure that path /filer2/HAShared is available in both hosts.
Give write permission to the location to all, for example, chmod -R 777 /filer2/HAShared.
In node2, go to <ORACLE_HOME>/bi/biapps/etl and unzip biapps_etl.zip in the same location.
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>
Complete the functional setup and register the source in BIACM.
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.
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
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 Analytics Server schemas with the Repository Creation Utility (RCU) with a RAC database.

Install Oracle Fusion Middleware Infrastructure and Oracle Analytics Server as described in Install Oracle Fusion Middleware Infrastructure (WebLogic Server) and Install Oracle Analytics Server.
Don't run Oracle Data Integrator and Oracle BI Applications yet.
Launch the RCU from $ORACLE_HOME/oracle_common/bin/rcu and select the System Load and Product Load option.
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.
Provide the prefix for the schemas, select all components, and then click Next.
View all the schemas to be created and click Next.
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.
Verify that the <Schema_Prefix>_STB.COMPONENT_SCHEMA_INFO table is populated with applicable details.
Run the installers for Oracle Data Integrator and Oracle BI Applications and create the BIAPPS schema using the RCU.

Configure SSL

You can configure Oracle BI Applications with SSL for secured connections.

See My Oracle Support note Doc ID 2943320.1 for instructions and details.

Uninstalling Oracle BI Applications

Use the following steps to uninstall Oracle BI Applications.

Stop all running Oracle WebLogic services using this command: $DOMAIN_HOME/bitools/bin/stop.sh.
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.
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
```
.
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
```
.
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.
Restart your system.
If you're trying to reconfigure, then keep ORACLE_HOME intact, create all schemas again, and then run the configure step.
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.