Since the two Application Servers are not in a cluster, the generated plugin-cfg.xml contains two separate ServerCluster elements. Each ServerCluster element has one Server element only. Obviously, IBM HTTP Server won't know how to load balance them. So, what I had to do is to modify the plugin-cfg.xml to minmic a cluster configuration. i.e.
- One ServerCluster element with 2 child Server elements
- Each Server element has an unique CloneID (this is required for session affinity)
- Add the PrimaryServers element with 2 child Server elements to the ServerCluster element