An on demand router (ODR) is a proxy with advanced capabilities
that WebSphere® Extended
Deployment uses to route work to application server nodes.
Before you begin
For basic dynamic operations, define a node
group specifically for nodes that are running dynamic clusters. See Creating or editing a node group
for more information. The ODR is a
server that acts as an intermediary for HTTP requests that are serviced by
application servers or Web servers. Make sure you have an application or Web
server installed.
About this task
Use this task to create an ODR to route requests to WebSphere Extended
Deployment nodes. Or, you can use the guided activity in the administrative
console for assistance. Access the guided activity by clicking
Guided Activities
> Preparing the hosting environment for basic dynamic operations. Note
that the configuration of the ODR in the DMZ is not supported.
A deployment
manager profile cannot be used as the target profile for an ODR. Only an application
server profile can be used as the target node when creating an ODR. To collocate
an ODR with a deployment manager, a separate WebSphere Extended Deployment-enabled
application server profile must be created and federated on the same machine
as the WebSphere Extended Deployment-enabled deployment manager
profile. Then, an ODR can be created within the application server profile.
Procedure
In the administrative console, select Servers > On demand routers.
- Click New.
- Select the node on which you want the ODR to be created.
The selected node is prepopulated with available nodes in the cell.
If your environment is a heterogeneous mix of WebSphere Extended Deployment and
non-WebSphere Extended Deployment nodes, select a WebSphere Extended Deployment node.
If you select a non-WebSphere Extended Deployment node, your ODR does not
start.
Tip: Select a node to run the ODR that does
not run any dynamic clusters, unless you are using z/OS
®.
In a z/OS environment,
you can co-locate the ODR on a node that hosts application servers.
- Determine whether to generate unique HTTP ports. If
you are creating multiple ODRs in the same node, select the option to generate
unique ports. An advanced configuration for port mapping might require unique
ports. For example, a balancer can load balance requests to the ODRs within
the same node, assuming that each ODR is listening on a unique HTTP port.
- Select a server template to base your new ODR. You
can use an application server template on which to model the servers for the
new ODR. You can use a default template, or map an existing application server.
Mapping preexisting ODRs can save time. You can build one ODR, apply all of
the configurations that your environment needs, and use that ODR as a template.
The ODR that you created automatically routes HTTP requests to WebSphere Extended
Deployment cells. To enable routing to another WebSphere Extended Deployment cell,
configure your cell to communicate with other WebSphere Extended Deployment cells.
What to do next
You might want to configure the ODR to route work to non-WebSphere
Extended Deployment nodes. After you create the ODR and apply any optional
configuration parameters, you can define the ability to route work to non-WebSphere
Extended Deployment nodes. Note that the configuration of the ODR in the DMZ
is not supported.