Aggregation in WESB6.1 Introduction


WESB V6.1 introduces aggregation into mediation flow logic. First lets define what aggregation is; In simple terms, an inbound request may map into several individual outbound requests. The responses from these requests may be aggregated into a single response for the original request.

A common example is Airline service, where user searches for a flight from one city to another,now there could be many flights between given cities, Here the aggregation functionality calls different service providers (say Kingfisher,Indigo...) with the same set of inputs (say Date, from , to ...) & aggregates the outputs into one final output & then sends back to user.

So from user it would be only one call but the service provider (say MakeMyTrip for end user) calls different service providers.

Here is the diagrammatic representation of the mentioned scenario :

Fan-In, Fan-Out, Service-Invoke & MessageElementSetter Usage

For more info : http://www.ibm.com/developerworks/webservices/library/ws-websphereesb1/

Working PI

More info on FanIn/Out terminals:

FanOut Out terminals

out: Propagates the original message. When in iterate mode the out terminal is fired once for each occurrence of the repeating element specified, using an XPath. In iterate mode the value of the current element is placed in the FanOutContext.

noOccurrences: Propagates the original message. The noOccurrences terminal is only used in iterate mode, and is used if the input message does not contain any occurrences in the repeating element.


FanIn In terminals

in: Receives input messages until a decision point is reached. When a decision point is reached the out terminal is fired.

stop: Causes the incomplete output terminal to be fired, and this stops the associated Fan Out primitive from sending any more messages.

FanIn Out terminals

out: Propagates the updated message.

incomplete: Stops the associated Fan Out primitive from sending any more messages. Fired if the Stop terminal receives an input message; also fired if a timeout occurs.

No comments:

Post a Comment