1 Verify failover with Trade3.1

Now that you have Trade3.1 up and running, verify WebSphere's failover functionality. The following outlines a scenario you could use to do so.

Before you begin, ensure that all servers are started.

1. Log into Trade3.1.

2. On one of the Webcluster servers (WEB1a, WEB1b, or WEB2) a session has been created. Stop two of the Web servers, for example WEB1a and WEB2:

Open up another browser window, log on to the WebSphere Administrative Console and select Servers -> Application Servers. Select the two appservers WEB1a and WEB2 and click Stop.

3. Continue using Trade3.1; this will force WEB1b to handle all your requests to the Trade3.1 application.

You are now certain that your session lives in the WEB1b server.

To verify WebSphere failover, you can now restart another Web server of the WEBcluster, for example WEB2. After this server has been restarted, you can then stop WEB1b:

4. Select appserver WEB2 and click Start. Wait until it has started.

5. Now stop appserver WEB1b.

6. After it has stopped, continue using Trade3.1, your session will still exist and you can continue using Trade3.1 without any interruptions.

This proves that session persistence is working on the WEBcluster. Another scenario could be to stop one or more EJBcluster appservers, or you could try shutting down an entire node.

  Prev | Home | Next

 

WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.