I did a near-full stack implementation in a sandbox for Oracle EPM / Hyperion 184.108.40.206 in Red Hat Enterprise Linux ("RHEL") 7. Essbase, Planning, CalcMgr, Foundation, and EAS all seem to be working fine. HFM of course is not available for Linux at this time.
FDMEE, however, has multiple issues and does not work. In short, Oracle needs to issue a patch. Clarification: this post is about the Linux edition only. The Windows edition does not have these issues.
A patch also needs to be issued for Analytic Provider Services ("APS"). I managed to get it to work by copying over aps.ear from my 220.127.116.11 sandbox. Unfortunately, this solution won't help you if you didn't grab 18.104.22.168 from Oracle eDelivery before it was removed. So Oracle will need to issue a patch for 22.214.171.124 APS as well.
I've downloaded 126.96.36.199 for Windows and will check if that version also has the same issues.
Here's the initial symptom with respect to FDMEE:
I had deployed it to WebLogic and started it. It binds to port 6550 as it should:
- The FDMEE database schema is incomplete; All of the SNP_* tables are missing.
- The WebLogic configuration is completely messed up where FDMEE ("ErpIntegrator" as WebLogic calls it) is concerned.
I had to do quite a bit of "surgery". At this point, 2 of 3 problems as previously reported by the validate.sh utility are now fixed.
Let's first address fixing the lack of SNP_* tables in the FDMEE database schema. When we run the "Configure Database" task for FDMEE, here's what happens behind the scenes. We can reproduce the issue at will by running the back-end utility manually.
Side note: I edited the utility to add echo statements for "Finished XYZ" so I could see which step was throwing the Java stack trace error.
The assertion that the supervisor password is blank is not true. The script follows the same format used in 188.8.131.52, whereby Supervisor's userid and password are encrypted and hard-coded within the script.
This is not an issue in 184.108.40.206, 220.127.116.11 and 18.104.22.168. While 22.214.171.124 and 126.96.36.199 are no longer available for download from Oracle eDelivery, I downloaded both releases when they were available, and I have an 188.8.131.52 sandbox online for reference purposes.
In crawling through the various jar files in 184.108.40.206, I found the offending class oracle.odi.setup.suppoort.MasterRepositorySetupImpl is located within Middleware/odi/sdk/lib/odi-core.jar.
When comparing 220.127.116.11 Linux vs. 18.104.22.168 Windows, I found size and timestamp mis-matches between the two systems.
22.214.171.124 Windows: 29,222,611 bytes dated Feb 1, 2020
126.96.36.199 Linux: 29,032,586 bytes dated Aug 22, 2017
So I backed up Middleware/odi/sdk in 188.8.131.52 and then copied over the whole directory structure from 184.108.40.206. Re-ran the utility in my screenshot above, and now all of the SNP_* tables are present.
So in the EPM 220.127.116.11 Linux installer, the subdirectory "odi" is apparently packaged incorrectly and we need a patch for that.
My follow-up post concerns a myriad of problems within WebLogic.