 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Trigger a batch file on a Domino Partitioned server</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/trigger-a-batch-file-on-a-domino-partitioned-server/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/trigger-a-batch-file-on-a-domino-partitioned-server/</link>
	<description></description>
	<lastBuildDate>Fri, 24 May 2013 10:59:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: klbg</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/trigger-a-batch-file-on-a-domino-partitioned-server/#comment-75691</link>
		<dc:creator>klbg</dc:creator>
		<pubDate>Thu, 08 Apr 2010 14:18:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-75691</guid>
		<description><![CDATA[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., &lt;b&gt; e:notesnserver -c &quot;tell amgr run &#039;folderfilename.nsf&#039; &#039;agentname&#039;&quot;.  When this trigger is invoked through MQ on the production box it always tries to setup a new Domino partition.&lt;/b&gt;]]></description>
		<content:encoded><![CDATA[<p>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., <b> e:notesnserver -c &#8220;tell amgr run &#8216;folderfilename.nsf&#8217; &#8216;agentname&#8217;&#8221;.  When this trigger is invoked through MQ on the production box it always tries to setup a new Domino partition.</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: brooklynegg</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/trigger-a-batch-file-on-a-domino-partitioned-server/#comment-75686</link>
		<dc:creator>brooklynegg</dc:creator>
		<pubDate>Thu, 08 Apr 2010 13:47:16 +0000</pubDate>
		<guid isPermaLink="false">#comment-75686</guid>
		<description><![CDATA[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&#039;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.]]></description>
		<content:encoded><![CDATA[<p>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&#8217;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.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 3/10 queries in 0.040 seconds using memcached
Object Caching 281/287 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-24 11:10:23 -->