| Author |
Message
|
| dominik.schweers |
 Posted: Wed Jan 07, 2009 1:18 am Post subject: Deploying one Flow multiple Times |
 |
|
Novice
Joined: 23 Oct 2008
Posts: 17
|
Hi Guys,
we have the following problem: There are some flows which are used in different configurations for different customers. The Source is exactly the same, only Queue Names and some other parameters are different.
At the moment we handle this by deploying the flows in different Execution groups. The parameters are applied during deployment (ANT scripts calling mqsicreatebar and customizing broker.xml). In general this works fine, but the number of additional EGs will get too high.
My idea was to rename the flow in the ANT scripts and deploy the flow multiple times into the same EG. This does not work, because the "nsURI" Tag in the .msgflow does not match the file name.
Is there any simple solution to this?
Thank you very much! |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Wed Jan 07, 2009 2:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| It's entirely possible to rename flows by changing the filename and editing the broker.xml. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Wed Jan 07, 2009 11:57 am Post subject: Re: Deploying one Flow multiple Times |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| dominik.schweers wrote: |
At the moment we handle this by deploying the flows in different Execution groups. The parameters are applied during deployment (ANT scripts calling mqsicreatebar and customizing broker.xml). In general this works fine, but the number of additional EGs will get too high.
|
How high?
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
| dominik.schweers |
| Posted: Tue Jan 13, 2009 2:17 am Post subject: |
|
|
Novice
Joined: 23 Oct 2008
Posts: 17
|
| mqjeff wrote: |
| It's entirely possible to rename flows by changing the filename and editing the broker.xml. |
Guys, thanks for your answers. mqjeff can you explain this in detail? Simply renaming the file does not work for me. The nsURI parameter in the .msgflow file does not match the new file name and mqsicreatebar cant create the bar. In .msgflow and broker.xml are many occurences of the original name. Which of these can be changed without destroying something?
@Peter
at the Moment we have 15 EGs. These are organized according to our process-naming schema. Now Im creating new EGs like ABC_Customer1, ABC_Customer2. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Tue Jan 13, 2009 2:32 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| dominik.schweers wrote: |
| mqjeff wrote: |
| It's entirely possible to rename flows by changing the filename and editing the broker.xml. |
Guys, thanks for your answers. mqjeff can you explain this in detail? Simply renaming the file does not work for me. The nsURI parameter in the .msgflow file does not match the new file name and mqsicreatebar cant create the bar. In .msgflow and broker.xml are many occurences of the original name. Which of these can be changed without destroying something?
@Peter
at the Moment we have 15 EGs. These are organized according to our process-naming schema. Now Im creating new EGs like ABC_Customer1, ABC_Customer2. |
You create the bar, you extract the bar, you manipulate the info (file name, broker xml), you zip the extracted manipulated info back into a .bar file... This should be your sequence. No more creating a second run using mqsicreatebar... or am i missing something (Jeff?) 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Jan 13, 2009 2:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Nope, that's the procedure.  |
|
| Back to top |
|
|
|
|
