Update your routing rules after you activate an application to
ensure that the on demand router can route requests to the appropriate application
edition.
About this task
A routing policy is stored as part of the configuration metadata
for an application. With a routing policy, you can express rules that instruct
an on demand router (ODR) to send particular application requests to one edition
or another based on a set of criteria. You can use various criteria that specify
which requests are sent to a particular application edition. Use this process
to send requests from certain users to one edition and requests from other
users to another edition.
Procedure
- Navigate to the routing policies for the application. Click Applications
> Enterprise applications > application_name or Applications > All applications > application_name. Click
the Routing policies tab. For example, select the my_application application.
- Expand Work classes for HTTP requests.
Because no routing rules are specified, all requests are routed to the
edition that is displayed on this page. For example, all requests
are routed to application edition, my_application-edition2.0.
- Click Rule builder.
- From the rule list, select a rule. For example, select Client
host (clienthost), and click Add.
- Select criteria for the rule. For example, select
an operator of Equals (=) and type a value of your
client host name. Click OK.
- Click OKagain.
- Expand Work classes for HTTP requests.
- Set the action associated with the new rule. For
example, requests from the host route to edition, my_application-edition1.0.
Select the corresponding action from the Then list,
and click Apply to save the rule.
- From the top of the Routing policies tab, click Apply.
- Save the changes to the configuration repository and synchronize
the nodes.
What to do next
If you are routing to multiple editions of the same application,
you can validate your new application edition before moving to the new edition.
See
Validating an edition