Portal Admin Tool needs modification to work in cluster with proxy plugin (Doc ID 776631.1)

Goal

The deployment guide has users hitting the Portal Admin Tool on the managed servers, since the applications are deployed there. Given that in production most users will use firewalls blocking direct access to WebLogic Server (WLS) in conjunction
with WebServer plugins, there will be an issue accessing the Portal Admin Tool. The plugins use the JSESSIONID cookie by default to direct the requests to the server holding the session. Because the PAT (Portal Admin Tool) uses a different cookie name
(JSESSIONID_ADMINTOOLS), requests for it are distributed in a round robin fashion to the servers. This leads to a user experience where dropdowns and trees behave weirdly. Basically, one server may have you with a tree in a particular
state, then you would hit the other server on your next request.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.