Mediation programming
Using the capabilities of the mediation infrastructure, you can program mediations to customize the way that a service integration bus handles messages. You develop the mediation code within a component called a mediation handler, and add the mediation handler to a handler list, which is an application that is ready to deploy and install. You can connect a number of mediation handlers together in a mediation handler list to create a set of operations to run on a message.
- Reformat messages from the format produced by one application to the format required by another
- Route messages based on message content
- Distribute messages to more than one destination
- Augment messages by adding information to a message from another data source
- Transcode messages from one concrete representation to another
- MediationHandler API
- A mediation handler must implement the MediationHandler interface. This interface defines the method that is invoked by the mediation runtime environment.
- SIMessage and SIMessageContext APIs
- These APIs allow your mediation to operate on the contents of the message.
- SIMediationSession API
- This API gives your mediation access to a service integration bus so that the mediation can send and receive messages.
You create a handler list by using an assembly tool, for example IBM® Rational® Application Developer, before deploying the mediation handler application as an Enterprise Archive (EAR file).
A handler list can contain one or many mediation handlers. At run time, each mediation handler in the list is invoked in sequence. Each time a handler returns a value of True, the same message context is passed to the next handler. If a handler returns the value False, then the context is not passed to the next handler. The message is discarded, and is not delivered to its target destination.