Before you start
Following service-oriented architecture (SOA), WebSphere Commerce uses Web services as the medium to integrate with backend systems like ERP, CRM, Yantra, or DOM. WebSphere Commerce has a Web services framework that has different business components containing both inbound and outbound Web services. This tutorial uses WebSphere Enterprise Service Bus (hereafter called WebSphere ESB) as the middleware for mediating outbound messages from WebSphere Commerce to a backend system.
In this tutorial, you will learn the basic tasks required to develop a mediation module for mediating messages from WebSphere Commerce to a backend system. WebSphere Commerce typically contains four Web services patterns: Get, Process, Sync, and Change. Part 1 will help you build mediation modules for Web services patterns Process, Sync, and Change. However, to develop a mediation module for a Web service Get pattern, certain additional tasks are required to perform, which are discussed in Part 2. If you have already used WebSphere ESB for mediation, then you may skip Part 1 and go to Part 2.
Learn how to:
- Create reusable libraries using resources from WebSphere Commerce and a backend system in WebSphere ESB.
- Log data objects using the message logger to audit a message flow.
- Use the XSL transformation and business object map to transform a business object.
You need to be familiar with the basic concepts of SOA and Web services. You also need to be familiar with the use of WebSphere Integration Developer as the Integrated Development Environment for the development of applications that run on WebSphere ESB.
To follow the examples in this tutorial, you need WebSphere Commerce V6.0 with Feature Pack 5 and WebSphere Integration Developer V6.1.2 with a Test Enterprise Service Bus V6.1 server profile.