Define routing policies for generic server clusters
We can define routing policies for generic server clusters. A routing policy is a set of rules that determine how the server routes incoming requests.
- In the administrative console, click...
Servers | Server types | On demand routers | ODR_name | On demand router properties | Generic server cluster routing policies | Work classes for HTTP requests | click | New
- Type a name for the work class in the Name field.
- Click Finish to confirm the new work class.
- To set a URI match condition for an existing rule, type the name of the URI in the field: "If URI matches".
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 the 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, we can define the ability to route work to nodes that are not running Intelligent Management.
Subtopics
- Configure rewriting rules
We can configure rewriting rules to redirect requests to the proxy server, which then routes the requests to the target server. The proxy server acts as an intermediary for HTTP requests serviced by application servers or Web servers.
Related:
Overview of request flow prioritization Define service policies for generic server clusters Configure rewriting rules Configure the ODR for multi-cluster failover and load balancing routing createodr.jacl script Intelligent Management: administrative roles and privileges Proxy server settings