Use this page to view information about and manage application servers, Java message service (JMS) servers, and Web servers.
For the Network Deployment product, you can also use this page to view information about and manage generic servers.
Application servers
The Application servers page lists the application servers in the cell. You can use this page to perform the following actions for the listed application servers:
If you are using the Network Deployment product,, you can also use this page to create a new application server or a new application server template. To create a new application server, click New. To create a new application server template, click Templates.
If you are using the Network Deployment product and have created clusters, you can also use this page to manage application servers that are cluster members if the Include cluster members in the collection console page preference is selected. When this preference is selected, a Cluster Name column is included in the application server information table. If an application server is part of a cluster, the Cluster Name column specifies the name of that cluster. If this preference is not selected, the Cluster Name column does not appear in the table and application servers that are cluster members are not listed in the list of application servers and cannot be managed from this page.
If you are using the Network Deployment product, this page displays the status of the application servers. The status indicates whether a server is running, stopped, or encountering problems.
To view this administrative console page, click Servers > Application servers.
Generic servers
You can also use this page to create a new generic server or a new generic server template. To create a new generic server, click New. To create a new generic server template, click Templates.
The Generic servers page is only available for the Network Deployment product. This page lists the generic servers in the cell and displays the status of these generic servers. The status indicates whether a server is running, stopped, or encountering problems. You can use this page to start and terminate these generic servers. You can also use this page to create new generic servers, create generic server templates, delete existing generic servers, or stop a generic server.
To view this administrative console page, click Servers > Generic servers.
Java message service (JMS) servers
The JMS servers page lists the JMS servers in the cell. You can use this page to start and stop these JMS servers. Each JMS server provides the functions of the JMS provider for a node in your administrative domain. There can be at most one JMS server on each node in the administration domain, and any application server within the domain can access JMS resources served by any JMS server on any node in the domain. To view this administrative console page, click Servers > JMS servers.
Web servers
The Web servers page lists the Web servers in your administrative domain. You can use this page to generate and propagate a Web server plug-in configuration file, create new Web servers, create new Web server templates, or delete existing Web servers. You can also use this page to start and stop these Web servers. To view this administrative console page, click Servers > Web servers.
Specifies a logical name for the server. For WebSphere Application Server, server names must be unique within a node.
On the z/OS platform, this is sometimes called the long name. Server names must be unique within a node. If you have multiple nodes in a cluster, the server names must also be unique within the cluster. You cannot use the same server name within two nodes that are part of the same cluster. WebSphere uses the server name for administrative actions, such as referencing the server in scripting.
Specifies the name of the node holding the server.
Specifies the version of the WebSphere Application Server product on which the server runs.
This field only displays for the Network Deployment product. It indicates whether the server is started, stopped, partially stopped, or unavailable. If the status is unavailable, the node agent is not running in that node and you must restart the node agent before you can start the server.
![]() |
Started | The server is running. |
![]() |
Partially stopped | The server is in the process of changing from a started state to a stopped state. |
![]() |
Stopped | The server is not running. |
![]() |
Unavailable | Status cannot be determined. A server with an unavailable status might, in fact, be running but has an unavailable status because the application server that is running the administrative console cannot communicate with this server. |