Managing the WebLogic Server/Portal 10 Agent

OpenSSO Enterprise stores version 3.0 policy agent configuration data (as well as server configuration data) in a centralized repository. To manage this configuration data, use these options:

• OpenSSO Enterprise Administration Console

  You can manage both version 3.0 J2EE and web agents from the OpenSSO Enterprise Console. Tasks that you can perform include creating, deleting, updating, listing, and displaying agent configurations. Using the Console, you can set properties for an agent that you previously set by editing the agent's AMAgent.properties file.

  For more information, refer to the Administration Console online Help.

• ssoadm command-line utility

  The ssoadm utility is the command-line interface to OpenSSO Enterprise server and is available after you install the tools and utilities in the ssoAdminTools.zip file. The ssoadm utility includes subcommands to manage policy agents, including:

  • Creating, deleting, updating, listing, and displaying agent configurations

  • Creating deleting, listing, and displaying agent groups

  • Adding and removing an agent to and from a group

  • Set agent configuration properties

  For information about the ssoadm utility, including the syntax for each subcommand, see the Sun OpenSSO Enterprise 8.0 Administration Reference.

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.

When you deploy the WebLogic Server/Portal 10 agent with OpenSSO Enterprise to use a local configuration, use one of these methods:

• In the OpenSSO Enterprise Administration Console, on the Edit agent-name page, set Location of Agent Configuration Repository to local.

  or

• Use the ssoadm utility to set the following property:

  com.sun.identity.agents.config.repository.location=local

Then, you must 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).

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 OpenSSO Enterprise 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.