Previous Topic: Restrict Changes to Local Configuration ParametersNext Topic: Configuration Files used by the Web Agent


Central and Local Configuration Together

If you have a large number of Web Agents that you want to configure centrally, but the settings of a few of those Web Agents need to be different than the others, you can use a combination of central and local configuration together.

For example, if you need to configure multiple cookie domain single sign-on across a SiteMinder network without configuring the Agents individually, you can use a central configuration for all of the agents, and local configuration settings for the smaller group that needs the different settings.

In the previous example, suppose the CookieDomain parameter in the Agent Configuration Object is set to example.com. However, for one Web Agent in your network, you want to set the CookieDomain parameter to .example.net, while still using all the other parameter values set in the Agent Configuration Object.

To implement the example configuration

  1. With the Administrative UI, create an Agent Configuration Object with all the parameters that you want for your environment. Set the CookieDomain parameter to .example.com
  2. Set the AllowLocalConfig parameter of the Agent Configuration Object to yes.
  3. At one Web Agent, change only the local configuration file (on the web server) to use example.net as the value of the CookieDomain parameter. Do not modify any other parameters.

The value for the CookieDomain parameter in the lone Agent's local configuration file overrides the value in the Agent Configuration Object, while the Agent Configuration Object determines the settings for all the other parameters.