+

Search Tips   |   Advanced Search

Configure an intermediary node for web services transactions

Intermediary nodes allow the exchange of Web Services Atomic Transaction (WS-AT) and Web Services Business Activity (WS-BA) protocol messages across firewalls and outside the WebSphere Application Server domain. We configure an intermediary node to specify which WebSphere Application servers the node routes requests to.


Tasks

  1. Decide what type of intermediary node to configure: a Proxy Server for IBM WAS, an HTTP server, or both.

  2. Complete one of the following steps, according to the choice we made in the previous step.

    • If we are creating an intermediary node that is a Proxy Server for IBM WAS, set up the proxy server. Enable web services support on the proxy server.

    • If we are creating an intermediary node that is an HTTP server, configure the HTTP server so that it routes WS-AT and WS-BA protocol messages to the appropriate WAS, rather than processing them itself, as follows.

      1. Allocate a set of unique virtual hosts to the HTTP server; one virtual host for each WAS that we want the HTTP server to communicate with.

      2. In the HTTP server, map each virtual host to a WAS. For example, we might allocate a virtual host name of vhost1 to the HTTP server, then within the HTTP server, map vhost1 to a WAS called server1.

      See the associated example subtopic for details of the configuration XML for IBM HTTP server.

    • If we are using both a Proxy Server for IBM WAS and an HTTP server:

      1. Follow the instructions in Set up the proxy server and follow-on topics, ensuring that we enable web services support on the proxy server.

      2. Configure the HTTP server to route requests to the proxy server

      3. Additionally, configure the HTTP server so that it routes WS-AT and WS-BA requests that are targeted at WAS to the proxy, rather than processing them itself. See the associated example for details of the configuration XML for IBM HTTP server.

We configured the intermediary node ready for use by WAS.


What to do next

Configure WAS to use the intermediary node by specifying, for each server, the appropriate virtual host of the intermediary node.


Subtopics

Next topic: Enable WAS to use an intermediary node for web services transactions


Related:

  • Web services transactions, high availability, firewalls and intermediary nodes
  • Use the transaction service
  • Set up the proxy server
  • Create a WebSphere proxy server
  • Routing requests from a plug-in to a proxy server
  • Proxy server settings