WebSphere Virtual Enterprise (formerly Operations Optimization), Version 6.1
             Operating Systems: AIX, HP-UX, Linux, Solaris, Windows, z/OS


Configuring passive HTTP session affinity in the on demand router

When the on demand router (ODR) processes a request, it obtains the session affinity descriptor policy of the cluster to which the server belongs. If you changed the default settings for any middleware servers, you might need to update the middleware descriptor properties so that the ODR can obtain the descriptor policy. In most cases, the on demand router (ODR) does not require configuration to support HTTP session affinity. However, some special cases exist where you must configure the ODR to learn about backup servers that the back end servers might be setting on the session affinity cookie.

Before you begin

The servers in your configuration must be in a generic server cluster or a dynamic cluster. You can use passive affinity with a static cluster.

About this task

Passive HTTP session affinity is used in the following situations:

Procedure

  1. If any of the default values for the server have changed, modify the session affinity descriptor. In the administrative console, click System administration > Middleware descriptors > middleware_server > default.
  2. Define the session affinity descriptor properties. Modify the values for any of the following fields that apply:
    • Learn clone IDs
    • Cookie names
    • URL rewrite
    • Clone ID separator
    • Alternate clone ID separator
    • Affinity mode
  3. Optional: You can create a cell-wide custom property, HttpAffinityPolicy.cookie_name.cell_name.cluster_name, to specify session ID cookie names as something other than JSESSIONID.
    1. In the administrative console, click System administration > Cell > Custom properties > New .
    2. Set the HttpAffinityPolicy.cookie_name.cell_name.cluster_name custom property at the following levels, which are listed in order of preference:
      • Web module
      • Application
      • Server
      • Cluster
    3. Click Apply and save your changes. Any changes are picked up dynamically; you do not need to restart the cell.

Results

When the ODR processes a request, it obtains the session affinity descriptor policy that is configured for the cluster to which the server belongs. The method in which the server clone identification is obtained depends on the property values of the policy attributes.




Related concepts
Overview of request flow prioritization
Related tasks
Creating ODRs
Routing requests to external nodes with generic server clusters
Creating and configuring ODRs
Task topic    

Terms of Use | Feedback

Last updated: Oct 30, 2009 6:17:06 PM EDT
http://publib.boulder.ibm.com/infocenter/wxdinfo/v6r1/index.jsp?topic=/com.ibm.websphere.ops.doc/info/odoe_task/todrpassive.html