Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS
Defining routing policies for generic server clusters
You can define routing policies for generic server clusters. A routing policy is a set of rules that determine how the server routes incoming requests.
Procedure
- In the administrative console, click Servers > On demand routers >ODR_name > On demand router properties > Generic server cluster routing properties.
- Click Work classes 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 404.
What to do next
After creating the ODR and apply any optional configuration parameters, you can define the ability to route work to nodes that are not running WebSphere® Virtual Enterprise.
Related concepts
Overview of request flow prioritization
Related tasks
Configure rewriting rules
Configure the on demand router for multi-cluster failover and load balancing routing
Related reference
createodr.jacl script
Administrative roles and privilegesRelated information
Defining service policies for generic server clusters
Proxy server settings