How to Create a New Hyperion Financial Management (HFM) Cluster and Configure Access From Workspace


General Information

yperion Financial Management (HFM) allows for the grouping of one or more HFM application servers behind a “friendly” cluster name. Advantages of using an HFM cluster over an explicit HFM application server by name is that the HFM cluster allows you to add and remove servers without end users having to make any changes. When more than one HFM application server is added to an HFM cluster, new user sessions randomly pick one of the HFM application servers to connect. If the HFM application server that was randomly selected is currently not online the then user session automatically directed to another HFM application server. HFM clusters do not allow for automatically failover of active user sessions. When a user makes multiple connections to an application using an HFM cluster, Sticky Server feature ensures that all user sessions are directed to the same HFM application server.

HFM allows for creating more than one cluster to allow for specific HFM application server(s) be accessed by specific users. The most common configuration uses 2 HFM clusters. The first HFM cluster is accessed by the majority of users to run reports, data grids and smart view and the second HFM cluster is used primarily by HFM application administrators to run consolidations. Most new installations will start off with a single HFM cluster. The need for a dedicated consolidation server usually arises when end users notice slower running reports or longer running refreshes while consolidations are running. Depending on how many HFM application servers exist in the current HFM cluster, a second HFM cluster can be created by moving a existing server(s) or by adding new HFM application server(s) to a second HFM cluster.

Important points to be aware of

  • You cannot choose which HFM application(s) run on a specific HFM application server or HFM cluster. All HFM applications defined in the database repository, that the HFM application server is configure to access, can run on that server.
  • You cannot prevent a user from accessing a specific HFM application server or HFM cluster.
  • All HFM applications servers in a HFM cluster must point to the same database schema. In System 9 this is configured manually in the UDL file and in System 11 the database connection string is configured in the EPM System Configurator.
  • If the goal is to separate HFM applications and limit which HFM applications run on which HFM application servers then you must configure HFM application server(s) or cluster(s) to access a different schema. This document will primarily focus on accessing the same HFM application from different HFM clusters from Hyperion Workspace but a brief explanation is also included to explain accessing different HFM applications that reside in different HFM clusters from Workspace.

In the case of adding a second HFM cluster to an existing environment, if an existing HFM application server is to be moved to the new cluster it must first be removed from the existing cluster. HFM application server can belong to only one cluster at a time.

Steps for removing an existing HFM application server from a HFM cluster

System 9

  1. On any HFM application server, run the Server and Web Configuration utility. This can be done on any HFM application server as these updates occur in the database.
  2. Select the Application Server Cluster tab.
  3. In the Servers that will participate in the Cluster window, select the server to be removed.
  4. Select Remove Server.
  5. Select Apply.
  6. Select OK to close utility.

System 11

  1. On any HFM application server, run the EPM System Configurator utility. This can be done on any HFM application server as these updates occur in the database.
  2. Under Financial Management, put a check next to Configure Application Cluster.
  3. Select Next.
  4. On the Configure Financial Management – Server /Cluster screen, select the server to be removed from the cluster under Servers in Cluster.
  5. Select Remove.
  6. Select Next.
  7. Select Next.
  8. Select Finish to close utility.

Steps for creating a new HFM cluster and adding a HFM application server

System 9

  1. On any HFM application server, run the Server and Web Configuration utility. This can be done on any HFM application server as these updates occur in the database.
  2. Select the Application Server Cluster tab.
  3. Select Add Cluster.
  4. Type in a Cluster Name.
  5. Select OK.
  6. Select Add Server.
  7. Enter the Hostname of the HFM application server.* Do not use Fully Qualified names here as Sticky server feature will not work – Unpublished Bug 7704770.
  8. Select OK.
  9. Select Apply.
  10. Select OK to close utility.

*Note that there is no validation here so if you incorrectly type the server name you will not be able to register this new cluster.

System 11

  1. On any HFM application server, run the EPM System Configurator utility. This can be done on any HFM application server as these updates occur in the database.
  2. Under Financial Management, put a check next to Configure Application Cluster.
  3. Select Next.
  4. On the Configure Financial Management – Server /Cluster screen, select Add.
  5. Type in a Cluster Name.
  6. Select OK.
  7. Under Available Servers, select the server to be added to new HFM cluster. **
  8. Select Add
  9. Select Next.
  10. Select Next.
  11. Select Finish to close utility.

**Only HFM application servers that have been previously registered to Hyperion Foundation will appear under Available servers.

Steps for making new HFM cluster available to Workspace users

System 9

  1. On each HFM Web servers, run the Server and Web Configuration utility.
  2. Select the Server/Cluster Registration tab.
  3. Ensure the Use Automatic Load Balancing radio button is selected.
  4. In the field, type in the hostname of HFM application server belonging to the cluster you want to add. If the HFM cluster has more than one HFM application server then you can type in any of the server hostnames.
  5. Select Add.
  6. Select Apply.
  7. Select OK to close utility.

System 11

  1. On each HFM Web server, run the EPM System Configurator utility.
  2. Under Financial Management, put a check next to Register Application Servers / Cluster.
  3. Select Next.
  4. On the Register Financial Management – Server /Cluster screen, select the HFM cluster under Available Servers / Clusters.
  5. Select Add.
  6. Select Next.
  7. Select Next.
  8. Select Finish to close utility.

Steps for users to configure to access new HFM cluster

Which HFM application server or HFM cluster an HFM application opens on when a user selects the application is not directly visible to users. Unless a user follows the steps provided below to set an Application Startup Preference, the HFM application will open on the last HFM server or HFM cluster that the HFM application was registered against. In most cases, this is the same HFM server or HFM cluster that they HFM application creator specified when creating the HFM application. In the event that you find an HFM application not opening on the expected HFM cluster, you can re-register the HFM application at anytime without having to restart. See the section below on Steps to change where HFM application opens by default from Workspace for steps on changing the default HFM cluster. For users that need to access an HFM application on an HFM cluster that is not the default follows the steps outlined below. Note that this must be done on a per user basis and is also a per HFM application setting.

Setting Preference for HFM application startup

  1. For Workspace File Menu, select Preferences.
  2. On the left side, select Consolidation.
  3. Under List of Applications, select the down arrow to return all HFM applications available.
  4. Select an HFM application.
  5. Under List of Clusters, select down arrow to return list of all available HFM servers and HFM clusters. If you do not see the HFM Cluster expected then see the section above on Steps for making new HFM cluster available to Workspace users to register the HFM cluster on all HFM Web servers.
  6. Select Save.
  7. Select OK to acknowledge the warning prompt that re-login is necessary.
  8. Select OK to close Preferences.
  9. Log out of workspace for change to take effect.

Steps to change where HFM application opens by default from Workspace

The following can be skipped if the existing HFM cluster is known to be working correctly.

To register a Classic System 9 HFM application from Workspace

  1. From the Navigate menu select Administer.
  2. Select Classic Application Administration.
  3. Select Consolidation Administration.
  4. In the left hand side, expand Tasks.
  5. Expand Consolidation Administration.
  6. Select Register Application.
  7. At this point you will see a list of HFM servers and HFM clusters, you only see what has been registered on the HFM web server. If you do not see the HFM Cluster expected then see the section above on Steps for making new HFM cluster available to Workspace users to register the HFM cluster on all HFM Web servers.
  8. Select the HFM cluster you want to be the default. This would be the HFM cluster you want users without a Preference set to access when logging in to Workspace.
  9. Select the HFM application.
  10. Verify the entry in Cluster/Server Name field points to the correct HFM Cluster.
  11. Set the User Management Project to the correct project. This should be the same as originally set and can be verified by finding the application under Projects in the Hyperion Shared Services Console.
  12. Verify Financial Management Web Server URL for Security Administration points to the correct location, this point wither to http://<workspace&gt;:<port>/hfm or to http://<HFM_WebServer>/hfm.
  13. Select Register.

To register a Classic System 11 HFM application from Workspace

  1. From the Navigate menu select Administer.
  2. Select Classic Application Administration.
  3. Select Consolidation Administration.
  4. Select Register Application.
  5. At this point you will see a list of HFM servers and HFM clusters, you only see what has been registered on the HFM web server. If you do not see the HFM Cluster expected then see the section above on Steps for making new HFM cluster available to Workspace users to register the HFM cluster on all HFM Web servers.
  6. Select the HFM cluster you want to be the default. This would be the HFM cluster you want users to access when logging in to Workspace.
  7. Select the HFM application.
  8. Verify the entry in Cluster/Server Name field points to the correct HFM Cluster.
  9. Set the User Management Project to the correct project. This should be the same as originally set and can be verified by finding the application under Projects in the Hyperion Shared Services Console.
  10. Verify Financial Management Web Server URL for Security Administration points to the correct location, this point wither to http://<workspace&gt;:<port>/hfm or to http://<HFM_WebServer>/hfm.
  11. Select Register.
Advertisements

Hyperion Financial Management (HFM) – Usage of JOM API “VALIDATECUSTOMMEMBERS” Produces “Socket Connection Error”


This is to tuning of HFM for those who have customizations and use the JOM API “VALIDATECUSTOMMEMBERS.”

If this API is called from the customer’s customization program too frequently (for example: 2-3 times a second) repeatedly, then you will encounter a “Socket Connection Error“.

Please note that HFM as a product will not encounter it; but when FDMEE calls our API (or a customer writes custom code that calls our JOM APIs), the users should be aware of this and make the recommended updates to the registry.

In order to avoid the error, please apply the following registry settings. A restart is required.

  • [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters]

“MaxUserPort”=dword:0000fffe

  • [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

Value Name: TcpTimedWaitDelay
Value Type: DWORD
Data: 30 (decimal)

Hyperion Financial Management (HFM) Metadata Load Is Very Slow


Loading Metadata to Hyperion Financial Management (HFM) application takes very long time.

During the metadata load when entity hierarchy is changed (members are moved, added or deleted) HFM has to verify calculation status for each scenario – year combination.

On HFM application server add the following Windows Registry Entry to use multiple processor threads instead of single thread to verify and update calculation status:

 HKEY_LOCAL_MACHINE\SOFTWARE\Hyperion Solutions\Hyperion Financial Management\Server
Value: NumThreadsToUseWhenUpdatingCalcStatusSystemWasChanged
Type: DWORD
Data: 1 (Decimal) (Default setting)

The maximum value for this setting is 8. After increasing this setting memory useage should be monitored, especially on 32-bit systems

Smart View Error “Provider Is not Shared Services Provider” When Using Shared or Private Connections


When using shared or private connections in SmartView the following error message is displayed:

Provider is not Shared Services Provider.

There are two possible causes for this issue:

  • Internet explorer timeout
  • Internet explorer proxy settings where the server needs to be added to the exception list

To prevent timeout issues, add modify Windows Registry on the client workstation where Smart View is installed:

  1. Open Windows Registry editor.
  2. Navigate to
    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings]
  3. Add the following values:
    “ReceiveTimeout”=dword:001b7740
    “KeepAliveTimeout”=dword:001b7740
    “ServerInfoTimeout”=dword:001b7740

If issue is related to proxy settings do the following:

  1. Open Internet Explorer
  2. Open menu Tools > Internet Options > Connections > LAN Settings > Proxy server > Advanced
  3. Add the server to the proxy exception list and save changes.
  4. Close IE and reopen

Thanks,

~KKT~

Calculation Manager Error “Internet Explorer cannot display the webpage” When Accessed Via Workspace


The fix is to just comment the line wlproxyssl in the file mod_wl_ohs.conf as follows:

1) Navigate to: Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\config\OHS\ohs_component\mod_wl_ohs.conf
2) Comment the line WLProxySSL ON
#WLProxySSL ON
3) Save/close
4) Restart OHS and workspace

Thanks,

~KKT~

How to Fix the Planning RMI Port to Permit Connection through Firewall


RMI connections to Planning are initiated on the common RMI Port (11333 by default) but are then redirected to a random port within a dynamic range. This can cause issues when the connection is made through a firewall, as the entire range of ports must be opened.

To avoid this, you can bind Planning to a particular port instead of the default dynamic port range.

  1. Confirm which common port RMI is using by checking the following file on the Planning server:

    \Hyperion\common\RMI\1.0.0\HyperionRMI_Port.properties

    In most cases this will be set to 11333.

  2. Log into any Planning application with an administrator user. Navigate to Administration > Manage Properties > System Properties. Click the “Add” button and add the following two rows (click “Add” again after you add the first row):

    Property Name:        Property Value:
    =====================================
    COMMON_RMI_PORT                 11333
    PLANNING_RMI_PORT               11444

    You can set any port you like for the PLANNING_RMI_PORT, as long as it is not in use. The COMMON_RMI_PORT must be the same as that determined in step 1.

  3. Click “Save” at the bottom of the screen.
  4. Restart the Planning and the RMIRegistry services.

Connections to Planning via RMI will now be made initially on port 11333 and traffic then redirected to port 11444. As long as these two ports are open in the firewall other products such as Hyperion Application Link (HAL), Oracle Data Integrator (ODI) or Data Integration Manager (DIM) should be able to connect.

Thanks,

~KKT~

Common Issues Using Hyperion Planning after Upgrade to Planning 11.1.2.4


1.  Planning cannot be accessed via Workspace and the following error is found in the Planning_WebApp.log file:
Servlet failed with Exception
java.lang.RuntimeException: Your session has timed out or was terminated by the application owner or an administrator. Please log on again.

2. Forms Folder cannot be expanded

3. No forms are visible in the Planning application

4. Attempting to export Planning applications using LCM results in the following error:
Source: APPNAME (Application) Destination: HP-APPNAME (File System)
EPMLCM-14000: Error reported from Hyperion Planning.
/Configuration/Adhoc Options:- Error loading objects from data source: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]The multi-part identifier “o1.object_id” could not be bound.
/Relational Data/Tablet Access:- Error loading objects from data source: java.sql.SQLException: [FMWGEN][SQLServer JDBC Driver][SQLServer]The multi-part identifier “o1.object_id” could not be bound.

 

Reason- The required ADF patches for 11.1.2.4 have not been applied. These should be installed during the upgrade by the system

To Fix-

The solution is to install the ADF Patches manually on the Planning server
The patches are: 16964825, 18514458 and 20326778

Assuming EPM is installed to E:\Oracle\Middleware
Edit E:\Oracle\Middleware to your specific location in all instructions below

Check which ADF Patches are applied:

1. Open Command Prompt.
2. CD to E: drive
3. run E:\Oracle\Middleware\EPMSystem11R1\OPatch\opatch.bat lsinventory -oh E:\Oracle\Middleware\oracle_common -jdk E:\Oracle\Middleware\jdk160_35 | findstr -i applied

Roll back any patches you find applied:

1. Stop All EPM Services on the Planning server
2. Open command prompt
3. CD to E:\Oracle\Middleware\oracle_common\OPatch
4. run opatch rollback -id 123456 -oh E:\Oracle\Middleware\oracle_common -jdk E:\Oracle\Middleware\jdk160_35

Apply the new ADF patches:

1. Stop All EPM Services on the Planning server
2. Open command prompt
3. CD to E:\Oracle\Middleware\oracle_common\OPatch\Patches\16964825
4. run E:\Oracle\Middleware\EPMSystem11R1\OPatch\opatch apply -oh E:\Oracle\Middleware\oracle_common -jdk E:\Oracle\Middleware\jdk160_35

5. CD to E:\Oracle\Middleware\oracle_common\OPatch\Patches\18514458
6. run E:\Oracle\Middleware\EPMSystem11R1\OPatch\opatch apply -oh E:\Oracle\Middleware\oracle_common -jdk E:\Oracle\Middleware\jdk160_35

7. CD to E:\Oracle\Middleware\oracle_common\OPatch\Patches\20326778\oui
8. run E:\Oracle\Middleware\EPMSystem11R1\OPatch\opatch apply -oh E:\Oracle\Middleware\oracle_common -jdk E:\Oracle\Middleware\jdk160_35

9. Start All EPM Services

Hope this will help.

Thanks,

~KKT~

ESSBASE: Using Environment Variables in an Essbase Calculation Script


In order to use environment variables in an Essbase calc script, the variables need to be set in the opmn.xml file and on Unix, at the operating system level.

Windows:

1. Create a directory where you want the exported file to go, for example D:\Data.

2. Add the environment variable to the /Oracle/Middleware/user_projects/epmsystem1/config/OPMN/opmn/opmn.xml file:

<variable id=”ENVFILE” value=”D:/Data/newexport.txt”/>

3. Stop/Start the Essbase service.

4. Test using the calc script taken from Essbase Database Administration Guide, run against Sample/Basic:

SET DATAEXPORTOPTIONS
{
DATAEXPORTLEVEL “ALL”;
DATAEXPORTOVERWRITEFILE ON;
};
FIX (“New York”, “100-10”);
DATAEXPORT “File” “,” $ENVFILE;
ENDFIX;

If the Sample applications were not installed, test using one of your databases.

 

UNIX:

1. Create a directory where you want the exported file to go, for example /u01/EPM/epmadmin/Data.

2. Add the environment variable to users login script, usually .bashrc or .profile, replacing with your pathing information:

ENVFILE=”/u01/EPM/epmadmin/Data/newexport.txt”
export ENVFILE

3. Add the environment variable to the /Oracle/Middleware/user_projects/epmsystem1/config/OPMN/opmn/opmn.xml:

<variable id=”ENVFILE” value=”/u01/EPM/epmadmin/Data/newexport.txt”/>

4. After making the changes, log out of the Unix system and log back in for the new environment variable to take effect.

5. Stop/start Essbase to load the opmn.xml changes.

6. Confirm the setting is correct at the Unix level:

echo $ENVFILE
/u01/EPM/epmadmin/Data/newexport.txt

7. Test using the calc script taken from Essbase Database Administration Guide, run against Sample/Basic:

SET DATAEXPORTOPTIONS
{
DATAEXPORTLEVEL “ALL”;
DATAEXPORTOVERWRITEFILE ON;
};
FIX (“New York”, “100-10”);
DATAEXPORT “File” “,” $ENVFILE;
ENDFIX;

If the Sample applications were not installed, test using one of your databases.