Stop and restart a cluster member

When you make configuration changes, you must stop and restart a cluster member.You can stop and restart a cluster member by using one of three methods: the administrative console, the MVS™ console or by issuing UNIX System Services commands.

  1. 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.
    • Quiesce the service integration bus.

  2. 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.

Some configuration changes require you to stop and restart server processes before the configuration change takes effect. This involves stopping and restarting of the dmgr, cluster member, and node agent.

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

You can use any of the following methods to stop and restart a server:


Procedure

  1. To stop and restart a server by using the administrative console:

    1. In the administrative console, navigate to Servers > Server Types > WebSphere application servers.

    2. Select the servers or cluster members that you want to stop. Click Stop, then wait for the cluster members to stop.

    3. Select the servers or cluster members that you want to restart. Click Start, then wait for the servers to start.

      Alternatively, you can stop and restart the complete cluster from the administrative console cluster panel by selecting Servers > Clusters > WebSphere application server clusters > cluster_name.

  2. To use the MVS console to stop and restart a server:

    1. From the MVS console, issue the following STOP command: 
      STOP  appserver_proc_name,JOBNAME= server_shortname

      appserver_proc_name

      Is the JCL procedure name in the proclib used to start the server.

      server_shortname

      Is the short name of the server which is also used as the process jobname.

      For example: 

      STOP BBO7ACR,JOBNAME=BBOS001

    2. To restart a server, issue the START command from the MVS console: 
      START  appserver_proc_name,JOBNAME= server_shortname,ENV= cell_shortname.node_shortname.server_shortname

      appserver_proc_name

      The JCL procedure name in the proclib used to start the server.

      server_shortname

      The short name of the server, which is also used as the process jobname.

      cellname.nodename.servername

      This element of the ENV parameter is a concatenation of the cell short name, the node short name, and the server short name.

      For example: 

      START BBO7ACR,JOBNAME=BBOS001,ENV=BBOBASE.BBONODE.BBOS001

      The following messages indicate that the controller is running: 

      $HASP100 BBO7ACR  ON STCINRDR 
$HASP373 BBO7ACR  STARTED     
BBOO0001I WEBSPHERE FOR Z/OS CONTROL PROCESS BBODMNB/SY1/BBOC001/BBOS001
          IS STARTING.
IRR812I PROFILE BBO*.* (G) IN THE STARTED CLASS WAS USED TO START BBOS001S 
        WITH JOBNAME BBOS001S.
$HASP100 BBOS001S ON STCINRDR                                         
$HASP373 BBOS001S STARTED
+BBOO0004I WEBSPHERE FOR Z/OS SERVANT PROCESS BBODMNB/SY1/BBOC001/BBOS001 
           IS STARTING. 
+BBOO0020I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS SERVANT PROCESS 
           BBOS001. 
BBOO0019I INITIALIZATION COMPLETE FOR WEBSPHERE FOR Z/OS CONTROL PROCESS 
          BBOS001.

  3. To stop and restart a server by using a UNIX System Services command, complete the following steps:

    1. Issue a stopServer command from the command line.
    2. Issue a startServer command.

      You can check that the server has successfully started by checking the startServer.log file.

      If the server has successfully started, the last two lines of the startServer.log file read: 

      Server launched.  Waiting for initialization status.
Server server1 open for e-business; process id is 1932.
      The startServer.log file is located in the profile_root/logs/server1/ directory