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 » Configuration

Post new topic  Reply to topic
 Configuration « View previous topic :: View next topic » 
Author Message
dipankar
PostPosted: Fri Nov 11, 2005 2:30 am    Post subject: Configuration Reply with quote

Disciple

Joined: 03 Feb 2005
Posts: 171

Hi,
Is it possible to configure the following setup for message broker 6.0?

1) Configmgr and Broker are on system A (windows).
QMGR 'TEST' for Configmgr in system A.

2)Workbench in other system B (windows).

I have created configmgr and broker using local user 'mqsiuid', not domain user in system A.
Now using local user 'mqsiuid', I want to work with workbench in system B.

When I wanted to create domain connection in workbench, it gives the following error-
BIP0915E Message Brokers Toolkit is unable to communicate with the Configuration Manager.
Reason:
Websphere MQ queue manager TEST cannot be reached.

In detail I found this
Quote:
User mqsiuid@B is not authorized to connect to queue manager 'TEST' (MQ reason code 2035 while trying to connect)

How can I give authorization to mqsiuid in system A? As both user mqsiuid are local, I could not able to add mqsiuid@B in local group mqm of system A.

Any idea?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Sun Nov 13, 2005 2:23 am    Post subject: 2035 == NOT AUTHORISED Reply with quote

Jedi Council

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

Your client can't connect to the ConfigMgr Queue Manager as it is not authorised.
There are many well documented ways to overcome this including but not limited to:-
- Make you client user a member of the mqm group
- change the mcauser param of your client connection channel to "MQM"
- etc etc etc

If you look in the error log of the TEST Queue manager, you will see the incoming connection request logged as it failed. It will show the 2035 error there.
This problem is part 2 of "I can't get my client to connect to the QMGR"
Part 1 is getting a 2059 error
_________________
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
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Configuration
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.