140 Smart SOA Connectivity Patterns: Unleash the power of WebSphere Connectivity Portfolio
Figure 3-89 Choose Service Integration as the mediation flow
10.Add the reference to the target FileNet service. Add ECMImportPartner as a Reference,
choose retrieveallAKOSSupplierContract as a Target Operation, and click OK. See
Figure 3-90 Choose a Reference and a Target Operation to integrate the services
11.The previous action creates the necessary mediation logic and places it on multiple tabs.
On the Request tab, connect queryDocument and retrieveallAKOSSupplierContract
using the XSLTransformation1 component, as shown in Figure 3-91 on page 141.
Chapter 3. Service Enablement pattern: Enterprise Content Management System 141
Figure 3-91 Wire the services using the XSLTransformation1 component
12.Double-click the XSLTransformation1 component to implement wiring the services. Enter
a valid name for the map and click Finish on the next window. On the map editor, connect
the whereclause of the queryDocumentRequestMsg to the whereclause of the
retrieveallAKOSSupplierContract, as shown in Figure 3-92.
Figure 3-92 Map the necessary fields
13.Follow similar steps to complete the response flow logic of the Mediation component. On
the Response tab, connect retrieveallAKOSSupplierContract’s response message to
queryDocument’s response. See Figure 3-93 on page 142.
142 Smart SOA Connectivity Patterns: Unleash the power of WebSphere Connectivity Portfolio
Figure 3-93 Connect the response flow of the Mediation component
14.Choose XSL Transformation as the type of mapping component for the response flow.
Double-click the XSLTransformation1 component. After naming the component, choose
the Auto map input to output icon to automatically map all the input fields to the
matching output fields. See Figure 3-94.
Figure 3-94 Auto mapping of input fields to output fields
15.On the next window, click Finish. Keep all the default values. See Figure 3-95 on
144 Smart SOA Connectivity Patterns: Unleash the power of WebSphere Connectivity Portfolio
16.You have completed the Web service binding configuration. Next, you create a JavaServer
Pages (JSP)-based Web service client and test it. To start the client generation process,
right-click the corresponding Web Services Description Language (WSDL) component
under the Web Service Ports section and choose Web Services Generate Client See
Figure 3-97 Launch the Web Service Client generation wizard
17.The Web Service Client generation wizard starts. On the first page of the wizard, for Client
type, select Java proxy and move the client generation-level slider to Test client and click
Next, as shown in Figure 3-98 on page 145.