Agent for multiple server setup

I’m suppose to create a reminder agent for a database that has (at this point unknown to me) x number of replicas. I’ve been reading about agents in clusters and such on the server. Not sure about the terminology here. Is this considered a cluster? Or maybe a hub?

In any case, right now I can think of two possiblities. I can write an agent to run on one of the servers to send out all the past due reminders. However, if I do that, and I include a link, won’t all those links point back to my server and not a different server than might be closer?

Or I can write some script that determines what server the agent is running on and then send out only reminders for documents that pertain to that location. If I do that, should it work? Have I overlooked anything? And would I set the agent to run on any server, or would I need to have each location set up the agent to just run on that server. If I do that, then couldn’t I just make a slightly different version of the agent for each location? Not sure what is the best way here?

Any suggestions would be welcomed. Thanks.

Subject: Agent for multiple server setup

A couple of suggestions:

Search Agent FAQ for the word “cluster”

http://www-10.lotus.com/ldd/46dom.nsf/7e6c7e584a76331b85256a46006f083e/574c99ccb345839185256976004e811e?OpenDocument

Search this forum for the words “cluster” and “agent”