| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| How to make broker unavailable during deployment |
« View previous topic :: View next topic » |
| Author |
Message
|
| ruimadaleno |
 Posted: Thu Oct 08, 2015 8:47 am Post subject: How to make broker unavailable during deployment |
 |
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi all,
this may be understand as an strange/weird question but what can be done in broker to disable users to execute services/applications in websphere message broker, while the operations team is deploying message flows.
The goal here is to prevent users to make changes in data while news versions of message flows are being deployed.
environment:
Websphere message broker 8.0.0.5 running on windows 2008R2 server
Best regards
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Oct 08, 2015 8:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
You mean, other than stopping the flows?
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
| ruimadaleno |
| Posted: Fri Oct 09, 2015 12:41 am Post subject: |
|
|
Master
Joined: 08 May 2014
Posts: 274
|
Hi mqjeff,
right , that's an option: Stop the message flows that will be deployed , but, is it possible to take it to "another level" ?
Our applications are mainly message flows built with soap nodes (xml/http web services), so, we are looking for some way of stopping http connections while deploying (we are using embbeded http listeners - each execution group has a listener). So , stopping the execution group http listener is a possibility , but, can it be done in message broker ?
_________________
Best regards
Rui Madaleno |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 09, 2015 12:55 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
don't you have quiet periods when activity is low?
In a previous job we used to schedule all WebServices updates for 02:00 on a Monday morning.
IMFO, this is far simpler that trying to update heavily loaded systems on the fly because I guess you are not using versioning on your WebService call URL
_________________
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 |
|
|
| fjb_saper |
| Posted: Fri Oct 09, 2015 3:34 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| ruimadaleno wrote: |
Hi mqjeff,
right , that's an option: Stop the message flows that will be deployed , but, is it possible to take it to "another level" ?
Our applications are mainly message flows built with soap nodes (xml/http web services), so, we are looking for some way of stopping http connections while deploying (we are using embedded http listeners - each execution group has a listener). So , stopping the execution group http listener is a possibility , but, can it be done in message broker ? |
This is a perceived answer to a perceived symptom...
What is the underlying requirement?? 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| Vitor |
| Posted: Fri Oct 09, 2015 5:03 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ruimadaleno wrote: |
| so, we are looking for some way of stopping http connections while deploying (we are using embbeded http listeners - each execution group has a listener). So , stopping the execution group http listener is a possibility , but, can it be done in message broker ? |
What's the difference between stopping the EG listener (if you can, which I believe you can't) and stopping the flows? Both methods will stop flows processing messages.
| ruimadaleno wrote: |
| The goal here is to prevent users to make changes in data while news versions of message flows are being deployed. |
What's wrong (as has been suggested) with either telling the users not to process during the deploy window (which we do here) or put versioning on the URLs?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Fri Oct 09, 2015 5:20 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
How about putting apache or WAS IHS in front of your EG listeners, so that among other benefits, all of your users can use a single hostname/port for all of your flows.
Then you can simply stop the http server.
Also.
You really don't need to stop the flows or the incoming requests during deployment. Broker has really always handled this just fine. It lets existing threads complete before it starts new threads with the new code.
_________________
chmod -R ugo-wx / |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
