Optionally, you can define routing policies for generic server
clusters.
Before you begin
You must have an on demand router (ODR)
created and configured. After the ODR is created, it senses the environment
and can route work to WebSphere® Extended Deployment application servers.
About this task
You can define routing policies for generic server clusters by clicking Servers
> ODRs > Select an ODR_name > On demand router settings > Generic server
cluster routing properties.
Procedure
- Select a work class for HTTP requests and
click New.
- Type a name for the work class in the Name field.
- Click Finish to confirm your new work class.
- To set a URI match condition for an existing rule, type the name
of the URI in the If URI matches field, and from the For virtual
host list, select a host name.
- Assign a work class with no rules and provide choices for the other
fields in the panel.
- Click Apply or OK to commit your new rule settings.
The new ODR has a default routing policy, a URI pattern of asterisk (*),
a virtual host selection of default_host and a default routing action of
Reject with return code with the reject return code set to 403.
What to do next
After you create the ODR and apply any optional configuration parameters,
you can define the ability to route work to non-Extended Deployment nodes.