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 » broker in MSCS environment

Post new topic  Reply to topic
 broker in MSCS environment « View previous topic :: View next topic » 
Author Message
pintrader
PostPosted: Wed Apr 16, 2014 5:26 pm    Post subject: broker in MSCS environment Reply with quote

Disciple

Joined: 22 Jan 2014
Posts: 164
hi,
a question on creating broker in MS clustering environment. the mqsicreatebroker command has a -w switch. (ie -w WorkPath). Can i confirm this switch need to be used when creating broker in MS clustering environment?

for example , if my shared disk is G drive and already there is an MQ directory there, then it is recommended to create in the MQ directory?

eg structure
--> G:\WMQ\qmgr
--> G:\WMQ\log

can i create it in say, G:\WMQ\log\Mybroker ?

Or is the -w switch not necessary in a clustering environment?
Back to top
View user's profile Send private message
smdavies99
PostPosted: Wed Apr 16, 2014 10:11 pm    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
There are a number of files created in the workpath directory when you create the broker.
ALL of these need to be available to the broker when running on the other node.
If they are not created by the

mqsiaddbrokerinstance

then IMHO you need to use it in a clustered environment. In my experience you can't create a service trace on the other node without them being there.

If you do use the -w option and defines a directory on your shared drive then you MUST also supply this to the

mqsiaddbrokerinstance

command.

You don't tell us what version of broker you are working with nor do you tell us what version of Windows you are running on. There might be other options you may need to use depending upon the version of Broker & Windows.
_________________
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
pintrader
PostPosted: Thu Apr 17, 2014 4:30 am    Post subject: Reply with quote

Disciple

Joined: 22 Jan 2014
Posts: 164
smdavies99 wrote:
There are a number of files created in the workpath directory when you create the broker.
ALL of these need to be available to the broker when running on the other node.
If they are not created by the

mqsiaddbrokerinstance

then IMHO you need to use it in a clustered environment. In my experience you can't create a service trace on the other node without them being there.

If you do use the -w option and defines a directory on your shared drive then you MUST also supply this to the

mqsiaddbrokerinstance

command.

You don't tell us what version of broker you are working with nor do you tell us what version of Windows you are running on. There might be other options you may need to use depending upon the version of Broker & Windows.


thanks for replying . cheers
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 » broker in MSCS environment
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.