Middleware server collection

Use this page to view and manage your middleware servers. Middleware servers are generic servers in the middleware tier that host applications or their data.

Use this page to create new middleware servers, middleware server templates, or delete existing middleware servers.

To view this administrative console page, click Servers > All servers, or select Servers > Server types, and then select a specific type of middleware server. Use the compound filtering icon filter icon

to form specific collection views by type.

Table 1. Middleware server buttons
Button	Resulting action
New	Opens a wizard that helps you create a middleware server. Server types include application, generic, on demand router, proxy, or Web server. Each server type has a unique wizard. You can also add a server that exists in your environment, but does not run WebSphere®, such as a PHP server, custom HTTP server, or WebSphere Application Server Community Edition server, or Liberty profile server.
Delete	Removes the server.
Templates	Opens the list of defined server templates. Server templates are copies of server configuration data that can be used as a starting point for creating servers. You can create or edit existing templates.
Start	Starts a server or multiple servers that you select. Enable the Select check box for each middleware server that you want to start, then click Start.
Stop	Stops a server or multiple servers that you select. Enable the Select check box for each middleware server that you want to stop, then click Stop.
Terminate	Terminates the server immediately.
Submit Action	Runs the action list for a Web server in the action column.
Set mode	Sets maintenance mode on the selected servers. Choose a maintenance mode and click Set mode. By setting maintenance mode, you can perform diagnostics, maintenance, or tuning on the server without disrupting incoming traffic to the server in a production environment. Maintenance mode Serves the remaining requests on the server. Any requests that have an open session on the server are routed to the server until the session ends or times out. After all requests are completed, the server is moved to maintenance mode. Any new requests are routed to servers that are not in maintenance mode. Maintenance mode - break affinity Moves the selected servers into maintenance mode, and breaks HTTP and SIP request affinity to the servers. Maintenance mode - immediate stop Immediately moves the server to maintenance mode, without serving the remaining requests on the server. Normal Disables maintenance mode for the selected servers.

Name

Specifies a name for the middleware server. The name for a middleware server must be unique in the cell.

Node

The node that the middleware server is on.

The actions in the drop-down menu depend on the type of server. For example, Generate and propagate plugin are only valid for Web servers.

Cluster Name

Specifies the name of the cluster to which the server belongs.

Status

Indicates whether the middleware server is started, stopped, or unavailable.

Table 2. Middleware server status
Icon	Action	Description
	Started	Server is running.
	Partial Start	Server is in the process of changing from a Stopped state to a Started state. Server is starting to run but is not fully running yet.
	Stopped	Server is not running.
	Partial Stop	Server is in the process of changing from a Started state to a Stopped state.
	Unavailable	Status cannot be determined.
	Not applicable	Server does not provide information as to whether it is running.

Maintenance mode

Specifies the maintenance mode status of the server.

Table 3. Middleware server maintenance mode status
Icon	Action	Description
	Maintenance mode	The server is in maintenance mode, and is no longer serving requests, so you can perform administrative actions on this server. While in maintenance mode, the server can be either started or stopped. When the node is started and in maintenance mode, the on demand router does not route HTTP or SIP traffic to the server.
	Normal mode	The server is serving requests.

Version

Specifies the version number for WebSphere Network Deployment.

Type

Specifies the middleware server type. Options include application server, generic server, on demand router, proxy server, apache server, and web server. Other server types include PHP, Apache Tomcat, BEA Weblogic, JBoss, WebSphere Application Server Community Edition, External WebSphere Application Servers, Liberty Profile Servers, WebSphere MQ Servers, and Custom HTTP.

Action

Specifies a specific action to perform on the selected middleware server.

You can perform the following actions:

Note: Actions are not available for the other server types. Actions are only available for web servers.

Table 4. Middleware server actions
Action	Server type
Generate plug-in	Web
Propagate plug-in	Web