Restarting application server processes

When you change a configuration at the cell-level, you must restart all IBM® WebSphere® Application Server Network Deployment processes to make the changes effective. You should restart the application servers, node agents, and deployment manager on each machine in a specific order.

About this task

You must restart all IBM WebSphere Application Server Network Deployment processes when you modify anything at the cell-level (deployment manager-level). For example, restart application server processes after you do any of the following tasks:
  • Change security at the cell-level (for example, when you enable SSL, replace SSL certificates, or switch user registry)
  • Modify configurations for a data source
  • Change other cell-level settings
For information about how to do the tasks involved in each of these steps in this topic, refer to the following tables.
Note: The simplest way to restart node agents and application servers (clusters) is through the WebSphere Application Server administrative console. If you use the command line tools instead, make sure to specify a WebSphere Application Server administrator user name and password.

Procedure

  1. Stop all WebSphere Application Server processes in the following order:
    1. Stop all application servers on every computer.
    2. Stop all node agents on every computer.
    3. Stop the deployment manager.
    To stop application servers, node agents, and deployment managers for IBM WebSphere Application Server Network Deployment, refer to the following table.
    Table 1. Stopping WebSphere Application Server processes
    WebSphere Application Server Process Stopping the process
    Application server (stopping)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/trun_wlm_cluster_stop.html
    Node agent (stopping)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rxml_stopnode.html
    Deployment manager (stopping)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rxml_stopmanager.html
  2. After you have stopped all WebSphere Application Server processes, you can proceed to restart them. Start all WebSphere Application Server processes in the following order:
    1. Start the deployment manager.
    2. Start all node agents on every machine.
    3. Start all application servers on every machine.

    To start application servers, node agents, and deployment managers for IBM WebSphere Application Server Network Deployment, refer to the following table.

    Table 2. Starting WebSphere Application Server processes
    WebSphere Application Server Process Starting the process
    Deployment manager (starting)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rxml_startmanager.html
    Node agent (starting)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/rxml_startnode.html
    Application server (starting)

    Go to:

    https://www.ibm.com/support/knowledgecenter/SSAW57_9.0.5/com.ibm.websphere.nd.multiplatform.doc/ae/trun_wlm_cluster_start.html
    Note: For more information about node agents, see Node agent collection.