| Author |
Message
|
| anthony.barnes |
 Posted: Mon May 01, 2006 5:06 pm Post subject: Triggering a 6.5.4 Lotus Notes Agent from MQ 5.3.11 on Winte |
 |
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
Greetings folks,
I have been having issues trying to get MQ 5.3.11 to trigger a 6.5.4 Lotus Notes agent on a Win2K3 server and was wondering if the 6.0.1 version of the trige22.exe I received in ma7K isn't up to the task.
The trigger appears to be firing as I am receiving EventLevel 2 information in my Event Log but the Agent isn't doing what the Lotus development guys are telling me it should be doing.
Anyone have any input one way or the other? Should the 6.0.1 trige22.exe be able to handle a 6.5.4 Notes Agent?
Your input is greatly appreciated!
Tony B |
|
| Back to top |
|
 |
| wschutz |
| Posted: Tue May 02, 2006 8:56 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
So is the agent running at all? or just not running? Can you turn the event tracing up to level 3 and post a "tiggered" event?
_________________
-wayne |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Tue May 02, 2006 12:43 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
Wayne,
All of the data I can see indicates that MQ is properly calling the Notes Agent however there is no 'activity' from the Notes Agent.
On your suggestion I bumped the tracing up (I went to 4) and have what appear to be valid events that do not indicate an errors that I can see. I can post snippets from the event logs if that would help.
To further test my triggering I shut down the Trigger Monitor and I was able to validate that my application queue is triggering a message to my initQ. Once I re-started the monitor the message in the initQ was consumed but again... nothing from the Notes Agent.
What else I can provide to help you help me? |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu May 04, 2006 2:55 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
You should see a log event with the eyecatcher of "AgentRun", your database nad agent names. If thats coming back with rc=0, then the agent should be running. Perhaps you can post that one event log entry.
_________________
-wayne |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Fri May 05, 2006 2:01 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
Wayne,
Below are logs for my latest test in which I:
1. Started the Trigger service.
2. Ran the application that generates and places a message in my App Q.
3. Verified that there is a message in my app Q.
4. Verified that some Eventlogs had been generated.
5. Stopped the Trigger service.
Here are the Application Event logs from the process:
WebSphere MQ Client Trigger Service V1.3.2 (20 Nov 2003) Starting.
WebSphere MQ Client Trigger Service Started using parms: WaitInterval=60000 LongRty=999999999 LongTmr=1200 ShortRty=10 ShortTmr=60 EventLevel=4.
Handle = 1335648, State = 4, Controls= 7, ExitCode = 0, Specific = 0, CheckPt = 0, WaitHint = 0
Thread started to watch: Q="SYSTEM.IDT.RESPONSE.AGENT.INITQ" Qmgr="IDTMQT1" NotesIni="D:\Lotus\Domino\notes.ini" (Th# 0).
Rc = 2033 from MQGET
Rc = 2033 from MQGET
Rc = 2033 from MQGET
Rc = 0 from MQGET
"MQCMIT" returned 0 for queue "SYSTEM.IDT.RESPONSE.AGENT.INITQ" and qmgr "IDTMQT1".
Starting: "D:\Program Files\IBM\WebSphere MQ\ma7k\trige22.exe" "TMC 2IDT.RESPONSE SYSTEM.IDT.RESPONSE.AGENT.PROCESS D:\Lotus\Domino\Data\iaw\intacctwebsite.NSF Test1 IDTMQT1 " 0004 "D:\Lotus\Domino\notes.ini".
User Requested Service Stop.
Handle = 1335648, State = 3, Controls= 7, ExitCode = 0, Specific = 0, CheckPt = 1, WaitHint = 5000
WebSphere MQ Client Trigger Service Stopped. (See previous event message for stop reason) |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri May 05, 2006 8:26 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
It does not look like you are using
to put your app in the background. Be aware that any action on the trm before the triggered program exits might kill said triggered program. As well it will prevent any other trigger from being executed until the current triggered program exits...
Enjoy 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat May 06, 2006 2:46 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Um... at event level 4, you should be getting lots of messages out of trige22.exe. I know there have been problems in the past when the ma7k install directory had blanks in the name. Can you try re-installing it into something like "c:\ma7k" ?
_________________
-wayne |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Sat May 27, 2006 12:28 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
I FINALLY was able to get back on the server having this issue (and yes... I am the client Jean Lynch ask you about)
I have verifed that I am running with EventLevel > 2 (I'm at 4). I have also uninstalled the trigger software, rebooted the server, removed the software and redeployed on the D:\ drive under D:\ma7k (no spaces), ran setup, started the trigger service, put a test message onto my queue and... still not seeing anything like "Entering: trige22.exe (v1.3.2--Linked with Notes API)... " in the Windows Event Log.
Here is the output from when I re-ran setup from the new directory:
-------------------------------------------------------------------------------------
D:\ma7k>setup.exe -f setup.ini
Using configuration file: setup.ini
ShortTmr 60, ShortRty 10, LongTmr 1200, LongRty 999999999
EventLevel 4, WaitInterval 60000, MQSeriesDLL "mqm.dll"
Thread 0, TriggerQueueName="SYSTEM.IDT.RESPONSE.AGENT.INITQ"
TriggerQueueMgrName="IDTMQT1"
NotesIni="D:\Lotus\Domino\notes.ini"
Installing New Service
"IBM MQSeries Server Lotus Notes Trigger Service " Service installed
Creating new StartUp information.
-------------------------------------------------------------------------------------
Here are the three Eventlogs I received when I put in my test message:
-------------------------------------------------------------------------------------
Rc = 0 from MQGET
"MQCMIT" returned 0 for queue "SYSTEM.IDT.RESPONSE.AGENT.INITQ" and qmgr "IDTMQT1".
Starting: "D:\ma7k\trige22.exe" "TMC 2IDT.RESPONSE SYSTEM.IDT.RESPONSE.AGENT.PROCESS D:\Lotus\Domino\Data\iaw\intacctwebsite.NSF Test1 IDTMQT1 " 0004 "D:\Lotus\Domino\notes.ini".
-------------------------------------------------------------------------------------
Anything look out of sorts to your trained eye? |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Sat May 27, 2006 12:34 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
I just noticed the author's name for the package I'm using... I'm honored!
 |
|
| Back to top |
|
|
| wschutz |
| Posted: Sat May 27, 2006 4:08 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Open a command window, and try:
"D:\ma7k\trige22.exe" "TMC 2IDT.RESPONSE SYSTEM.IDT.RESPONSE.AGENT.PROCESS D:\Lotus\Domino\Data\iaw\intacctwebsite.NSF Test1 IDTMQT1 " 0004 "D:\Lotus\Domino\notes.ini".
and tell me what you see....
_________________
-wayne |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Thu Jun 08, 2006 3:00 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| wschutz wrote: |
Open a command window, and try:
"D:\ma7k\trige22.exe" "TMC 2IDT.RESPONSE SYSTEM.IDT.RESPONSE.AGENT.PROCESS D:\Lotus\Domino\Data\iaw\intacctwebsite.NSF Test1 IDTMQT1 " 0004 "D:\Lotus\Domino\notes.ini".
and tell me what you see.... |
I get success is what I get! Thank you!
I'm not clear on which of your suggestions did the trick but after the reisntall (to remove spaces from the path) and updating the system PATH to everything I could find in the Lotus directory I am up and triggering.
I will review my findings again and post a "tips" on the end of this thread so I can share your wisdom (and my learnings) with the world.
Thanks so much. |
|
| Back to top |
|
|
|
|
