If your Integration Server sits behind an internal firewall and is not allowed to accept communications from external clients through the DMZ, you can set up a webMethods Enterprise Gateway to allow this server to process requests from external clients such as mobile applications.

In an Enterprise Gateway configuration, the Integration Server that remains behind the inner firewall is referred to as an Internal Server. You place another Integration Server, called an Enterprise Gateway Server, in your DMZ. The Enterprise Gateway Server acts as an intermediary between the external clients and your Internal Servers to protect your Internal Servers and their applications, services, and data from malicious attacks. Enterprise Gateway Server supports nearly all requests that a regular Integration Server handles, including guaranteed delivery.

By default, all user validation and transaction processing is performed on the Internal Server, but you can configure Enterprise Gateway Server to perform user validation. You can also set up rules on Enterprise Gateway Server to filter requests before they are passed to the Internal Server.