| Author |
Message
|
| Kalianne |
 Posted: Sat May 08, 2010 12:26 pm Post subject: I cant connect on my new Broker on AIX |
 |
|
Newbie
Joined: 08 May 2010
Posts: 4
|
Hi everyone!
I was trying to create a broker instance on AIX.
First I created the database in DB2 and after I did this:
mqsicreateconfigmgr CMBKRTEST -i user -a password -q QMBKRTEST
mqsicreatebroker BKRTEST -i user -a password -q QMBKRTEST -n DBBKRTEST
mqsistart CMBKRTEST
mqsistart BKRTEST
Everythig was created with sucess!!!
SVRCONN channel is started and I can listen port 1414, but I can't connect using my Toolkit.
I commited some mistake or I forgot some step?
Thanks! |
|
| Back to top |
|
 |
| harish_td |
| Posted: Sat May 08, 2010 9:25 pm Post subject: |
|
|
Master
Joined: 13 Feb 2006
Posts: 236
|
Are you able to telnet to this server on port 1414?
What is the error that you see when the toolkit attempts to connect to the remote broker? |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sun May 09, 2010 4:46 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
As you're obviously not using the toolkit on AIX, did you create the ACL entry on the config mgr for the id running the toolkit? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Kalianne |
| Posted: Mon May 10, 2010 6:00 am Post subject: |
|
|
Newbie
Joined: 08 May 2010
Posts: 4
|
| harish_td wrote: |
Are you able to telnet to this server on port 1414?
What is the error that you see when the toolkit attempts to connect to the remote broker? |
Yes... I can do that!
I got this error: User Kalianne is not authorized to connect to queue manager 'QMBKRTEST' (MQ reason code 2035 while trying to connect)
But I had already done this:
mqsicreateaclentry CMBKRTEST -u Kalianne -m mymachinename -x F -p |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 10, 2010 9:34 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Kalianne wrote: |
But I had already done this:
mqsicreateaclentry CMBKRTEST -u Kalianne -m mymachinename -x F -p |
So that user's allowed to connect to the WMB component, but not the underlying queue manager. 2035 is a WMQ error not a WMB one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Kalianne |
| Posted: Mon May 10, 2010 9:46 am Post subject: |
|
|
Newbie
Joined: 08 May 2010
Posts: 4
|
| Vitor wrote: |
| Kalianne wrote: |
But I had already done this:
mqsicreateaclentry CMBKRTEST -u Kalianne -m mymachinename -x F -p |
So that user's allowed to connect to the WMB component, but not the underlying queue manager. 2035 is a WMQ error not a WMB one. |
Right, my bad.
That user (Kalianne) is trying to connect on queue manager 'QMBKRTEST' using Toolkit (it is in other machine).
What kind of authorization should I give?
Thanks! |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 10, 2010 10:19 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Kalianne wrote: |
| What kind of authorization should I give? |
Well, connect at least! 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| Kalianne |
| Posted: Mon May 10, 2010 10:27 am Post subject: |
|
|
Newbie
Joined: 08 May 2010
Posts: 4
|
| Vitor wrote: |
| Kalianne wrote: |
| What kind of authorization should I give? |
Well, connect at least! |
My user (Kalianne) isn't in the same server where broker is...
So I got this error:
home/wbiadmin $ setmqaut -m QMBKRTEST -t qmgr -p Kalianne +all
AMQ7026: A principal or group name was invalid. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon May 10, 2010 10:41 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Kalianne wrote: |
| My user (Kalianne) isn't in the same server where broker is... |
Then you'll need a user that is. Or use some other method to supply credentials. This is standard WMQ security stuff, you'll find a lot of discussion of this in here & obviously the documentation.
Don't let the fact that this queue manager is being used by WMB components confuse you.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| dsch |
| Posted: Fri Dec 21, 2012 2:31 am Post subject: |
|
|
Newbie
Joined: 21 Dec 2012
Posts: 1
|
the problem was solved for me by setting
MCAUSER to 'mqsi' on SYSTEM.BKR.CONFIG svrconn channel |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Fri Dec 21, 2012 8:11 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
So, you don't care about securing this Qmgr or broker?
Or you don't understand you opened this up to all comers... |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Dec 21, 2012 12:38 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| dsch wrote: |
the problem was solved for me by setting
MCAUSER to 'mqsi' on SYSTEM.BKR.CONFIG svrconn channel |
So you solved the security problem by removing security?
This is analogous to fixing a stuck lock by removing the door to your house.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
