This page shows how to configure JEAF Workload Proxy.
Configuration of JEAF Workload Proxy basically consists of the following parts: Proxy Configuration and Pipeline configuration:
Proxy Configuration
The so called proxy configuration contains all the configuration parameters for the proxy itself as well as the configuration of the proxy targetsPipeline Configuration
The pipeline configuration defines the several pipelines that are used for request dispatching.
Configuration Files
Proxy Configuration Parameters
Parameter | Default | Description |
---|---|---|
Settings for Workload Container | ||
|
| Port that is used to server requests by the so called workload container. The workload container is used to server all kinds of non-management requests. |
|
| Minimum amount of threads that are used by the workload container. |
|
| Maximum amount of threads that are used by the workload container. |
|
| Enables the REST interface so that REST service can be used. |
|
| Enables the servlet interface so that Web servlets can be used. |
|
| Context path of the workload container. |
|
| Root path under which REST resources will be available. |
Settings for Management Container | ||
|
| Enables management interface. |
|
| Port under which the management interface is accessible. |
|
| Minimum amount of threads that are used for requests to the management interface. Depending on the used Java Runtime Environment it may happen that you need to increase minimum amount of management threads. In this case an exception will occur during startup. |
|
| Maximum amount of threads that are used for requests to the management interface. |
|
| Context path under which the management interface will be available. |
Common Settings for Proxy Server Some of the parameters below are very similar to those of pipelines. so please be aware that here we are talking about the configuration of the proxy server itself and not of its pipelines. In general the resource requirements of the proxy server itself are rather low. | ||
|
| Idle time after which a thread will be stopped and removed from pool. Timeout is defined in milliseconds. |
|
| Initial size of queue that is used to store requests until they are dispatched to the matching pipelines. |
|
| Maximum size of queue that is used to store requested until they are really processed.
|
|
| Size of which the request queue should be increased until the maximum is reached. |
|
| Size of input buffer in bytes that is used when request data is read. |
|
| Size of output buffer in bytes that is used when response data is written. |
|
| HTTP I/O timeout of the HTTP connector. This timeout comes into play if a client does not consume further response data for a certain amount of time. |
|
| Enables sending the server version as a response header field. It's recommended to not enable this info for security reasons. By default information about server version is not send in response header for security reasons. |
|
| Enables sending the server version as a response header field. It's recommended to not enable this info for security reasons. By default information about server version is not send in response header for security reasons. |
|
| Enables graceful shutdown behavior. Graceful shutdown means that request that are already processed will be finished but new ones will not be accepted. |
|
| Timeout for graceful shutdown. If this timeout is exceeded then running threads will be killed. |
|
| Defines if server should be stopped when a |
|
| Defines if uncaught |
|
| Defines if server should be stopped when a |
|
| Defines if uncaught |
|
| Defines if JMX should be enabled or not. By default JMX is disabled to prevent security issues. By default JMX is disabled for security reasons. |
Pipeline Configuration Parameters
Parameter | Default | Description |
---|---|---|