Posted: Mon Sep 26, 2005 8:36 am Post subject: Message broker and web services:
Newbie
Joined: 27 May 2003 Posts: 7
We are using message broker to invoke web service hosted on WAS 5.1. Presently we are creating an xml message on mainframe and giving it as the input to message broker.
Some other applications on the mainframe need to invoke the same web service and Application teams think that creating an xml message adds an extra overhead, so they want to use fixed format or TDS.
I can create a different flows for different applications to invoke the same web service. I have couple of questions regarding this design.
1) Is it good practice to create multiple flows to invoke same web service?
2) If I have about 50 web services and lets say each has 5 consumers. I may have to create 250 message flows. Can we have these many number of flows?
You could also enhance the existing message flow to discover and handle input messages of different formats.
The discovery part can be fairly simple, as long as you ensure that sending applications include an MQRFH2 header. Then you can just check the Properties.MessageSet identifier or etc. and use the result for a RouteToLabel branch.
Then maybe a set of different nodes that format each input message into a common layout, and another RouteToLabel to the part of the flow that will invoke the WebService.
You can have more than 250 message flows.
If you really have 50 web services, you might want to break the above design up into different flows. Have one flow that invokes the webservice. And one flow for each input type. Maybe connect your consumers to their input type, or give them their output via a Pub/Sub setup. _________________ I am *not* the model of the modern major general.
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