Trigger a batch file on a Domino Partitioned server
Is there a way to use a batch file to trigger agent manager without having the batch file try to set up a new partition on the server?
Software/Hardware used:
Lotus Domino 8.5.1, Windows 2008 64 bit, 2 Domino partitions
Software/Hardware used:
Lotus Domino 8.5.1, Windows 2008 64 bit, 2 Domino partitions
ASKED:
April 7, 2010 3:31 PM
UPDATED:
April 9, 2010 7:33 PM
Answer Wiki:
I would recommend you set this up as a Server Progam document in the Domino Directory (NAB) with a repeat interval of 1.
This is the syntax.
Basics
Program name: nserver
Command line: -c "tell amgr run 'folderfilename.nsf’ 'agentname'"
Server to run on: servername here
Comments: Appropriate comment here so people know what it is doing.
Schedule
Enabled/disabled: Enabled
Run at times: 12:00 AM - 11:59 PM each day
Repeat interval of: 1 minutes
Days of week: Sun, Mon, Tue, Wed, Thu, Fri, Sat
Ensure your apostrophes and double apostrophes are straight, not curly.
Our dev server is partitioned. I just tested that this will work and it works fine.
To see all answers submitted to the Answer Wiki: View Answer History.
Can you explain the requirements so that I understand why you would use a batch file to run agent manager? And describe the results you are seeing, as I don’t see why running a batch file would set up a partition. Agent manager should already be running. You should use agent scheduling to run agents at the appropriate time, or, if there is extremely complicated logic for when the agent should run, write a LotusScript agent that runs on some schedule, evaluates that logic, and triggers the agent when it should run.
This agent I currently have running uses LotusScript to call Websphere MQ channel to pull XML messages to a Lotus Notes database. The current requirement is to have it polling Websphere as frequently as possible. I have setup a scheduled agent every minute. The issue I ran into was channels being left open on the MQ side due to no messages to retrieve (that has been resolved). This was setup on a dev box, non-partitioned and working more efficiently. The trigger I tried to use was placed on the program partition, i.e., e:notesnserver -c “tell amgr run ‘folderfilename.nsf’ ‘agentname’”. When this trigger is invoked through MQ on the production box it always tries to setup a new Domino partition.