HTTP Server Page

The HTTP Server Page groups together information about the operation of the Web server and SOAP server of 4D Server. The Web server lets you publish Web content such as HTML pages or pictures bound for Web browsers. The SOAP server manages the publication of Web Services. These two servers rely on the internal HTTP server of 4D Server. This page also includes buttons that can be used to control the activation of these servers:

The upper part of the page provides information about the current status of the HTTP server of 4D Server.

• State: Started or Stopped émarré ou Arrêté
• Starting time: Date and time the HTTP server was last launched. This value may differ from that of the application server when the launching of the HTTP server is not carried out "on startup."
• Uptime: Time elapsed since last startup of the HTTP server.
• Total HTTP hits: Number of (low level) HTTP hits received by the HTTP server since it was started.

This button toggles and can be used to control the activation of the 4D Server HTTP server.

• When the HTTP server state is "Started," the button is titled Stop HTTP Server. If you click on this button, the 4D Server HTTP server is immediately stopped; the Web server and SOAP server no longer accept any requests.
• When the HTTP server state is "Stopped," the button is titled Start HTTP Server. If you click on this button, the 4D Server HTTP server is immediately started; Web and SOAP requests are accepted (note that it is possible to stop the SOAP server separately, see the “SOAP Information” paragraph below).

Notes:

• You must have a suitable license in order to be able to start the HTTP server.
• The HTTP server can also be launched automatically on application startup (option in the Preferences) or by programming.

This area provides specific information about the Web server of 4D Server.

• Web requests: Accepted or Rejected. This information indicates whether the Web server is activated. Since the Web server is directly linked to the HTTP server, Web requests are accepted when the HTTP server is started and rejected when it is stopped.
• Maximum connections: Maximum number of Web connections allowed. This value depends on the license installed on the server machine.

This area provides specific information about the SOAP server of 4D Server and includes a control button.

• SOAP requests: Accepted or Rejected. This information indicates whether the SOAP server is activated. In order for SOAP requests to be accepted, the HTTP server must be started and the SOAP server must explicitly accept the requests (see the Accept/Reject button).
• Maximum connections: Maximum number of SOAP connections allowed. This value depends on the license installed on the server machine.
• Accept/Reject SOAP requests button: This button toggles and can be used to control the activation of the 4D Server SOAP server. This button modifies the value of the Allow SOAP Requests option on the "Web Services/SOAP" page of the Preferences (and vice versa).
  If you click on the Accept SOAP requests button and the HTTP server is stopped, 4D automatically starts it.

This area provides information about the configuration parameters and operation of the HTTP server:

• Auto-launched at startup: parameter set via the 4D Server Preferences.
• HTTP Server processes (used/total): number of HTTP processes created on the server (current number of processes / total of all processes created).
• Cache memory (used/total): size of HTTP server cache memory, when it is activated (size actually used by cache / maximum size theoretically allocated to the cache in the Preferences).
• Listening to IP, TCP Port (80 by default), SSL enabled for HTTP connections (does not concern 4D nor SQL connections) and HTTPS Port used: current configuration parameters of HTTP server, specified on the Web/Configuration page of the Preferences (see the Web Server Settings section in the 4D Language Reference manual).
• Log file information: location, format and date of the next automatic log backup of the HTTP server (logweb.txt file).