webMethods ebXML Module uses a proxy server in scenarios where the trading partner does not want to expose the ebXML Module services to another trading partner. The ebXML Module uses webMethods Enterprise Gateway to provide the proxy feature. To configure the Enterprise Gateway Server for a sender that uses ebXML Module, see the webMethods Integration Server Administrator’s Guide for your release.

For scenarios where the sender requires a proxy server (for example, outside a firewall), ebXML Module sends the outbound message first to the proxy server, which forwards it to the receiver. The sender's server receives an inbound message from the receiver first to the proxy server, which forwards the message to the sender. For the sender and the receiver to communicate with each other using the proxy server, it is necessary to provide the URL of the proxy server to both the sender and the receiver.

In the following diagram, Company A sends an outbound message to Company B through Company A's proxy server. The proxy server picks up the message and forwards the message to Company B's server. Company B responds by sending an outbound message to Company A through the proxy server. To do so, Company A's and Company B's servers should have the Delivery Method set to the URL of the proxy server in the trading partner profile.