Policy Server Guides › Policy Server Configuration Guide › Agents and Agent Groups › How to Configure a Web Agent › Create a Host Configuration Object

Create a Host Configuration Object

You can create a new Host Configuration object or duplicate an existing object.

To create a host configuration object

1. Click Infrastructure, Hosts.
2. Click Host Configuration, Create Host Configuration.

   The Create Host Configuration pane opens.

3. Do one of the following:
   • (Recommended) Create a copy of an existing Host Configuration object and modify its properties. You can copy the DefaultHostSettings object and use its settings as a template for the new object. The DefaultHostSettings object is installed by the Policy Server installation program.

     Important! Do not directly modify and use the DefaultHostSettings object. Always copy this object and then modify it.

   • Create a new object.
4. Click OK.

   The Create Host Configuration: Name pane opens.

   Note: Click Help for descriptions of settings and controls, including their respective requirements and limits.

5. Type the name and a description in the fields on the General group box.
6. Specify the Host Configuration settings in the Configuration Values group box.
7. Click Submit.

   The Create Host Configuration task is submitted for processing.

Configure Web Agents Locally

The Web Agent reads both the Agent Configuration Object and the local Agent configuration file, overriding values in the Agent Configuration Object with the values in the local Agent configuration file. The Web Agent merges them together into one configuration source. This enables you to modify only a small subset of Agent parameters locally, then rely on the central Agent Configuration Object for the rest of an Agent’s configuration.

To better understand how central and local configuration work together, read Combined Central and Local Configuration.

To configure parameters locally

1. Obtain permission to perform local configuration from a Policy Server administrator.
2. Complete the steps in How to Configure a Web Agent. These tasks apply to local and central configuration of a Web Agent.
3. In the Agent Configuration Object, set the AllowLocalConfig parameter to yes.
4. Edit the Web Agent configuration file (WebAgent.conf and/or LocalConfig.conf).

   Be sure to modify a copy of the Web Agent configuration file and maintain a backup copy.

   For all Web Agents except IIS 6.0, there is a WebAgent.conf.sample file In the <web_agent_home>\config directory. You should modify this file, then save it under the name WebAgent.conf to the appropriate web server location.

   For IIS 6.0 Web Agents, this Agent uses the LocalConfig.conf file in <web_agent_home>\bin\IIS directory as its active configuration file. Modify this file if you want to make changes. The copy of the LocalConfig.conf file in <web_agent_home>\config is the original that you should not change.

   Note: If you are using an IIS 6.0 Web Agent, the main configuration file is called LocalConfig.conf. The WebAgent.conf file is still used, but only for core Agent settings that enable the Agent to start and connect to the Policy Server.

   More information about local configuration and parameter descriptions exists in the Web Agent Configuration Guide.

Combined Central and Local Configuration

When a Web Agent is enabled, it searches the Agent Configuration Object for configuration information, and notes the value of the AllowLocalConfig parameter. If this parameter is set to yes, the Web Agent searches the corresponding Agent’s local configuration file for modified or additional parameters, overriding any Agent Configuration Object parameters with the value from its configuration file.

Using the central and local configuration sources, the Agent creates a unified local copy of an Agent Configuration Object that it uses for configuration. The local copy does not alter the Agent Configuration Object that resides at the Policy Server.

Example of Using Central and Local Configuration

Scenario:

You want to configure multiple cookie domain single sign-on across your SiteMinder network without having to configure each Agent individually.

The CookieDomain parameter in the Agent Configuration Object is set to acmecorp.com. However, you want to set the CookieDomain parameter to test.com for one Web Agent in your network, while continuing to use all of the other parameter values set in the Agent Configuration Object.

Solution:

To implement the example configuration

1. Configure an Agent Configuration Object with all the parameters applicable for your environment.
2. In the Agent Configuration Object, set the AllowLocalConfig parameter to yes.
3. For the single Web Agent, change only the CookieDomain parameter to test.com. Do not modify any other parameters.

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