|
|
In our environment, we killed the process ID of the appserver and shut down the system:
| 1. | Ensure HACMP services are active on both HHOST1 and HHOST2. |
| 2. | Conduct a failover test by ending the appserver process using the kill -9 Application_server_process_ID command on HHOST1. You can find the PID of the appserver by looking at the application_servername.pid file in the appserver's log directory. |
| 3. | Verify the Transaction Manager's failover: |
| a. In the Administrative Console click Servers | Core groups | Core group settings | Core_group_name. Select the Runtime tab. |
| b. Enter type=WAS_TRANSACTIONS into the Group name properties field, and then click Show groups. A panel similar to the one in Figure 11-8 is displayed. This panel shows all Transaction Manager High availability groups of your environment. |
Figure 11-8 Checking Transaction Manager failover - 1
c. Select the High availability group which is related to the failed appserver's Transaction Manager. The panel in Figure 11-9 is shown. Then verify that the Transaction Manager's Status is active and the Transaction Manager is running on the other appserver.
Figure 11-9 Checking Transaction Manager failover - 2
If there are any in-doubt transactions when the failover happens, you would see transaction recovery messages in the SystemOut.log of the take-over appserver.
