The Web Server 7.0 agent is supported on these platforms:
Solaris OS on SPARC platforms, versions 9 and 10 (32–bit/64–bit)
Solaris OS on x86 platforms, versions 9 and 10 (32–bit/64–bit)
Red Hat Enterprise Linux Advanced Server 4.0 and 5.0 (32–bit/64–bit)
Windows 2003, Enterprise Edition (32–bit/64–bit)
Windows 2003, Standard Edition (32–bit/64–bit)
Notes about 32–bit and 64–bit systems:
On 32–bit Solaris SPARC and x86 systems, run Web Server 7.0 web container only in 32–bit mode and install only the 32–bit Web Server 7.0 agent.
On 64–bit Solaris SPARC and x86 systems, run Web Server 7.0 web container only in 64–bit mode and install only the 64–bit Web Server 7.0 agent.
On Windows and Linux systems, run the Web Server 7.0 web container instance in 32–bit mode.
You can deploy the Web Server 7.0 agent on the following deployment containers. The links are to the Web Server documentation collections.
Web Server 7.0 Update 3: http://docs.sun.com/coll/1653.3
Web Server 7.0 Update 2: http://docs.sun.com/coll/1653.2
Web Server 7.0 Update 1: http://docs.sun.com/coll/1653.1
Web Server 7.0: http://docs.sun.com/coll/1308.3
Access Manager 7.1 and Access Manager 7 2005Q4 are compatible with version 3.0 policy agents. However, because Access Manager 7.1 and Access Manager 7 2005Q4 do not support centralized agent configuration, a version 3.0 agent deployed with Access Manager must store its configuration data locally in the OpenSSOAgentBootstrap.properties and OpenSSOAgentConfiguration.properties files. The OpenSSOAgentBootstrap.properties file on the server where the agent is deployed contains the information required for the agent to start and initialize itself.
A version 3.0 agent automatically detects the host server it is accessing. In the case of Access Manager 7.1 or Access Manager 7 2005Q4, a version 3.0 agent will switch to “local” mode and use the properties from the agent's OpenSSOAgentConfiguration.properties file.
OpenSSO Enterprise supports both version 3.0 and version 2.2 agents in the same deployment. The version 2.2 agents, however, must continue to store their configuration data locally in the AMAgent.properties file. And because the version 2.2 agent configuration data is local to the agent, OpenSSO Enterprise centralized agent configuration is not supported for version 2.2 agents. To configure a version 2.2 agent, you must continue to edit the agent's AMAgent.properties file.
For documentation about version 2.2 agents, see http://docs.sun.com/coll/1322.1.
This agent works with the reverse proxy feature built into Sun Java System Web Server 7.0. No separate agent configuration is required. To use the reverse proxy feature, however, ensure that the Web Server 7.0 instance has been upgraded to the most recent release with the latest patches.