WebSphere Integration Developer Guide Tutorial Part 3rd building a simple service-oriented application

WebSphere Integration Developer Guidance Tutorial Part 3rd building a simple service-oriented application

Introduction

The previous article in this series discusses the basic concepts of WebSphere integration Developer and the set of tools it provides. In this article, we also learned about the main steps in building an order Processing application (orderprocessing) using a service-oriented architecture. You may not have read the previous article at this time, or have read it, but you can't remember all the details. Don't worry, before delving into how to implement the application's services, we will briefly review it to lay the groundwork for a step-by-step discussion.

The Order Processing application (orderprocessing) receives order information from external customers. It then checks to see if the customer's reputation is good (preferably extremely rich) and, if so, forwards the order to the Distribution department. When the distribution department confirms that the order has been shipped, a message is output.

To implement this application, we need a business object that represents the order information. Business objects are sometimes referred to as the currency of the application, because all services use business objects. When it comes to services, we will also need services for retrieving orders, checking customer information, and distributing orders. These services are represented in Figure 1 as three black boxes.

Figure 1. A simple order-processing application

In the previous article we learned that each service can be defined and connected together without knowing the actual implementation details of any service. To do this, I created a module (orderprocessing module) and then created each service. Next, we identify the interfaces that each service will support, and the interfaces of each other service that it plans to invoke. Finally, we connect the services together according to the invocation relationship between the services. This approach is extremely useful because it allows the top-down approach to design the entire application without worrying about the implementation of each service until the entire architecture is complete. In fact, we can have a designer design the layout of the entire service-oriented architecture, and let each team member implement one of the services based on the contract (interface) specified by the architect.

What you are going to learn

Now that we've reviewed the order processing application, we're going to start working on the build.

In the following sections, you will learn how to accomplish the following tasks:

Create a module to host all artifacts that will be authored.

Create business objects to identify customer orders.

Create components and their interfaces.

Connect the components together.

Specifies the implementation of these components.

Deploy and test the built content in the WebSphere test environment.