| Author |
Message
|
| SarahMQ |
 Posted: Fri May 25, 2007 8:21 am Post subject: MQ Client Setup |
 |
|
Newbie
Joined: 25 May 2007
Posts: 3
|
Hi there,
first time I am setting up the MQ client and I have few questions , I did the follwing :
1. install MQ client on the client machine.
2. created SVRC channel on the server machine where the queue manager is .
3. Copy the AMQCLCHL.TAB file to the client machine from the server.
4. created the env variables on the client.
Is that all I need to do ?
The things which I am not sure about is :
1. when I created the new SVRC channel on the server , the AMQCLCHL.TAB didn't get updated and the date stamp was the same .
2. When I try to put a message to a queue using the client , I am able to do so , however , i don't see the SVRC channel starting .
3. There is an existing SVRC channel from before for a different client machine , will that cause an issue?
well you might as where is the question , humm ,, How will I know the set up if fine , if the .TAB file is not updated and when I tried to view it , I see old info in there , nothing related to the new channel I just created. Please advice |
|
| Back to top |
|
 |
| Al Pacino |
| Posted: Fri May 25, 2007 8:25 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
I am assuming we are talking about Intel servers here ?
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| SarahMQ |
| Posted: Fri May 25, 2007 9:00 am Post subject: |
|
|
Newbie
Joined: 25 May 2007
Posts: 3
|
| sorry for getting back late , yes I am using MQ 5.3 on Winodws 2003. |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri May 25, 2007 9:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Your method sounds right. Client connections are not specific to a given client machine, and one client channel can be used by multiple clients.
Make sure you take the TAB file from the @ipcc folder. I've seen early verions of v5.3 put copies in some odd places.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bbburson |
| Posted: Fri May 25, 2007 10:01 am Post subject: |
|
|
Partisan
Joined: 06 Jan 2004
Posts: 378
Location: Nowhere near a queue manager
|
To update your tab file you have to create CLNTCONN channel(s) that correspond to your SVRCONN channel(s). Make sure the CLNTCONN definitions include the connection information (IP, port) for access to your queue manager.
On the server side make sure the MQ listener is running. |
|
| Back to top |
|
|
| Al Pacino |
| Posted: Fri May 25, 2007 10:06 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2005
Posts: 114
|
You still need to create client connection , you never mention that in ur steps.
_________________
"We can't solve problems by using the same kind of thinking we used
when we created them." |
|
| Back to top |
|
|
| SarahMQ |
| Posted: Fri May 25, 2007 10:09 am Post subject: |
|
|
Newbie
Joined: 25 May 2007
Posts: 3
|
| Exactlly what I was missing , a client connection , thanks for all your help. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu May 31, 2007 5:43 am Post subject: |
|
|
Guest
|
| Quote: |
| You still need to create client connection , you never mention that in ur steps. |
Read the MQ V6 Clients manual. There are two flavors of clients. SVRCONN channels answer inbound requests for clients.
If you set MQSERVER=channelname/transporttype/connname, you don't invoke the client channel table. This method is simple, but somewhat inflexible.
If you set MQCHLLIB= and MQCHLTAB=, specifying the path to the table and the name of the table, then you invoke the client channel table. The table contains the CLNTCONN channel definitions created on the mq server AND exported to the client platform. This methodis more complicated; but is very flexible. |
|
| Back to top |
|
|
|
|
