SOAP documents differ from other types of documents exchanged over HTTP/S. This section describes how to send and receive SOAP documents between WebSphere Business Integration Connect and WebSphere Business Integration Message Broker over the HTTP transport protocol.
The way to configure Business Integration Connect and Message Broker for
transfer of SOAP documents is very similar to the configuration for
transferring non-SOAP documents over the HTTP protocol. summarizes
where to find information on how to configure these two integration
components.
Table 87. Configuring Business Integration Connect and Message Broker for transfer of SOAP documents
Integration component | Configuration step | For more information |
---|---|---|
WebSphere Business Integration Connect | You configure the target and gateway the same way for SOAP documents as for non-SOAP documents over HTTP. |
Configuring for outgoing documents over HTTP transport protocol Configuring for incoming documents over HTTP transport protocol
|
WebSphere Business Integration Message Broker | The message flows to handle SOAP documents are very similar to those for non-SOAP documents over HTTP. Only one additional transport node is required to handle SOAP documents. |
For sending a SOAP document to Message Broker, see Table 88. For receiving a SOAP document from Message Broker, see Creating the message flow for HTTP transport.
|
For Message Broker to correctly process a SOAP document that Business Integration Connect sends, the message flow must contain an HTTPRequest node to handle communication with the Web Services client. Table 88 lists the nodes in a Message Broker message flow needed to handle a SOAP document sent by Business Integration Connect.
Table 88. Nodes for sending SOAP documents to Message Broker
Node type | Purpose | Notes |
---|---|---|
HTTPInput | Receives the Business Integration Connect request document into the message flow |
Set this transport node's URL Selector field (in the Basic properties) to the URL where Business Integration Connect sends its documents. Therefore, it must be set to the URL configured in the Business Integration Connect gateway. The URL should have the following format: http://hostName:port/path where hostName is the name of the machine on which Business Integration Connect resides, port is the HTTP port number on which the Business Integration Connect Receiver is listening, and path identifies the location on this machine. For more information, see Configuring for outgoing documents over HTTP transport protocol. |
Compute | Performs business-logic tasks, such as updating header information | Use ESQL to perform the business logic. The compute node sends the resulting message to the HTTPReply node. |
HTTPRequest | Sends the SOAP request to the external Web Service Provider (WebServices) and gets back a response from that WebService. | None |
HTTPReply | Returns a response to Business Integration Connect | By default, this node sends the output message to the client. |