|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
|
|
MA7k Support Pac |
« View previous topic :: View next topic » |
Author |
Message
|
prudvi raj |
Posted: Tue Mar 19, 2019 2:58 am Post subject: MA7k Support Pac |
|
|
Newbie
Joined: 11 Apr 2017 Posts: 3
|
Hello All,
I are using MQ v9.0.4.0. I have a requirement to send an email if the queue depth is greater than 1000 for that i wrote a java program and build a batch file to call the java program and place the batch file as a application id in process definition.
i tried to use MA7K support pac to always run the trigger monitor as a windows service in the background instead of doing it in console. i installed the MA7K support pac as a windows service by running the setup file but it is not generating any mail and triggering the application in process definition.
console command ex:RUNMQTRM -m TESTQMGR -q IQ
by running this i am able to get the mail.
MA7K service and my queue manager are in the same machine so i am using MQSeriesDLL=mqm.dll
Below is the configuration in my setup file can you please check and do need full.
*****************************************************************************
**
** This is a sample setup file that can be used with SETUP program
** from the MA7K supportpac.
**
** To use this file, enter: setup -f setup.ini
**
** Lines with a "*" in column 1 are comments.
** Lines that are totally blank are ignored.
**
** Blanks and tabs at the beginning and end of lines are ignored.
**
** See the "readme" for more information.
**
**
** The following stanza defines global variables
**
** Careful! Keywords are Case Sensitive
**
Global:
ShortTmr=60
ShortRty=10
LongTmr=1200
LongRty=999999999
EventLevel=11
WaitInterval=60000
MQSeriesDLL=mqm.dll
** The following is used to indicate where to find the key repository
** It is only relevant if one or more threads use MQCONNX (see "threads" below)
* KeyRepository=C:\mqm\Qmgrs\SSLTEST\ssl\key
** You can specify a service userid (in the form: domain\user) and password
** if ServiceUserid is specified but ServicePassword is NOT specified, then setup will
** prompt for it. If neither is specified, then "LocalSystem" is used.
** If the user is invalid, you will receive a "Error number 1057" at setup time
** Ensure the user has rights to logon as a service
* ServiceUserid=.\servUser
* ServicePassword=servPass
**
** The following only applies to Lotus Notes agents, see the readme
**
AgentRedirStdout=Yes
**
** If you wish to run this with the server libraries, change the
** following line to:
**
**MQSeriesDLL=mqm.dll
**
* MQSeriesDLL=mqic.dll
** For each thread to run, there is a "thread" stanza, maximum 16 stanzas
** Queue Manager names and Notes ini file names are optional.
** This defines a simple thread to read from the default initiation queue
** on the default queue manager.
*Thread:
*TriggerQueueName=SYSTEM.DEFAULT.INITIATION.QUEUE
** This starts and stops a simple service that is defined on the default queue manager
*Service:
*ServiceName=SYSTEM.DEFAULT.SERVICE
**This starts and stops a simple service that is defined on qmgr "Venus"
*Service
*ServiceName=MY.SERVICE
*ServiceQueueMgrName=Venus
** This defines a thread to read from a initq on qmgr "Venus"
* Thread:
TriggerQueueName=IQ
TriggerQueueMgrName=TESTQMGR
** This allows us to use the qmgr group facility of the client
* Thread:
* TriggerQueueName=MY.INITQ
* TriggerQueueMgrName=*QmgrGroup
** We can explicity call out the Notes ini filename for this thread
* Thread:
* TriggerQueueName=MY.INITQ
* NotesIni=c:\lotus\notes\mynotes.ini
** Or we can say to get the name from the Envrdata field of the trigger message
* Thread:
* TriggerQueueName=MY.INITQ
* NotesIni=Envrdata
** Or we can say to get the name from the Userdata field of the trigger message
* Thread:
* TriggerQueueName=MY.INITQ
* NotesIni=Userdata
** Or we can say to get the name from the Trigdata field of the trigger message
* Thread:
* TriggerQueueName=MY.INITQ
* NotesIni=Trigdata
* This thread uses MQCONNX to make the connection to the remote qmgr.
* MQCONNX is used when the CONNAME and CHANNEL parameters are specified, everything else
* can be defaulted.
* Thread:
* TriggerQueueName=MY.QUEUE.VIA.MQCONNX
* CONNAME=localhost(3000)
* CHANNEL=SYSTEM.DEF.SVRCONN
* These are optional and default to values shown
* Please note that chained exits are not supported, so you can only specify one exit for each exit type.
* LOCLADDR=
* HBINT=300
* RCVDATA=
* RCVEXIT=
* SCYDATA=
* SCYEXIT=
* SENDDATA=
* SENDEXIT=
* USERID=
* SSLCIPH=
* SSLPEER=
* KAINT=AUTO
*
*** End of sample |
|
Back to top |
|
|
Vitor |
Posted: Tue Mar 19, 2019 5:07 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
What does the event viewer say about your service? Or are you asserting that the service is running but your application is not producing emails?
How does your application react if (for example) it tries to send the email but can't connect to the email server? How and where would it report the error?
Where I'm going here is that it's all working when you run it from the a console logged on as you, but not when it runs from the non-terminal service context running as LocalSystem or some other user (unless the service is running with your personal credentials, which is a whole different can of worms!). So the first diagnostic path is the differences betweent the 2 scenarios and any resulting error messages. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
|
|
|
|
|
Page 1 of 1 |
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|
|