Installing and Configuring Financial Management Integration Types for Financial Close Management 11.1.2.3

Purpose

This tutorial covers installing and configuring Oracle Hyperion Financial Management (HFM) integration types for Oracle Hyperion Financial Close Management (FCM) 11.1.2.3.

Time to Complete

Approximately 1 hour.

Introduction

The Close Manager module of Oracle Hyperion Financial Close Management 11.1.2.3 (FCM) supports end user and system automated integrations with Oracle Hyperion Financial Management (HFM). This tutorial covers installing and configuring HFM integration types for FCM.

Prerequisites

• Because HFM is supported only on the Microsoft Windows platform, it is required that both FCM and HFM are in the same WebLogic domain and that the entire configuration is available on Microsoft Windows OS.
• It is recommended that you apply FCM 11.1.2.3.000 Patch Set Update 16989110, as it contains some important fixes.
• You should have access to the FMIntegrationTypes_11_1_2_3.xml integration types XML file. This is available from My Oracle Support as patch 16825751.

You must create a keystore using the JDK 1.6 based keytool utility, and then use Enterprise Manager to set up message protection for Web services.

Note: The steps that follow can also be found in the Configuring Oracle Web Services Manager for EPM System Products section of the Oracle® Enterprise Performance Management System Installation and Configuration Guide. You should perform these steps as part of post-EPM product configuration.

1. Open a DOS window and navigate to /Oracle/Middleware/user_projects/$DOMAIN_HOME/config/fmwconfig, in the server running the WebLogic Administration Server hosting your EPM System domain.

2. Execute the following command:
   keytool -genkeypair -keyalg RSA -alias aliasName -keypass password –keystore keystoreName.jks -storepass password -validity 3600

3. Note: If the keytool command is not recognized, the Path environmental variable might not include the JDK. Add the JDK to the Path variable using the following command:
   set PATH=%PATH%;C:\Oracle\Middleware\JDK160_35\bin\;.;..

When running the command above, the user is required to perform the following:

• Set the –keypass and –storepass password parameters to the desired password, for example ‘oracle1’.
• Update the –alias aliasName parameter to the desired alias name, for example orakey.
• Update the –keystore parameter to the desired keystore name, for example EPMKeystore.jks.

3. Log in to Enterprise Manager (for example http://WebLogicAdminServerHost:7001/em) using WebLogic administrator credentials.

4. Expand WebLogic Domain, and then select EPMSystem (or the domain name used for the EPM System deployment).

5. Right-click EPMSystem, select Security, and then select Security Provider Configuration.

6. Scroll to the Keystore section, expand the section, and then click Configure.

7. For Keystore Path, enter the path and name for the keystore that you created, for example ./EPMKeystore.jks.

8. Enter the keystore password you used when creating the keystore, and confirm it.

9. Enter an alias and password for both Signature Key and Encryption Key, using the alias and password that you used when creating the keystore. Confirm the passwords, and then click OK.

   The alias and password for the signature and encryption keys define the string alias and password used to store and retrieve the keys.

10. Log out and restart Oracle Enterprise Manager Fusion Middleware Control so that the changes take effect, and then restart the EPM System managed servers.

You create integration points between HFM and FCM by importing the file FMIntegrationTypes_11_1_2_3.xml into Close Manager.

1. Login to Close Manager as an administrator.

2. Select Manage > Integration Types.

   

3. In the Manage Integrations Types dialog box toolbar, click Import.

   

4. Browse to select FMIntegrationTypes_11_1_2_3.xml, and click Next.

   

5. Select the integration types for which you want to automatically create task types, and click Next to import the integration types.

   

6. At the Results screen, click Close.

   

The following sections cover some typical problems and suggested solutions.

PolicySet Invalid: WSM-06102 PolicyReference The policy referenced by URI oracle/wss11_saml_or_username_token_with_message_protection_service_policy could not be retrieved.

• Occurrence: This issue could occur when a user is trying to specify HFM task parameters such as Cluster, Application or POV dimension.

• Cause: Java keystore is not configured.

• Fix: The Java keystore needs to be configured for the EPM domain as described in the Generating the Java Keystore for Message Protection section. Additionally, verify that the wsm-pm application is set to Active in the WebLogic Console’s Deployments.

Invalid XML specified for the dimension selector. The following exception has occurred in XMLError.flushErrors1(): oracle.xml.parser.v2.XMLParseException with message: Start of root element expected.

• Occurrence: This issue occurs when a user is trying to specify the HFM task parameter Application.

• Cause: The logged in user is not provisioned to access the HFM application.

• Fix: To address this issue it is recommended to apply FCM 11.1.2.3.000 Patch Set UPdate16989110. This patch will help to avoid the exception being thrown. After applying the patch, the user will not be able to select the POV dimension if he or she is not provisioned for the application. User must be provisioned using HSS to access the HFM application.

In this tutorial, you learned to:

• Generate the Java keystore for message protection
• Import HFM integration types into Close Manager
• Perform troubleshooting

Credits

• Lead Curriculum Developer: Mark Mitsock
• Other Contributors: Ashutosh Bhatikar, Ron Reiley