Preparations for CXO Installation (Version 20) for Financial Management HFM (HFM 11.1.2.4+, Oracle EPM FM)
This document describes the prerequisites and preparations for installing and configuring the CXO software as a dashboard on Oracle Hyperion Financial Management. It does not describe the installation and configuration itself.
The tables should be used as a check-list: either the indicated piece of information must be provided (enter it in the ‘Information’ column) or the specified action should be carried out / component should be installed (put a checkmark in the ‘Done’ column).
CXO Software Application Server
Provide the following information for the CXO software application server. We also support virtual servers.
Requirement / Action |
Information |
Done |
Windows 2012 / 2014 / 2016 / 2019 |
|
|
Amount of RAM (min. 16Gb) |
|
|
Number of cores (min. 4) |
|
|
Check Disk Space available (> 25Gb) |
|
|
Name (full DNS) |
|
|
IP |
|
|
Account to log on |
|
|
Domain (if applicable) |
|
|
Password1 |
|
|
SQL Server Management Studio installed (optional)2 |
|
|
Microsoft Components
The following Microsoft Components should be available on the server
Requirement / Action |
Information |
Done |
IIS 7 / IIS 8 / IIS 10 |
|
|
.NET Framework 4.8 (CXO installer will install it if it is not there yet, so there is no need to pre-install it) |
|
|
Service Account
For communication between the Web-application and the OLAP database and for running the CXO software services, we need a service account. If Analysis Services (see below) is installed on the CXO software application server, this service account can be a local machine account. Otherwise it should be a Domain account. The password of the account should never expire.
Requirement / Action |
Information |
Done |
Name |
|
|
Password |
|
|
Domain (if applicable) |
|
|
SQL Server
Data and meta-data of a CXO software application are stored in SQL Server databases. A SQL Server should be available, or SQL Server should be installed on the CXO software Application Server.
Requirement / Action |
Information |
Done |
Edition (Enterprise/ Standard / Express3) |
|
|
Version (2012 / 2014 / 2016 / 2017 / 2019) |
|
|
Windows Server Name (full DSN) |
|
|
IP |
|
|
Instance name (or specific port)4 |
|
|
SQL Account (role = dbcreator)5 |
|
|
Domain (or local) account to log-on to the server (optional: see3) |
|
|
Password |
|
|
Analysis Services
The OLAP database in which we store the data extracted from HFM runs on SQL Server Analysis Services. As a rule, Analysis Services is installed on the same Windows Server as the SQL Server Database Engine, but this is not a requirement. Only provide information if it differs from the SQL Server specifications.
Requirement / Action |
Information |
Done |
Edition (Enterprise/ Standard) |
|
|
Version (2012 / 2014 / 2016 / 2017 / 2019) |
|
|
Multidimensional model |
|
|
Windows Server Name (full DSN) |
|
|
IP |
|
|
Instance name (or specific port) |
|
|
Domain (or local) account to log-on to the server (optional: see3) |
|
|
Password |
|
|
Financial Management
To connect to the HFM Application cluster, we need to know where the HFM database is located and with which (read-only) user we can connect with.
Requirement / Action |
Information |
Done |
HFM Version |
|
|
SQL Server Name (full DSN) / IP |
|
|
Database name |
|
|
Application name |
|
|
Username (read-only) |
|
|
Password |
|
|