Workiva Support Center

With the Oracle® Hyperion® Financial Management connector, you can use commands in a chain to interact with Oracle Hyperion Financial Management (HFM) version 11.1.2.4.x or 11.2.x. For example, you can create a chain to extract data from Oracle HFM as a file to upload to a Wdata table.

Important: While this connector was built by Workiva to connect to a HFM system, our Support team can only help configure this connector within your workspace; we are unable to troubleshoot or otherwise assist with any issues that originate outside of the Workiva platform.

Note: To connect to Oracle HFM versions 9.3.1 through 11.1.2.3, use the Oracle HFM Legacy connector.

Prerequisites

To set up the connection, you'll need:

• A server with access to Oracle HFM.
  It should have the entire HFM suite installed (including JDKs, supporting assets, etc.)
• Installations of:
  • The Java runtime that comes bundled with HFM.  As of 2026, this is usually the Oracle Java Runtime Environment (JRE) 8. This runtime should be installed as the system-level JRE.

  • This runtime must be accessible from the command line. 
    You can test this by opening a terminal (Linux) or Command Prompt/PowerShell (Windows) and entering java -version. The response should look look something like this: (version 1.8.x is JRE 8)

    java version "1.8.0_481"
    Java(TM) SE Runtime Environment (build 1.8.0_481-b10)
    Java HotSpot(TM) 64-Bit Server VM (build 25.481-b10, mixed mode)

    If it is not accessible, you will need to adjust your PATH environment variable.

    Note: If you try to use other JVMs, the connector may not work properly; this is due to some legacy requirements of the Oracle HFM Java libraries.

• A GroundRunner execution agent

  Note: Install the GroundRunner on an Enterprise Performance (EPM) server machine hosting the HFM Application Service.  Workiva cannot provide troubleshooting support when the GroundRunner runs on a different server or network than the Oracle HFM instance.

• Paths to the Oracle Enterprise Performance (EPM) system instance and its HFM home directory.
• The cluster name of the HFM server as it appears in the EPM Shared Services Registry.

• An Oracle HFM integration user, used to authenticate with the Oracle HFM instance.

  Note: The integration user must be a Native Directory user —not a Microsoft® Active Directory® (MSAD) user— with access to data required for Reporting and Extended Analytics. The MSAD user is still needed, but its purpose is to communicate with the GroundRunner.

• A GroundRunner to perform the tasks in Oracle HFM and the relational database.

  Note: To enable the connection, the GroundRunner's integration user requires Execute privileges to the HFM home directory.

For assistance when creating and building chains, we also recommend you identify:

• Your Workiva admins
• The Oracle HFM admins
• Your network and infrastructure engineering teams

Set up the connection to Oracle HFM

To set up the connection, an IT admin configures the server, and a workspace owner creates the connection to Oracle HFM.

Step 1. Configure the server

1. In Oracle HFM, create the integration user, and grant them access to Reporting and Extended Analytics.
2. On the server that can access Oracle HFM:

   • Install the Java runtime that comes bundled with HFM. This will be Java Runtime Environment 8 or greater.

     Note: When installing Java, you may be asked whether to install the Java Development Kit (JDK) or Java Runtime Environment (JRE). Only the JRE is required.

   • Add the path to the JVM packaged with the Oracle HFM (this is usually the JAVA_HOME of the JRE and then the bin folder) to the system PATH.
   • Download, install, and activate the GroundRunner execution agent.
   • Allow the host domains for Workiva.

Step 2. Set up the Oracle HFM connector

Note: To make the connector available for use in your organization's chains, an org security administrator must first enable it from Configuration.

1. From Chain Builder, click Connections compare_arrows, and then Create at the top right.
2. Under Connector Connection, select Oracle Hyperion Financial Management and the GroundRunner installed on the server.
3. Under Basic Info, enter a unique name and description to help identify the connection.

4. Under Properties, enter the connection's details:

   Note: Consult your Oracle HFM admin for the correct values.

   Property	Details
   Username	Enter the Oracle HFM integration user's username.
   Password	Enter the Oracle HFM integration user's password.
   EPM home	Enter the path to the HFM home directory for the Oracle EPM system.  The default is: C:/Oracle/Middleware/EPMSystem11R1.
   EPM instance	Enter the path to the EPM system.  The default is: C:/Oracle/Middleware/user_projects/epmsystem1.
   HFM cluster	Enter the cluster name for the Oracle HFM server, as it appears in the EPM Shared Services registry.

   Note: All sensitive credentials are automatically encrypted and stored at Advanced Encryption Standard (AES)-256 encryption.

5. Select the workspace environments to use with the connector, and click Save.
6. To test the connection, create and run a chain with the Oracle HFM connector's Extract Members List command, and verify it returns a valid output.

Troubleshooting

Can I use the HFM connector on a load balanced server?

Load balancing is built into HFM and is not controlled by Chains, but you can enter your configuration into the ClusterName field when setting up the connector.

The connection to Oracle HFM fails

Verify the name of the Oracle HFM cluster to connect to, and the Oracle HFM integration user's authentication credentials.

The connector returns a blank output or no response

To ensure the GroundRunner can communicate with the Oracle HFM JAR files, verify the paths to the HFM home directory and EPM instance.

The connector returns an "insufficient permissions" error

Verify the Oracle HFM integration user has both Read and Write access -- not Read only.

Note: The MSAD user--which the GroundRunner depends on--must also have sufficient Read/Write access to any directories that contain files that Chains will interact with.

A command returns an exit code of Success but has no output

If the Clear slice, Copy data, Extract data to database, or Extract data to file command succeeds but has no output, verify its "Expand only" property is not selected. Select "Expand only" to view members with no extraction, such as for testing.

An authentication error occurs when installing on multiple servers

Look for the following line is found in the logs:

 INFO: The file reg.properties could not be found.

If this is found, copy the reg.properties file from Oracle\Middleware\user_projects\config\foundation\11.1.2.0

to

Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0.