Server collection

Use this topic to learn how to navigate within the administrative console to the pages where you can 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:

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.

To view the Version 5 Java message service (JMS) servers page, in the administrative 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 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.

Avoid trouble: JMS servers apply only to WebSphere® Application Server Version 5.x nodes. You cannot create a JMS server on a node that is not running WebSphere Application Server Version 5.x, but existing Version 5.x JMS servers continue to be displayed, and you can modify their properties. However, you cannot use this page to delete a Version 5.x JMS server.gotcha

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 host name 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 only displays when the Include cluster members in the collection console page preference is selected on the Applications server page.

If you 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

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

Table 1. Server status and meaning. The following table describes the server status.
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.
[jul2010] Unavailable [jul2010]
jul2010
[jul2010] Unavailable [jul2010]
jul2010
[jul2010] The server status cannot be determined. [jul2010]
jul2010



Related tasks
Managing application servers
Related reference
Object names: What the name string cannot contain
Application server settings
Node agent collection
Version 5 JMS server settings
Version 5 JMS server collection
Reference topic    

Terms of Use | Feedback

Last updated: Oct 21, 2010 10:04:34 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-nd-mp&topic=urun_rsvr
File name: urun_rsvr.html