264 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
processes” on page 266. The data model for the process and the services can
be created with tools that are provided by Rational XDE Developer. Refer to the
Rational XDE Developer documentation for details on how to use the tool. The
main steps to create the data types are:
1. Create a Java or EJB modeling project and a Java or EJB code model.
2. Add packages, Java classes, or EJBs that are needed to detail the data
model.
3. Generate code for all UML elements that you have defined.
Having successfully completed the code generation, Java data types including
attributes and relationships are available that can be used later to implement the
services and the BPEL process. To design the WSDL interfaces, however, XML
schemas are needed. XML schemas can be generated from Java objects using
WebSphere Studio Application Developer Integration Edition tools.
Designing the process and service interfaces
From an SOA perspective, all elements in the architecture are services and are
described by a WSDL interface definition. Both BPEL processes and the invoked
services are described by their WSDL interfaces.
WebSphere Studio Application Developer Integration Edition provides a WSDL
editor that we used to design the process interfaces. As an example, we show
the steps to create the interface for the trader system process in more detail. The
process model is depicted in Figure 6-6 on page 139.
The trader system process requires a StockOrderRequest business object as
input and returns a StockOrderConfirmation object. XML schema definitions for
the business objects have already been generated when we created the Trader
EIS service as detailed in 6.4.3, “Enabling the EIS component using JMS” on
page 156.
To create a WSDL interface definition, complete the following steps:
1. In the Business Integration perspective, select File
→ New → Service
Interface to create the WSDL file.
2. Specify a package name and a file name (for example, com.itso and
TraderSPInterface), and click Finish.
3. In the WSDL editor, in the Imports section at the top-left, right-click and select
Add child
→ Import. Make sure that the entry that appears in the Imports
section remains selected and go to the Ellipses button next to Location
(Figure 9-12 on page 265).
Chapter 9. Integration into business processes 265
Figure 9-12 Import XML schemas into WSDL interface definitions using the WSDL editor
4. From the Select wizard, navigate to the XSD file to import (for example,
StockOrderConfirmation.xsd). Click OK.
5. Go to the Port Types section to define a new operation. Right-click the port
type (for example, TraderSPInterface), and select Add child
→ operation.
Enter the name of the operation (for example, invokeTraderSP).
6. To create input and output parameters, highlight the operation and select Add
child
→ Input and Add child → Output.
7. Create a message that describes the input by highlighting the input and
selecting Set Message. From the Specify Message wizard, choose the
Create a new Message option, and enter the name of the message (for
example, invokeTraderSPRequest). Also, specify the output message.
8. Messages comprise parts. Create a part for each message by highlighting the
message and selecting Add Child
→ Part. Enter the name of the part (for
example, request).
9. For the parts, set the type by right-clicking and selecting Set Type. From the
Specify Type wizard, choose the Select an existing type option and select
the type from the list (for example, xsd1:StockOrderRequest). (This is the
data structure that you imported in step 4). Click Finish.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset