Controllinghow often Agent Manager runs agents

These NOTES.INI settingsaffect how often the Agent Manager executes agents. In general, themore frequently agents run, the sooner they perform their tasks. Runningagents more frequently, however, may increase demand on server resourcesand adversely affect overall system performance.

AMgr_DocUpdateAgentMinInterval

Thissetting specifies the minimum elapsed time, in minutes, between executionsof the same document update-triggered agent. This lets you controlthe time interval between executions of a given agent. Default is30 minutes. A longer interval can result in the agent running lessoften, reducing server demand. If document update events are infrequent,you can reduce the delay.

AMgr_DocUpdateEventDelay

Thissetting specifies the delay time, in minutes, the Agent Manager schedulesa document update-triggered agent after a document update event. Thedefault is 5 minutes. The delay time ensures the agent runs no moreoften than the specified interval, regardless of how frequently documentupdate events occur. When the agent executes, it will also processall additional events (if any) that occurred during the interval.A longer interval results in the agent running less often, thus reducingdemand for server time. If document update events are infrequent,however, you can reduce the delay to ensure the agent runs soon afterthe event occurs.

AMgr_NewMailAgentMinInterval

Thissetting specifies the minimum elapsed time, in minutes, between executionof the same new mail-triggered agent. The default is 0 (no intervalbetween executions). Similar to AMgr_DocUpdateAgentMinInterval, enteringan interval can result in the agent running less frequently.

AMgr_NewMailEventDelay

Thissetting specifies the time (in minutes) that the Agent Manager delaysbefore scheduling a new mail-triggered agent after new mail is delivered.The default is 1 minute. Similar to AMgr_DocUpdateEventDelay, thedelay time ensures the agent runs no more often than the specifiedinterval. When the agent executes, it will also process all additionalevents (if any) that occurred during the interval. A longer intervalresults in the agent running less often, thus reducing demand forserver time. If document update events are infrequent, however, youcan reduce the delay to ensure the agent runs soon after the eventoccurs.

DominoAsynchronizeAgents

Thissetting specifies whether Web agents triggered by browser clientscan run at the same time (asynchronously). The default is zero (onlyone agent can run at a time). Set this to 1 to allow multiple agentsto run simultaneously. This can result in faster execution of agents.However, a high number of agents executing at the same time can slowoverall system performance. Open the Server document you want to change,and click the Internet Protocols -Domino® WebEngine tab. In the Web Agents section, enable or disable theRunWeb agents concurrently? option. ForWeb agenttime-out (in seconds), the default is 0 (no time-outs).

Controllinghow quickly the Agent Manager queues agents

The Agent Managerperiodically checks to see if it has any new agents that it needsto schedule. These NOTES.INI settings control how quickly an agentgets into the schedule queue.

AMgr_SchedulingInterval

Thissetting specifies a delay (in minutes) between running of the AgentManager's scheduler. Valid values are 1 minute to 60 minutes. Thedefault value is 1 minute.

AMgr_UntriggeredMailInterval

Thissetting specifies a delay (in minutes) between running of the AgentManager's check for untriggered mail. Valid values are 1 minute to1440 minutes (the number of minutes in a day). The default value is60 minutes.

Controllingwhen the Agent Manager runs agents

When you create or modifyan event-triggered agent, the Agent Manager schedules it to run immediately.This ensures the agent can quickly process new documents. These NOTES.INIsettings let you specify a time interval between subsequent runningof the agent. This can prevent repeated running of the agent -- forexample, because of a rapid series of triggering events.

Schedulingan agent to run immediately means that it will execute as soon aspossible after agents scheduled earlier.

Thesesettings control when the Agent Manager runs agents.

• AMgr_NewMailEventDelay
• AMgr_DocUpdateEventDelay
• AMgr_DocUpdateAgentMinInterval
• AMgr_NewMailAgentMinInterval

Monitoringthe load on the Agent Manager

If your server attempts toschedule agents at a rate faster than the Agent Manager can run them,the message AMgr:Agent scheduling is paused appearson the console. The Agent Manager will not schedule any new agentsuntil the server processes some agents that are already scheduled.Therefore, the running of new agents may be slightly delayed.

Controllinghow many concurrent agents are running

You can relievea heavily loaded Agent Manager by allowing agents to run concurrently.To do this, modify theMax concurrent agents fieldin the Server Tasks/Agent Manager section of the Server document.Values greater than 1 allow more than one agent to run at the sametime. Valid values are 1 through 10. Default values are 1 for daytimeand 2 for nighttime.

An Agent Executive runs each concurrentagent. To see a snapshot of the Agent Manager status, including thenumber of Agent Executives currently running, enter the command tellamgr status at the server console. To see a list of scheduled agents,enter the command tell amgr schedule at the server console.