13.3 Deploying BI

Keep the following in mind as you deploy Oracle Business Intelligence (BI).

  • About BI Session Failover
    If a BI Managed Server and/or host crashes, a user may need to log in again. This depends on which application they are using at the time of the crash and whether or not SSO is in use.
  • About BI Essbase
    Essbase doesn't support a high availability configuration. If a server fails, there is no loss of state; you can recover from a failure by redploying Essbase Cube.
  • About BI Studio
    Studio doesn't support a high availability configuration. Oracle recommends performing xml import/export on a regular basis. This is the best practice for Studio recovery from a catalog failure.
  • About Specifying Ports for Multiple Node Managers
    If you have more than one node manager per machine, verify that you specify your ports.
  • About RAC Database Post Installation Configuration
    Oracle BI requires additional configuration steps for whole server migration after installation.
  • About Scaling Out BI Publisher
    Completing BI scale out requires tasks in addition to typical scale out steps.

13.3.1 About BI Session Failover

If a BI Managed Server and/or host crashes, a user may need to log in again. This depends on which application they are using at the time of the crash and whether or not SSO is in use.

13.3.2 About BI Essbase

Essbase doesn't support a high availability configuration. If a server fails, there is no loss of state; you can recover from a failure by redploying Essbase Cube.

13.3.3 About BI Studio

Studio doesn't support a high availability configuration. Oracle recommends performing xml import/export on a regular basis. This is the best practice for Studio recovery from a catalog failure.

13.3.4 About Specifying Ports for Multiple Node Managers

If you have more than one node manager per machine, verify that you specify your ports.

For more information, see About Node Manager Configuration in a Typical Enterprise Deployment in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.

13.3.5 About RAC Database Post Installation Configuration

Oracle BI requires additional configuration steps for whole server migration after installation.

See Using Whole Server Migration and Service Migration in an Enterprise Deployment in Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence for these steps.

13.3.6 About Scaling Out BI Publisher

Completing BI scale out requires tasks in addition to typical scale out steps.

Oracle BI requires additional steps after you follow scale out steps in Scaling Out a Topology (Machine Scale Out). Oracle BI requires you to change setDomainEnv.sh to the updated singleton-data-directory setting (SDD).

To complete Oracle BI scale out:

  1. Move the SDD from local to shared storage so that all hosts can access it using the same path. For example, move it to:

    DOMAIN_HOME/bidata/net/yoursystem/scratch/sdd

  2. Open DOMAIN_HOME/config/fmwconfig/bienv/core/bi-environment.xml (element bi:singleton-data-directory).
  3. Change the xdo.server.config.dir path to refer to the new SDD path you just created.
  4. Restart the server.