HTTP Service receives HTTP requests from clients and responds to them by returning the HTML files that correspond to the requested URL. It is a session service – that is, it is installed on both dispatcher and server nodes to process more client requests. HTTP Service is developed in accordance with HTTP 1.1 specification (RFC 2068).
The system administrator at runtime can set the following properties from the “Runtime” tab of the Visual Administrator tool. This can be done only on server nodes of the cluster:
../../docs
.Visual Administrator toolbar provides the following option for HTTP Service runtime control:
|
Dispatcher |
|
Property Key |
Description |
Default Value |
General Properties |
|
|
|
|
|
Port
|
Specifies the port where the service listens for HTTP requests.
|
80 |
Socket queue
|
Specifies maximum queue length for incoming connection indications. |
200 |
SSL port |
Specifies the port for security connections where the service listens for HTTPS requests.
|
443 |
Accepting threads count
|
Specifies the number of threads that wait to be acted on by the socket. |
10 |
ExtraLayers |
Specifies the classes that parse the headers of the http requests. Each class must implement one interface. When more than one class is specified, they are separated by a comma. If this property in not specified, the communication protocol is pure HTTP.
|
com.inqmy.services.httpserver.dispatcher.ICMExtraLayerV1 |
KeepAliveTimeout |
The period (in seconds) from the last server response to the client until the server shuts the client-server connection down. The value of this property is an integer. If set to 0 or less, there is no timeout.
|
15 |
|
Server |
|
Property Key |
Description |
Default Value |
General Properties |
|
|
|
|
|
File buffer size
|
This is the maximum size of the buffer when downloading a file.
|
4096 |
KeepAliveEnabled |
Specifies whether a connection is “kept alive” or is closed each time. |
true |
Min File Length For LDT
|
If the file size is bigger than the specified length, it is transferred by Long Data Transfer.
|
204800 |
Log in Common Log Format
|
The current state of the HTTP Service can be stored in the common log format. Thus, it can be restored in case of a crash.
|
|
LogFile (CLF)
|
Specifies the path to the common log file.
|
./services/http/work/http.log |
Use Cache
|
If this indicator is set, cache is used.
|
|
Max File Length
|
The maximum file size that can be written to the cache. |
16348 |
Cache size
|
The number of files in cache. |
1000 |
Directory List |
If the default file cannot be found in the current directory, the server returns a list of directories.
|
|
InferNames |
If the server cannot find the start page indicated in the “Start Page” field (it may be left empty), it searches for these listed filenames (in order of appearance). The first one found is returned to the browser.
|
|
EnableZipped Response |
Determines if the service returns the requested file to the client as ZIP archive. |
true |
NotZippedFiles |
A comma-separated list of file extensions. Files with such extensions are either inappropriate to archive or they already represent different types of archives and do not need additional reduction of their size. |
|
CacheTimeout |
The period (value range from 1 to 15 seconds) until the system checks the version of all files in the cache and updates them. If set to 0 or less, this option is switched off.
|
-1 |
SapCacheControl |
The period (in seconds) for which requests are kept in the ICMan cache. If a second equal request comes up within the specified period, the same response is returned straight from ICMan (without requesting SAP J2EE Engine again).
|
86400 |
MIME Types |
|
|
|
|
|
MIME Types |
A list of file extensions and their associated mime types. These types are known to the server. If a type is unknown to the server, it returns “content/unknown.”
|
|
HTTP Service can be administered using the Shell commands from the
HTTP
command group as well.
Note: For information on HTTP shell commands, refer to the Shell Commands Reference section.
../cluster/dispatcher/services/http/properties
HTTP Service properties specified in the
Visual Administrator
section can be set from this property file as well.
../cluster/server/services/http/properties
HTTP Service properties specified in the
Visual Administrator
®
Properties
section can be set from this property file as well.
../cluster/server/services/http/default.properties
HTTP Service properties specified in the
Visual Administrator
®
Runtime Control
section can be set from this property file as well.
For the proper functioning of HTTP Service, it is critical that the port for connections is specified. If the default port is already in use on the same machine, the system administrator must make sure that another value is given to the Port property of HTTP Service. However, if it is running on different machines, you can use the same value for the Port property. The Host property value may be either a hostname or FQDN (Fully Qualified Domain Name), or be specified in dotted quad notation (the IP address). Note that all added virtual hosts must be registered on local or global DNS servers to be located when such a host is requested. Setting the Root Directory is also important for the service. It is recommended that the default values provided (especially Port) be kept.