Considerations if you are installing Reporting and Analysis in a distributed environment:
Install only one instance of Reporting and Analysis Framework services and Interactive Reporting services on each host, and run EPM System Configurator on each machine. You can then use EPM Workspace to replicate services on each host. Each instance is part of the cluster and is used for load balancing and high availability. See Clustering Reporting and Analysis Framework Services and Common Libraries.
The GSM and ServiceBroker services must be enabled on all instances of the Reporting and Analysis services for high availability of Reporting and Analysis. By default, the GSM and ServiceBroker services are enabled only on the first instance of the Reporting and Analysis services.
Note: | Clustering without high availability or failover does not require that the GSM and Service Broker services be enabled on all instances. |
If you are running multiple instances of the Reporting and Analysis Repository Service, all instances should share the file system location. Specify the file system location during configuration with EPM System Configurator, on the Configure Reporting and Analysis Framework Services page, or with the Administer section of EPM Workspace. If you are running this service as a Windows service, use a UNC path instead of a mapped drive. This prevents potential permissions errors than can occur when Windows attempts to create a mapped drive at startup. See “Configure Reporting and Analysis Framework Services” in Chapter 4, “Configuring EPM System Products, ” of the Oracle Hyperion Enterprise Performance Management System Installation and Configuration Guide.
On Windows platforms, when replicating common Reporting and Analysis services and using the network shared folder for the repository location, run the Reporting and Analysis agent Windows service under a user account with sufficient privileges for the network shared folder (not under a Local System account).
For the Financial Reporting Web application, you can have only one active instance of the Scheduler component in a clustered environment.
Use the same path to MIDDLEWARE_HOME on all machines. (Otherwise, multiple Reporting and Analysis nodes are displayed in Shared Services.)
For more information about configuring Reporting and Analysis for a distributed environment, see the Hyperion Reporting and Analysis Framework Administrator’s Guide.