| Author |
Message
|
| grasher134 |
 Posted: Wed Jan 21, 2015 5:37 am Post subject: Cannot connect to AIX MQ BROKER |
 |
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
I'm trying to connect to remote broker from Windows client and getting 2035 error.
MQ Broker is on AIX server.
First I've added my user to mqm and mqbrkrs groups on server. It didn't work.
Then I tried to set chlauth to my user.
SET CHLAUTH(*) TYPE(USERMAP) CLNTUSER('AleksandrAz') USERSRC(CHANNEL)
SET CHLAUTH(SYSTEM.ADMIN.SVRCONN) TYPE(ADDRESSMAP) ADDRESS('172.26.21.1-254') MCAUSER('mqm')
Got the same result.
Then I disabled chlauth but it didn't work either.
On windows server you must only add user to groups restart the server and that's it. Only had difficulties once, I solved it by creating .broker file. But it seems that it is impossible to create this file from console, is it?
Is there any place where I can see logs of connection attempts or something similar to it?
Sorry for my English. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jan 21, 2015 5:38 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Are you sure the windows client is using SYSTEM.ADMIN.SVRCONN? |
|
| Back to top |
|
|
| grasher134 |
| Posted: Wed Jan 21, 2015 5:42 am Post subject: |
|
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
| When I'm trying to add new QM in MQ Explorer I see SYSTEM.ADMIN.SVRCONN at server-connection channel field. So I think yes. |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Jan 21, 2015 6:54 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Adding a remote Qmgr in MQ Explorer will by default use SYSTEM.ADMIN.SVRCONN. Please don't use that channel and substitute one of your making.
Adding a remote Broker to IIB Explorer or Toolkit will by default use SYSTEM.BKR.CONFIG. Please don't use that channel and substitute one of your making.
Note that you can use the same channel to add both the Qmgr and Broker. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Jan 21, 2015 7:51 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| JosephGramig wrote: |
Adding a remote Qmgr in MQ Explorer will by default use SYSTEM.ADMIN.SVRCONN. Please don't use that channel and substitute one of your making.
Adding a remote Broker to IIB Explorer or Toolkit will by default use SYSTEM.BKR.CONFIG. Please don't use that channel and substitute one of your making.
Note that you can use the same channel to add both the Qmgr and Broker. |
Doing this is a lot easier to do when you use a .broker file.
Export your config to a .broker file. Edit to reflect the new remote broker and then setup a connection using the imported file. Doing it this way save me a lot of time the last time I did it.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| grasher134 |
| Posted: Wed Jan 21, 2015 9:47 pm Post subject: |
|
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
| JosephGramig wrote: |
Adding a remote Qmgr in MQ Explorer will by default use SYSTEM.ADMIN.SVRCONN. Please don't use that channel and substitute one of your making.
Adding a remote Broker to IIB Explorer or Toolkit will by default use SYSTEM.BKR.CONFIG. Please don't use that channel and substitute one of your making.
Note that you can use the same channel to add both the Qmgr and Broker. |
I'll do this in future. Now my immediate task is to connect to it somehow. I disabled CHLAUTH. It means no matter which channel do I use, it must let me connect to it. Or I got something wrong...
Is there any other port I must use?
| Quote: |
Export your config to a .broker file. Edit to reflect the new remote broker and then setup a connection using the imported file. Doing it this way save me a lot of time the last time I did it.
|
How can I create .broker file from AIX? I used this method in Windows, as I mentioned before. I tried to create broker file from my Windows server and replace ip address, but it didn't work. It shows me 2035/AMQ4036 |
|
| Back to top |
|
|
| grasher134 |
| Posted: Wed Jan 21, 2015 11:07 pm Post subject: |
|
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
Hate these *nix systems!!! 
I couldn't connect, because I created user in uppercase 'Aleksandraz'
and windows transferred it as 'aleksandraz', though it is in uppercase in Win.
Created new user, added it to mqm and mqbrkrs groups. And everything worked perfectly. Now I'll try to create specific channel, as was advised before.
Here is the instruction, that helped me a lot
http://www-01.ibm.com/support/docview.wss?uid=swg21250706 |
|
| Back to top |
|
|
| grasher134 |
| Posted: Wed Jan 21, 2015 11:31 pm Post subject: |
|
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
Now one problem left.
I cannot see my integration node from MQ Explorer, even using SYSTEM.ADMIN.SVRCONN. |
|
| Back to top |
|
|
| grasher134 |
| Posted: Wed Jan 21, 2015 11:44 pm Post subject: |
|
|
Acolyte
Joined: 22 Oct 2014
Posts: 62
|
Changed to SYSTEM.BKR.CONFIG and used modified .broker file.
Have no idea why did it worked only that way. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Thu Jan 22, 2015 8:37 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| grasher134 wrote: |
Changed to SYSTEM.BKR.CONFIG and used modified .broker file.
Have no idea why did it worked only that way. |
Possibly because some versions of the broker require you to manually edit the .broker file if your channel is not SYSTEM.BKR.CONFIG. No matter what you entered the .broker file gets saved with the default channel from Broker Explorer...
I believe that got fixed in later versions. If you edited the .broker file and replaced the channel name with the actual value it used the updated value from the .broker file when attempting to connect.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
