| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Promoted properties and deployed subflows |
« View previous topic :: View next topic » |
| Author |
Message
|
| NealM |
 Posted: Thu Feb 07, 2013 3:36 pm Post subject: Promoted properties and deployed subflows |
 |
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
Here is something I haven't had a chance to fully experiment with and understand yet on MB8. I noticed that when I tried to deploy a library of common subflows, the deploy stopped me dead on one that contained a TCPIPServerInput Node with the "Connection details" promoted to the flow, such that which port (or configurable service) is to be used is set in the parent flow. And since at the subflow's level I left the (default) value set to 0, the deploy slapped me.
Now, obviously, I could set the subflow default to some number >0 and get by the error on deploy.
But what I am wondering (without yet testing this for myself; maybe tomorrow) is, is that value locked in on the deployed subflow, or will the calling parent flow's port/service value overide it? If it is the former, it would appear that IBM's documentation should do a better job of pointing this out as a possible issue in deploying subflows with promoted properties in a separate library. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Thu Feb 07, 2013 3:40 pm Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
so you're deploying the library containing the subflows as a standalone container in an EG, and deploying the flows that invoke the subflow as standalone flows, and not part of an application?
I.e. you are deploying everything to the default application - the eg itself - and not a named application.
There are also some bugs in v8, even at FP1, around subflows, particularly nested subflows. |
|
| Back to top |
|
|
| NealM |
| Posted: Thu Feb 07, 2013 3:50 pm Post subject: |
|
|
Master
Joined: 22 Feb 2011
Posts: 230
Location: NC or Utah (depends)
|
Yes, that is the idea Jeff. We have several common subflows that are used in almost every web service, so I was looking at leaving the web services as independent resources, removing the common subflows from their bars, and just deploying and maintaining those in one or two libraries.
Regarding the v8.0.0.1 subflow errors, we did just get an ifix built last week for those, contains ~ 50 install files to replace, so I guess Hursley had some work to do....
Incidently, the deploy has several other bugs/differences. It can't handle an ESQL file that has a blank first line (says 'BROKER' error. Only), nor deploy an ESQL function that has an Atomic section with a database select and shared variables (the deploy just hangs until the 6 minute timeout). All one can do is find the problems through elimination. |
|
| 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
|
|
|
|
