238 Managing Information Access to an EIS Using J2EE and Services Oriented Architecture
Figure 8-27 System process interaction - adapters service providers
The system process uses the context information to route the request, including
the domain object, to the adapter service partner link. For this particular scenario,
the partner link is the JDBC adapter service BPEL process, which does the data
transformation and the request on the WebSphere Business Integration Adapter
for JDBC.
The design and development of a system process using BPEL is explained in
Chapter 9, “Integration into business processes” on page 241.
Here are the high-level steps that are required to incorporate the adapter process
into the system process:
1. Map the InputVariable to the incoming domain object by setting the message
file name to the system process WSDL that contains the domain schema.
Then, set the message type on InputVariable.
2. In the Assign StockInfo snippet, set the data from the input variable into the
adapter request variable, QuoteIn.
3. Create and map an OutputVariable to the outgoing domain object by setting
the message file name to the system process WSDL that contains the domain
schema. Then, set the message type on OutputVariable.
4. Set the returned result from the adapter, QuoteOut, into the corresponding
values for the OutputVariable.
5. Integrate the adapter business process into the system process as the
appropriate remote service call partner link.
System Process
Partner
Link
(PL)
Context
Adapter Service
Process
Data Transformation
LOCAL
REMOTE
Domain Data
JDBC
Data Transformation
SAP
Adapter Service
Adapter
Adapter for
mySAP
Adapter for
JDBC
Partner
Link
(PL)
LOCAL
REMOTE