Server collection

Use this topic to learn how to navigate within the admin 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.

Use these respective admin 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:

• 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.

  Immediate Stop

  This option is only available for appservers.

  When you click this button, 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.

  Terminate

  This option is not available for Version 5 JMS servers.

  You should only click Terminate if the server does not respond when you click Stop, or, Immediate Stop or when you issue the Stop or ImmediateStop commands. Some application clients can receive exceptions. Therefore, you should always attempt an immediate stop before clicking 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. This option is not available for V5 JMS servers.

To view the Application servers page, in the admin 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 admin 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 admin console, click...

Servers | Server Types | Web servers

This page lists all of the Web servers in the admin domain. In addition to the previously mentioned actions, we can use this page to generate and propagate a Web server plug-in configuration file.

To view the V5 Java message service (JMS) servers page, in the admin console page, click...

Servers | Server Types | Version 5 JMS servers

This page lists all of the JMS servers in the cell. Each JMS server provides the functions of the JMS provider for a node in the admin domain. There can be, at most, one JMS server on each node in the administration domain, and any appserver within the domain can access JMS resources served by any JMS server on any node in the domain.

JMS servers apply only to WAS V5.x nodes. We cannot create a JMS server on a node not running WAS V5.x, but existing Version 5.x JMS servers continue to be displayed, and we can modify their properties. However, we cannot use this page to delete a V5.x JMS server.

Name

Logical name for the server. For WAS, server names must be unique within a node.

Node

Node on which the server resides.

Host Name

Version

Version of WAS on which the server runs.

Cluster Name

Name of the cluster to which the appserver belongs. This field only displays when the preference...

Include cluster members in the collection console page

...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, appservers that are cluster members are included in the list of appservers that displays on the Application servers page. These cluster members can be managed in the same manner as any of the other appservers in the list.

If the Include cluster members in the collection console page preference is not selected, appservers that are cluster members are not listed in the list of appservers 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 restart the node agent before we can start the server.

Table 1. Server status and meaning

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

---

 

Related tasks

Manage appservers

 

Related

Object names: What the name string cannot contain
Application server settings
Node agent collection
Version 5 JMS server settings
Version 5 JMS server collection