 | Level: Intermediate Sravan Yallapragada (syallapr@in.ibm.com), Industry Architect , IBM
Geert Van De Putte (vdputteg@us.ibm.com), Solutions Architect, IBM
18 Mar 2009 This tutorial takes you through developing a WebSphere Enterprise Service Bus
(WESB) Mediation Module, which can proactively invoke an external system from time
to time and fetch the updates, based on a given time interval. This is a common
requirement, to poll systems, which cannot proactively post the updates occuring within them, to the other subscriber systems. This is achieved by a combination of a startup bean, scheduler, messaging task and a WESB mediation module.
About this Tutorial
In many SOA integration scenarios, we use WebSphere Enterprise Service Bus (WESB)
to integrate multiple systems, with varied messaging formats and transports. One of the challenges in the WESB V6.1 environment is that there is no Timer node which can proactively invoke a mediation flow, at a specified time interval.
This is a desired functionality in many customer scenarios, since there are systems
which cannot proactively post the updates happening within themselves, to the other
systems. In this tutorial, we would develop a Proactive Mediation module which will continuously poll such a system and fetch the updates periodically, based on a given time interval.
Objectives
- Designing a proactive mediation module on WebSphere Enterprise Service Bus V6.1
- Learn the use case for Scheduler and Startup bean and connecting them to a mediation module
Prerequisites
This tutorial is written for SOA Developers/Architects, that are developing SOA Solutions.
It requires prior experience of developing solutions on WebSphere Integration Developer and deployment experience on
WebSphere Process Server or WebSphere Enterprise Service Bus
System requirements
To run the examples in this tutorial, you need a WebSphere Integration Developer with WebSphere Process Server Test Environment
(recommended on a machine with at least 2GB RAM)
Duration
1 hour
Formats
html, pdf
| |
