|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
MQSI reusability |
« View previous topic :: View next topic » |
Author |
Message
|
pauillac |
Posted: Wed Jul 25, 2001 11:49 pm Post subject: |
|
|
Novice
Joined: 13 Jul 2001 Posts: 21
|
I am investigating MQSI reusability. I came up with an interesting situation goes like this:
Suppose I have 4 identical message flows deployed to 4 execution groups. The reason why I would like to do this is I want to set up 1 message flow for each of 4 sub-systems. e.g. Global Finance, Securities, Accounting, Reporting. It so happens that all sub-systems share the same message flow when the version 1.0 of my system is rolled out. As my sub-systems evolve, they need different flavours of the same message flow. If all changes are unique to just 1 message flow I can change any message flow independently without affecting others. However, when some changes are sharable among, say, 3 of them, is there any way of making changes to just 1 place, be it a node or message flow, so that it can take effect on all the 3 message flows.
The reusable unit in MQSI is message flow, i.e. you can join message flows into a mega message flow. Since I don't know which node will be changed, should I convert all nodes in the message flow deployed in the above case into single node message flows, i.e. a single node with output and input terminals as a message flow on its own, so that I can change just 1 such single node message flow to have the change propagated to all the 3?
This is a trivial situation. If the system has 1000 message flows, it's really not a joke. |
|
Back to top |
|
 |
kolban |
Posted: Thu Jul 26, 2001 6:23 am Post subject: |
|
|
 Grand Master
Joined: 22 May 2001 Posts: 1072 Location: Fort Worth, TX, USA
|
Good question. The answer is "sub-flows". When you create a message flow, that message flow can itself be incorporated in other message flows. You can then think of the original sub-flow as a subroutine or function. You can even externalize parameters (properties) of the sub-flow so that each instance has different characteristics. This then gives you excellent re-use of business flows at whichever granularity you wish. |
|
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
|
|
|
|