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 » messageflow should be stopped immediatly after deployment

Post new topic  Reply to topic Goto page 1, 2  Next
 messageflow should be stopped immediatly after deployment « View previous topic :: View next topic » 
Author Message
sandy vish
PostPosted: Tue Jan 29, 2013 11:43 pm    Post subject: messageflow should be stopped immediatly after deployment Reply with quote

Apprentice

Joined: 18 Nov 2012
Posts: 27

Hi i need to deploy a flow and the flow should be stopped, do we have option for doing so.... without using mqsistopmsgflow, i need to check wheter the we have permission to deploy in EG or not.....Valid response plzz
Back to top
View user's profile Send private message
Senthamizh
PostPosted: Wed Jan 30, 2013 1:02 am    Post subject: Reply with quote

Apprentice

Joined: 21 Dec 2009
Posts: 47

sandy vish wrote:
i need to deploy a flow and the flow should be stopped, do we have option for doing so.... without using mqsistopmsgflow


Don't deploy the flow, deploy it when you want to start the msgflow per your case...
Back to top
View user's profile Send private message
sandy vish
PostPosted: Wed Jan 30, 2013 1:10 am    Post subject: Reply with quote

Apprentice

Joined: 18 Nov 2012
Posts: 27

Valid usefull responses plz....
Back to top
View user's profile Send private message
kash3338
PostPosted: Wed Jan 30, 2013 1:25 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

http://publib.boulder.ibm.com/infocenter/wmbhelp/v8r0m0/index.jsp?topic=%2Fcom.ibm.etools.mft.doc%2Fbf23600_.htm

If your are using a lesser version of the product, you have other options as well like,

1. If the flow is listening to a MQ Queue, inhibit the queue
2. Use of Administrative API to do the deployment
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Wed Jan 30, 2013 1:43 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

kash3338 wrote:

1. If the flow is listening to a MQ Queue, inhibit the queue


Perhaps this should read

1. If the flow is listening to a MQ Queue, GET inhibit the queue

perchance?

Think about what would happen if the user enabled PUT inhibit?

Please note that GET Inhibiting the queue will cause an error to be logged to the system event log. Some sysadmins might get into a hissy fit over such trivialities.
_________________
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
zpat
PostPosted: Wed Jan 30, 2013 3:12 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

I raised this as a requirement some time back and it's now in WMB v8.

I vaguely remember seeing it mentioned in a WMB v7 fixpack but I am not 100% sure.
Back to top
View user's profile Send private message
kash3338
PostPosted: Wed Jan 30, 2013 3:14 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

smdavies99 wrote:

Perhaps this should read

1. If the flow is listening to a MQ Queue, GET inhibit the queue



Agreed. I should have been more specific.
Back to top
View user's profile Send private message Send e-mail
kash3338
PostPosted: Wed Jan 30, 2013 3:18 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

zpat wrote:
I vaguely remember seeing it mentioned in a WMB v7 fixpack but I am not 100% sure.


I guess this is the fix pack you mentioned.
Back to top
View user's profile Send private message Send e-mail
zpat
PostPosted: Wed Jan 30, 2013 4:11 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

kash3338 wrote:
zpat wrote:
I vaguely remember seeing it mentioned in a WMB v7 fixpack but I am not 100% sure.


I guess this is the fix pack you mentioned.


Ah yes, however 7005 is now available (which of course will include it).
Back to top
View user's profile Send private message
zpat
PostPosted: Wed Jan 30, 2013 4:13 am    Post subject: Reply with quote

Jedi Council

Joined: 19 May 2001
Posts: 5866
Location: UK

Oh look, my 4000th post - will I get a new title?

Sadly, No!
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Jan 30, 2013 7:12 am    Post subject: Re: messageflow should be stopped immediatly after deploymen Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

[quote="sandy vish"]Hi i need to deploy a flow and the flow should be stopped, do we have option for doing so.... without using mqsistopmsgflow, i need to check wheter the we have permission to deploy in EG or not.....

sandy vish wrote:
Valid response plzz


It would help if you asked a valid question. You asked:

sandy vish wrote:
Hi i need to deploy a flow and the flow should be stopped


which is not the correct question. You asked the correct question later which is:

sandy vish wrote:
i need to check wheter the we have permission to deploy in EG or not


to which the answer is not to deploy a flow and see if it fails, but to check the deploy security settings for the user id.

I'm assuming here you have some kind of generic automated deployment tool which needs to verify that a given user has deploy permissions against a given EG before doing a deploy in an environment with very granular security. Which makes the question only slightly valid. If you're just checking to see if the magic's gone away since the last time you checked then that's not a valid thing to do at all.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Jan 30, 2013 7:13 am    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA

zpat wrote:
Oh look, my 4000th post - will I get a new title?

Sadly, No!


But you do get congratulations.





_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
sandy vish
PostPosted: Thu Jan 31, 2013 12:53 am    Post subject: Reply with quote

Apprentice

Joined: 18 Nov 2012
Posts: 27

I have done GET inhibit the queue and still the input count is showing as 1 and the flow didnot stop.


Vitor

we are using automated deployment tool.

thanks for the inputs..........
Back to top
View user's profile Send private message
kash3338
PostPosted: Thu Jan 31, 2013 1:05 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

sandy vish wrote:
I have done GET inhibit the queue and still the input count is showing as 1 and the flow didnot stop.


When you GET inhibit a queue, it does not mean you are stopping a Message Flow. They are totally independent components. Your flow just would not be able to pick any messages from the queue and process. It should help in your scenario, since the message flow wont be processing the messages in the queue when you deploy the flow.
Back to top
View user's profile Send private message Send e-mail
mqjeff
PostPosted: Thu Jan 31, 2013 4:55 am    Post subject: Reply with quote

Grand Master

Joined: 25 Jun 2008
Posts: 17447

what, exactly, are you trying to do?

In broker v8, you can explicitly control the state that a newly deployed message flow will be in, as part of the settings on the BAR file.

But if the only reason to deploy something is to *find out* if you are able to deploy something, this is the *wrong* thing to do.

You should *know* at all times who can and can not deploy things, because you have taken steps to secure the system and made records of each access modification made.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Goto page 1, 2  Next Page 1 of 2

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » messageflow should be stopped immediatly after deployment
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.