Connecting to JADE Applications from an Apache HTTP Server
Your connections from the Apache HTTP Server to JADE applications can be via a TCP/IP connection only. The design and configuration of the mod_jadehttp module fully conforms to Apache HTTP Server 2.4 module usage and configuration practices.
You can obtain more information about the Apache Software Foundation from the Apache web site.
JADE supports the Apache HTTP Server by supplying mod_ jadehttp. Only
The mod_ jadehttp library module supplied by JADE for the Apache HTTP Server implements support for the following Multi-Processing Modules (MPMs). The selection of the default MPM is selected based on the operating system on which the Apache server is running; that is, mpm_winnt is the default value for Microsoft-based operating systems.
If you build the Apache server from source code, you can build and select whichever MPM you want to use, on the operating system of your choice.
Some relevant MPMs with respect to JADE and the mod_ jadehttp library are listed in the following table.
Multi-Processing Module (MPM) | Implements a … |
---|---|
mpm_winnt | Multiple-threaded single process Web server |
prefork | Non-threaded, pre-forking Web server |
worker | Hybrid multiple-threaded multiple-process Web server |
The mod_ jadehttp module ensures that the same destination IP address and port number combination are used for a specific logical connection, by using the hidden fields that both the jadehttp and the mod_ jadehttp libraries insert into the HTML data.
To install the mod_ jadehttp module
-
Copy the mod_ jadehttp.so file into the modules directory of your Apache HTTP Server.
The name mod_ jadehttp.so applies to all operating systems.
Ensure that you use the correct operating system binary.
Apache and the HTTP generally use UTF-8 as the encoding scheme for Unicode data on the Web. As mod_jadehttp currently does not allow for this and it passes the data directly to JADE, only ANSI data can be read from or written to the
For details about configuring the Apache HTTP Server, see "Configuring Apache for Remote Connections", later in this chapter.