Policy Agent 2.2 guides do not explain
configuration of J2EE Agents and Access Manager SDK on the Same Deployment
Container

Currently, no information is provided in Policy Agent 2.2 documentation
for J2EE agents regarding this issue. Therefore, the required task for this
scenario is presented at this time in this document.

If you install a J2EE agent instance on the same deployment container
(such as an application server) as an Access Manager SDK instance, you must
edit a property in the AMConfig.properties file of the Access Manager SDK
instance.

This task is necessary to ensure proper evaluation of policies. The
configuration task described in this section applies to J2EE agents, not web
agents, in the Policy Agent 2.2 software set. Therefore, no additional
configuration steps are required when an Access Manager SDK instance and a
web agent instance are installed on the same deployment container (such as
a web server).

Note –

The configuration task described in this section applies to situations
where Access Manager SDK was installed as a separate component using the Sun
Java Enterprise System installer. The configuration task described in this
section is not required for the following versions of the SDK: