One day after my 11.2.4 Initial Thoughts post, I have a near-full-stack online consisting of everything except for Tax and Cost/Profitability. (The customers I've worked with who used those modules were a small slice of my customer population, so elected to go for the "biggest bang for the buck" where my "spare time" is concerned.
(Disclaimer - as of Jan 29, 2021 this post is a rough draft and may contain typos. I'll fix them over the weekend if any are found)
For the most part, standing up Oracle EPM / Hyperion 188.8.131.52 is exactly the same as Releases 184.108.40.206 through 220.127.116.11. Meaning:
- Microsoft SQL Server 2016 SP2 only if you're going the Microsoft route, or Oracle RDBMS through 19c.
- Oracle WebLogic 12c is still behind one "dot" release. Oracle Fusion Middleware ("FMW") 18.104.22.168 versus 22.214.171.124. The Certification Matrix suggests EPM 11.2.4 could work on FMW 126.96.36.199, as it says FMW "188.8.131.52+". This may be a permutation I attempt later after all Unit Testing is complete.
- Windows Server 2016 and 2019 and Linux 7 (RHEL and Oracle's only). Essbase 21c is still limited to Linux 7-8 as of this writing.
- While Essbase 21c is certified for Linux 7 and 8, Essbase 11.2.4 (really 184.108.40.206 behind the scenes) is certified for Windows 2016-2019 and Linux 7 only. Pro tip: if you're going to upgrade, don't use Windows 2012.... Essbase 11.2.4 (220.127.116.11) works on it, but 2012 is coming out of support before you will see a budget approved for another upgrade.
- DRM and HFM still restricted to MS Windows servers only.
- RCU hasn't gone away in 11.2.4 and we still need to deal with it. Click the link to see my posts which mention RCU.
- RCU does not support MS SQL Server when MSSQL is configured for SSL.
- Certain Financial Reporting and EAS Server configurations require manual edits of WebLogic and/or Oracle HTTP Server ("OHS") files. Instructions are contained within the 11.2.4 Release Notes.
- OHS does not get setup as a Windows service. The corresponding Linux pre-delivered startup scripts don't start OHS, either. See my OHS StoreUserConfig post for a reminder on how OHS in 11.2.x (it is OHS 12c in this release) is different from all prior EPM releases going back to over a decade ago.
- Installing OHS under the Foundation node in installTool is deselected by default. You need to manually select it and then ignore the warning message in the bottom pane about a missing "null" folder. It installs just fine.
- Planning RMI still does not bind to its port and you have to apply my RMI Java solution.
- The Java JDK that is bundled with EPM 18.104.22.168 is still over one year old: Java 8 update 181. You need to grab a newer Java 8 from the latest quarterly Oracle Critical Patch Update before your IT department runs a scanner and starts hectoring you about running vulnerable software.
- "Configure Database" step in configTool moved the checkbox that makes all DB entries the same. Instead of being at the top left corner, it is now above the DB Name column. In my testing, clicking that checkbox in an attempt to deselect all rows en-masse did not work. I had to click each row by hand, so that I could make the database/schema names different.
- "Deploy to Single Managed Server" is still the default. But now if you deselect it, deploy Foundation only, and then go back to deploy more things, the option is no longer grayed out. I have not explored this further. I avoid the "Single Managed Server" architecture and someday I'll write a lengthy blog post explaining my rationale. I understand why some folks like it. I don't. To each their own!
- The pre-delivered validate batch file in EPM_INSTANCE/bin produces an HTML report that begins with "EPM Deployment Topology Report (Release 22.214.171.124.0)". This is a typo.
- The EPM Workspace home page is back!!!!