Server collection

Learn how to use the administrative console to view information about the application servers, generic servers, Java message service (JMS) servers, and web servers that are defined for your system.

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

  • Select one or more of the listed servers, and then click Start to start those servers.
  • Select one or more of the listed servers, and then click one of the following options to stop those servers:
    STOP
    When you click this option, the normal server quiesce process is followed. This process allows in-flight requests to complete before the entire server process shuts down. The time limit for the normal server quiesce process is governed by the com.ibm.ejs.sm.server.quiesceTimeout Java virtual machine (JVM) custom property, which defaults to 180 seconds.
    Restart
    The restart option applies to WebSphere® Application Server Network Deployment and WebSphere Application Server for z/OS®.

    When you click this option, the restart MBean is issued to the node agent of a server. This MBean stops the server and after the server is stopped, the MBean restarts the server. Occasionally, a restart might fail if all the necessary resources are not yet released after the server is stopped.

    [8.5.5.16 or later] If problems occur with the restart, you can set the com.ibm.websphere.console.server.restart.delay custom property to allow a wait period between the issuing of the stop and the issuing of the start. For more information about the com.ibm.websphere.console.server.restart.delay custom property, see the Java™ virtual machine custom properties topic.

    Immediate Stop
    This option is only available for application servers.

    When you click this option, the selected server stops but the normal server quiesce process is not followed. This shutdown mode is faster than the normal server stop processing, but some application clients might receive exceptions if an in-flight request does not complete before the server process shuts down. If you use this option, the com.ibm.ejs.sm.server.quiesceTimeout JVM custom property employs a value of 0 seconds.

    Terminate

    Select Terminate only if the server does not respond when you click Stop or Immediate Stop, or when you issue the Stop or ImmediateStop commands. Because this option is analogous to an OS command-line kill -9 <pid> command, some application clients might receive exceptions. Therefore, always attempt an immediate stop first before you select Terminate.

  • Click New to create a new server.
  • Click Templates to create a new server template.
  • Select one or more of the listed servers, and then click Delete those servers.

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

Name

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

[z/OS]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.

Node

Specifies the 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 hostname for the server.

Version

Specifies the version of the product on which the server runs.

Cluster Name

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

If you create clusters and the Include cluster members in the collection console page preference is selected, application servers that are cluster members are included in the list 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 on the Application servers page.

Status

Specifies whether the server is started, stopped, partially stopped, or unavailable. If the status is unavailable, the node agent is not running inin that node and you must restart the node agent before you can start the server.

Table 1. Server status and meang. The following table describes the server status.
Icon Status Description
Started Started The server is running.
Partially stopped Partially stopped The server is in the process of changing from a started state to a stopped state.
Stopped Stopped The server is not running.
Unavailable Unavailable The server status cannot be determined.