| Author |
Message
|
| satya_jammy |
 Posted: Mon Jan 04, 2010 5:39 am Post subject: Unable Connect to remote broker |
 |
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
Hi
i have installed MQ 7.0.1 and MB 7.0 in solaris machine and created a broker in the solaris machine.
I have installed MB7.0 toolkit in the windows (no mq s/wwas installed in the windows) and trying to connect to the newly created broker in the solaris machine.
I have given full permissions to the user id for accessing Qmanager in soalris . When i am trying to connect the windows is showing that it is trying to connect and giving an message that the remote broker is not running thought the broker is running in the solaris machine. do i need to do any setup for the broker running in the soalris so that i can connect to it from remote toolkit?? |
|
| Back to top |
|
 |
| mqmatt |
| Posted: Mon Jan 04, 2010 5:46 am Post subject: |
|
|
Grand Master
Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK
|
In order to administer a v7 broker remotely, there needs to be a SVRCONN channel running on the broker's queue manager with an associated TCP/IP listener active.
It's all (just) MQ configuration - you don't need to enable anything on the broker specifically.
You might want to try:
a) connecting to the broker using a local command (e.g. mqsilist), and
b) connecting remotely to the queue manager using an arbitrary MQ client application (i.e. not to the broker).
Whether or not these work will help you determine where the problem lies.
-Matt |
|
| Back to top |
|
|
| satya_jammy |
| Posted: Mon Jan 04, 2010 10:59 pm Post subject: |
|
|
Acolyte
Joined: 01 Oct 2009
Posts: 66
|
Hi
I tried to connect to the broker QM from the MQ explorer and able to connect successfully. But while i am trying to access the remote broker initially it gave me mq access related errors which i solved providing access to the user id for the Qmnager.
While i am trying to connect the broker the access related got fixed and it is connecting to the QM and failing with the error remote broker not running . I have checked the status of the broker and it says it is running. i am using trail version of the broker installed on solaris. please let me know what are the other factors i need to consider to access the remote broker from the toolkit 7.0. as i am successfully able to connect to the QM it seems some issue with broker.. please share your taughts |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Mon Jan 04, 2010 11:42 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| satya_jammy wrote: |
Hi
I tried to connect to the broker QM from the MQ explorer and able to connect successfully. But while i am trying to access the remote broker initially it gave me mq access related errors which i solved providing access to the user id for the Qmnager.
While i am trying to connect the broker the access related got fixed and it is connecting to the QM and failing with the error remote broker not running . I have checked the status of the broker and it says it is running. i am using trail version of the broker installed on solaris. please let me know what are the other factors i need to consider to access the remote broker from the toolkit 7.0. as i am successfully able to connect to the QM it seems some issue with broker.. please share your taughts |
That is a step forward.
Are you using EXACTLY the same connection details for the toolkit?
This includes the channel name.
_________________
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 |
|
|
| ronsho |
| Posted: Thu May 20, 2010 10:00 am Post subject: Same problem |
|
|
Newbie
Joined: 20 May 2010
Posts: 6
|
Hey,
I'm having the same problem with WMB 7.0 on Linux.
Did you succeed in solving this?
Thanks,
Ron. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu May 20, 2010 11:34 am Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
Lets pretend its a new problem... Tell us what you have done and sw versions.
_________________
-wayne |
|
| Back to top |
|
|
| ronsho |
| Posted: Thu May 20, 2010 2:48 pm Post subject: |
|
|
Newbie
Joined: 20 May 2010
Posts: 6
|
I made some progress, here's the info:
I'm running WMB 7.0.0.0 on RHEL 5.3 64bit
Toolkit version 7.0.0 on Windows
Steps I'm performing:
1. Create the broker with command:
mqsicreatebroker WMB_BK -q WMB_QM
2. Open the toolkit, and create a remote broker connection
* I'm getting several 2035 errors so I use the following commands to fix them:
setmqaut -m WMB_QM -t qmgr -p [username] +all
setmqaut -m WMB_QM -n SYSTEM.BROKER.DEPLOY.QUEUE -t q -p [USER_NAME] +all
3. Try to connect with the toolkit again
* This time I get an error: "Remote broker is not running"
4. I added the user to unix groups mqm and mqbrkrs and now the toolkit connects without problems
So my new question is: what are the proper permissions needed in order to connect the toolkit to WMB and administer it?
The documentation (http://publib.boulder.ibm.com/infocenter/wmbhelp/v7r0m0/topic/com.ibm.etools.mft.doc/be10200_.htm) states that only connect permission is enough, but it didn't work.
Thanks,
Ron. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu May 20, 2010 2:58 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
you didn't list "mqsistart" ...
_________________
-wayne |
|
| Back to top |
|
|
| ronsho |
| Posted: Thu May 20, 2010 2:59 pm Post subject: |
|
|
Newbie
Joined: 20 May 2010
Posts: 6
|
Good observation 
but I did start the broker.. |
|
| Back to top |
|
|
| wschutz |
| Posted: Thu May 20, 2010 3:07 pm Post subject: |
|
|
Jedi Knight
Joined: 02 Jun 2005
Posts: 3316
Location: IBM (retired)
|
what does mqsilist say?
_________________
-wayne |
|
| Back to top |
|
|
| ronsho |
| Posted: Thu May 20, 2010 3:19 pm Post subject: |
|
|
Newbie
Joined: 20 May 2010
Posts: 6
|
BIP1284I: Broker 'WMB_BK' on queue manager 'WMB_QM' is running.
BIP8071I: Successful command completion.
When you create a new broker, which MQ permissions (setmqaut) do you give it to connect with the toolkit? Only +connect as the documentation suggests? |
|
| Back to top |
|
|
| humanRebody |
| Posted: Tue Jan 11, 2011 4:01 am Post subject: |
|
|
Novice
Joined: 05 Feb 2010
Posts: 15
|
Any updates on this issue?
I also got the 2035 error but I have already followed the procedure mentioned in MQv7 infocenter. Please advise. Thanks.
Regards,
THomas  |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 11, 2011 4:03 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| humanRebody wrote: |
Any updates on this issue?
I also got the 2035 error but I have already followed the procedure mentioned in MQv7 infocenter. Please advise. Thanks.
Regards,
THomas |
Let's pretend it's a new issue.
Start a new thread.
Post all of the details of the configuration you have done. |
|
| Back to top |
|
|
| ronsho |
| Posted: Tue Jan 11, 2011 7:46 am Post subject: |
|
|
Newbie
Joined: 20 May 2010
Posts: 6
|
| I solved the problem by adding the user to the mqm group |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Jan 11, 2011 8:05 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ronsho wrote: |
| I solved the problem by adding the user to the mqm group |
That's like solving the problem of your front door squeaking by taking the door off the hinges. 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
