For more information on using the BPEL palette activities, refer to Chapter 5, which
covers the BPEL Designer.
Building a Sample Application
[ 218 ]
The receive activity is always mapped to the BPEL implementation of the partner
service. You have the option to select the correct operation from the partner link
WSDL. The invoke activity's partner link points to the EJB implementation. The
following screenshots shows the Receive, Invoke, and Reply activities configuration:
Chapter 10
[ 219 ]
NetBeans offers an intuitive way of processing and directing BPEL process data
through BPEL mapper. For more information on the BPEL, refer to Chapter 5 on
BPEL Designer. The screenshot on the next page shows how we can copy the
guest itinerary data across variables. Once you have successfully added Receive,
Invoke and Reply activities as shown in the above figures, you need to assign
variables. Drag-and-drop an Assign activity from the Palette between Receive
and Invoke activity. Switch to Mapper view from Design View.
Building a Sample Application
[ 220 ]
From WSDL_NorthAir_ReservationOperationIn | inputItinerary, drag-and-drop
the itinerary details to the corresponding elements under ProcessItineraryIn |
parameters as shown in the following screenshot:
Now, when NorthAir Web Service processes the request and sends a response back,
the output variable of Invoke activity should be copied to the variable associated
with the Reply activity so that the invoking web clients get the appropriate message.
Pages:
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196