Compatibility and Coexistence of Policy Agent 3.0 with Previous Releases

This section consists of information about the compatibility and coexistence of the J2EE agents in the Policy Agent 3.0 software set with previous releases of both Access Manager and Policy Agent.

J2EE Agents in the Policy Agent 3.0 release are compatible with versions of Access Manager as described in this section.

Compatibility of Policy Agent 3.0 with Access Manager 7.1 and Access Manager 7 2005Q4

Access Manager 7.1 and Access Manager 7 2005Q4 are compatible with Policy Agent 3.0. However, because Access Manager does not support centralized agent configuration, an agent in the 3.0 release deployed with Access Manager must store the core of its configuration data locally in the OpenSSOAgentConfiguration.properties file.

• local: Configuration data is stored locally in the OpenSSOAgentConfiguration.properties file on the server where the agent is deployed.

• centralized: Configuration data is stored in the OpenSSO Enterprise centralized data repository.

For both configurations, the OpenSSOAgentBootstrap.properties file on the server where the agent is deployed contains the information required for the agent to start and initialize itself.

Coexistence of Policy Agent 3.0 With Policy Agent 2.2

OpenSSO Enterprise supports both Policy Agent 3.0 and Policy Agent 2.2 in the same deployment.

Be aware that while Policy Agent 3.0 and Policy Agent 2.2 can exist in the same deployment, they cannot exist on the same container.

However, agents in the 2.2 release only have the option to store their configuration data locally in the AMAgent.properties file. Therefore, the OpenSSO Enterprise centralized agent configuration option is not supported. To configure an agent in the Policy Agent 2.2 release, you must edit the AMAgent.properties file.

For more information about Policy Agent 2.2, see the documentation collection: http://docs.sun.com/coll/1322.1