Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS

---

 

Configure ODRs

 

+

Search Tips   |   Advanced Search

 

You can configure an on demand router (ODR) to determine how it handles failure scenarios and tunes certain work requests. You can configure...

• Connections and requests to the application server
• Requests that must be rejected
• How error responses are handled
• Location of the proxy logs

The configuration of the ODR in the DMZ is not supported.

1. Create an ODR proxy.

2. Define the configuration

   Servers | On Demand Routers | odr_name | On demand router properties | On demand router settings

3. Configure SSL offload for all HTTPS traffic

4. On demand router system and custom properties

5. Proxy server settings

6. Custom error page policy

7. Set Compression Policy information

   Checking Enable 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.

After creating 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.

---

 

Related concepts

Overview of request flow prioritization

 

Related tasks

Configure the on demand router for multi-cluster failover and load balancing routing

 

Related reference

createodr.jacl script
Administrative roles and privileges

Related information

On demand router system and custom properties
Configure SSL offload for all HTTPS traffic
Proxy server settings