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


Cell affinity function

Using the cell affinity function, you can configure unbridged, on demand router (ODR) topologies to preserves sessions even in the event of on demand router (ODR) outages. With this function, you can configure your topology in such a way that, when an ODR receives misrouted, in-session traffic, the ODR reroutes the traffic back to a working ODR in the original cell. Thus, you can configure an IBM HTTP Server to route to ODRs in multiple cells and still preserve session affinity.

[Version 6.1.0.5 only]
New feature: You can use this feature if you have Version 6.1.0.5 or later installed.newfeat

The cell affinity function prevents the loss of sessions when there are multiple ODRs within multiple, unbridged cells, and the IBM HTTP Server is configured to forward session traffic, either through load-balancing or failover, to more than one ODR. For example, in a network configuration where ODRs are situated between the IBM HTTP Server and the back-end application servers, the IBM HTTP Server is not able to recognize the servers identified on the JSESSIONID cookies contained within in-session traffic, because it is configured to recognize and route to the ODRs. Thus, the IBM HTTP Server generally selects different ODRs and sprays the session requests. If the IBM HTTP Server selects a router within the same cell as the hosting application server, or if the application servers all share session data through a common database, the risk of loss of sessions is not a concern. However, without cell affinity, if the IBM HTTP Server selects an ODR within another cell, the ODR does not recognize the server ID, does not know how to route the request, and consequently the session is lost.

Aspects in cell affinity function

There are two major aspects in the cell affinity function. The first aspect enables the IBM HTTP Server to affine, or always route to, a specific ODR after a session is established. Configuring the IBM HTTP Server to preserve session affinity through a particular ODR is accomplished by enabling cell affinity - producing a plugin-cfg.xml,, moving the plugin-cfg.xml to the IBM HTTP Server, and restarting that server. The produced plugin-cfg.xml instructs the IBM HTTP Server plug-in to use the ODRSESSIONID cookie for its session ID, thereby enabling session affinity to the ODRs.

The second aspect of cell affinity is the ability to route session traffic across cell boundaries in order to direct misrouted traffic into the correct cell. To enable this ability, configure the IBM HTTP Server to preserve session affinity by routing through a particular ODR, as described previously, and configure generic server clusters for each cell for which the ODR can receive traffic. The members of those generic server clusters must be the ODRs in remote cells. When an ODR receives misrouted session traffic and cell affinity is enabled, the ODR refers to the list of generic server clusters to see whether the ODR identified by the ODRSESSIONID can be found. If a match is found, the ODR will reroute the traffic to the containing generic server clusters. If the reroute is successful, the final ODR adopts the session.




Related information
Enabling cell affinity
Configuring cell affinity in a multi-tiered environment
Defining generic server clusters for remote ODR cells
pluginMergebat|.sh script
Creating and configuring ODRs
Configuring ODRs
Concept 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/codoeaffinity.html