This has become a pesky issue for me when I was trying out the latest version of Hyperion suite (EPM 11.2.0) from Oracle. Having installed and worked on pretty much every version of Hyperion since the famed 9.3 release, I found it frustrating when the very last step in the configuration process, where we get the HTTP server to listen on the standard port 19000 didn’t work.
A bit of internet search for similar issues sent me down the rabbit hole of httpd.conf files and mod_wl_ohs.conf files etc. They all had the right settings in them, namely “Listening 19000”, telling the EPM service to listen on that port. Unfortunately those settings didn’t help. I was frustrated.
However in a flash of inspiration, an idea dawned on me, and it was a rather simple fix. I remembered that there is actually a setting on the weblogic admin console, where we can check and update the listening port of any managed servers. When I checked it, what do you know, it was pointing to port 9000.
This was in spite of the configuration tool being used to update the logical address, and the configuration files showing the port 19000. Why is the admin server showing 9000 instead of 19000, I do not know. But what I do know is that I can update that entry easily, and that’s what I did.
Once the port has been updated for the managed server, I proceeded to restart the EPM server, and the port 19000 kicked into action and I was able to access the workspace front-end at that port. Problem solved. 🙂
I hope this post helps some of you who may find yourself in similar situations. As always, looking forward to your feedback and questions.
You can reach the author Rajesh Valluri via his LinkedIn profile.