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 » MB6.0 on Uinx

Post new topic  Reply to topic
 MB6.0 on Uinx « View previous topic :: View next topic » 
Author Message
Mensch
PostPosted: Thu Mar 16, 2006 10:40 pm    Post subject: MB6.0 on Uinx Reply with quote

Disciple

Joined: 17 Jul 2005
Posts: 166

Hi

I have to install and configure WBIMB6.0 on Unix environment .

Can we have Configuration manager , toolkit and broker running on the same UINX machine or we have to create Config mgr on separate Windows machine and deploy the flows on Broker running on Unix box?
_________________
Thanks and Regards ,
Mensch
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Thu Mar 16, 2006 11:04 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi Mensch,

I am not sure about the configMgr, but the toolkit is supported only on Linux and Windows....

You could go for the configMgr on the windows system itself as anyway in production, it need not be running all the time....that will save some resources on your prod. system.

Regards.
Back to top
View user's profile Send private message Send e-mail
Mensch
PostPosted: Thu Mar 16, 2006 11:10 pm    Post subject: Reply with quote

Disciple

Joined: 17 Jul 2005
Posts: 166

Hi
Thank you very much for ur reply...

U mean to say ,
I have to create beoker on UniX machine ....and create COnfig manager on Windows machine ..Q managers of both Will communicate using MQSeries channels .. But Hows does Toolkit interact with Broker and Config manager??
Any PDF or Link would appericiate.
_________________
Thanks and Regards ,
Mensch
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Thu Mar 16, 2006 11:19 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi Mensch,

In the toolkit create a new domain in the Domain view(Admin perspective).

Give the location of the configMgr and create a *.config file....

Now add the broker by giving the broker's name and QM name....

It should work...not sure about which document has this info...if i find it, i'll post it....but this should work with some fooling around

Do set up the channels. Best of luck.

Regards.
Back to top
View user's profile Send private message Send e-mail
lehare
PostPosted: Thu Mar 16, 2006 11:36 pm    Post subject: Reply with quote

Apprentice

Joined: 25 Jul 2005
Posts: 48

Mensch,

check out the book tp://ftp.software.ibm.com/software/integration/wbibrokers/docs/V6.0/messagebroker_Configuration_Administration_and_Security.pdf

should point you to the right direction

regards
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Mar 17, 2006 12:38 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

And you don't have to. In fact you can run the config manager on any platform the broker runs (V 6.0).

The toolkit however will only run on Win and Linux (V6.0).

Enjoy
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
Mensch
PostPosted: Fri Mar 17, 2006 1:22 am    Post subject: Reply with quote

Disciple

Joined: 17 Jul 2005
Posts: 166

Hi
If Config Manager and broker are running on Unix machine and toolkit is on other windows machine could you please tell me how toolkit wil communicate with config mgr and broker??

Also As far as performance is considered what is the best way to create database ..whether BKDB and CMDB should be on same unix machine or they should be on windows machine (where toolkit running)??
_________________
Thanks and Regards ,
Mensch
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Fri Mar 17, 2006 1:39 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi Mensch,

When the toolkit is installed the requisite MQ jars etc are installed too...

When you specify the QM of the configMgr you are also giving te IP address and port too...these are enough to connect to the remote ConfigMgr.

Once the ConfigMgr is connected you can give the Broker and Broker QM name....and since you have set up the channels between the configMgr and Broker, u dont have to worry about the location of the Broker.

Quote:
Also As far as performance is considered what is the best way to create database ..whether BKDB and CMDB should be on same unix machine or they should be on windows machine (where toolkit running)??

In v6 the database for the configMgr is created without user interaction and is not on DB2 but cloudscape.

In some projects i've found all databases on a seperate box...so the Broker and configMgr database are remote to the Broker and configMgr respectively.

If your Windows box running the toolkit has a decent RAM (1Gb) then put the configMgr there along with its database.
The broker's database, well you will have to see what other applications are running along with Broker...like WAS etc....
Also...is the application database also on the same system....you just have to consider your environment....

Regards.
Back to top
View user's profile Send private message Send e-mail
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

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