ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker toolkit not connecting Remote broker

Post new topic  Reply to topic
 Message Broker toolkit not connecting Remote broker « View previous topic :: View next topic » 
Author Message
praveenmq
PostPosted: Sun Apr 15, 2012 9:24 pm    Post subject: Message Broker toolkit not connecting Remote broker Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Hi ,

I am trying to connect a remote broker which is in AIX machine through MB toolkit in Windows.

I right clicked on brokers and selected a connect to remote broker.
Gave the QMname, Host, Port and channel name as SYSTEM.BKR.CONFIG.

When i clicked on connect it is display error as

A broker has not been defined on queue manager 'MQ01' (MQ reason code 2085 while trying to open a queue)

Check that,
1. The broker is running.
2. The TCP/IP port of the queue manager is active if it is remote


I checked and confirmed that broker is still running and the port 1414 is opened.

Could you please let me know is there anywhere i went wrong as am not able to connect to my broker remotely.

Thanks,
Praveen
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Apr 15, 2012 10:03 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Did you look in the MQ Infocentre for information relating to what

Code:

A broker has not been defined on queue manager 'MQ01' (MQ reason code 2085 while trying to open a queue)


This means?

That should be your starting point.
_________________
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
View user's profile Send private message
praveenmq
PostPosted: Sun Apr 15, 2012 10:05 pm    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Broker is alread configured with the queuemanager.
When i do a mqsilist i can see the Broker along with the Queue Manager configured.
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Apr 15, 2012 10:54 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

What does WMQ error 2085 tell you?

What does the WMQ Documentation tell you about the error?
It tells me this


Code:

C:\Users\sdavi>mqrc 2085

      2085  0x00000825  MQRC_UNKNOWN_OBJECT_NAME

C:\Users\sdavi>

_________________
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
View user's profile Send private message
praveenmq
PostPosted: Sun Apr 15, 2012 10:57 pm    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Yeah i checked the Channel

SYSTEM.BKR.CONFIG which am using to connect in MB Toolkit, Which exists in the Queue manager and the status of the channel is also running.

I dont know why it is telling Unknown object name?
Back to top
View user's profile Send private message
praveenmq
PostPosted: Sun Apr 15, 2012 11:09 pm    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

I think i found the answer ......

Its here

http://www.mqseries.net/phpBB2/viewtopic.php?p=279749&sid=d6abaecd1078ccb08791375ede1347dc


Thank you
Back to top
View user's profile Send private message
mapa
PostPosted: Mon Apr 16, 2012 12:40 am    Post subject: Reply with quote

Master

Joined: 09 Aug 2001
Posts: 257
Location: Malmö, Sweden

I assume you are telling us you were using a V7 toolkit for a V6 broker?

If you had written which versions of toolkit and broker in your initial post we would all have saved time...lesson learned for next question I hope
Back to top
View user's profile Send private message Visit poster's website
praveenmq
PostPosted: Mon Apr 16, 2012 12:45 am    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Sure ...Thank you
Back to top
View user's profile Send private message
praveenmq
PostPosted: Thu May 10, 2012 4:00 am    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Hi

The error is not cleared still. I tried using V6.1 MB Toolkit to connect remote broker V6.1 in AIX.

The below error is displayed when i tried to connect with the same version of toolkit.

BIP1711W: The ConfigManagerProxy is not viewable by user ict\pkumar

An attempt was made to view or manipulate the ConfigManagerProxy with UUID '', but the user who initiated this operation does not have the required authority to do so.

Ask the domain's administrator to grant your user ID the necessary authority to perform the requested action.


Also i have created aclentry using mqsicreateaclentry for the the user ict\pkumar

but still am unable to connect.
Is there any where i need to give special permission for my username in broker.

Thanks,
Praveen
Back to top
View user's profile Send private message
mqjeff
PostPosted: Thu May 10, 2012 4:44 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

praveenmq wrote:
Also i have created aclentry using mqsicreateaclentry for the the user ict\pkumar

You didn't create the correct one.
Back to top
View user's profile Send private message
praveenmq
PostPosted: Thu May 10, 2012 5:07 am    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

This is the command i executed for creating acl entry.

mqsicreateaclentry CONFIGMGR01 -u ICT -m "pkumar" -x F -b BROKER01
Back to top
View user's profile Send private message
praveenmq
PostPosted: Thu May 10, 2012 5:12 am    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

I just listed the acl entry but the entry shows something different


mqsilistaclentry CONFIGMGR01 -b BROKER01
BIP1778I: virtualxp-95421\xpmuser - USER - F - Broker - BROKER01
BIP1778I: ictpkumar - USER - V - Broker - BROKER01
BIP1778I: pkumar\ict - USER - F - Broker - BROKER01
BIP8071I: Successful command completion..
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu May 10, 2012 5:26 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

praveenmq wrote:
I just listed the acl entry but the entry shows something different


Imagine that.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
praveenmq
PostPosted: Thu May 10, 2012 5:36 am    Post subject: Reply with quote

Voyager

Joined: 28 Mar 2009
Posts: 96

Sorry for it.

I deleted the acl entry and recreated it. Now everything is perfect and am able to connect through Toolkit.
Thanks
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Message Broker toolkit not connecting Remote broker
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.