8.7.5 Verifying BeenThere
The last step is to verify that BeenThere is working correctly.
- Open the BeenThere start page...
http://cproxy.itso.ibm.com/wlm/BeenThere
cproxy.itso.ibm.com resolves to the IP address of our caching proxy (10.20.10.101), which points to the Web server cluster (10.20.10.100) associated with the load balancer machine (10.20.10.101).
You can also bypass the caching proxy and directly use one of the Web servers (http1 or http2) in the URL.
If you encounter problems accessing BeenThere through your Web server or caching proxy, try to access BeenThere directly via your appserver's WebContainer Inbound Chain using:
http://<your_app_server>:9080/wlm/BeenThere
In our environment, the URL is:
http://app1.itso.ibm.com:9080/wlm/BeenThere
The port number depends on your configuration.
- If you keep reloading the page you should see that all WEBcluster members are round-robin chosen by the plug-in workload management. As this application does not use sessions, this is the expected behavior.
- Enter 6 for the number of Bean invocations and click Run.
As you can see, the six EJB requests have been workload-managed across the EJB cluster members on both appserver nodes app1Node and app2Node. This demonstrates EJB weighted round robin workload management.
Each time you click the Run button there is only one request to the Web cluster. The application logic itself invokes the EJB sample method as many times as you asked.
You can now play around with the BeenThere application and with the cluster configuration. Using the BeenThere application you can see some run-time statistics and inspect the cluster member weights. Additional things to test are for example:
Stopping cluster members to see how the remaining members serve the requests.
Change appserver weights to see how many requests are served by each member.