In general, for a new installation, Oracle recommends that for each machine, you configure all EPM System products at the same time for the products installed on the machine. By default, EPM System Configurator preselects all products for you. Foundation Services must be installed and configured for other products to configure successfully. The configuration sequence for various deployment scenarios is described in the following sections.
Configuration sequence notes:
If you are configuring Financial Close Management, there is a required configuration sequence. See Financial Close Management Installation and Configuration Prerequisites and Roadmap.
By default, EPM System Configurator uses the same database for all products that you configure at one time. To use a different database for each product, perform the “Configure Database” task separately for each product. In some cases you might want to configure separate databases for products. Configure the Web server last.
You must perform the “Configure Database” task at the same time as or before you perform the “Deploy to Application Server” task.
If you have already configured the Web server, and you configure any additional products, you must run EPM System Configurator again and select the Foundation Services “Configure Web Server” task. Then, restart the Web server and EPM Workspace.
Automatic Web server configuration with EPM System Configurator is supported only for the Oracle HTTP Server installed by EPM System Installer or IIS.
Configure the following products after you have completed all the configuration tasks using EPM System Configurator:
Data Relationship Management. See the Oracle Hyperion Data Relationship Management Installation Guide.
FDM. The tasks in EPM System Configurator register the FDM Web server in the Shared Services Registry. The remainder of the configuration is done in FDM. See the Oracle Hyperion Financial Data Quality Management Configuration Guide.
Note: | If you want to install Essbase in standalone mode (not using Foundation Services), you can skip the installation for Foundation Services Web applications. However, you must still configure the Shared Services Registry. To configure the Shared Services Registry without installing Foundation Services, you run EPM System Configurator from the command line using the –forceRegistry option. See Setting Up Essbase in Standalone Mode. |