Figure 8 shows a more detailed of a call-triggered flow, initiated,
in this case, by an access client that is a client browser.
Figure 8. Sample call-triggered flow initiated by a client browser

As shown in Figure 8:
- The client browser issues a request in a specific protocol and format (for
example, an HTTP protocol and an XML data format).
- The enterprise Web server loads a
servlet to handle the request. This servlet is the access
client. It is programmed to look for the name of the CORBA-compliant
IBM WebSphere Business Integration Server Express and Express Plus (from the
CORBA registry).
- The access client, via an IIOP connection, logs in to IBM WebSphere
Business Integration Server Express and Express Plus by creating an
access session with the
IgetInterchangeAccessSession() method of the
IAccessEngine interface of the Server Access API.
- Note:
- To execute the collaboration, IBM WebSphere Business Integration Server
Express and Express Plus does not create any threads of its own,
but uses the CORBA thread. See the Collaboration
Development Guide for details on how collaborations use threads.
- The access client uses the
IcreateBusinessObjectFrom() method in the
IInterchangeAccessSession interface to transform the XML data into
a generic IBM WebSphere Business Integration Server Express and Express Plus
business object. In response to this method call, the Server Access
within IBM WebSphere Business Integration Server Express and Express Plus
invokes the XML data handler to perform the data transformation and then
returns the business object to the access client.
- The access client uses the
IexecuteCollaboration() method in the
IInterchangeAccessSession interface to send the triggering access
call, which contains the business object as the triggering access data.
This process requests the execution of a collaboration that manipulates the
business object.
- Note:
- The Server Access API also provides the
IexecuteCollaborationExtFmt() method, which combines step 4 and step 5 into a single method call.
- Traversing connectors, the collaboration places requests,
sorts, and fetches data, manipulating enterprise applications as
required. The collaboration returns requested data, or results of
requested actions, to the access client in business-object format.
- If the access client has used the
IexecuteCollaborationExtFmt() method to issue the access request,
it does not need to explicitly perform the actions in step 6. The IexecuteCollaborationExtFmt() method
automatically transforms the business object back to its original format (in
this case, the XML format) and returns this serialized data to the access
client.
- The results are delivered to the client browser.
As shown in Figure 8, the Web server handling the call loads a servlet to handle
the call, which connects to IBM WebSphere Business Integration Server Express
and Express Plus.
