| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Establishing a TCP connection |
« View previous topic :: View next topic » |
| Author |
Message
|
| Hanuman |
 Posted: Mon Sep 25, 2006 9:29 pm Post subject: Establishing a TCP connection |
 |
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
is it necessary to do thos on solaris in order create a tcp channel....
| Quote: |
Establishing a TCP connection
To establish a TCP connection, follow these steps.
Edit the file /etc/services.
Note:
To edit the /etc/services file, you must be logged in as a superuser or root. If you do not have the following line in that file, add it as shown:
MQSeries 1414/tcp # MQSeries channel listener
Edit the file /etc/inetd.conf. If you do not have the following line in that file, add it as shown:
MQSeries stream tcp nowait mqm /opt/mqm/bin/amqcrsta amqcrsta
[-m queue.manager.name]
Find the process ID of the inetd with the command:
ps -ef | grep inetd
Run the command:
kill -1 inetd processid |
Found this on http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.csqzae.doc/csqzae1056.htm |
|
| Back to top |
|
 |
| anthony.barnes |
| Posted: Mon Sep 25, 2006 10:55 pm Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
What you have outlined is required on Solaris (up to 2.9 that is. Solaris 2.10 is a bit different in how the inet services are configured) if you want to have inetd monitor/create your connections for you. This is only the beginning of a TCP/IP connection.
The entry in the /etc/services file defines a logical name and binds it to a port number. This logical name is used by inetd when spawning amqcrsta to handle your connections.
In addition to this you will also need to define your sender/receiver channels as needed.
If you can elaborate a bit more on what you are trying to do it might be possible to help you a bit more. |
|
| Back to top |
|
|
| Hanuman |
| Posted: Mon Sep 25, 2006 11:39 pm Post subject: |
|
|
Voyager
Joined: 28 Aug 2006
Posts: 89
|
The thing is that i am trying to connect to solaris MQ server through Winxp mq client.
I have created a Qmanager, Q'e and a channel but still i get this error when i try to connect to the solris mq server....
I was seraching a lot on thsi i got this,,,, so i posted do i need to do the above setttings...
The error
| Quote: |
C:\Documents and Settings\942504> amqscnxc -x 3.209.124.60 QM_orf_qa01
Sample AMQSCNXC start
Connecting to queue manager QM_orf_qa01
using the server connection channel SYSTEM.DEF.SVRCONN
on connection name 3.209.124.60.
MQCONNX ended with reason code 2035 |
I need to resolve this pls help me out.... |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Sep 25, 2006 11:54 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Hanuman wrote: |
The thing is that i am trying to connect to solaris MQ server through Winxp mq client.
I have created a Qmanager, Q'e and a channel but still i get this error when i try to connect to the solris mq server....
I was seraching a lot on thsi i got this,,,, so i posted do i need to do the above setttings...
The error
| Quote: |
C:\Documents and Settings\942504> amqscnxc -x 3.209.124.60 QM_orf_qa01
Sample AMQSCNXC start
Connecting to queue manager QM_orf_qa01
using the server connection channel SYSTEM.DEF.SVRCONN
on connection name 3.209.124.60.
MQCONNX ended with reason code 2035 |
I need to resolve this pls help me out.... |
If you search a bit more on what a reason code 2035 means, you'll crack your problem. 
Hint - I doubt it's a network problem. I think your TCP/IP is probably right 
Tip - once you've got it all working, you might want to consider defining your own channel rather than using SYSTEM.DEF.SVRCONN. Search through this forum for a few discussions as to why; but it's only best practice. Keep going as you are until it works. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| anthony.barnes |
| Posted: Tue Sep 26, 2006 12:08 am Post subject: |
|
|
Apprentice
Joined: 01 Jul 2003
Posts: 26
Location: Oak Brook, Illinois
|
| Hanuman wrote: |
The thing is that i am trying to connect to solaris MQ server through Winxp mq client.
I have created a Qmanager, Q'e and a channel but still i get this error when i try to connect to the solris mq server....
I was seraching a lot on thsi i got this,,,, so i posted do i need to do the above setttings...
The error
| Quote: |
C:\Documents and Settings\942504> amqscnxc -x 3.209.124.60 QM_orf_qa01
Sample AMQSCNXC start
Connecting to queue manager QM_orf_qa01
using the server connection channel SYSTEM.DEF.SVRCONN
on connection name 3.209.124.60.
MQCONNX ended with reason code 2035 |
I need to resolve this pls help me out.... |
The error code you gave resolves out to:
| Quote: |
2035 X'07F3' MQRC_NOT_AUTHORIZED
The user is not authorized to perform the operation attempted:
On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager.
|
It may be that the account you are running the command with is not a member of the local mqm group? Not sure.
I do recall their being a few ENV variables that I needed to set when making a client connection. One was MQSERVER and I think there where two others if you wanted to use a table file for the client channel def.
You will want to check out the MQ Client document. It's all in there. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 26, 2006 12:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anthony.barnes wrote: |
I do recall their being a few ENV variables that I needed to set when making a client connection. One was MQSERVER and I think there where two others if you wanted to use a table file for the client channel def.
You will want to check out the MQ Client document. It's all in there. |
Quite right, but these have nothing to do with a 2035, and the resolution to this is not found in the Clients manual! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Sep 26, 2006 12:26 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| anthony.barnes wrote: |
The error code you gave resolves out to:
| Quote: |
2035 X'07F3' MQRC_NOT_AUTHORIZED
The user is not authorized to perform the operation attempted:
On an MQCONN or MQCONNX call, the user is not authorized to connect to the queue manager.
|
It may be that the account you are running the command with is not a member of the local mqm group? Not sure.
|
Hanuman
Ok, so you don't need to look up 2035 now.... 
Again as a best practice point don't add too many people into the local mqm group in the manner anthony.barnes implies. It's a common problem where this is done, people end up with global authorities and all sorts of things start to happen. Define new groups, authorise them for the MQ objects they need to use and add people to them as required. It's far easier to keep control than take it back! 
Only my 2 cents obviously. Your system, use it as you see fit. You can resolve your 2035 by putting mqm in the MCA User Id of the channel if you want, that'd do it.
But I really wouldn't recommend it. Really, really wouldn't. 
_________________
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
|
|
|
|
