The EPM 11.2.x README (linked above) has been updated for 11.2.7. The software is available on eDelivery for both 64-bit Windows and 64-bit Linux.
I'm in the process of standing up a fresh Windows Server 2019 VM and will share my findings after I get through the Install+Config of EPM 11.2.7. I will be doing it fresh, rather than as an in-place upgrade from a prior release. That exercise will come later.
One of the main things I'm interested in is to see how 11.2.7 handles the October 2021 Oracle Critical Patch Update ("CPU"). In particular... WebLogic. When doing the patch search for the October 2021 CPU, I kept seeing "this patch has been superseded". Grabbing the latest & greatest WebLogic patch actually bricked my 11.2.6 system and so I had to roll back the patch to get things working again.
Hi dave, thank you for your fantastic blog. One questions while I am aournd do we still have to have a unique Instance names such as epmsystem2, epmsystem3, etc. in distrb HA environemts ?ReplyDelete
Hi Sam, thanks for following! In 220.127.116.11 I was a fan of unique instance names such as epm-fnd1, epm-pln1, etc., as determined by the server's role. This was to facilitate vertical scaling if that was needed later on. Vertical scaling is deprecated in 11.2.x, so we're back to the old days of scaling horizontally. In the current 11.2.x world, the last few customer implementations I've either done myself or assisted with used the default epmsystem1 across the board. If vertical scaling returns in the future, I'll change my tune.Delete
So in case the scaling is horizontal no need of having EPMSystem1 on FND1 and EPMsystem2 on FDN2...
Right. Each needs their own unique RCU prefix, but instance names may all be epmsystem1 to keep things easy for your start/stop scripts and such.Delete