SOAP documents differ from other types of documents exchanged over HTTP/S. This section describes how to send and receive SOAP documents between WebSphere Partner Gateway and WebSphere Business Integration Message Broker over the HTTP transport protocol.
The way to configure WebSphere Partner Gateway and Message Broker for the transfer of SOAP documents is very similar to the configuration for transferring non-SOAP documents over the HTTP protocol. Table 68 summarizes where to find information on how to configure these two integration components.
Integration component | Configuration step | For more information |
---|---|---|
WebSphere Partner Gateway | You configure the target and gateway the same way for SOAP documents as for non-SOAP documents over HTTP. |
Configuration for sending documents over the 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 69. 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 WebSphere Partner Gateway sends, the message flow must contain an HTTPRequest node to handle communication with the Web Services client. Table 69 lists the nodes in a Message Broker message flow needed to handle a SOAP document sent by WebSphere Partner Gateway.
Node type | Purpose | Notes |
---|---|---|
HTTPInput | Receives the WebSphere Partner Gateway request document into the message flow |
Set this transport node URL Selector field (in the Basic properties) to the URL where WebSphere Partner Gateway sends its documents (the URL configured in the WebSphere Partner Gateway gateway). The URL should have the following format: http://hostName:port/path where hostName is the name of the computer on which WebSphere Partner Gateway resides, port is the HTTP port number on which the WebSphere Partner Gateway Receiver is listening, and path identifies the location on this computer. For more information, see Configuration for sending documents over the 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 Web Service. | None |
HTTPReply | Returns a response to WebSphere Partner Gateway | By default, this node sends the output message to the client. |