Previous Topic: Framework and Traditional Agent ArchitecturesNext Topic: Agent Configuration Methods


Parameters Requiring a Server Restart when Changed

Some Agent parameters be updated dynamically. You must restart the web server to apply any changes to the following parameters:

AgentConfigObject

Defines the name of an Agent Configuration Object (stored on a policy server) in a local agent configuration file. This parameter is not used in Agent Configuration Objects.

Default: no default

CacheAnonymous

Specifies if the Web Agent caches anonymous user information. You may want to set this parameter in any of the following situations:

Default: No

HostConfigFile

Specifies the path to the SMHost.conf file (in an IIS 6.0 or Apache agent) that is created after a trusted host computer has been successfully registered with a Policy server. All Web Agents on a computer share the SMHost.conf file.

Default: No default

MaxResourceCacheSize

Specifies the maximum number of entries that the Web Agent keeps in its resource cache. An entry contains the following information:

When the maximum is reached, new resource records replace the oldest resource records.

If you set this value to a high number, be sure that sufficient system memory is available.

If you are viewing Web Agent statistics using the OneView Monitor, you may notice that the value shown for the ResourceCacheCount is greater than the value you specified for the MaxResourceCacheSize parameter. This is not an error. The Web Agent uses the MaxResourceCacheSize parameter as a guideline and the values may at times differ because the MaxResourceCacheSize parameter represents the maximum number of average-sized entries in the resource cache. The actual cache entries are most likely larger or smaller than the pre-determined average size; therefore, the effective maximum number of entries may be more or less than the value specified.

Note: For Web Agents that use shared memory, such as the framework Agents, the cache is pre-allocated to a constant size based on the MaxResourceCacheSize value and will not grow.

Default: (Domino web servers) 1000

Default: (IIS and Sun Java System web servers) 700

Default: (Apache web servers) 750

MaxSessionCacheSize

Specifies the maximum number of users the Agent maintains in its session cache. The session cache stores the session IDs of users who authenticate successfully. Authenticated users accessing other resources within the realm during a session, are authenticated using the session cache instead of the Policy Server. When the maximum number is reached, the Agent replaces the oldest user records with new user records.

Base the value of this parameter on the number of users that you expect to access and use resources for a sustained period. If you set this value to a high number, verify that sufficient system memory is available.

Note: Regardless of the cache size, all entries in the session cache of the Web Agent expire automatically after one hour.

Default: (Domino web servers) 1000

Default: (IIS and Oracle iPlanet web servers) 700

Default: (Apache web servers) 750

PostPreservationFile

Enables the transfer of POST preservation data between Traditional and Framework Agents by specifying the path to one of the following POST-preservation-template files:

Default: No default

Example: web_agent_home/samples/forms/fw2tr.pptemplate

ResourceCacheTimeout

Specifies the number of seconds that resource entries remain in the cache. If a user tries to access a protected resource after the time interval has been exceeded, the Web Agent removes the cached entries and contacts the Policy server.

Default: 600 (10 minutes)

Multiple Agent for IIS Directory Structures According to Operating Environment

The directory structure added to your IIS web server for your Agent files varies according to the operating environment of your IIS web server. The following directory structures exist:

More information:

Run the Installation Wizard to Upgrade your Agent for IIS