Oracle Hyperion Server not listening on port 19000

The logical address was configured and port 19000 was assigned.
All the configuration steps have been successfully completed.

Nothing's listening on 19000. Grr.
EPM http server is not listening on port 19000.

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.

You can see the EPMServer0 managed server is actually listening on port 9000.

After clicking on “Lock and Edit” tab, and then the EPMServer0, update the listen port.

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.

The quirk with this version is it requires you to start and stop using “run as administrator”. Starting EPM server after configuration changes in weblogic admin console.

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. 🙂

You can see how the EPMServer0 is now listening on port 19000

All Hyperion Services have started successfully.

Accessing workspace and planning applications from the standard 19000 port. Woohoo!!

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.

You may also like...

Leave a Reply

%d bloggers like this: