The WAS the plugin has no "intelligence". The "default" WAS plugin uses round robin or a random algorithm for WLM of new requests. Each plugin operates independently in managing their individual instances of the request routing table.
When an http request creates an affinity, the WAS plugin does not keep track of affinity, but routes to proper sever based on the JSessionID.
If a server goes down the plugin sending a request to that server will note that the server is down and not route requests to that sever. This information is not share across plugins. Each plugin discovers this information on its own.
You can set routing weights in the plugin, but these are static and created by modifying the http plugin config file.
If you want "intelligence" in routing requests to a WAS ND environment, then you need to consider using WebSphere Virtual Enterprise (WVE) in WAS releases prior to WAS v8.5 and Intelligent Management in WAS 8.5.x releases.
The On Demand Router (ODR) available in WVE and WAS v8.5 and the Intelligent Managment (IM) routing plugin available with WAS v8.5.5 adds "intelligence" to the plugin. The IM plugin supports a subset of ODR capabilities.
When you enable Intelligement Management in WAS v8.5.x, you enable additional "processes" (application placement monitor (APC) and dynamic workload monitor (DWLM)) that works with the ODR to understand the workload charateristics of the WAS v8.5.x environment.
The APC and DWLM with the Autonmic Request Flow Manager (ARFM) work together to determine server routing weights, application placement, and server availability dynamically based on service policies create when the application is deployed to a WAS dynamic cluster. All ODRs deployed in a WVE or IM environment have this information available to them and can all dynamically adjust routing information.
ODR capabilities not supported in the IM plugin:
1) ODR routing rules
‒No load balancing or failover for the same application in multiple cells
‒Note that different applications in different cells is currently supported
2) CPU/memory overload protection
3) Request prioritization
‒No queueing and re-ordering of requests based on service policies
‒Note that dynamic clusters ARE supported
‒
4) Highly available deployment manager
5)Dynamic Cluster Lazy Start
See chapter 13 of the WebSphere Application Server V8.5 Administration and Configuration Guide for the Full Profile Redbook for an overview of IM -
www.redbooks.ibm.com/abstracts/sg248056....