|
Node agent and appserver
A node agent process will run on each node that is part of the cell. The node agent will look after appserver processes running on that node.
Installation
To install a node agent and create a profile, do the following:
| 1.
| Start HACMP services on the first LPAR to mount the shared file system from the VIO Server.
|
| 2.
| Install WebSphere Application Server Network Deployment V6.0 on the first LPAR. The installation path should be on the shared file system.
|
| 3.
| If necessary, install Refresh Packs or Fix Packs. WebSphere Install Factory could (and should) be used to streamline this process.
|
| 4.
| Create a custom profile on the first LPAR. The profile directory should be a subdirectory of the WebSphere <install_root>, which is on the shared file system. If you select a different profile directory, then ensure that it is on the shared file system. When creating the profile, use the virtual host name as the Host name. Do not use the physical host name or physical IP address.
|
| 6.
| Create appservers on the node as desired.
|
Configuration
To configure HACMP to run the node agents and appservers, add the node agent stop and start commands as well as the appropriate start and stop commands for each appserver in the failover unit to the HACMP stop and start scripts. Follow these steps:
| 1.
| Add the node agent and appserver stop commands to the HACMP stop script (ha.stop) on both LPARs. Be aware that the appserver names are case sensitive, and make sure that you specify the correct profile directory.
|
For example, if your node had two clones called svr01 and svr02, then in the profile called svr, the script might contain the following:
/usr/WebSphere/AppServer/profiles/svr/bin/stopServer.sh svr01
/usr/WebSphere/AppServer/profiles/svr/bin/stopServer.sh svr02
/usr/WebSphere/AppServer/profiles/svr/bin/stopNode.sh
| 2.
| Add the node agent and appserver start commands to the HACMP start script (ha.start) on both LPARs. It is usually prudent to add a sleep command after the node agent start command, because the appservers depend on an active node agent to be able to start successfully. The length of the sleep will need to be adjusted for your environment, depending on the time the node agent takes to start.
|
Using the preceding example with a sleep length of 60 seconds, the start script might contain the following:
/usr/WebSphere/AppServer/profiles/svr/bin/startNode.sh
sleep 60
/usr/WebSphere/AppServer/profiles/svr/bin/startServer.sh svr01
/usr/WebSphere/AppServer/profiles/svr/bin/startServer.sh svr02
| 3.
| Ensure that the HACMP services are active on the second LPAR.
|
Testing
During the failover process, the appservers hosted on the HACMP node cannot serve any client requests. At a minimum, the following two failover scenarios should be tested.
| Conduct a graceful failover test using the HACMP takeover option. Watch the SystemOut.log on the node agent and each appserver for a successful start. Check the node agent to make sure it can synchronize with the Deployment Manager before and after failover. There might be failed synchronization attempts during the failover.
|
|
| Fall back to the first LPAR and conduct a shutdown failover test using reboot -q on this LPAR. Watch the SystemOut.log on the node agent and each appserver for a successful start.
|
|