1. Installation and Configuration Guide
  2. Installing EPM System Products in a New Deployment
  3. Installation Prerequisites and Requirements

Installation Prerequisites and Requirements

Note the following installation prerequisites.

  • Review the system requirements in the (http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html).

  • If you are using Windows 2016, see the post configuration information under the Oracle Hyperion Technology section in the Known Issues in 11.2.15 topic to enable support for Windows 2016 on Oracle Essbase 21c embedded with EPM 11.2.15.

  • You must install and configure all EPM WebLogic instances on the same operating system.

  • EPM System Installer installs Oracle WebLogic Server for you. If you have an existing WebLogic Server installation and want to use it instead of the WebLogic Server installed by EPM System Installer, it must be the version supported by Oracle Enterprise Performance Management System.

    Note:

    Ensure that you note the Middleware home location for the WebLogic Server installation. During installation, you must install EPM System products to this same Middleware home. If EPM System Installer detects an existing WebLogic Server installation in the installation location, it does not install WebLogic Server.

  • Ensure that there is 4 GB of temp space available. You can specify an alternate /tmp directory if needed.

  • If you are configuring a Essbase Failover environment in Windows, ensure that the common shared Essbase application directory is mounted on the same drive (for example, Z:) on the nodes and use it as the application directory in the EPM configuration tool.

    Note:

    UNC Shared directory path is not supported as Essbase application directory in Windows.

  • When updating an existing Essbase environment (Version 11.1.2.4) where EAS Lite is configured independently, the machine where EAS Lite was previously available will no longer be availalable on the same machine after updating to Release 11.2.15. It will be removed from the machine, along with the registry entries related to it. As an alternative, it will be set up on the same system as Essbase Server.

  • If the files (for example, "Calc Scripts", "Rule Files") in your 11.2.x Essbase instance have names that contain non-English characters , they might not be converted to Essbase 21c as part of the upgrade to EPM 11.2.15. Ensure that you manually migrate those files.

  • Essbase is upgraded to version 21c from 11.1.2.4.x as part of the upgrade to Release 11.2.15. This upgrade needs at least three times the amount of free space in your system that the overall Essbase cube size occupies. This is only utilized for short-term activities, and it will be cleaned up after the upgrade. See Differences Between Essbase 11g and Essbase 21c for more information.

  • EPM products using JAPI -Ensure that you take a backup of the file EPM_ORACLE_HOME\common\EssbaseJavaAPI\11.1.2.0\bin\essbase.properties and copy it to EPM_ORACLE_HOME\common\EssbaseJavaAPI-21C\11.1.2.0\bin\essbase.properties after the upgrade to EPM 11.2.15.

  • Install the 32 bit version of on Visual C++ Redistributable Packages for Visual Studio 2013 on the Windows machine where Oracle Hyperion Financial Reporting is installed. (https://www.microsoft.com/en-us/download/details.aspx?id=40784).

    On Linux:

    Make sure libstdc++.so.6 is installed on the machine whereFinancial Reporting is installed.

  • On Linux systems, ensure that ulimit is 8096 for the ODI patch to apply. You can query for the current ulimit setting with the following command: ulimit -n

  • See Preparing Your Environment for installation prerequisites.

  • For Oracle Hyperion Tax Provision, you must also install all Oracle Hyperion Financial Management components, although they do not need to be installed on the same machine as Tax Provision.

  • If you are installing on the same machine on which Oracle Business Intelligence Enterprise Edition or Oracle Business Intelligence Publisher are installed, install into two different Middleware homes. Future patch sets for EPM System and Oracle BI EE will be released at different times, which would create constraints for the upgrades of a merged Fusion Middleware Home.

    For information about Fusion Middleware, see https://www.oracle.com/middleware/technologies/bi-foundation/hyperion-supported-platforms.html.

  • If you are installing and configuring Oracle Hyperion Financial Data Quality Management, Enterprise Edition, Oracle Data Integrator is automatically installed and configured for you. The database for Oracle Data Integrator is in same database as FDMEE and the Oracle Data Integrator agent application is deployed in same JVM as FDMEE.

  • FDMEE is required for Account Reconciliation Manager in Oracle Hyperion Financial Close Management. Configure Financial Close Management and Account Reconciliation Manager before configuring FDMEE.

  • If you have an existing Oracle SOA Suite installation you plan to use with Financial Close Management, note the Middleware home location for the SOA Suite installation.

    During installation, you must install EPM System products to this same Middleware home.