Hyperion Profitability and Cost Management (HPCM) FAQ’s


FAQ #1: Having issues deploying the Essbase cube, any suggestions?
By default, Profitability and Cost Management uses APS mode to connect to Essbase, and APS uses many TCP ports while deploying the Essbase cubes. This situation may cause a network error which is displayed in the Profitability and Cost Management log file. If this error occurs, switch the Connection Type to embedded mode, and redeploy the cube.

To set the Connection Type to Embedded mode:

1. In Profitability, from Task Areas, select Manage Model, then Model Summary.
2. On the Model Summary screen, select the Model Level Preference tab.
3. Under Essbase Information, select embedded from the Connection Type drop-down list.
4. Click the Save icon.

FAQ #2: Changed to ’embedded’ but am still having issues deploying the Essbase Cube…
Seeing errors such as “Network Error” or “Unable to connect” in the logs, or if the cube deployment fails in embedded mode, or if using APS mode, modify the Windows registry TCPIP parameters – TcpTimedWaitDelay and MaxUserPort – as recommended by the Windows Operating System documentation.

To improve the ability of the Windows operating system to deal with a high rate of network connections:
1. From the Windows Registry, navigate to KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TCPIP\Parameters
2. Add or modify the following registry entries
TcpTimedWaitDelay – Set this to a low value (for example, 30) for the sockets to be released quickly. This DWORD value ranges between 30-300.
MaxUserPort – Set this to a high value (for example, 33000) to increase the total number of sockets that can be connected to the port. This is a DWORD value.
FAQ #3: How do I change the level of logging in HPCM?

By default, Profitability and Cost Management sets the logging level to ‘INFO’. Changing to ‘Debug’ will provide a greater level of detail; however, be aware that the log files will be much larger.
To change the logging level to Debug, edit the file for your configuration:
For Typical Installs:

1. Locate the log4j.properties file: %HyperionHome%\deployments\Tomcat5\Profitability\webapps\profitability\WEB-INF\classes\log4j.properties
2. Edit the following line. Change the log4j.logger.com.hyperion.profitability=INFO, HPMLOGFILE, CONSOLE to log4j.logger.com.hyperion.profitability=DEBUG, HPMLOGFILE, CONSOLE
For OAS, Websphere, Weblogic Installs:
1. Navigate to the folder where HPCM is installed and look for the following path: Profitability\webapps\profitability\WEB-INF\classes\log4j.properties
2. Edit the following line. Change the log4j.logger.com.hyperion.profitability=INFO, HPMLOGFILE, CONSOLE to
log4j.logger.com.hyperion.profitability=DEBUG, HPMLOGFILE, CONSOLE
FAQ #4: Reporting Cube won’t deploy, what should I do?
The use of shared hierarchies in business dimensions will not work properly as EPMA does not allow the “Alternate Hierarchy Enabled” property to be set. Do not use alternate hierarchies in the business dimensions.

Other things to look for include:

1. Check to ensure that the ‘NoMember’ member is last and set to consolidation = ‘ignore’ or ‘~’ and the dimension root member Data Storage property is set to ‘Label Only’.
2. Check to ensure that no shared members exist under the first Gen2 child
If there are shared members under the second or later Gen2 members:

Check to make sure the root dimension has the Hierarchy Type property set to ‘Enabled’
Check to make sure the first Gen2 hierarchy has the Hierarchy Type property set to ‘Stored’
Check to see that the Gen2 member that is the ancestor of the shared member has the Hierarchy Type property set to ‘Dynamic’

FAQ #5: Are there any hardware recommendations for HPCM?

There are plenty of factors that should be weighed before making a suggestion. There is no set hardware recommendation. It would be on a case by case basis.
FAQ #6: What is the best way to get started on an HPCM project?
HPCM projects require proper consulting. Software installation and configuration should be performed by an administrator familiar with working in the Hyperion technology stack.
FAQ #7: The HPCM logging mechanism:
By default, Profitability and Cost Management sets the logging level to ‘INFO’.
Changing to ‘Debug’ will provide a greater level of detail; however, you will need to be aware that the log files will be much larger.

To change the logging level to Debug, edit the file for your configuration:
For Typical Installs:

1. Locate the log4j.properties file: %HyperionHome%\deployments\Tomcat5\Profitability\webapps\profitability\WEB-INF\classes\log4j.properties
2. Edit the following line. Change the log4j.logger.com.hyperion.profitability=INFO, HPMLOGFILE, CONSOLE to log4j.logger.com.hyperion.profitability=DEBUG, HPMLOGFILE, CONSOLE
For OAS, Websphere, Weblogic Installs:

1. Navigate to the folder where HPCM is installed and look for the following path: Profitability\webapps\profitability\WEB-INF\classes\log4j.properties
2. Edit the following line. Change the log4j.logger.com.hyperion.profitability=INFO, HPMLOGFILE, CONSOLE to log4j.logger.com.hyperion.profitability=DEBUG, HPMLOGFILE, CONSOLE

Thanks,
~KKT~

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s