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, you must use a local configuration.
With a local configuration, you manage the version 3.0 agent by editing properties in the agent's local OpenSSOAgentConfiguration.properties file (in the same manner that you edit the AMAgent.properties file for version 2.2 agents).
If you are creating a new agent profile in the OpenSSO Console, set Configuration to Local.
To specify a local configuration for an existing agent profile with a centralized configuration, edit the agent profile in the OpenSSO Console:
Log in to the Console as amadmin.
Click Access Control, realm-name, Agents, Web, and then the name of the agent profile you want to edit.
The Console displays the Edit page for the agent profile.
On the Edit page, check Local for Location of Agent Configuration Repository.
A version 3.0 agent also stores configuration information in the local OpenSSOAgentBootstrap.properties file. The agent uses information in the bootstrap file to start and initialize itself and to communicate with Oracle OpenSSO server. In most cases, you won't need to edit the bootstrap file; however, if you do edit the file, be careful or the agent might not function properly.