Configuring Adaptive Agent Settings after Deployment
149
n
ov
do
cx (e
n)
16
Ap
ril 20
10
(by default, 336 hours or 14 days). For example, suppose that a cache entry is added on June 10
at 3:00 p.m. With the default
Cache Life
setting, the expiration time is set to June 24 at 3:00
p.m.
The agent does not attempt to update a cache entry until after the entry’s expiration time. At
that point, the agent updates the cache entry the next time it contacts the ZENworks Server to
refresh its information.
NOTE:
Updates to expired cache entries occur only for cache entries that are content-related
(bundles, policies, configuration settings, registration settings, and so forth). Updates to cache
entries that are event-related (remote management, inventory, reporting, and so forth) only
occur at the time the event takes place on the device.
A higher
Cache Life
setting reduces the traffic load on your network because cache entries are
refreshed less frequently. A lower setting provides newer information but increases the traffic
load.
This setting affects only how often the agent requests updates to a cache entry. Cache entries
can also be updated before their expiration time if information is changed in ZENworks
Control Center that causes the information to be pushed from the ZENworks Server to the
agent.
Cache Orphaning Threshold:
Over a period of time, it is possible for entries to be inserted in
the cache database but not removed. This can cause the cache to grow unnecessarily.
An orphan is an entry that is inserted into the cache but not accessed within the number of days
specified by the
Cache Orphaning Threshold
setting. For example, suppose that a cache entry
is accessed on July 1 at 10:00 a.m. Without the default
Cache Orphaning Threshold
setting (30
days), the entry becomes an orphan if it is not accessed again before July 31 at 10:00 a.m.
A higher
Cache Orphaning Threshold
setting ensures that infrequently accessed information is
not removed from the cache database. A lower setting can reduce the cache size.
Times to Retry Requests to a Busy Server:
Lets you specify the number of times that the
agent retries a request to a busy server before considering the server as bad instead of busy.
The default value is 15. The maximum value that you can specify is 20.
Initial Retry Request Wait:
The
Initial Retry Request Wait
setting lets you specify the initial
amount of time that the agent waits before retrying a Web service request after receiving a busy
response from the server. The wait time increases by one second with every busy response. The
default setting is four seconds. The maximum value that you can set is ten seconds. Each
subsequent request is incremented by one second.
For example, suppose that you leave this setting at the default (four seconds). After receiving a
busy response from the server, the agent waits four seconds for the first retry attempt. If the
server is still busy, the agent waits five additional seconds (4 + 1) before making the second
retry attempt. The third retry attempt is 15 seconds after the initial retry attempt (4 + 5 + 6). The
time increments until the value specified in the
Maximum Retry Request Wait
setting is reached.
The retry attempts stop when the value specified in the
Times to Retry Requests to a Busy
Server
setting is reached.
Maximum Retry Request Wait:
Lets you specify the maximum amount of time to wait
before retrying a Web service request after receiving a busy response from the server.
The default setting is 16 seconds. The maximum value that you can specify is 20 seconds.
