AGENT: Category They are part of the SysAdmin category .
Instance Agent rule: Rule-Agent-Queue class. Rule-Agent-Queue class. Agent schedules: schedules: Data-Ag Dat a-Agent ent-Queue -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 AGENT rule are to be executed. 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 +anager checks checks for new or updated updated agents rule &and anually anually updated updated agent agent schedules( schedules( once every ten minutes. minutes . After you create an agents rule, the Agent +anager generates generates one Agent Agent "chedule "chedule instance instance for each node running running on your #rocess #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 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: Important: Te Agent Scedule Scedule instances instances must not "e created "y de#elopers – they are created only by only by the syste. -o not create or copy copy these instances instances /oweve /owever, r, the intern internal al +aster +aster Agent Agent proce process ss always always runs runs the highes highest'n t'nub ubere ered d versio version, n, not not rule rule resolution. i.e., Although 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 af ter 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 can run on all nodes. Agents that use the 1egacy %ueue ode, do not enable such such agents on ore than one one node.
Access The Nodes tab 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 "ta rt the the "yst "yste e +ana +anage geent ent app applic licati ation. on.
5. "e "ele lect ct a no node de.. 6.
"elect the Agent the Agent +anageent +anageent enu enu ite &Agents or "yste 7ueue +anageent(.
8. $lick a single single radio button button to identify identify a thread thread of an agent. &Each &Each agent agent activity activity executes executes in a separate thread.( 9.
se the button buttonss at the top of of the page to to start the the agent, agent, stop the agent agent,, or pause agent agent process processing. ing. 2ou can affect only the selected activity activity &one row of the for( or all activities. activities.
4.
Agent 3ide 3ide settings settings lo ;Enable ;Enable this agent< agent< ni check check cheyakap cheyakapothe othe agent agent schedule schedule create create avvadaa== avvadaa==
Agent schedule won>t create 5.
f two nodes were there, then Agent is created by a user 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 3hat >s the exact ean eaning ing of ;+ax !ecord !ecords< s< in in schedule schedule tab= 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.
