Oracle EPM 11.1.2.3 in Windows 2012 Server - Installation and configuration

Oracle EPM 11.1.2.3 in Windows 2012 Server - Installation and configuration

"We had come across a situation where we did not get any Windows server other than 2012 and temporarily we had to install Oracle EPM 11.1.2.3 including HFM in 11.1.2.3 in that server. This was a temporary environment with Classic option of HFM."

Now the question is: Does Windows 2012 Operating System or OS is supported for Oracle EPM 11.1.2.3 or HFM (Hyperion Financial Management) 11.1.2.3?

It is certain that, it is not certified, but is it is supported?

During our exercise I have  evaluated and found that is supported but not certified.

Is this straight forward like any other installation?

The answer is, No.

What we have to do differently if we want Windows 2012 OS for Oracle EPM 11.1.2.3 for Oracle EPM and Classic HFM?

If you follow standard Oracle EPM installation and configuration everything else will work except HFM Web.

• Ensure ASP and ASP.net is enabled in IIS
• EPM Configurator will fail and four IIS Application for HFM will not be created.

            o  Financial management web application - hfm
            o  Smart view Provider - hfmofficeprovider
            o  Lifecycle Management - hfmlcmservice
            o  Financial Management Web Services - hfmapplicationservice

• Create the IIS Application pool for each of the four above IIS Application
• Add each of them . Use the same folder that comes during the configuration

Once all the above steps are done, Oracle EPM including Classic HFM will work properly. Use IE9 or IE11 in Enterprise mode unless you have reached 700 patch level.

In order to use EPMA, EPM registry need to be updated with the information that HFM Web configuration has been completed successfully along with its correct property value.

Upgrade Oracle EPM - Hyperion Financial Management Upgrade - Upgrade HFM from old release (i.e. 11.1.2.3) to new release 11.1.2.4

Upgrade Oracle EPM - Hyperion Financial Management Upgrade - Upgrade HFM from old release (i.e. 11.1.2.3) to new release 11.1.2.4

Requirement:

1. Need a simple HFM upgrade where minimum 7 years of historical data will be migrated along with their numbers verification.
2. Minimum cost and duration

Always there is fight which one to chose between In place (existing servers) vs. out of place (new servers). There is many writing including Oracle Document, have almost forced everyone that there is no other was than applying maintenance release on top of old version of environment. But this is certainly not the only option rather the costliest risky option.

I will never encourage my customer to follow this technique. I have got an opportunity to upgrade two HFM application from 11.1.2.3 to 11.1.2.4.101. Applying HFM 102 patch is in progress.

While discussing the available options I could not resist to say to my customer why not "Put the old liquor in a new bottle." My Scottish customer immediately had show a positive response on my recommendation.

Here I am discussing what I had proposed during  that time. Yes, I have successfully executed what I am saying here. We have got support from Oracle on few of ICT related issues (read BUG) after our upgrade in Oracle EPM / Hyperion Financial Management 11.1.2.4. I hope you have understood what I meant to say here.

"Hyperion Financial Management 11.1.2.4 can be upgrade from earlier release using old CopyApp utility."

Following are the high level steps:

1. Log into Old version HFM server and create new UDL to point new 11.1.2.4 version HFM schema.
2. Execute CopyApp and copy existing application along with data and audit data. Audit data is optional.
3. Update HFM DSN for the newly copied HFM Application
4. Launch EPM 11.1.2.4 Configuration Utility and upgrade 11.1.2.4 version HFM schema using Configuration Utility

          5. Register the HFM Application and do the provisioning. 

          6. Old version application is upgrade to 11.1.2.4 and all signed off data are in same status. A quick high-level reconciliation can be performed to sign off the migration.

Benefit we have received:

1. Post upgrade the application data reconciliation was 100% correct and there was not a single data issue
2. All the former sign-off was already in place
3. Consolidation for past data was never required to be executed, though for checking purpose last 2 year data was consolidation to build confidence in the new upgraded application in UAT environment. That test was also successful.
4.  As-Is rule have seen a performance gain around 20%
5. A separate CR was kicked of to convert few  Member List loops to Data Unit in rule file. Post Data Unit implementation the consolidation time was reduced to 30 minutes compared to 1 Hour 20 Min in old version.  (16 thousand lines of Rule was there in the rule file)

Oracle EPM - Hyperion Financial Management - Upgrade Options and Recommendation for version 11.1.2.4

Oracle EPM - Hyperion Financial Management - Upgrade Options and Recommendation for version 11.1.2.4

Upgrade Options and Recommendation

Two methods: In place (existing servers) vs. out of place (new servers)

Note: In place upgrade is also known as a “maintenance release”

In place upgrades do not allow you to make other system-wide changes:

•         No server operating system updates

o   On July 14th, 2015 Windows 2003 will have all support end –this includes mainstream and extended support

•          I.T. departments are forced to move forward with a new platform or face security risks

o   On January 13th, 2015 Windows 2008 saw mainstream support expire

•          Only security updates until January 14th, 2020

o   Version 11.1.2.4 enabled Windows 2012 support so upgrading the OS and EPM together makes sense

• When you perform an in place upgrade, you lose the ability to upgrade hardware
• Performance issues are generally not solved by upgrading your software
• This is not as important with virtualized configurations
• You will not be able to restructure your environment
• Unable to solve performance issues
• Looking to add a new product (FCM, Planning, etc.)
•          Oracle is not good at cleaning up after itself
•          Old applications and data are left behind
•          Upgrading to 11.1.2.4 will leave FDM classic intact!
•          Shared Services database often has incorrect data remaining that can cause issues down the road
• Running an in place upgrade on production means bringing down the environment for an extended period of time

o   Risky

o   No opportunity to do proper UAT and data reconciliation

• Version 11.1.2.4 had consolidation engine rebuilt to support Linux –you will want to tie out your data

For all of these reasons, it is always advised to go for Fresh Installation than in place upgrade.

I am sounding the same voice that Finit Solution has already said.

An approach to backup and restore Essbase Application using traditional file system backup

An approach to backup and restore Essbase Application using traditional file system backup

"...few year back during a server name change for an Essbase server due to a crash that could not be restored, several finding was made to know the alternates to restore Essbase from file system backup. Every time I say this is still in conceptualization stage. But it should work even in 11.1.2.4..."

Abstract— This document discusses a method to accomplish Essbase Application backup without logging into the application and bypassing the traditional data export method in either levels.
This document also focusses on the possible benefits and concerns associated with this method.

Keywords: Essbase, Oracle EPM 11.1.*, Essbase Backup, Essbase File system

The white paper is still available. Incas anyone want to read.

techrepublic still hosts the white paper since 2013. techrepublic link