Oracle® Hyperion Enterprise Performance Management System Installation and Configuration

Oracle® Hyperion Enterprise Performance Management System Installation and Configuration  

Release 11.1.2.1.000 Patch Set Exception (PSE): 12552933

Readme

[Skip Navigation Links]

About this Patch

Patch Type

Supported Paths to this Patch

Prerequisites

Supported Platforms

Supported Languages

Defects Fixed in this Patch

Applying this Patch

Rolling Back this Patch

Troubleshooting FAQs

About this Patch

This Readme file describes the defects fixed in this patch and the requirements and instructions for installing this patch.

Caution: You are urged to carefully read and understand the following requirements. Failure to comply may result in applying a patch that can cause your application to malfunction, including interruption of service and/or loss of data. Before installing or applying this patch:

·         Verify that the issue described in the Readme matches the issue that you are encountering.  Review the Bug Number referenced in the Readme for additional information. 

·      Verify that your system configuration (product version, patch level, and platform) exactly matches what is specified in the Readme.

Patch Type

This Patch Set Exception replaces files in the existing installation and is a stand-alone patch. 

Supported Paths to this Patch

You can apply this patch to the following releases:

·         11.1.2.1.000

Prerequisites

Required User Rights

The user applying the patch should be the user who was set up to install and configure EPM System products. Required user privileges or rights:

Windows:
Use the user account that has Local administrator rights and was set up for installation and configuration. This user is an administrator and is the same for all EPM System products. Assign local policies if required by the product. Such assignments typically are: “Act as part of the operating system, Bypass traverse checking, Log on as a batch job, Log on as a service.”

UNIX/Linux:
Use the account that was used to install EPM System products and has Read, Write, and Execute permissions on $MIDDLEWARE_HOME. If you installed other Oracle products, the user who installed EPM System products must be in the same group as the user who installed the other Oracle products. OPatches are not intended to be applied using a root user.

Edit Shared Services Registry

Before applying the patch (if and only if you have configured Reporting and Analysis components in your system), you need to edit the Shared Services Registry so that security roles are properly retrieved from Shared Services during the login process. Then, apply the patch on any machine where Reporting and Analysis Framework services are installed and ready to be configured.

1.    Stop Foundation Services, the Reporting and Analysis Framework Web application, and the Reporting and Analysis agent services.

2.    Execute the following query against the Shared Services Registry database:

select application_id from css_provisioning_info where lower(application_id) like 'hava%';

Take note of this application id, e.g., HAVA:0000012b3072bf63-0000-6717-0acc1bac

3.    Edit the Shared Services Registry:

Go to EPM_ORACLE_INSTANCE/bin and run the following command:

epmsys_registry updateproperty RA_FRAMEWORK/@applicationId
Where applicationId is the id returned from the query above. For example, using the id above:

epmsys_registry updateproperty RA_FRAMEWORK/@applicationId HAVA: 0000012b3072bf63-0000-6717-0acc1bac

4.    Restart the processes above and login to Workspace again.

Supported Platforms

Applies to all supported platforms.

Supported Languages

This patch supports English only.

Top of Document

Defects Fixed in this Patch

Defect Number	Defect Fixed
• 12552921	Two Reporting and Analysis nodes are displayed in Shared Services Console after a second Reporting and Analysis instance is configured.

Top of Document

Applying this Patch

The section includes important information about applying this patch for EPM System Installer.

Note: You must apply the patch BEFORE the EPM System configuration process.

To apply this patch:

1.    Stop all services on any machine where Reporting and Analysis Framework services are installed and ready to be configured. 

2.    Download and unzip the downloaded patch file, <PATCH FILE NAME>.zip, to the <EPM_ORACLE_HOME>/OPatch directory (by default,Oracle/Middleware/EPMSystem11R1/OPatch).

NOTE: <PATCH FILE NAME>.zip is the name that My Oracle Support assigns to this patch. When you download the file, a message indicates the file name.

3.    On any machine where Reporting and Analysis Framework services are installed, from a command line, change the directory to <EPM_ORACLE_HOME>/OPatch.

4.    To apply the patch, enter the following command on one line:

Windows:
opatch.bat apply <EPM_ORACLE_HOME>\OPatch\12552933 -oh <EPM_ORACLE_HOME>
-jre <MIDDLEWARE_HOME>\jdk160_21
NOTE: The default for <EPM_ORACLE_HOME> is C:\Oracle\Middleware\EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX/Linux:
./opatch apply <EPM_ORACLE_HOME>/OPatch/12552933 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>/jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc
NOTE: The default for <EPM_ORACLE_HOME> is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

5.    Use EPM System Configurator to configure EPM System.

6.    Restart all services on the machine.

7.    This patch fixes generation of wrong Shared Services registry entries for additional RA nodes to be configured; be sure you have done the steps in “Edit Shared Services Registry” in the Prerequisites section to correct Reporting and Analysis entries for components that have been configured already.

Top of Document

Rolling Back this Patch

To roll back a patch:

1.    Stop all services on the machine(s). 

2.    From a command line, change the directory to <EPM_ORACLE_HOME>/OPatch (by default, Oracle/Middleware/EPMSystem11R1/OPatch).

3.    To roll back the patch, enter the following command on one line:

Windows:
opatch.bat rollback -id 12552933 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME>\jdk160_21

NOTE: The default for <EPM_ORACLE_HOME > is C:\Oracle\Middleware\EPMSystem11R1. The default for <MIDDLEWARE_HOME> is C:\Oracle\Middleware.

UNIX/Linux:
./opatch rollback -id 12552933 -oh <EPM_ORACLE_HOME> -jre <MIDDLEWARE_HOME> /jdk160_21 -invPtrLoc <EPM_ORACLE_HOME>/oraInst.loc

NOTE: The default for <EPM_ORACLE_HOME > is $HOME/Oracle/Middleware/EPMSystem11R1. The default for <MIDDLEWARE_HOME> is $HOME/Oracle/Middleware.

4.    Restart all services on the machine(s).

Top of Document

Troubleshooting FAQs

How can I find out which releases and patches of EPM System products are installed in a deployment?

In EPM System Release 11.x, you can use the lsinventory command to OPatch to find the release and patches that are installed in an Oracle Home. For example, enter the following command on one line:

Windows:

opatch.bat lsinventory -oh /user/Oracle/Middleware/EPMSystem11R1 -jdk /user/Oracle/Middleware/jdk160_11

UNIX/Linux:

./opatch lsinventory -oh /user/Oracle/Middleware/EPMSystem11R1 -jdk /user/Oracle/Middleware/jdk160_11

Why do I get the following patch conflict error message when running OPatch?

If the patch that you apply conflicts with a previously applied patch, you may receive the following error message when running OPatch:

Patch(es) <PreviousPatch#> conflict with the patch currently being installed (<NewPatch#>).

If you continue, patch(es) <PreviousPatch#> will be rolled back and the new patch (<NewPatch#>) will be installed.

If a merge of the new patch (<NewPatch#>) and the conflicting patch(es) (<PreviousPatch#>) is required, contact Oracle Support Services and request a Merged patch.

This error is returned when one patch attempts to update a previously patched file. When this conflict happens, you can either (1) roll back the previous patch and apply the new patch (this action might be appropriate if the previous patch was not critical) or (2) request a “merged patch” consisting of the new patch and the patch that it conflicts with. To request a merged patch, contact your Oracle Support representative.  

Why do I get the OUI-67078 warning message when applying OPatch?

This warning means that the patch being applied is a superset of a patch already on the deployment and the existing patch will be rolled back. The following snippet shows the context of this warning.

The following warnings have occurred during OPatch execution:
1) OUI-67078:Interim patch 12345678 is a superset of the patch(es) [77777777] in OH C:\Hyperion
-----------------------------------------------------------------------------------
OPatch Session completed with warnings.

Top of Document

Copyright © 2011, Oracle and/or its affiliates. All rights reserved. http://www.oracle.com

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1 or 11.1.2.2

Utilities for Troubleshooting Oracle Hyperion Enterprise Performance Management 11.1.2.0 or 11.1.2.1 or 11.1.2.2 [ID 1303200.1]

Hyperion Essbase - Version 11.1.2.1.000 to 11.1.2.2.000 [Release 11.1]

Hyperion Planning - Version 11.1.2.0.00 to 11.1.2.2.000 [Release 11.1]

Hyperion Financial Management - Version 11.1.2.0.00 to 11.1.2.2.000 [Release 11.1]

Hyperion BI+ - Version 11.1.2.0.00 to 11.1.2.2.000 [Release 11.1]

Information in this document applies to any platform.

(1) \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh

(2) \Oracle\Middleware\ohs\ccr\bin\

(3) \Oracle\Middleware\ohs\rda\rda.cmd

(4) \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh

(5) \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat

Goal

This article aims to help users use various troubleshooting tools to validate or troubleshoot an installation of Oracle EPM 11.1.2.0. or 11.1.2.1

Fix

(1) Ziplogs A troubleshooting tool introduced in Oracle EPM 11.1.2.1 is \Oracle\Middleware\user_projects\epmsystem1\bin\ziplogs.bat|.sh file. The output of this is generated in \Oracle\Middleware\user_projects\epmsystem1\diagnostics\ziplogs\EPM_logs_<servername>_11.1.2.1.0.zip Starting with EPM 11.1.2.2 the logs under \Oracle\Middleware\user_projects\domains\EPMSystem\servers\<server>\logs are also collected. 

(2) Oracle Configuration Manager (OCM) is an advanced tool which collects and evaluates settings from configuration files (but not Hyperion Registry) and stores them in a central database administered by Oracle. It was first introduced into EPM in version 11.1.2.0 

(3) Remote Desktop Assistant (RDA) collects and zips up a large amount of information concerning the software and hardware environments of Oracle products. If Perl 5.005 or later is installed on the computer and accessible from the command line (test: perl -version), then run: \Oracle\Middleware\ohs\rda\perl rda.pl from the command line to access the RDA tool. Alternately, precompiled RDA executables are available for several platforms (rda.cmd, rda.sh, rda.bat). View an RDA webcast from the https://oracleaw.webex.com reference site listed below. This tool is frequently updated.

(4) epmsys_registry Configuration settings have been moved from configuration files to a database repository associated with Shared Services. These may be extracted to an HTML formatted file by running \Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat|.sh without parameters from the command line. The output is generated to file \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\registry.html The username/login/jdbc URL for the Hyperion/HSS registry are kept in \Oracle\Middleware\user_projects\epmsystem1\config\foundation\11.1.2.0\reg.properties file. 'epmsys_registry.bat|.sh report deployment' will generate a file named deployment_report.html in the same \reports\ directory starting with EPM version 11.1.2.2.

(5) Validate A validation tool is available in \Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat. In EPM 11.1.2.1 and later the output files are of the form \Oracle\Middleware\user_projects\epmsystem1\diagnostics\reports\instance_report_20YYMMDD_######.html (where YY is the year, MM is the month, DD is the day, and ###### is a unique integer). It also runs the tool under (1) and gives the output of that tool.

(6) Non-ziplog Individual log files may be found in subdirectories under (those 'starred' are not collected by ziplogs prior to EPM 11.1.2.2):

\Oracle\Middleware\user_projects\domains\EPMSystem\servers\<server>\logs *

\Oracle\Middleware\logs *

\Oracle\Middleware\wlserver_10.3 *

\Oracle\Middleware\user_projects\epmsystem1\tmp *

\Oracle\Middleware\ohs\cfgtoollogs\opatch *

\Oracle\Middleware\EPMSystem11R1\diagnostics\logs

\Oracle\Middleware\user_projects\epmsystem1\diagnostics\logs\ 

\Program Files\Oracle\Inventory\logs

C:\Users\<username>\Oracle\oradiag_<username>\diag\

C:\Users\<username>\.oracle\logs\

(7) Client Debug Some debug tools (*) can be activated if under http://<servername>:19000/workspace/index.jsp > Navigate > Administration > Workspace Server Settings > Client Debug Enabled: is set to Yes (then click 'OK' button, close all browser windows, and restart browser).

* http://hostname:19000/workspace/debug/configInfo.jsp

* http://hostname:19000/workspace/debug/userInfo.jsp

* http://hostname:19000/workspace/debug/userGroupQuery.jsp

Other tools are available at these URLs (largely derived from validate.bat output). A non-Error response indicates that the web service of each particular application is active.:

http://hostname:19000/workspace/status

http://hostname:19000/workspace/BPMContext

http://hostname:8600/mappingtool/faces/info.jspx

http://hostname:10080/easconsole/console.html

http://hostname:16000/WebAnalysis

http://hostname:6373/oracle-epm-fm-webservices/ApplicationService

http://hostname:8300/HyperionPlanning/

http://hostname:13080/aps/APS

http://hostname:8200/hr/status.jsp

http://hostname:19091/awb/conf/AwbConfig.xml

http://hostname:8500/calcmgr/index.htm

(8) Enterprise Manager Fusion Middleware is the standard Oracle graphic user interface debugging and configuration tool. Although advanced versions require extra cost licensing, there is a bundled version of Enterprise Manager Fusion Middleware control available by default with EPM.  It is hoped that ECID (Execution Context ID) functionality will be widely incorporated with the 'Hyperion' product stack after EPM version 11.1.2.2. 

(9) registry-cleanup From EPM 11.1.2.2 a new tool has been made available to clean the Hyperion Registry: \Oracle\Middleware\user_projects\epmsystem1\bin\registry-cleanup.bat|.sh.

(10) resetConfigTask From EPM 11.1.2.2 another new tool has been made available to reset configurations: \Oracle\Middleware\user_projects\epmsystem1\bin\resetConfigTask.bat|.sh.

(11) epmsys_hostname checker From EPM 11.1.2.2 another new tool has been made available from the install directory: epmsys_hostname.bat|.sh which confirms the hostname in the network environment.

Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1

Where are Application Install Inventories Stored in Oracle EPM 11.1.2.1

Hyperion BI+ - Version 11.1.2.1.000 and later
Hyperion Essbase - Version 11.1.2.0.00 to 11.1.2.1.000 [Release 11.1]
Hyperion Planning - Version 11.1.2.0.00 to 11.1.2.1.000 [Release 11.1]
Information in this document applies to any platform.

*** Checked for Relevance 24-Sep-2012 ***
Goal
Identify the location of software inventories associated with Oracle EPM 11.1.2.1.
Fix
It is important to know where installation inventory lists are stored: to detect the completeness of an install, to determine whether a patch has been applied, or to delete as part of a reinstall.
\Oracle\Middleware\EPMSystem11R1\oraInst.loc points to the location of the central inventory. oraInst.loc may have been installed in a previous Oracle install on Unix in: /var/opt/oracle or /etc or $HOME (of the user installing Oracle software), preventing the 'reinstall' of OHS or other software.
\Program Files\Oracle\Inventory is typically the location of the central inventory (despite the name 'central inventory', there may exist mutually exclusive inventories generated with the install of other Oracle products). On Unix/Linux the central inventory is in the installer's 'home' directory.
A local inventory is typically found in \Oracle\Middleware\EPMSystem11R1\.oracle.products This file is used to recreate an inventory if need be (but a regeneration of an inventory will exclude service fixes/patches installed via OPatch. To recreate an inventory after one is corrupted...run \Oracle\Middleware\EPMSystem11R1\OPatch\createInventory.bat.)
A local pointer (.oracle.instances) to the instance(s) set by EPM 11.1.2.0 and EPM 11.1.2.1 (and referenced by EPM 11.1.2.1 Installer for 'Apply Maintenance Release' option) is put in C:\Users\<username>\ Ensure the same user installs both versions.
\Oracle\Middleware\ohs\.patch_storage (holds records of previous OPatches)

HyS9FDMTaskManagerSrv

---

Applies to:

Hyperion Financial Data Quality Management - Version: 7.0.0.0.00 and later   [Release: 7.0 and later ]
Information in this document applies to any platform.

Symptoms

When attempting to configure the Task Manager the following error occurs:

"Hyperion FDM Task Manager Configuration. Make sure the windows service named HyS9FDMTaskManagerSrv exists. If not, please reinstall the Task Manager"

Cause

Performing the installation on a Citrix or Terminal Services server without placing the server into install mode prior to performing the installation

Solution

1. Uninstall Financial Data Quality Management (FDM)
2. Place the server in install mode by launching add/remove programs via the control panel. This places the server into install mode 
3. Navigate to the FDM setup executable file
4. Launch the FDM install executable and proceed with the install as normal

How to Migrate an EPMA Planning Application Using LCM

How to Migrate an EPMA Planning Application Using LCM


  Solution

     How to Migrate an EPMA Planning Application Using LCM

     Overview
     I. Exporting from the source environment
     II. Importing to the destination environment
     Appendix A - Workforce Applications
     Appendix B - How to make Local dimensions Shared
     References

Applies to:

Hyperion Planning - Version: 11.1.1.0.00 to 11.1.1.3.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Goal

How to migrate a Planning application that is managed by Enterprise Performance Management Architect (EPMA) using the the Life Cycle Management (LCM) utility.
Solution

LCM offers a means of migrating Planning applications. When these Planning applications are managed in EPMA, both the Planning tier and the EPMA tier of each application must be migrated. This document explains how to do this, and how to avoid issues caused by dependencies between objects.

This guide assumes that you are migrating applications from one environment to another which is the same version. If that is not the case (e.g. migrating an application from an 11.1.1.0 environment to an 11.1.1.3 environment) then LCM is not supported.

A workaround for such situations is discussed in Note 1187985.1.

How to Migrate an EPMA Planning Application Using LCM

Overview

To migrate a Planning application using LCM, three distinct sets of artifacts need to be exported and imported:
The application metadata as it exists in EPMA
The provisioning for this application defined in Shared Services
The artifacts (forms, task lists, etc) which exist in Planning
Note: migration of Essbase data is not covered in this article. Data in Essbase cannot be migrated using LCM, and must be exported and imported in the same way as in earlier versions. See the Essbase documentation for more information.

The application must be migrated following a certain sequence, because of the dependencies between each set of artifacts. For example, the application metadata in EPMA must be imported, and the Planning application deployed, before the Planning artifacts can be successfully imported.

I. Exporting from the source environment

Export the application metadata from EPMA to the file system:

Application Groups > Foundation > EPM Architect > Application Metadata > Planning Applications > Check box for application > Define Migration > Name export file (e.g. 'EPMA_tier') > Execute Migration

Export the application's provisioning from Shared Services to the file system:

Application Groups > Foundation > Shared Services > Native Directory > Assigned Roles > Planning Application Group > Check box for application > Define Migration > Name export file (e.g. MyProvisioning) > Execute Migration

Export the Planning artifacts (web forms, security, etc) to the file system:

Application Groups > Planning Application Group > Application Name > Check boxes for all artifacts > Define Migration > Name export file (e.g. 'Planning_tier') > Execute Migration
Exports are saved to:

%HYPERION_HOME%\common\import_export\\

II. Importing to the destination environment

A. Import EPMA application metadata

The name of the Planning application is embedded in the export files. You cannot change the application's name during import.

If the application does not exist in the EPMA Application Library in the destination environment when the import is run, it will be created. If the application already exists, you are offered the choice of merging or replacing the existing dimensions with those being imported.

Note that all imported dimensions will be imported as Local dimensions, even if they were Shared in the source environment. See Appendix B below for more details.

If this is a new application in the destination environment, create a data source so that the application can be deployed to Planning after being imported to EPMA.

Copy the exported folders from the source environment to the destination environment. Place them in:

%HYPERION_HOME%\common\import_export\\


Note: if you are migrating a Planning Workforce application see Appendix A below before proceeding further.

In Shared Services, import EPMA metadata from the file system to EPMA:

Application Groups > File System > 'EPMA_tier' > Check box for Application Metadata > Define Migration

At this point you can choose to merge or replace existing dimension, decide whether to immediately deploy the application and Rules to Planning after import, and so on. Select the desired options and click Next > Execute Migration.

The application should now be imported to EPMA and be visible in the EPMA Application Library. If you did not choose to deploy to Planning immediately after import, do so now. Validate the application and deploy. If this is a new application, use the data source created in step 1 above.

B. Import Provisioning

In Shared Services, import the provisioning for this application:

Application Groups > File System > 'MyProvisioning' > Check box for Native Directory > Define Migration

At this point you can choose to create or update existing users/groups/roles. Select the desired options and click Next > Execute Migration.

Once the migration is complete, check in Shared Services to make sure that users have indeed been provisioned for the application. If they have not then Planning security (access rights to members, forms, and task lists) cannot be imported correctly.

Log in to the Planning application and navigate to Administration > Manage Database. Check the "Security Filters" option and click the "Refresh" button. The refresh will synchronize the list of provisioned users and groups in Shared Services (imported in the previous step) with the list of users and groups in the Planning relational database. This will allow migration of Planning security in the next step.

C. Import Planning artifacts and security

In Shared Services, import Planning artifacts from the file system to Planning:

Application Groups > File System > 'Planning_tier' > Check all boxes > Define Migration

Select your destination Planning application from the list of available destinations. Click Next > Execute Migration.

Log in to the Planning application and confirm that security has been correctly migrated. To confirm that EPMA, Planning and Essbase are all in sync, deploy the application again from EPMA, refreshing the outline in Essbase as part of the process. If this is successful, the application should be fully migrated and working.

Appendix A - Workforce Applications

If the Planning application being migrated is a Workforce application, you may be unable to validate and deploy the application from EPMA in step A-4 above, and receive an error "unable to find members". This problem does not always occur, and is most common when the Workforce application has been extensively customized.

In such a situation, the migration fails unless a Workforce application with the same properties (Plan Type names, calendar settings, default currency, start year, etc) is already present in EPMA in the destination environment.

The workaround is therefore to create such an application. There are two ways to do this.
Workforce migration workaround - Option 1

Create a classic Workforce application in the destination environment with the same properties as the source application using the classic application creation wizard. Refer to the application in the source environment when selecting the options during application creation, so that you create it with the same options.

If you do not have access to the source environment, you can examine the metadata export files (called 'EPMA_tier' and 'Planning_tier' in the steps above) in a text editor. The metadata is exported in XML format and contains the application properties

Once the application has been created, log into it and initialize Workforce

Using the Application Upgrade wizard (in Workspace, Navigate > Administer > Application Upgrade), upgrade the classic Workspace application to EPMA

Continue from step A-3 in the instructions above, choosing to replace the existing metadata in EPMA.
Workforce migration workaround - Option 2

Create an EPMA Workforce application in the destination environment with the same properties as the source application using the EPMA application creation wizard. Refer to the application in the source environment when selecting the options during application creation, so that you create it with the same options.

If you do not have access to the source environment, you can examine the metadata export files (called 'EPMA_tier' and 'Planning_tier' in the steps above) in a text editor. The metadata is exported in XML format and contains the application properties

The newly created Workforce application will then be deployed

Continue from step A-3 in the instructions above, choosing to replace the existing metadata in EPMA.

Appendix B - How to make Local dimensions Shared

As noted above, all dimensions in an EPMA application that have been migrated using LCM are imported as Local dimensions in the destination environment, irrespective of whether they were Local or Shared in the source environment. This is by design, and cannot be changed.

However, there is nothing to prevent you sharing these Local dimensions again once they have been imported. To do so, follow the procedure below:
Edit the application in the EPMA Dimension Library

Right-click on the Local dimension in the application > Share Dimension

In the options screen, choose to "create a new shared dimension" if the dimension does not already exist in the Shared Library. Choose to "merge as shared" if the dimension already exist in the Shared Library and you want to merge it with the newly imported dimension. Choose to "replace" if you want to replace the dimension in the Shared Library with the newly imported dimension.

Tips for FDM Registering with Shared Services

Tips for FDM Registering with Shared Services

To re-register FDM with Shared Services

Re-register applications with Shared Services

Applies to:

Hyperion Financial Data Quality Management - Version: 11.1.1.0.00 to 11.1.1.1.00 - Release: 11.1 to 11.1
Information in this document applies to any platform.
Purpose

Provide the following tips & tricks for FDM and Shared Services

To re-register FDM with Shared Services
Re-register applications with Shared Services

Questions and Answers

To re-register FDM with Shared Services

Edit the FDM_1_Config.xml file changing the HUB Registration from ‘Configured’ to ‘’
File is located at <HyperionHome>\common\config\9.5.0.0\product\fdm\9.5.0.0\fdm_1_config.xml
<bean name="taskConfiguration">
 <property name="fdmDataConfiguration">Configured</property>
 <property name="hubRegistration">Configured</property>
 <beanList name="preSelectedTasks">
  <listItem>
   <property>fdmDataConfiguration</property>
  </listItem>
 </beanList>
</bean>
<bean name="taskConfiguration">
 <property name="fdmDataConfiguration"></property>
 <property name="hubRegistration"></property>
 <beanList name="preSelectedTasks">
  <listItem>
   <property>fdmDataConfiguration</property>
  </listItem>
 </beanList>
</bean>
Re-launch the EPM System Configuration to re-register FDM with Shared Services.
Start -> All Programs -> Oracle EPM System -> Foundation Services -> EPM System Configurator
Re-register applications with Shared Services

Ensure the FDM application is not listed in Shared Services
Use the <Add Application> function of FDM web to remove the application
http://<servername>/HyperionFDM
Choose <Add Application> from the drop Down
Log In
Highlight desired application & click modify
Note all information on the General & Database tab for future use
Click cancel
Hightlight desired application & click remove
Use the <Add Application> function of FDM web to add the application
http://<servername>/HyperionFDM
Choose <Add Application> from the drop Down
Log In
Click add
Re-create application from noted information from the General & Database tab
On the General tab ensure to select appropriate Shared Services project group
Click OK

How to Automate Financial Management Consolidation Process Using Taskflow Automation

How to Automate Financial Management Consolidation Process Using Taskflow Automation [ID 1109543.1]
		Modified 05-AUG-2011     Type REFERENCE     Status PUBLISHED

In this Document
  Purpose
  Scope
  How to Automate Financial Management Consolidation Process Using Taskflow Automation

---

Applies to:

Hyperion Financial Management - Version: 9.3.1.0.00 to 11.1.1.3.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.

Purpose

This document describes the process to automate a consolidation in Hyperion Financial Management using Taskflow Automation .

Scope

This document is intended for use by Financial Management Administrators and Users that normally execute the Consolidation process manually and are looking for a solution to automate this process.

How to Automate Financial Management Consolidation Process Using Taskflow Automation

Note: To create Taskflows a user must be assigned the Task Automation security role for Financial Management.

The following steps give an example of how to automate the HFM consolidation process using a Task Flow.

  1. Logon to Hyperion Workspace.

       

  2. Open up the HFM application for which the taskflow will be created via Hyperion Workspace.

       

   3. Select the Manage Taskflows option under the Administration menu.

       

  4. Click on the New button to create a new Taskflow.

       

  5. Define the Taskflow being created with Name, Application, and a Description of the process.

       

  6. Enter the name and Description of Task for Stage1 of the Taskflow.
      Select the options for Run As as either the Initiator or fill in the credentials (User Name and Password) for a particular user.

       

  7. Select the Processing Tab

       a. Select the Application you’re configuring the Task to run against.
       b. Select an Action to be performed for this Stage. (The example below is to run a consolidation)

       

       c. Select the POV (Point of View) the consolidation should run against. Type would be URL and then click 'Edit' which will bring up the POV selection window.

       
    
      d. Select the POV for the Scenario, Year, Period and Entity; select OK.
          The URL line will now be filled out with the POV selected for consolidation.
 
       

       e. Select the Type of HFM Consolidation to be run. In this example we have selected. [All with Data]   
  
  8. Select Add Link and update the Link Name and Description.

       


  9. Set the Receiving Stage to ‘End’ to complete the Taskflow.

10. Click Save to save the newly created Taskflow.

11. To run a Taskflow, from the Taskflow Listing Summary page, select the saved Taskflow and click the Run Now button.

       


12. The status page should now show that the Taskflow Initiated successfully.

       

13. To view the status of the running Taskflow you can view it by selecting the View Taskflow Status from the Administration menu.

       

       

Note: Additional HFM processes can be added to a Taskflow by adding additional Stages to the Taskflow, and connecting them by adding Links and setting the Receiving Stage.

Types of HFM processes that can be facilitated by Task Automation are as follows:

Allocate, Calculate, Calculate Contribution, Translate, Consolidate, Load Journals, Extract Journals, Load Data, Extract Data, Execute Journal Action, Extended Analytics, and Process Management.

Attachments  AddLink.jpg (51.17 KB)  DefineTaskFlow.jpg (63.31 KB)  GeneralTaskFlowTab1.jpg (78.88 KB)  LogOnWorkspace.jpg (65.53 KB)  NewTaskFlow.jpg (80.77 KB)  OpenHFMApplication.jpg (74.44 KB)  POV Selection URL.jpg (148.65 KB)  POVSelectionAction2.jpg (108.83 KB)  ProcessingTabTaskFlows.jpg (90.69 KB)  RunTaskFlow.jpg (43.39 KB)  SelectManageTaskFlow.jpg (82.65 KB)  TaskFlowInitiated.jpg (28.3 KB)  TaskFlowStatus.jpg (37.64 KB)  ViewTaskFlowStatus.jpg (23.61 KB)

Financial Management Error "Object doesn't support this property or method" or a Blank Page is Displayed When Clicking Taskflow POV Selector

Financial Management Error "Object doesn't support this property or method" or a Blank Page is Displayed When Clicking Taskflow POV Selector 

Applies to:

Hyperion Financial Management - Version 9.3.1.0.00 to 11.1.1.3.00 [Release 9.3 to 11.1]

Information in this document applies to any platform.

Symptoms

Clicking on 'Edit' link, that allows to select Point of View for Taskflow stage causes following error:

Object doesn't support this property or method. 

line 114 

char 34 

http://servername/hfm/mbrsel/mbrsel.asp?iscontained=Yes

In some cases a blank page without any error message may be displayed.

Cause

Two most common causes of this issue are:

1.       The cluster name used to register the application with Shared Services was different from the one that is now selected in the Taskflow under "Application Name".

2.       User is accessing Workspace using URL different from the one that was used in the "Financial Management Web Server URL for Security Administration" when the application was registered with Shared Services.  

For example HFM application was registered using http://server1/hfm as administration URL, but now user is accessing Workspace using  Fully Qualified Domain Name like http://server1.domain.com/workspace    

This may cause the user's browser to block communication between the Shared Services web application and the Financial Management web server.

Solution

To find which URL was used as "Financial Management Web Server URL for Security Administration" when the application was registered, application instance file should be examined. In all versions of Hyperion Shared Services before 11.1.2, the instance files can be found by accessing the link http://<hss-server>:port/interop/content/. The instance files cannot be accessed this way in EPM System 11.1.2 or higher releases. Instance file information can be found in the EPM System Registry in version 11.1.2. When accessing the above URL user will be prompted to enter a username and password.  It is suggested to enter the username "admin" and the password of the admin user from the Native Directory, as this user is most likely to have the necessary rights.

The application instance files can be found in the folder files > Products > HFM-x.y.z (where xyz is a number corresponding to the version of the HFM product) > Published.

The following information in the instance file is relevant:

<connection type="" description="Hub Callback" protocol="http" server="server1" port="80" uri="hfm" searchable="false" />

<context id="hfm_HFMCluster" path="http://server1:80/hfm/security/" logoffUri="../logon/ProcessLogoff.asp" keepAliveUri="../logon/ping">

<property name="cluster">HFMCluster</property> 

<property name="app">SIMPLE</property>

<AgentURL>http://server1:80/hfm/EIE/CESAgent.asp?Cluster=HFMCluster&Application=SIMPLE</AgentURL>

Parts highlighted in red indicate what servername (and port) was used when registering the application with Hyperion Shared Services, and the server name or cluster name highlighted here in blue indicate what server name or cluster name was used to do the registration. Both of these have to exactly match what is now being used to create the taskflow.  For example http://server1:80 is not the same as http://server1.oracle.com:80

Oracle recommends the use of Fully Qualified Domain Names at all stages of configuring the EPM system.

To check the cluster name being used in the task flow, open the HFM application, access "Administration" -> "Manage Taskflows", edit the taskflow, select the tab "Processing" and verify what cluster or server name appears in the drop down list of next to the application name.

If the cluster name in the instance file and the taskflow application dropdown menu are not the same, or if the Financial Management Web Server URL in the instance file does not match the way the Hyperion Workspace is currently being accessed (short host name vs. Fully Qualified Domain Name) the application will need to be re-registered with Hyperion Shared Services.

CAUTION : Before re-registering an application, customers may like to shut down all EPM services and processes and take a backup of the Hyperion Shared Services relational database schema and OpenLDAP data directory.   Instructions for backing up the OpenLDAP (Native Directory) can be found elsewhere in the My Oracle Support Knowledge Base.  Only proceed with the below steps if you are happy there exists a secure backup of OpenLDAP (Native Directory) and Shared Services relational database.

Use the Workspace menu option  Navigate -> Administer -> Classic Application Administration -> Consolidation Administration -> Register Application and repeat the registration step.   Take care to select the correct cluster/server name and enter the correct URL for "Financial Management Web Server URL". This should normally be in the form of 

http://httpserver.domain.com:port/hfm

if using Apache / Oracle HTTP Server, where "httpserver" is the name of the server hosting Apache or Oracle HTTP Server component of EPM System, that has been configured to allow pass through to the HFM web server.

If the environment has been installed to use Microsoft IIS as the http server in front of workspace, the Financial Management Web Server URL should be "http://", then the fully qualified address of that IIS server followed by "/hfm". No other paths should be entered in this field before clicking "OK" to complete the registration. After the application has been reregistered succesfully, log off and exit the Workspace, close the browser window, launch a fresh browser window and repeat the Taskflow step.

Unable To Login to FDM Application 11.1.2.1 "Error: An Error occurred logging onto the system. -Unable to connect to database.

Unable To Login to FDM Application 11.1.2.1 "Error: An Error occurred logging onto the system. -Unable to connect to database. Please check the database information and verify database is accessible".


Hyperion Financial Data Quality Management - Version: 11.1.2.1.000 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.
Symptoms

When attempting to login to an Oracle FDM Application the following error is returned:

Error: An Error occurred logging onto the system. -Unable to connect to database. Please check the database information and verify database is accessible".
Cause

Currently the oracle 32 bit client is installed on the FDM application server and the 32 bit Oracle Provider for OLE DB is able to connect to the Oracle Database with "Test Connection".  The issue is that the TnsNames.ora file is not currently located in the Oracle Client Home\Network\Admin directory.  FDM looks to this directory in order to establish the connection with the Oracle Database, since the TNSNames.ora file is not in this location, it returns the database connection error.
does not exist and results in the error message returned.
Solution

A) Copy the TNSNames.ora file from the root of the C:\ drive on the FDM Application Server to the <ClientHome>\Network\Admin directory on the FDM application server
B) Test the login to FDM.

SmartView Unable to Connect to the Provider [ID 1376223.1] Hyperion Financial Management - Version 11.1.2.0.00 and later Information in this document applies to any platform. Symptoms When you attempt to connect to Hyperion Financial Management (HFM) in Smart View, the following error occurs: "Unable to connect to the provider." When you try to browse the hfmofficeprovider virtual directory, the web browser returns the error message: Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately. Parser Error Message: Could not load file or assembly 'Oracle.Web, Version=2.111.6.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified. Cause This issue is caused because at some point Oracle Providers for ASP.NET were installed on the HFM Web Server and then uninstalled leaving an orphan entry in the Machine.config file. Solution Open Machine.Config, which is under C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG file in a text editor such as Notepad, and comment out the 'OracleWebEventProvider' section that looks similar to this: Bracket the above section like this: Repeat for all the HFM Web Servers.

SmartView Unable to Connect to the Provider [ID 1376223.1]

Hyperion Financial Management - Version 11.1.2.0.00 and later
Information in this document applies to any platform.
Symptoms

When you attempt to connect to Hyperion Financial Management (HFM) in Smart View, the following error occurs:

"Unable to connect to the provider."

When you try to browse the hfmofficeprovider virtual directory, the web browser returns the error message:

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Oracle.Web, Version=2.111.6.20, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.

Cause

This issue is caused because at some point Oracle Providers for ASP.NET were installed on the HFM Web Server and then uninstalled leaving an orphan entry in the Machine.config file.

Solution

Open Machine.Config, which is under C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG file in a text editor such as Notepad, and comment out the 'OracleWebEventProvider' section that looks similar to this:
<providers>
<add name="OracleWebEventProvider" type="Oracle.Web.Management.OracleWebEventProvider, Oracle.Web, Version=2.111.7.0, Culture=neutral, PublicKeyToken=89b483f429c47342" connectionStringName="OraAspNetConString" buffer="true" bufferMode="OracleNotification" />
</providers>

Bracket the above section like this:

<providers><!--
<add name="OracleWebEventProvider" type="Oracle.Web.Management.OracleWebEventProvider, Oracle.Web, Version=2.111.7.0, Culture=neutral, PublicKeyToken=89b483f429c47342" connectionStringName="OraAspNetConString" buffer="true" bufferMode="OracleNotification" />
-->
</providers>

Repeat for all the HFM Web Servers.