#adminconsole

Over the past couple of months I have been tasked on a number of projects to upgrade from Oracle 10g middleware to Oracle's 11g Fusion Middleware. As an IT resource who primarily deals in the middleware space I can say that this is a welcomed initiative!

However, during the upgrade of a number of environments I was running into a strange situation that baffled myself and my colleagues for a few weeks. Today though, we finally sorted it out.

As part of our move to Oracle Weblogic Application Server, we also wanted to place the Oracle WebTier (primarily Oracle HTTP Server) out in front of each install to better manage and secure our web traffic. The installations of both Weblogic Application Server and Oracle WebTier were very straight forward and configuring Oracle HTTP Server to talk to Oracle Weblogic Server was a piece of cake with the mod_wl_ohs plugin.

The issue we ran into though was related to the way that the Weblogic Admin Console redirects traffic after saving a configuration change. We were able to navigate the Admin Console through when accessing through Oracle HTTP Server, but when we made a configuration change, and clicked save we were being redirected away from the Oracle HTTP Server to the Weblogic AdminServer port. Confused yet, me too! Example time:

We were accessing the Admin Console through Oracle HTTP Server so our URL was:

http://localhost:7777/console

While navigating through the console we remained on localhost:7777. However, when we clicked save after making a configuration change, we were redirected to:

http://localhost:7001/console

I know what your thinking, big deal. Well, this does pose a big problem if you plan on accessing the console through a reverse proxy. Because when the redirect happens, you will get a nasty connection reset message because you may not necessarily have access to port 7001.