You can use intermediary nodes with Web Services Atomic Transactions (WS-AT) or Web
Services Business Activities (WS-BA) to support the exchange of associated requests across firewalls
and outside the WebSphere® Application Server domain. You configure WebSphere Application Server to use an intermediary node by
specifying the external endpoint URL information for the intermediary node in each server that is
accessed through the intermediary.
Before you begin
Configure the intermediary node that you want to use, and ensure that you know the address
or addresses of the intermediary node that you want to map to servers in your WebSphere Application Server
configuration.Configure the intermediary to listen on a specific port for protocol messages and
to route these messages to the specific WebSphere Application Server instance that you want to enable. See the
related information for an example configuration where an IBM® HTTP server is the
intermediary.
Procedure
-
In the administrative console, click .
-
In the External WS-Transaction HTTP(S) URL prefix section, click Specify custom
prefix, then type the external endpoint URL information for the intermediary node in the
field.
Use one of the following formats for the prefix, where
host_name and
port represent the intermediary node that is an HTTP or HTTPS proxy for the
server, and
port is optional.
-
http://host_name:port
-
https://host_name:port
-
Click Apply or OK.
-
Save your changes to the master configuration.
-
Repeat the previous steps for each server that is accessed through the intermediary node.
-
Restart the servers.
Results
You configured your system to use an intermediary node. Test your configuration to ensure
that messages are routed as you expect.