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 » Define broker in config manager using command line?

Post new topic  Reply to topic
 Define broker in config manager using command line? « View previous topic :: View next topic » 
Author Message
jnoubi
PostPosted: Mon Jun 02, 2008 3:05 am    Post subject: Define broker in config manager using command line? Reply with quote

Novice

Joined: 26 Sep 2006
Posts: 24

Initially I was trying to create an execution group but I got the following error:
"$ mqsicreateexecutiongroup -i HOSTNAME -p 1414 -q QMNAME -b BROKERNAME -e EG64
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1046E: Unable to connect with the Configuration Manager (Could not connect to queue manager 'QMNAME' (MQ reason code 2195)).
The utility encountered a problem while attempting to connect to the Configuration Manager's queue manager to put a message to its request queue."

After researching I noticed that I didnt configure the broker in the config manager, so I run the command: So I ran the deploy command and got the following:
BIP1044I: Connecting to the Configuration Manager's queue manager...
BIP1046E: Unable to connect with the Configuration Manager (Could not connect to queue manager 'QMNAME' (MQ reason code 2195)).

I guess somehow I need to make my config manager recognize my broker. I am doing all of this using AIX without toolkit. Any suggestions? good links that could help?
Back to top
View user's profile Send private message
Gaya3
PostPosted: Mon Jun 02, 2008 3:28 am    Post subject: Reply with quote

Jedi

Joined: 12 Sep 2006
Posts: 2493
Location: Boston, US

i dont think so you can create domain connections through command line prompt.

use your toolkit to create domain and connect to the broker.

regards
Gayathri
_________________
Regards
Gayathri
-----------------------------------------------
Do Something Before you Die
Back to top
View user's profile Send private message
AkankshA
PostPosted: Mon Jun 02, 2008 3:39 am    Post subject: Reply with quote

Grand Master

Joined: 12 Jan 2006
Posts: 1494
Location: Singapore

which version of MB are u on ??

U can connect broker with configMgr thru Command line only in 6.1
_________________
Cheers
Back to top
View user's profile Send private message Visit poster's website
broker_new
PostPosted: Mon Jun 02, 2008 3:51 am    Post subject: Reply with quote

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC

Using the setmqaut give the permisssions(+Connect)(For the user from which you are trying to connect Broker) on the Broker Queue manager.

setmqaut -m BrokerQM -t qmgr -userid +connect.
Then try to create execution group.
_________________
IBM ->Let's build a smarter planet
Back to top
View user's profile Send private message
jnoubi
PostPosted: Mon Jun 02, 2008 5:59 am    Post subject: Re: Reply with quote

Novice

Joined: 26 Sep 2006
Posts: 24

Thanks for the replies.

I am on 6.1, and I have created only one queue manager, on top of which I have built the broker and the config manager.

I tried the setmqaut but I am still getting the same error.
I think this is the source of the problem/solution but I may have to do some more tweaking.

Any other suggestions? is using 2 queue managers one for broker and another for Config Mgr is the better practice?
Back to top
View user's profile Send private message
ADV
PostPosted: Mon Jun 02, 2008 6:02 am    Post subject: Reply with quote

Apprentice

Joined: 24 Apr 2007
Posts: 44
Location: Boston, MA

BIP1046E: Unable to connect with the Configuration Manager

Check that the Configuration Manager's QM and listener are running, with correct port is specified for the QM.

If QM looks good, then it could be a authority issue. Do dspmqsut to see what authority user has? Can try adding Message Broker Toolkit local user ID to the mqm group on the Configuration Manager?
Back to top
View user's profile Send private message
mqmatt
PostPosted: Mon Jun 02, 2008 8:37 am    Post subject: Reply with quote

Grand Master

Joined: 04 Aug 2004
Posts: 1213
Location: Hursley, UK

To add a broker to a Configuration Manager domain in v6.1, use mqsicreateexecutiongroup -f.
Back to top
View user's profile Send private message
broker_new
PostPosted: Mon Jun 02, 2008 9:35 am    Post subject: Reply with quote

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC

Hey,
your userid is added into cfgmgr using mqsiaclentry
_________________
IBM ->Let's build a smarter planet
Back to top
View user's profile Send private message
DIPU@2007
PostPosted: Mon Jun 02, 2008 8:57 pm    Post subject: Is ur problem resolved..?? if not jus try this...:) Reply with quote

Novice

Joined: 13 Dec 2007
Posts: 18

Just try with -n CfgParameterFileName which specifies the name of .configmgr file that describes the connection parameters to the configuration manager.

for example :

mqsicreateexecutiongroup –n domain2.configmgr –b FRED –e EG3 –w 300 –v trace.txt
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 » Define broker in config manager using command line?
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.