Implement Central Configuration

Web Agent Guides › Web Agent Configuration Guide › Web Agents › Web Agent Configurations › Parameters Requiring a Server Restart when Changed › Implement Central Configuration

Implement Central Configuration

Central configuration is enabled by default. The Web Agent uses the configuration settings from the existing Agent Configuration Object that you specified when you configured the Web Agent with the configuration wizard. You can change the settings of the parameters to suit your needs at any time.

To implement central configuration

Log into the Administrative UI.
The Welcome screen appears.
Click Infrastructure, Agent Configuration.
A list of agent configuration tasks appears.
Click Modify Agent Configuration.
The search window appears.
(Optional) Fill out the search form to narrow your search criteria.
Click Search.
A list of Agent Configuration objects appears.
Click the radio button to the left of the Agent Configuration Object associated with the Agent on which you want to implement central configuration. Click Select.
The Modify Agent Configuration window appears.
Ensure the value of the AllowLocalConfig parameter is set to no.
Use the Administrative UI to add, edit or delete the settings of any other parameters according to your needs.
Click Submit when you are finished making changes.
The Modify Agent Configuration window closes, and a confirmation message appears. Central configuration is implemented. Most parameter changes occur dynamically, but some changes require a web server restart to take effect.

More information:

Parameters Requiring a Server Restart when Changed

Local Agent Configuration

Local Configuration

A local agent configuration manages a Web Agent using local files that are installed on the system hosting the web server. The parameter settings in the local file override any settings stored in an Agent Configuration Object on the Policy Server. The settings in the Agent Configuration Object do not change. Situations to consider local agent configuration include the following:

When you have three Apache Web Agents, and the first two (A and B) use identical parameter settings, but you want the third Apache Agent (C) use the most of the settings from A and B while acting as a reverse proxy. To accomplish this, use central agent configuration for Apache Agents A and B, but use local configuration for Apache Agent C.

When the Policy Server administrator is not the same person (or group) who configures an Agent. For example, the information technology department in a company maintains the Policy Server, but the finance department uses an Agent to control access to an accounting application. Someone from the information technology department enables local configuration for the Agent on the Policy Server, but another person from the finance department controls the specific configuration settings for the Agent that protects the accounting application.

Framework Web Agents use the following files for local configuration:

WebAgent.conf: Contains the core settings that the Framework Web Agent uses to start and connect to a Policy Server.
LocalConfig.conf: Contains the configuration settings for the Framework Web Agents.

Traditional Web Agents use the following file for local configuration:

WebAgent.conf: Contains all of the configuration settings for traditional Web Agents.

WebAgent.conf File Locations

The following table shows the locations of the WebAgent.conf file on various web servers:

web_agent_home

Indicates the directory where the SiteMinder Agent is installed.

Default (Windows 32-bit installations of SiteMinder Web Agents only): C:\Program Files\CA\webagent

Default (Windows 64-bit installations [SiteMinder Web Agents for IIS only]): C:\Program Files\CA\webagent\win64

Default (Windows 32-bit applications operating on 64-bit systems [Wow64 with SiteMinder Web Agents for IIS only]): C:\Program Files (x86)\webagent\win32

Default (UNIX/Linux installations): /opt/ca/webagent

Web Server	File Location
IIS	web_agent_home\bin\IIS
Oracle iPlanet (iPlanet/SunOne)	Oracle_iPlanet_server_home/https-hostname/config where Oracle_iPlanet_home is the location in which theOracle iPlanet web server is installed and hostname is the name of the server.
Apache, IBM HTTP Server Oracle HTTP Server	web_server_home/conf where web_server_home is the installed location of the web server
Domino	Windows: c:\lotus\domino UNIX: $HOME/notesdata

More information:

Enable a Web Agent

Disable a Web Agent