WebSphere brand IBM WebSphere Presence Server, Version 7.0

Stopping and starting the server

After making changes to the server configuration, you must restart the application server.

About this task
In a clustered environment, some tasks require you to restart the deployment manager for changes to take effect. To stop the deployment manager, you must stop all application servers, all node agents, and then the deployment manager. To restart the deployment manager, you must start the deployment manager, all node agents, and then the cluster (which starts all application servers).

The following instructions describe how to stop and restart resources both from the Integrated Solutions Console and from a command-line prompt.

Note: was_profile_root is the directory for a WebSphere® Application Server Network Deployment profile called profile_name. By default, this directory is:
  • AIX /usr/IBM/WebSphere/AppServer/profiles/profile_name
  • Linux /opt/IBM/WebSphere/AppServer/profiles/profile_name

Stopping a cluster

About this task
When you stop a cluster, all application servers on the cluster are stopped.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Stop the cluster:
    1. In the Integrated Solutions Console, click Servers > Clusters > WebSphere application server clusters.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Clusters.
    2. Select the check box associated with the name of the cluster.
    3. Click Stop.

Stopping a server (console)

About this task
Stopping an application server stops all applications automatically.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Stop the application server:
    1. In the Integrated Solutions Console, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Select the check box associated with the name of the server.
    3. Click Stop.

Stopping a server (command line)


Run the following command:
  • AIX was_profile_root/bin/stopServer.sh server_name -username user_name -password password
  • Linux was_profile_root/bin/stopServer.sh server_name -username user_name -password password

Where:

  • The was_profile_root path contains the name of the application server profile (for example, AppSrv01).
  • server_name is name of the application server.
  • user_name represents your WebSphere Application Server administrator user ID.
  • password represents the password associated with your user_name.

Stopping the node agent (console)

About this task
When stopping the deployment manager and application servers, you must also stop the node agents. If you are stopping a cluster, you must stop all node agents.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Stop one or more nodes:
    1. In the Integrated Solutions Console, click System administration > Node agents.
    2. Select the check boxes associated with each node.
    3. Click Stop.

Stopping the node agent (command line)


Run the following command:
  • AIX was_profile_root/bin/stopNode.sh -username user_name -password password
  • Linux was_profile_root/bin/stopNode.sh -username user_name -password password

Where:

  • The was_profile_root path contains the name of a federated node profile (for example, Custom01).
  • user_name represents your WebSphere Application Server administrator user ID.
  • password represents the password associated with your user_name.

Stopping the deployment manager (console)

About this task
When stopping the servers and node agents in a cluster, you must also stop the deployment manager. When the deployment manager is stopped, you will not be able to access the Integrated Solutions Console.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Stop the deployment manager:
    1. In the Integrated Solutions Console, click System administration > Deployment manager.
    2. Click Stop.

Stopping the deployment manager (command line)


Run the following command:
  • AIX was_profile_root/bin/stopManager.sh -username user_name -password password
  • Linux was_profile_root/bin/stopManager.sh -username user_name -password password

Where:

  • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).
  • user_name represents your WebSphere Application Server administrator user ID.
  • password represents the password associated with your user_name.

Starting the deployment manager

About this task
Start the deployment manager before starting the node agents and application servers. When the deployment manager is started, you will have access to the Integrated Solutions Console.

Run the following command:
  • AIX was_profile_root/bin/startManager.sh
  • Linux was_profile_root/bin/startManager.sh

Where:

  • The was_profile_root path contains the name of the deployment manager profile (for example, Dmgr01).

Starting the node agents

Before you begin
After starting the deployment manager, you must start the node agents before you can start the cluster or the application server.

Run the following command:
  • AIX was_profile_root/bin/startNode.sh
  • Linux was_profile_root/bin/startNode.sh

Where:

  • The was_profile_root path contains the name of a federated node profile (for example, Custom01).

Starting a cluster

About this task
When you start a cluster, all application servers on the cluster are started.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Start the cluster:
    1. In the Integrated Solutions Console, click Servers > Clusters > WebSphere application server clusters.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Clusters.
    2. Select the check box associated with the name of the cluster.
    3. Click Start.

Starting a server (console)

About this task
Applications that were running when the server was stopped are restarted automatically.
  1. Log in to the Integrated Solutions Console:
    1. Open a browser and navigate to the following URL: https://host_name:port/ibm/console.
      Where:
      • host_name is the fully qualified host name of the server where the application or the network deployment manager is deployed.
      • port is the secured port used to access the console. The default port is 9043.
      Note: The default unsecured port is 9060. If you use 9060, you must have "http" instead of "https" in the URL.
    2. Enter an administrator user ID and password.
    3. Click Log in.
  2. Start the application server:
    1. In the Integrated Solutions Console, click Servers > Server Types > WebSphere application servers.
      Note: If you are using WebSphere Application Server version 6.1.0.x, reach this window by clicking Servers > Application servers.
    2. Select the check box associated with the name of the server.
    3. Click Start.

Starting a server (command line)


Run the following command:
  • AIX was_profile_root/bin/startServer.sh server_name -username user_name -password password
  • Linux was_profile_root/bin/startServer.sh server_name -username user_name -password password

Where:

  • The was_profile_root path contains the name of the application server profile (for example, AppSrv01).
  • server_name is name of the application server.
  • user_name represents your WebSphere Application Server administrator user ID.
  • password represents the password associated with your user_name.



Terms of use
(C) Copyright IBM Corporation 2009. All Rights Reserved.