Some web agent guides show a colon rather than an equal sign (=) as the separator to set the com.sun.am.policy.agents.config.local.log.size property. To set this property, always use the equal sign. For example:
com.sun.am.policy.agents.config.local.log.size = n
Where n represents the size of a file in bytes. The file size should be a minimum of 3000 bytes. The default size is 10 megabytes.
The Policy Agent 2.2 guides refer to Sun Java System Access Manager. The version 2.2 policy agents, however, are also compatible with Sun OpenSSO Enterprise and Sun OpenSSO Express releases.
Considerations for using a version 2.2 policy agent with OpenSSO Enterprise or OpenSSO Express include:
A version 2.2 policy agent must continue to store its configuration data locally in its AMAgent.properties file. Therefore, because the version 2.2 policy agent configuration data is local to the agent, the OpenSSO centralized agent configuration option is not supported for version 2.2 agents. To configure a version 2.2 policy agent, you must continue to edit the agent's AMAgent.properties file.
When you are configuring a version 2.2 policy agent with OpenSSO, the default Primary Server Deployment URI (and Failover Server Deployment URI, if required by the agent) is /opensso rather than /amserver.
You can create a version 2.2 Java EE (formerly J2EE) or web agent profile in the OpenSSO Administration Console under Access Control, realm-name, Agents, and 2.2 Agents. However, you must configure the agent by editing its AMAgent.properties file.
OpenSSO Enterprise supports both version 3.0 and version 2.2 policy agents in the same deployment.
For more information about policy agents, see the following documentation collections: