To illustrate the architecture of the components at a high level, this
section describes two data flows. Figure 3 illustrates the two scenarios. These two scenarios
are described below.
Figure 3. Flow of an HTTP message

Request processing illustrates the sequence of events that
occurs when a collaboration makes a service call request to the
connector. In this scenario, the collaboration plays the role of a
client, sending a request to a server.
- A
- The collaboration sends a service call request to the connector, which
calls a data handler to convert the business object to a request
message.
- B
- The connector invokes the URL of the enterprise web server by sending the
request message.
- C
- The enterprise web server invokes the URL of the HTTP server (HS2).
- D
- The HTTP server HS2 processes the request and returns the response.
The response is returned as part of the same connection.
- E
- The enterprise web server returns the response message to the
adapter.
- F
- The connector receives the response (or fault) message, calls the data
handler to convert the message to a business object, and returns it to the
collabortion.
Event processing illustrates the sequence of events that occurs
when a collaboration is invoked by an HTTP client. In this scenario,
the collaboration plays the role of the server, accepting a request from a
client, external or internal, and responding as required.
- 1
- The HTTP client (C1) sends a request message to the destination--the
collaboration.
- 2
- If the HTTP client is external, the gateway receives and routes the
message to the connector.
- 3
- The connector sends the message to the data handler for conversion to a
business object. The connector invokes the collaboration.
- 4
- The collaboration returns a response (or fault) business object.
- 5
- The connector calls the data handler to convert the response (or fault)
business object to a response message. The connector returns the
response to the gateway.
- 6
- If the client is external, the gateway routes the response message to the
HTTP client (C1).
