You typically install EPM System products in a distributed environment. The number of computers you need depends on several factors, including:
The size of the applications
The number of users
The frequency of concurrent use by multiple users
Any requirements your organization has for high availability
Your organization's security requirements
See the Oracle Hyperion Enterprise Performance Management System Installation Start Here for sample deployment diagrams to help plan your deployment.
EPM System Installer simplifies the task of installing components in a distributed computing environment. You can install, configure, and validate any components you want on any computer. Once you have installed, configured, and validated the components on that machine, you can repeat the process on another machine.
For information about which assemblies you need on each machine in a distributed environment, see Preparing for Installation.
Note the following information about planning for an installation in a distributed environment:
If you are deploying to a shared drive (UNIX only), not all of the following notes apply.
While you can install products in any order in a distributed environment, there is a required configuration sequence in a distributed environment. In particular, note that you must configure Foundation Services first. Foundation Services must be installed and configured for other products to configure successfully. To configure Foundation Services, select the Foundation tasks on the Task Selection panel of EPM System Configurator: “Configure Common Settings,” “Configure Database,” “Configure Oracle Configuration Manager,” and “Deploy to Application Server.” Configure the Web server last.
In a distributed environment, EPM Oracle home must be the same on each machine. For example, if the path for EPM Oracle home is /Oracle/Middleware on the first machine you configure, it must be /Oracle/Middleware on all the machines in the deployment.
On the machine on which you plan to administer the WebLogic Server, you must install all Web applications for all applications you plan to deploy on any machine in the environment. (The WebLogic Administration Server is installed and deployed on the Foundation Services machine.)
On each remote machine in a distributed environment, install the Web applications you plan to run on that machine and then use EPM System Configurator to deploy the Web applications automatically, or manually deploy the Web applications.
Note that EPM System Installer installs WebLogic Server on each machine (for Web tier and Service tier components) in a distributed environment.
If you are deploying Web applications on a machine other than the WebLogic Administration Server machine, WebLogic Administration Server must be running.
All Web applications in an EPM System deployment must be deployed on either all Windows machines or on all UNIX machines. However, because Financial Management runs only on Windows, if you are using Financial Management with Reporting and Analysis, you must also deploy Reporting and Analysis on a Windows machine. (Financial Management is not supported as a data source on a UNIX platform.) If your other Web applications are deployed to UNIX machines, you must deploy Financial Reporting and Web Analysis on Windows using a manual process.
See Deploying Financial Reporting and Web Analysis on Windows for use with Financial Management.
You can have more than one OHS Web server in a deployment for load balancing and failover. In this scenario, configure the Web server on each machine in the environment.
If you are using IIS as the Web server, install each IIS application so that it is co-located with an IIS Web server. This means that any machine hosting an IIS application also requires an IIS Web server.
If you are installing in multiple environments (for example, Development, Test, and Production), install Foundation Services products in each environment.
You must install the Financial Management Smart View Provider and the Financial Management LCM Provider on the same box as the Financial Management Web application.
For IIS 6.0, you cannot install 32-bit components on a 64-bit system on which 64-bit components are already installed. You must install the 32-bit components on another system or install all of the 32-bit components on a 32-bit system. Specifically FDM (32-bit) and Strategic Finance (32-bit) cannot be deployed on the same computer where Financial Management (64-bit) and Performance Management Architect (64-bit) are deployed. On 32-bit platforms, all EPM System products can co-exist. For IIS 7 (the default on Windows 2008 systems), 32-bit and 64-bit components can co-exist.
During configuration, the Oracle HTTP Server machine needs connectivity to the machine hosting the Shared Services Registry.
EPM System static content, including product online Help, is installed with Oracle HTTP Server.
In a distributed environment, for Financial Close Management, you must install Oracle SOA Suite on the following machines in the deployment, although you need to configure it on only one machine (the machine on which you want to run SOA Server): Financial Close Management, WebLogic Administration Server, Foundation Services, Financial Management (Web application), Financial Reporting (Web application), FDM (Web application).
Note: | Oracle SOA Suite and EPM System must be deployed to the same domain. |
For FDM, when you are using Financial Management, Essbase, Planning, or Hyperion Enterprise as target systems, the target system clients must be installed on the same server as FDM.
If you are using FDM and you are using IIS as the Web Server to host EPM Workspace, you must install the FDM Web application and the EPM Workspace Web application on the same box.
If you are using Financial Management and IIS as the Web Server, you must install Financial Management Web applications and the Web Server on the same box.
If you are using Performance Management Architect and IIS as the Web Server, you must install Performance Management Architect Web applications and the Web Server on the same box.