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 » ConfigMgr Design

Post new topic  Reply to topic
 ConfigMgr Design « View previous topic :: View next topic » 
Author Message
Monk
PostPosted: Tue Jun 26, 2007 4:24 am    Post subject: ConfigMgr Design Reply with quote

Master

Joined: 21 Apr 2007
Posts: 282

Hi All,



Machine 1 : Runs Toolkit
Machine 2 : ConfigMgr1 and Broker1
Machine 3 : ConfigMgr1 and Broker1

Now I can access the Configuration managers on both Machine 2 and Machine 3 using Machine 1 in the toolkit and creating a new domain.

Is this a best practice?
_________________
Thimk
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Jun 26, 2007 4:38 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

It's a common practice.

If both configmgrs are using the same user repository, then it's redundant. If they aren't, then it's necessary.
_________________
I am *not* the model of the modern major general.
Back to top
View user's profile Send private message
Monk
PostPosted: Tue Jun 26, 2007 5:42 am    Post subject: Reply with quote

Master

Joined: 21 Apr 2007
Posts: 282

thanx for the reply ...

Now if I have the following configuration...

Machine 1 : Runs Toolkit and ConfigMgr1
Machine 2 : Broker1
Machine 3 : Broker2

Broker1 and Broker2 are connected to ConfigMgr1 thru MQ.

Is this better than the previous one.?

Is this the best practice?.
_________________
Thimk
Back to top
View user's profile Send private message
jefflowrey
PostPosted: Tue Jun 26, 2007 6:12 am    Post subject: Reply with quote

Grand Poobah

Joined: 16 Oct 2002
Posts: 19981

I guess best practice is to do what is correct for your situation.

If you're going to put ConfigMgr on a separate machine, it make some sense to throw Toolkit on there as well - it makes it easier to do things like register new brokers.

But I would never expect any broker deployment to only have Toolkit on a single machine.

It's equally valid to run one configmgr per broker as it is to run one configmgr per larger environment (dev, test, production).

It may be necessary, because of user registries, to run more than one configmgr per environment.

It may be redundant, because of user registries, to run one configmgr per broker. It's not wrong to do so, even if it's redundant.
_________________
I am *not* the model of the modern major general.
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 » ConfigMgr Design
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.