The high availability plugin-cfg generation service automatically
regenerates and propagates the web server plug-in configuration file
each time a change is made, which should affect how the plug-in routes.
When you use this service, the web server plug-in routes traffic by
application, deployment target, or node group to a specific ODR cluster.
Before you begin
The ability to segregate HTTP traffic by ODR cluster is
supported only through the use of the high availability plugin-cfg
generation service. It is not supported when a specific ODR is configured
to generate a plug-in configuration file.
Procedure
Set the following custom property to configure the high
availability plugin-cfg generation service and direct traffic to different
ODR clusters.- In the administrative console, select .
- Specify the name of the custom property as ODCPluginCfgRoutingPolicy_<config>. The <config> variable is the name of the configuration that
you choose. As a result, the properties end in the same variable to
define a single configuration for the generation of the high availability plugin-cfg.xml file.
- Specify the value of the custom property as a comma-separated
list of elements formatted as <webModuleSpec>=ODR=<odrClusterName>. You can specify the <webModuleSpec> portion
of the value as one of the following formats:
- WebModule:<cell>[/<application>/[<edition>/[<webModule>]]]]
Specifies
one or more web modules. Note that the brackets indicate optional
elements. If any part is omitted or if the value of any part equals
"*", it matches any value. For example, a custom property named ODCPluginCfgRoutingPolicy_1 with
a value of WebModule:myCell/myApp1=ODR=odrCluster1,WebModule:mycell/myApp2=ODR=odrCluster2 routes
traffic for the myApp1 application through odrCluster1 and
traffic for the myApp2 application through odrCluster2.
- Cluster:<cell>/<cluster>
Specifies
web modules that are deployed to the cluster. For example, a custom
property named ODCPluginCfgRoutingPolicy_1 with
a value of Cluster:myCell/myCluster1=ODR=odrCluster1,Cluster:myCell/myCluster2=ODR=odrCluster2 routes
traffic targeted for any application, which is deployed to myCluster1,
through odrCluster1. Similarly, traffic targeted
for any application that is deployed to myCluster2 is
routed through odrCluster2.
- NodeGroup:<cell>/<nodeGroup>
Specifies
web modules that are deployed to one or more nodes in the node group.
For example, a custom property named ODCPluginCfgRoutingPolicy_1 with
a value of NodeGroup:myCell/myNodeGroup1=ODR=odrCluster1,Cluster:myCell/myNodeGroup2=ODR=odrCluster2 routes
traffic targeted for any application, which is deployed to a node
in nodeGroup1, through odrCluster1.
Traffic targeted for any application that is deployed to a node in nodeGroup2 is
routed through odrCluster2.
- VirtualHost:<cell>[/<VirtualHost>]
Specifies
all of the web modules that are deployed to the virtual host. For
example, a custom property named ODCPluginCfgRoutingPolicy_1 with
a value of VirtualHost:myCell/default_host=ODR=odrCluster1,VirtualHost:myCell/special_host=ODR=odrCluster2 routes
traffic for applications that are deployed to default_host through odrCluster1.
Traffic targeted for applications that are deployed to special_host is
routed through odrCluster2.
You can specify the <odrClusterName> variable
as a simple cluster name, or you can format it as <cell>/<cluster> to
reference an ODR cluster in a different cell from which the service
is running. In general, the value is read as meaning all traffic that
matches the <webModuleSpec> variable is
routed through the ODR cluster named <odrClusterName>.