When using a Standard agent you must be creating queue items. Each queue item represents a work object that needs to be processed. Agents running on multiple nodes will distribute the load automatically and work on distinct queue items. Unless you are setting requeueOnSuccess flag , once the queue item is processed it gets deleted from the queue table. This way a work object will not be processed more than once.Standard Agents support Auto Queue management by default and you do not have to take explict code to handle multinode configuration. 

Thanks Talaa.

Requirement: EOD file has to be generated and it should be single file.

Environment structure: Multiple nodes.

By following the above approach it will created four different files on four nodes.

Is there a way we can achieve this with out manual intervention.

Thanks in Advance

Vinay.

Hi Vinay,

You can configure agent running on single node so that only single file gets created. You can configure to run this activity every hour based on the load etc.

2) if you want agent  to execute on all nodes, it may require to configure to get data from all the nodes and create another file at EOD

One of our team members created a logic to distribute the load. Lets say there are 10 nodes. Create 1 agent per node, amounting to a total of 10 agents. Then enable 1 agent per node from the scheduler. Finally write custom Java code using public apis to distribute the file to a different agent.

What if I am using advanced agent in the above scenario instead of Standard agent? How can i stop the agent to pick up the same item multiple times?

Is there a way we can eliminate contention and locking issue while using Advanced Agent