AboutPaski K. Paskaradevan Expertise I have 3 + years in Lotus Notes application development. I am a CLP R5 Application Development. I can answer any question pertaining to application development.
Experience R5 CLP. In addition, I have a bachelors degree in Engineering and a MBA.
Expert: Paski K. Paskaradevan Date: 12/31/2007 Subject: Call on agent in another database
Question Hi,
I'm wondering/hoping that this is possible. I'm trying to run an agent in one database from another. This is the basic scenario:
I have databases Audits.nsf on LOCAL and Questions.nsf on LOCAL.
I also have databases Audits.nsf on SERVER and Questions.nsf on SERVER.
During the runtime of the primary agent in Audits on local, the computer is not connected to the network.
Currently, I have an agent, part simple action, part Java, that when the computer is connected to the network, it copies all the documents in Audits on local to audits on server, then it deletes all documents in audits on local, and creates a starter document to serve as an example on audits.
This works just fine.
What I'd like to do in addition to this, is copy the Questions database from the server, and replace the Questions database on the local machine.
I'd also like to search for documents where a particular field value is null and delete it from the Audits database on the server.
I'm not too worried about writing agents to do these things, but I need the user to be able to do all of them with the click of ONE button, not 3 or 4.
So to recap, I need to execute agents that work on other databases from one database.
Do you have any suggestions?
Thanks in advance for your help!
Answer Hi,
As long as the agent is being run by a user (manual agent), it is possible to run agents in one database, which works on other databases on any server as well.
So, you will have one agent in one of your database, which will first connect to the Audits database and does what it is supposed to do. Once you finish this, in that same agent, write code to connect to the Questions database and do whatever you want to do.
So, in short, you will have one agent with two sets of codes one after the other which will do what you want to do.
If the operation you are doing on both databases are same, then you can have that in a subroutine or script library and call that routine, passing the necessary arguments to connect to the different databases. This way, it is easy to maintain the code. But if the actions are different, just put the whole thing in one agent.
In either case, the user will click only one button, since all the codes are in one agent.
