Wednesday, June 20, 2018

SSL TLS 1.2, OHS, and... Calculation Manager???

With more and more folks migrating Oracle EPM / Hyperion from on-premises data centers to 3rd-party hosted environments, the topics of Secure Socket Layer ("SSL") and support for TLS 1.2 are becoming much more common conversations.

The devil, of course, is in the details.

As a matter of policy, many 3rd-party hosting companies and/or IT departments are disabling SSL protocols 2.0, 3.0, TLS 1.0, and TLS 1.1 by default.  Security vulnerabilities for those older protocols are to blame.  This leaves us with TLS 1.2 as the preferred option for SSL.

The problem, though, is EPM uses Oracle HTTP Server ("OHS") under the covers, and guess what?  OHS cannot support any TLS protocol higher than version TLS 1.0.

But wait!  Isn't EPM certified by Oracle to use Microsoft IIS 8.5 as the web proxy, which supports TLS 1.2?  Yes, indeed it is.  But, the SSL configuration documentation for EPM is OHS-centric;  the IIS-related matters are incomplete and several important configuration details are missing in various blogs and Knowledge Base articles.  (Case in point: manual edits required for iisproxy.ini are completely missing in the EPM-centric documentation currently available as of this writing).

This brings us to the Oracle Knowledge Base article named "How To Update OHS In EPM System To (Doc ID 2406726.1)"

This article provides steps on how to perform an in-place upgrade from OHS to for EPM  Oracle certifies that OHS supports the TLS 1.2. SSL protocol.  The procedure to upgrade OHS is easy to follow.

But, there's a catch, and this is the point of today's blog post.

OHS and Hyperion Calculation Manager do not play well together!  After applying the OHS in-place upgrade, attempting to login to Calculation Manager results in a blank tab in EPM Workspace.  There are no blog posts or Knowledge Base articles on how to fix this.... until now!

The fix is buried within the release notes for the EPM Shared Services patch

Open a command prompt and CD to your Oracle EPM Instance home's \bin folder on any of your Hyperion servers.  The default location for this is D:\Oracle\Middleware\user_projects\epmsystem1\bin for most Microsoft-based systems.   UNIX nerds like me; you know the drill!  (Swap the direction of the slashes)

Paste this command:

epmsys_registry addProperty /CALC_MANAGER_PRODUCT/@BINDOWS_ENABLED true  

Then restart your Calculation Manager service, and you're good to go.

What you've just done is you went back in time to the days and instructed Calculation Manager that it should not use the Application Development Framework ("ADF") interface, which apparently OHS has an issue with.

Hopefully, Oracle will use a future patch to remediate this.  But for now, carry on and be safe out there!