Stopping and restarting a cluster member

When you make configuration changes, you must stop and restart a cluster member.

Before you begin

You must use a user ID and password with WebSphere Application Server administrator or operator privileges to perform this task.

Prevent new work from entering the cluster member:
- If you are using the IBM® HTTP Server, change the plugin_cfg.xml file to remove the cluster member for HTTP traffic. If you are using another HTTP server, follow the directions for your HTTP server to remove the cluster member.
- For IIOP traffic, set the runtime weight to zero for the cluster member.
Verify that work that is destined for the cluster member is complete. Either wait a period of time or use Performance Monitoring Infrastructure counters to determine when the cluster completes all of the queued work.

About this task

Some configuration changes require you to stop and restart server processes before the configuration change takes effect. This involves stopping and restarting of the deployment manager, node agents, and cluster members.

Note: All command files (alternatives to using the administrative console) are located in the install_root/bin subdirectory.

To stop and restart a server by using the administrative console, complete the following steps:

Procedure

In the administrative console, navigate to Servers > Server Types > WebSphere application servers.
Select the servers or cluster members to be stopped and click Stop.
Wait for the servers or cluster members to stop.
Select the servers or cluster members to be restarted and click Start.
Wait for the servers or cluster members to start.
Note: Alternatively, you can stop and restart cluster members from the command line using the stopServer and startServer commands for your operating system or from the administrative console cluster panel by selecting Servers > Clusters > WebSphere application server clusters > cluster_name.