A DMZ server is a server that might not allow you to open untrusted network ports. Since the AdminServer uses ports which might be interpreted as untrusted, the standard WSA configuration might run on such a server. The WSA supports a "remote" configuration to work around this issue. The remote configuration installs only enough of OpenEdge on the remote server to run the WSA. This installation includes the WSA Java Servlet and the files used to support its local configuration.

The remote WSA uses a ubroker.properties file with a limited set of static startup parameters. You must manually edit this file to change the WSA instance's static configuration properties.

You can continue to administer the remote WSA's dynamic run-time properties and deploy and manage SOAP services by mapping it to an AdminServer on the Intranet behind the DMZ server. The Intranet AdminServer uses HTTP/S to pass WSA administration operations as SOAP messages to the WSA's Administration service.

To run a remote WSA configuration:

  1. Install the remote WSA on the DMZ server. Manually edit the static startup parameters in its ubroker.properties file and install the WSA as a Web application in the local Web server's JSE.
  2. Start the WSA the Web server's JSE and verify that a browser can access its URL from the Internet.
  3. Connect to an AdminServer on the Intranet and configure a "remote" WSA instance using OpenEdge Management and OpenEdge Explorer or the WSAMAN utility by specifying the remote WSA's URL.

    The Intranet AdminServer creates a WSA mapping entry in its local ubroker.properties file with the URL of the remote WSA's administration SOAP service.

  4. Use OpenEdge Management and OpenEdge Explorer or the WSAMAN utility to manage the "remote" WSA's dynamic run-time properties and deploy and manage the WSA's SOAP services.

    OpenEdge Management and OpenEdge Explorer connects to the Intranet AdminServer where you mapped the WSA and then connects to the remote WSA's SOAP administration service. When OpenEdge Management and OpenEdge Explorer sends an operation to the Intranet AdminServer, the AdminServer turns it into a SOAP message and forwards it to the WSA's SOAP administration service which executes the operation.