Sun OpenSSO Enterprise Policy Agent 3.0 Guide for Apache HTTP Server 2.0.x

Managing a Version 3.0 Agent With a Local Configuration

In some scenarios, you might need to deploy a version 3.0 agent using a local configuration. For example, if you deploy the agent with Access Manager 7.1 or Access Manager 7 2005Q4, which do not support centralized agent configuration, local configuration is used by default.

The following property in the OpenSSO Enterprise server Agent Service schema (AgentService.xml file) indicates that the configuration is local:


In this scenario, you must manage the version 3.0 agent by editing properties in the agent's local file (in the same manner that you edit the file for version 2.2 agents).

Caution – Caution –

A version 3.0 agent also stores configuration information in the local file. The agent uses information in the bootstrap file to start and initialize itself and to communicate with OpenSSO Enterprise server. In most cases, you won't need to edit the bootstrap file; however, if you do edit the file, be very careful, or the agent might not function properly.