Previous Topic: Use One Agent Configuration Object and Multiple Agent Configuration Files

Next Topic: Use a Shared Agent Configuration File and Configuration Object for All Agent Modules

Use Module-Specific Agent Configuration Objects

By default, the SiteMinder TAI, SiteMinder Login Module, and SiteMinder JACC Provider each have their own Agent configuration files that all reference the same, previously created Agent Configuration Object. However, you can create separate Agent Configuration Objects for each module, enabling centralized control of settings for each module from the Policy Server.

To configure the SiteMinder Agent to use separate Agent Configuration Objects for each ASA module

  1. In the SieMinder Administrative UI, do the following for each Agent module type:
    1. Create an Agent identity with a name appropriate for the module that it represents (for example, WSAgentTAI).
    2. Create a duplicate of the Agent Configuration Object that you created for the SiteMinder Agent components before installation.
    3. Set the DefaultAgentName parameter to the Agent identity defined in Step a. You can also set other module-specific Agent configuration parameters, if you know them. Otherwise, these are described in-context later.
    4. Save the Agent Configuration Object with a name appropriate for the module to which it relates (for example, AsaTAISettings).
  2. On the system where the SiteMinder Agent is installed:
    1. Edit the AsaAgent-assertion.conf file to change the value of the AgentConfigObject parameter to match the name of the Agent Configuration Object that you created for SiteMinder TAI modules.
    2. Edit the AsaAgent-auth.conf file to change the value of the AgentConfigObject parameter to match the name of the Agent Configuration Object that you created for SiteMinder Login Modules.
    3. Edit the AsaAgent-az.conf file to change the value of the AgentConfigObject parameter to match the name of the Agent Configuration Object that you created for SiteMinder JACC Provider modules.

Note: The single Agent identity and Agent Configuration Object you created before installation are no longer be in use; optionally, you can delete them now.