Server collection

Use this topic to learn how to navigate within the console to the pages where we can view information about the application servers, generic servers, Java message service (JMS) servers, and web servers defined for the system.

We can use these respective console pages to view the status of the listed servers. The status indicates whether a server is running, stopped, or encountering problems. We can also use these pages to perform the following actions for the listed servers:

To view the Application servers page, in the console page, click Servers > Server Types > WebSphere application servers. This page lists all of the application servers in the cell.

To view the Generic servers page, in the console, click Servers > Server Types > Generic servers. This page lists all of the generic servers in the cell.

To view the web servers page, in the console, click Servers > Server Types > Web servers. This page lists all of the web servers in the administrative domain. In addition to the previously mentioned actions, we can use this page to generate and propagate a web server plug-in configuration file.


Name

Logical name for the server. For WebSphere Application Server, server names must be unique within a node.

(zos) On the z/OS platform, this is sometimes called the long name. Server names must be unique within a node. If we have multiple nodes in a cluster, the server names must also be unique within the cluster. We 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.


Node

Node on which the server resides.


Host Name

Specifies the IP address, the full domain name system (DNS) host name with a domain name suffix, or the short DNS host name for the server.


Version

Version of the product on which the server runs.


Cluster Name

Name of the cluster to which the application server belongs. This field only displays when the Include cluster members in the collection console page preference is selected on the Applications server page.

If we have created clusters, and if the Include cluster members in the collection console page preference is selected, application servers that are cluster members are included in the list of application servers that displays on the Application servers page. These cluster members can be managed in the same manner as any of the other application servers in the list.

If the Include cluster members in the collection console page preference is not selected, application servers that are cluster members are not listed in the list of application servers that can be managed from this page.


Status

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 we can start the server.

Icon Status Description

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 The server status cannot be determined.


Related

  • Object names: What the name string cannot contain
  • Application server settings
  • Node agent collection