Application server settings

An application server is a server which provides services required to run enterprise applications. Use this page to view or change the settings of an application server instance.

To view this administrative console page, click Servers > Application Servers > server_name.

On the Configuration tab, you can edit fields. On the Runtime tab, you can look at read-only information. The Runtime tab is available only when the server is running.

Configuration tab

Name

Specifies a logical name for the server. Server names must be unique within a node. However, for multiple nodes within a cluster, you may have different servers with the same server name as long as the server and node pair are unique.

For example, a server named server1 in a node named node1 in the same cluster with a server named server1 in a node named node2 is allowed. Configuring two servers named server1 in the same node is not allowed. WebSphere Application Server uses the server name for administrative actions, such as referencing the server in scripting.

Data type String
Default server1

Parallel start

Select this field to start the server on multiple threads. This might shorten the startup time.

That you want the server components, services, and applications to start in parallel rather than sequentially.

The default setting for this option is true, which indicates that the server be started using multiple threads. Setting this option to false specifies that the server will not be started in using multiple threads (which may lengthen startup time).

Note that the order in which the applications start depends on the weights you assigned to each them. Applications that have the same weight are started in parallel. You set an application's weight with the Starting weight option on the Applications > Enterprise Applications > application_name page of the Administrative Console. For more information about the Starting weight option, see Enterprise application settings.

Data type Boolean
Default true

Class loader policy

Select whether there is a single class loader to load all applications or a different class loader for each application.

Class loading mode

Whether the class loader should search in the parent class loader or in the application class loader first to load a class. The standard for Developer Kit class loaders and WebSphere Application Server class loaders is Parent first.

If you select Parent last, your application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or linkage errors if you have mixed use of overridden classes and non-overridden classes.

Runtime tab

Process Id

The native operating system's process ID for this server.

The process ID property is read only. The system automatically generates the value.

Cell name

The name of the cell in which this server is running.

The Cell name property is read only.

Node name

The name of the node in which this server is running.

The Node name property is read only.

State

The run-time execution state for this server.

The State property is read only.

Sub-topics

Ports collection

Custom property collection

Server component collection
Thread pool collection

Related concepts
Application servers
Class loaders

Related tasks
Administering application servers