< Previous | Next >

Overview

In this sample, your goal is to invoke an existing Web service by using a Web service import. This existing Web service has already been implemented and supplied for you, but you need to bring it into your workspace and deploy it to your server. It is implemented using a mediation module, but you need not know or care how it is implemented. You only need to know that there is a WSDL file defining not only its interface but where and how to invoke it with SOAP over HTTP.

Your objective is to allow other integration developers to invoke the Web service by calling your mediation module so they are not calling the Web service directly and so that you have the flexibility and resilience to change and evolve that Web service without impacting the clients that call it; all changes are absorbed in the mediation module. Furthermore, using a mediation module allows you to expose a different interface for that Web service, such as you will do in this scenario.

Because the interface that this sample exposes through an export with an SCA binding is different than the interface of the Web service it uses through an import with a Web service binding, you need to map the parameters (request) and what is returned (response) in a mediation flow component, with one flow for the request and another for the response. Mediation flows are built from mediation primitives that are wired together. Each primitive is a pre-supplied capability that acts on or processes the message flowing through it. Typically, the message contains the request and response parameters that are passed to or returned from an external call.

A high-level overview of this sample is shown in the following figure:

Mediation Module overview

Modules in this tutorial






Feedback



(C) Copyright IBM Corporation 2007, 2008. All Rights Reserved.

< Previous | Next >