EntireX Version 9.7
 —  Administration under Windows  —

Settting up and Administering the Broker HTTP(S) Agent

The Broker HTTP(S) Agent is a Java-based component that implements a Java servlet for servlet-enabled Web servers. It builds the bridge between a Web server and EntireX Broker in the intranet. This component was formerly referred to as "Tunnel Servlet".

This document covers the following topics:

HTTP(S) Tunneling with EntireX


When communicating with EntireX Broker over the internet, direct access to the EntireX Broker's TCP/IP port is necessary. This access is often restricted by proxy servers or firewalls. With EntireX, Java-based communication components can pass communication data via HTTP or HTTPS. This means a running EntireX Broker in the intranet is made accessible by a Web server without having the need to open additional TCP/IP ports on your firewall (HTTP tunneling). HTTP or HTTPS tunneling can also be used for Java RPC.

How the Communication Works

The EntireX Java ACI is able to send and receive data via an HTTP protocol controlled by constructor com.softwareag.entirex.aci.Broker. See How to Enable HTTP Support in a Java Component under Writing Advanced Applications - EntireX Java ACI.

The EntireX Java component com.softwareag.entirex.aci.TunnelServlet.class implements a Java servlet for servlet-enabled Web servers. It builds the bridge between Web server and EntireX Broker in the intranet.

Java communication

The figure above shows how the communication works. In this scenario, a Java client program communicates via HTTP and EntireX Broker with an EntireX server. By using a Broker ID starting with http:// (passing the URL of the installed HTTP(S) Agent) each Broker request is sent to a Web server, which immediately processes the HTTP(S) Agent, passes the contents to EntireX Broker, receives the response and sends it back via HTTP. For the two partners (client and server) it is transparent that they are communicating through the Web. Java server programs can also communicate via HTTP if necessary.

Top of page

Configuring the HTTP(S) Agent

To use the HTTP(S) Agent you need a servlet-enabled Web server.

Parameter Description
broker The broker you want to address (syntax: as Broker ID in Java).
Yes Default. Servlet writes logging information to its standard output.
No No log is created.

In the following, "tunnel" is used as the agent name.

Start of instruction setTo adapt the HTTP(S) Agent

The following steps describe the deployment with the Web archive entirex.jar in detail. You can test the HTTP(S) Agent with http://<host>:<port>/entirex/tunnel, where entirex is the name of the Web application.

  1. Create the new subfolders in the Web application directory of your Web server, e.g. tunnel, tunnel/WEB-INF, tunnel/WEB-INF/lib.

  2. Copy the entirex.jar into tunnel/WEB-INF/lib.

  3. Create a file named web.xml in the folder tunnel/WEB-INF with the following content:

  4. Restart your Web server and test the installation by calling the HTTP(S) Agent in your Web browser. The URL is: http://<yourhost>/tunnel. If the agent is installed properly, an information page is displayed.

  5. Run the Java ACI client/server example or the Java RPC example delivered with EntireX and use the agent's URL for client or server or both.

Top of page

Using Internationalization with the HTTP(S) Agent

Internationalization is transparent for the HTTP(S) Agent. The client sending the EntireX ACI request with HTTP over the Web server through the HTTP(S) Agent fully controls Internationalization. No configuration is necessary for the HTTP(S) Agent.

Top of page

Activating Tracing for the HTTP(S) Agent

Start of instruction setTo switch on tracing for the HTTP(S) Agent

Start of instruction setTo switch on logging

Top of page