You can configure an on demand router (ODR) to determine
how it handles failure scenarios and tunes certain work requests.
You can configure the connections and requests to the application
server, configure the requests that must be rejected, define how error
responses are handled, and specify the location of the proxy logs.
The configuration of the ODR in the DMZ is not supported.
Before you begin
You
must first create an ODR, a proxy with advanced capabilities that WebSphere® Virtual
Enterprise uses to route work to
application server nodes. See Creating ODRs for
more details.
About this task
You can define the configuration of the ODR by editing its
proxy configuration. Define the configuration further by clicking
Servers
> On Demand Routers >odr_name> On demand router properties
> On demand router settings. Note that the configuration of the
ODR in the DMZ is not supported.
To configure
ODRs to perform a SSL offload, see Configuring SSL offload for all HTTPS traffic. For information on other custom properties, see On demand router system and custom properties. Procedure
- Follow the WebSphere Network
Deployment instructions in the Proxy server settings topic for instructions
to configure ODRs, and the Overview of custom error page policy topic
for additional information. The WebSphere Virtual
Enterprise-specific field for Compression
Policy information follows.
- Compression Policy. Check Enable to enables
the compression of the HTTP response message body before sending it
to the client. Choices include:
| Option |
Description |
|---|
| gzip-only |
Compress the response using the gzip compression mechanism.
The response is compressed only if it is acceptable to the client,
based on the Accept-Encoding request header. |
| deflate-only |
Compress the response using the deflate compression mechanism.
The response is compressed only if it is acceptable to the client,
based on the Accept-Encoding request header. |
| auto-only |
Use either gzip, deflate, or no compression as determined
by the client preference. |
What to do next
After you create and configure the ODR and apply any configuration
parameters, you can define the ability to route work to nodes that
are not a part of your
WebSphere Virtual
Enterprise environment.