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 » Cannot deploy bar file to broker

Post new topic  Reply to topic
 Cannot deploy bar file to broker « View previous topic :: View next topic » 
Author Message
javaforvivek
PostPosted: Thu Jan 27, 2005 10:50 pm    Post subject: Cannot deploy bar file to broker Reply with quote

Master

Joined: 14 Jun 2002
Posts: 282
Location: Pune,India

I am getting following error while trying to deploy the .bar file on WBRK_BROKER on my own machine.

BIP1549E: Unable to find required execution group document in the configuration repository.

When deploying configuration data, the document for execution group '5538c7a8-0101-0000-0080-dd2035824edc' could not be found in the configuration repository. Another document has referenced this document, and it is required for the successful completion of the deploy operation. The referencing broker document is of type 'null'.

The execution group document '5538c7a8-0101-0000-0080-dd2035824edc' is not available. This is an internal error. Contact your IBM support center.

I am on WBIMB5+CSD4, Win2K, admin login, both Config Mgr and Broker are on the same machine.
There are three exec groups : admin,defult and the third one shows:
Execution Group Restricted Access.

This error appeared when I tried to delete the third exec group from my domain through toolkit.
Any solution?
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
kirani
PostPosted: Fri Jan 28, 2005 12:38 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

You may have restricted authorizations for the EG that you are trying to delete.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
kirani
PostPosted: Fri Jan 28, 2005 12:40 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

You may not have authorizations for the EG that you are trying to delete.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
javaforvivek
PostPosted: Fri Jan 28, 2005 12:55 am    Post subject: Reply with quote

Master

Joined: 14 Jun 2002
Posts: 282
Location: Pune,India

Well,
This is an administrative task then...
I have one more question about this:
We (I mean most of us) have A Primary Domain Controller Windows Machine as DOM1 and our workstations are in LAN with each other.
As one of the developers of WBIMB, I have installed it on my machine with a userid 'admin' which is local userid (This id doesn't exist in domain).
I also have my domain id - puranikv on DOM1.
During installation of WBIMB it created all the mqm and mqbr* groups on my machine.
I added DOM1\puranikv to these groups. And it worked fine.. I had all the rights to configure and administer WBIMB.

But some time afterwards, my machine was configured to other domain DOM2, and I had to login using DOM2\puranikv. Again, I added this userid to the mqm and mqbr* groups on my machine, but it didn't work.
I couldn't connect to my configmgr through the toolkit and it gave the famous error of:
TopicRoot information was not received from the Configuration Manager. Either the Configuration Manager is not available or the user 'puranikv@DOM2' does not have authority to view the object. (UUID='TopicRoot', required attribute='topicroot.defaultpolicy')
and so on


Then I had to recreate my configmgr and broker with DOM2\puranikv login.
It worked fine again.
I fear, if in future my domain again changes to DOM3, I will have to recreate configmgr and broker using that userid.
Is there any solution to this?
Is it the same funda of creating new usergroups mqm and mqbr* on DOM2 domain controller and adding these global groups to my machine's mqm and mqbr* groups, instead of adding the domain users directly to my machine's mqm and mqbr* groups??
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
kirani
PostPosted: Fri Jan 28, 2005 11:35 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

What command did you use to create config mgr? Do you have mqb* groups defined on your domain?
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
javaforvivek
PostPosted: Sun Jan 30, 2005 9:48 pm    Post subject: Reply with quote

Master

Joined: 14 Jun 2002
Posts: 282
Location: Pune,India

There are NO mqm and mqbr* groups defined on my PDC(Primary Domain Controller) machine.
I think, that is what gives me trouble.
As my question says, I have two domains DOM1 and DOM2.
Should I ask my network administrator to create these groups on both PDC machines? And then add these groups to the local mqm and mqbr* groups of my machine?
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
jefflowrey
PostPosted: Mon Jan 31, 2005 5:59 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

You can only configure the ConfigMgr to authenticate against a single domain, as I understand it.

That doesn't mean you can't authenticate users in DOM1 from a configMgr set up on DOM2, though.

You should schedule a meeting with your domain administrator, and together figure out what users need to be authenticated, and where you want the ConfigMgr to connect, and then try and figure out how to set up the ConfigMgr.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
javaforvivek
PostPosted: Mon Jan 31, 2005 8:40 pm    Post subject: Reply with quote

Master

Joined: 14 Jun 2002
Posts: 282
Location: Pune,India

Yes,
You are right jefflowry.
The scenario is that when many developers working on different domains,
should have access to a single configmgr, which is created on a different domain.
They should be able to connect to the broker domain through their toolkit and should be able to deploy and debug the message flows.
The unfortunate part is that the Network administrators are innocent about what previleges do the developers need for this and I think that we, the senior team members of the project, should confirm it ourselves that what previleges we need to do our tasks.
_________________
Vivek
------------------------------------------------------
...when you have eliminated the impossible, whatever remains, however improbable, must be the truth.
Back to top
View user's profile Send private message Visit poster's website MSN Messenger
PeterPotkay
PostPosted: Tue Feb 01, 2005 6:00 am    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722

Vivek, I am about to start dealing with this myself. The Config Manager will be in DOMAIN1, a Win2000 domain. Users from DOMAIN1, DOMAIN2 and DOMAIN3 will need access. DOMAINs 2 and 3 are not Win2000 domains, but NT4 domains.

Check out pages 90-92, 267-270 in the Message Broker Configuration Administration and Security Manual.
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
kirani
PostPosted: Tue Feb 01, 2005 11:45 pm    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Some of the page numbers could change dependin on the version number of the manuals. Most of these manuals were refreshed with CSD4.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Cannot deploy bar file to 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.