| Author |
Message
|
| neeha_kashyap120 |
 Posted: Wed Aug 10, 2011 12:43 pm Post subject: Editing the Setup.ini for ma7k fix pac |
 |
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
Hi
I am setting up the Client monitor service on a Windows client machine. I edited the setup.ini file to include the Channel table. I am not sure where to put those two lines. I want the client to connect using the MQCHLTAB file , I am not sure where to place these two statements.
SET MQCHLLIB
SET MQCHLTAB
When I use the Server name and channel name it works perfectly but I want to use the client channel tab
Please help
Here is my setup.ini file
| Code: |
*****************************************************************************
**
** 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
** 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=INITQ.TEST
** 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 "MDGTYD01"
Thread:
TriggerQueueName=INITQ.TEST
TriggerQueueMgrName=QM_TEST
** 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=INITQ.TEST
*CONNAME=TESTSERVER(1440)
*CHANNEL=QM_TEST
* 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
|
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
 |
| neeha_kashyap120 |
| Posted: Wed Aug 10, 2011 1:15 pm Post subject: |
|
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
I think my question should be how do I use CCDT in ma7k . There is an option to use the channel name and server name, but how do I use the CCDT
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 10, 2011 1:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Like you would if you weren't using the support pack.
You still need the environment variables to be set
you still need to pass a qmgr name.
You don't pass host or channel name.
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| neeha_kashyap120 |
| Posted: Wed Aug 10, 2011 1:46 pm Post subject: |
|
|
Apprentice
Joined: 05 Mar 2009
Posts: 31
|
Hi
I specified the two lines in the setup.ini file, but since I didnt know where to i commented out the CONNAME and channel name and added the two SET lines below them.
I got an error saying Invalid statement.
My requirement is this Windows clinet will need to connect to three different qmgrs. I am not sure how to do that.
Thanks
_________________
Neeharika Kashyap
IBM Certified System Administrator - WebSphere MQ V6.0
Trying to be IBM Certified System Administrator - WebSphere Message Broker V6.1 and IBM Certified Solution Developer - WebSphere Message Broker V6.1 |
|
| Back to top |
|
|
| exerk |
| Posted: Wed Aug 10, 2011 2:24 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| neeha_kashyap120 wrote: |
| My requirement is this Windows clinet will need to connect to three different qmgrs. I am not sure how to do that... |
Create your CCDT with the relevant CLNTCONN information for each of the queue managers and SET the environment variables, as already stated by fjb_saper. Search the Info Centre, it's all in there.
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Wed Aug 10, 2011 8:29 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Although I did not see in his sample
I imagine that some research and maybe an email or 2 to the writer/maintainer of the support pack would clarify that point, if simply using QMGRNAME does not work...
The other thing that I find bizarre is that you would want a trigger monitor to run against a channel table and not for each of the qmgrs in your channel table... Typically you do not run a trigger monitor on a random qmgr out of a specified set of qmgrs...
As such you would always specify the exact conname and channel even with a Multi-Instance qmgr (difference is in the conname)...
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Aug 12, 2011 9:17 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Right, so if you actually wanted to do this, it should be a matter of ensuring that the CCDT information is set in the environment that MA7K will be running under - that is, you need to set the relevant MQ environment variables in the SYSTEM so that they are available when the MA7K service starts.
Then you would use the standard
** This defines a thread to read from a initq on qmgr "MDGTYD01"
Thread:
TriggerQueueName=INITQ.TEST
TriggerQueueMgrName=QM_TEST
And it would find QM_TEST in the CCDT and use the information there to connect to it in the same way that any normal MQ Client would use the CCDT.
If this doesn't work, please *do* contact me by email so I can further assist you. |
|
| Back to top |
|
|
|
|
