If the WebSphere Application Server/Portal Server agent is installed and configured to operate in ALL mode, you must create the appropriate URL policies.
Note: Since WebSphere Portal Server is protected by J2EE declarative security, the agent should operate in J2EE_POLICY or ALL mode.
For example, if WebSphere Application Server with the Administration Console is listening on ports 10027 (http) and 10041 (https), respectively, and WebSphere Portal Server is listening on port 10040 (http), create the following polices for the WebSphere Administrative user ID (wasadmin or wpsadmin) to allow the user access to the WebSphere Administration Console and Portal Server URLs:
http://agenthost.example.com:10027/*
https://agenthost.example.com:10041/*
http://agenthost.example.com:10040/*
https://agenthost.example.com:10041/*?*
http://agenthost.example.com:10040/*?*
Notes:
These examples assume that http://agenthost.example.com:10027/ibm/console is the Administration console URL on WebSphere_Portal and http://agenthost.example.com:10040/wps/myportal is the Portal Server URL.
Port 10041 is the corresponding https port of http port 10027. When an http request comes to port 10027, it will be redirected to 10041 as an https request.
Only the protected portal http://agenthost.example.com:10040/wps/myportal is supported by the agent. The non-protected portal http://agenthost.example.com:10040/wps/portal is not supported.
http://agenthost.example.com:10001/*
https://agenthost.example.com:10003/*
http://agenthost.example.com:10000/*
https://agenthost.example.com:10003/*?*
http://agenthost.example.com:10000/*?*
Notes:
These examples assume that http://agenthost.example.com:10001/ibm/console is the Administration console URL on server1and http://agenthost.example.com:10000 is the server1 server URL.
Port 10003 is the corresponding https port of http port 10001. When an http request comes to port 10001, it will be redirected to 10003 as an https request.