Skip to main content

skip to main content

developerWorks  >  WebSphere  >

Build and deploy a business process model using WebSphere Business Process Modeler Advanced and Lotus Forms, Part 3: Implement a mediation flow

developerWorks
Page 1 of 12 Go to the next page

Document options
PDF format - Fits A4 and Letter

PDF - Fits A4 and Letter
1903 KB (48 pages)

Get Adobe® Reader®

Sample code


My developerWorks needs you!

Connect to your technical community


Rate this tutorial

Help us improve this content


Level: Intermediate

Attila Kiss (attila_kiss_bme@yahoo.com), Student, Budapest University of Technology and Economics
Viktor Muller (viktormuller@gmail.com), Student, Budapest University of Technology and Economics

14 Oct 2009

In Part 3 of this series, you'll learn how to implement a mediation flow in WebSphere® Integration Developer V6.1.2, including integrating a mediation flow with a business process.

Before you start

This series of four tutorials covers basic use of the complete IBM WebSphere business process management (BPM) software suite for service oriented architecture (SOA) environment from modeling a business process through implementation and execution to monitoring. In this series, we'll use a single example process to illustrate the BPM life cycle and how it is supported by IBM products.

Prerequisites

  • Intermediate knowledge of Eclipse technology.
  • Intermediate understanding of application integration concepts and technology, such as service component architecture (SCA), service data objects (SDO), mediation flow, and more.

System requirements

  • IBM WebSphere Integration Developer V6.1.2

Introduction

In Part 3, we'll continue to work with the IBM BPM V6.1.2 product suite. Our use case is a human resource process of hiring a new employee. In Part 1, we modeled the process in WebSphere Business Modeler. Next, we implemented the process using WebSphere Integration Developer (hereafter called Integration Developer). The process uses a service to send e-mail to applicants, which we implemented as a dummy Java™ service component in Part 2. In Part 3, we'll change the implementation to a mediation flow. Our example company has access to two email service providers that have different cost and quality of service attributes. Sending email is a general service in the company and cannot be bound to any specific business process, which is why it is implemented as a standalone module.

As mentioned, there are two services to consume. The first service uses a local, more secure SMTP server, and is used for the most important partners, while the second uses Google™ mail as the SMTP provider. The company has a database containing the list of important partners. We'll use this database to choose the appropriate service. In case of any failure of the remote service, the other service is used as a backup.


Page 1 of 12 Go to the next page