AGENT:

Category
They are part of the SysAdmin category.
Instance
Agent rule: Rule-Agent-Queue class.
Agent schedules: Data-Agent -Queue class.
Purpose
An agent is an internal background process operating on the server on a periodic basis, i.e., the activities
which are specified in AGENT rule are to be executed.
The nae of an agents rule is the nae of a !ule"et and there can be only one agents rule defined for
each !ule"et and version in a #rocess $oander syste.
The order in which you list agents in an agent rule does not create a se%uence. Each agents activity runs
individually on its own interval schedule, as a separate re%uestor thread.
Agent Scedule data instances deterine whether an agent is enabled, and &on a ulti'node syste(on
which server node that agent will run.
After the Agent "chedules have been created, they provide agent inforation to the syste. After the
"chedules are present, the original values entered in the Agents rule for schedule intervals or enabling
agents are not used) the syste uses the inforation in the Agent "chedules only.
Agent !anager: *y default, the Agent +anager checks for new or updated agents rule &and anually
updated agent schedules( once every ten minutes. After you create an agents rule, the Agent +anager
generates one Agent "chedule instance for each node running on your #rocess $oander syste the
next time it checks for new agents rules.
The Agent +anager on your #rocess $oander syste generate at least one agent schedule instance
for each agents rule. ,n a ultinode syste, for each agents rule, the Agent +anager generates one agent
schedule instance for each node.
Important: Te Agent Scedule instances must not "e created "y de#elopers they are
created only by the syste. -o not create or copy these instances.
/owever, the internal +aster Agent process always runs the highest'nubered version, not rule
resolution.
i.e., Although the agents rule for contains a 0ersion, the Agent +anager does not use rule resolution to
deterine which version of an agents rule to run. The highest version always runs.
Agent schedules cannot "e created manually. *ut they can be odified and it should be save,
$hanges take effect only after the Agent +anager aster agent notices the changes.
The Agent +anager aster agent generates agent schedule instances fro agents rules.
Agents that use the "tandard %ueue ode can run on all nodes.
Agents that use the 1egacy %ueue ode, do not enable such agents on ore than one node.
Access
The Nodes tab on an agents rule lists all the agent schedules generated for that rule.
2ou can also use the !ules explorer to list agent schedules: select SysAdmin $ Agent Scedule.
Starting and stopping agents
Norally, all agents start each tie you start your #rocess $oander syste. Agents running on a
specific node start as that node starts. 3hen testing or any other purpose, you can use the "yste
+anageent Application&"+A( to onitor or control agents:
4. "tart the "yste +anageent application.
5. "elect a node.
6. "elect the Agent +anageent enu ite &Agents or "yste 7ueue +anageent(.
8. $lick a single radio button to identify a thread of an agent. &Each agent activity executes in a
separate thread.(
9. :se the buttons at the top of the page to start the agent, stop the agent, or pause agent processing.
2ou can affect only the selected activity &one row of the for( or all activities.
4. Agent 3ide settings lo ;Enable this agent< ni check cheyakapothe agent schedule create avvadaa==
Agent schedule won>t create
5. ,f two nodes were there, then Agent is created by a user then whether two agent schedules created or not i.e.,
for each node. Two agent schedules created for each node
6. ,f interval is not specified then when it runs whether it saves or not= No it won>t save
8. 3hat>s the exact eaning of ;+ax !ecords< in schedule tab=
+y assupttion: +ax !ecords replace the eaning for +ax attepts, i.e., when agent unable to process the work
ite&activity ex: data class is lock by other operator( then that ite %ueued i.e., agent %ueue, fro that it retrives
and process it, if it solved its ok but if not solved then again it arranges in %ueue and again it process, it continues
until it reache nuber specified in +ax records field if and only if it fails to process.