Keep the following in mind as you deploy Oracle Business Intelligence (BI).
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.
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.
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.
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.
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.
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:
xdo.server.config.dirpath to refer to the new SDD path you just created.