Manage application servers



Use either the admin console or command-line tools to manage the application servers.

Before changing the system clock, stop all the application servers, the node agent servers, the dmgr server, the administrative agent server, and the job manager server first. After you stop the servers, change the system clock, and then restart the servers. If we change the system clock on one system, ensure the clocks on all systems that communicate with each other and have WAS installed are synchronized. Otherwise, we might experience errors, such as security tokens no longer being valid.

If migrating from a previous version of WAS ND, we can upgrade a portion of the nodes in a cell, while leaving others at the previous release level. This means that, for a period of time, we might be managing servers that are running at different release levels in the same cell. In this mixed environment, some restrictions exist for what we can do with servers that are running at a previous release level. No restrictions exist for what we can do with the servers that are running on the newest release level.

You can perform the following steps to view and manage an appserver from the admin console.



  1. In the admin console click...

      Servers | Server Types | WebSphere application servers

    The Application servers page lists the appservers in the environment and the status of each of these servers.

    We can...

    • Create additional servers.
    • Monitor running servers.
    • Control the status of a server.
    • Create a server template
    • Delete a server.

    When you select a server for deletion, click Delete and OK before the server is deleted.

    If the server we are deleting has applications or modules mapped to it and is not part of a cluster, remap the modules to another server, or create a new server and remap the modules to the new server, before you delete this server. After a server to which modules are mapped is deleted, we cannot remap these modules to another server. Therefore, if we do not remap the modules to another server before you delete this server, uninstall all of the modules that were mapped to this server, and then reinstall them on a different server.

    If the server we are deleting is part of a cluster, any application that is installed on this server is automatically installed on all of the other servers in the cluster. Therefore, deleting one cluster member does not affect the other cluster members, and the application remains installed in the cluster. Similarly when a new member is added to an existing cluster, any applications that are installed on the servers in that cluster are automatically installed on the new cluster member.

  2. Click the name of a listed server to set the settings for that server.

    Use this admin console page to:

    • Change the settings for the selected server.

      For example, if we do not need to have all of the sever components start during the server startup process, we might want to select Start components as needed, which is not automatically selected when a new server is created. When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the startup process. Therefore, selecting this property usually results in improved startup time because fewer components are started during the startup process.

    • View the status of applications running on the selected server. To view the status of applications running on this server, under Applications, click Installed Applications.

  3. Click Review, select Synchronize changes with Nodes.

  4. Click Save to save any configuration changes that you made.

  5. If we made any configuration or custom property changes, start the appserver, or stop and restart the appserver if it is already running.



View the state of each server...

View any configuration changes...


Server collection
Application server settings
Core group service settings
Environment entries collection
Starting an appserver
Detecting and handling problems with runtime components
Stopping an appserver
Change time zone settings
Web module or appserver stops processing requests
Create appservers
Getting started with scripting
Hot deployment and dynamic reloading
Restarting an appserver in recovery mode
Considering security specific to a multi-node or process ND environment
Administer appservers
Create clusters