Search Tips   |   Advanced Search

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


Creating and configuring ODRs

The on demand router (ODR) is an intelligent HTTP and Session Initiation Protocol (SIP) proxy server in WebSphere® Virtual Enterprise. The ODR is the point of entry into a WebSphere Virtual Enterprise environment and is a gateway through which HTTP requests and Session Initiation Protocol (SIP) messages flow to back-end application servers. You can configure the ODR to determine how it handles failure scenarios and how it tunes certain work requests.


About this task

The ODR can momentarily queue requests for less important applications in order to allow request from more important applications to be handled more quickly or to protect back-end application servers from being overloaded. The ODR is aware of the current location of a dynamic cluster instance, so that requests can be routed to the correct endpoint. The ODR can also dynamically adjust the amount of traffic sent to each individual server instance based on process utilization and response times. By default, the ODR binds to ports 80 and 443 for listening on HTTP and HTTPs, which requires running the ODR as a root user. If you want to run the ODR as a non-root user, change the PROXY listening ports to values greater then 1024.




What to do next

Configure the middleware servers and dynamic clusters for your environment.


Creating ODRs

Configure ODRs

Configure a Web server as a trusted proxy server

Configure SSL offload for all HTTPS traffic

Defining routing policies for generic server clusters

Defining service policies for generic server clusters

Next topic

Adding middleware servers to configurations

Next topic

Adding middleware servers to configurations

Next topic

Creating dynamic clusters


Related concepts

Overview of request flow prioritization


Related tasks

Preparing the hosting environment for dynamic operations


Related reference

createodr.jacl script