Application server settings



Search Tips   |   Advanced Search


An appserver is a server that provides services required to run enterprise apps. A cluster member template is the set of application server settings that are assigned to new members of a cluster.

To configure an appserver or a cluster member template.

Servers | Server Types | WebSphere application servers | server_name

On the Configuration tab, we can change field settings. We can also click Installed applications to view the status of applications that are running on this server. On the Runtime tab, we can view read only information. The Runtime tab is available only when the server is running.


Logical name for the server. Server names must be unique within a node. However, for multiple nodes within a cluster, we might have different servers with the same server name as long as the server and node pair are unique. We cannot change the value that appears in this field.

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. However, we cannot have two servers named server1 in the same node. WAS ND v7.0 uses the server name for admin actions, such as referencing the server in scripting.

Default server1

Run in development mode

Enable this option might reduce appserver start-up time because it changes some of the JVM settings, such as disabling bytecode verification, and reducing just-in-time (JIT) compiler compilation costs. Do not enable this setting on production servers. This setting is only available on an application server that is running in a V6.0 or later cell.

Before selecting this option, add -Xverify and -Xquickstart as generic arguments to the JVM configuration.

For example, change...

${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=${USER_INSTALL_ROOT}/PortalServer/derby -Xgcpolicy:gencon

${WPS_JVM_ARGUMENTS_EXT} -Dderby.system.home=${USER_INSTALL_ROOT}/PortalServer/derby -Xgcpolicy:gencon -Xverify -Xquickstart

If we select this option, then save the configuration, and restart the server before this configuration change takes effect.

The default setting for this option is false, which indicates that the server does not start in development mode. Setting this option to true specifies that the server starts in development mode with settings that decrease server start-up time.

Data type Boolean
Default false

Parallel start

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

Specifies 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 when the server starts, the server components, services, and applications start on multiple threads. Setting this option to false specifies that when the server starts, the server components, services, and applications start on a single thread, which might lengthen start-up time.

The order in which the applications start depends on the weights that you assign to them. Applications that have the same weight start in parallel.

To set the weight of an application, in the admin console, click...

Applications | Application Types | WebSphere enterprise apps | application_name | Startup behavior

...and then specify an appropriate value in the Startup order field.

The more important an application is, the lower the startup order value should be. For example, we might specify a startup order value of 1 for the most important application, and a value of 2 for the next most important application. We might then specify a startup order of 3 for the next four applications because you want all four of those applications to start in parallel.

Data type Integer
Default 1
Range 0 - 2147483647

Start components as needed

Select this property if we want the server components started as they are needed by an application that is running on this server.

When this property is selected, server components are dynamically started as they are needed. When this property is not selected, all of the server components are started during the server startup process. Therefore, selecting this option can improve startup time, and reduce the memory footprint of the server, because fewer components are started during the startup process.

Starting components as they are needed is most effective if all of the applications, that are deployed on the server, are of the same type. For example, using this option works better if all of the applications are Web apps that use servlets, and JSPs. This option works less effectively if the applications use servlets, JSPs and Enterprise Java Beans™ (EJB).

To ensure compatibility with other WebSphere products, the default setting for this option is deselected. Before selecting this option, verify that any other WebSphere products, that we are running in conjunction with this product, support this functionality.

Access to internal server classes

Whether the applications that are running on this server can access multiple server implementation classes.

If we select Allow, then applications can access many of the server implementation classes. If we select Restrict, then applications cannot access multiple server implementation classes. The applications get a ClassNotFoundException error if they attempt to access those classes.

Usually you should select Restrict for this property, because most applications use the supported APIs and do not need to access any of the internal classes. However, if the application requires the use of one or more of the internal server classes, select Allow as the value for this property.

The default value for this property is Allow.

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 searches in the parent class loader or in the application class loader first to load a class. The standard for Developer Kit class loaders and WAS class loaders is Parent first.

This field only applies if we set the Class loader policy field to Single.

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

Process ID

The process ID for this server on the native operating system.

Is read only. The system automatically generates the value.

Cell name

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

Is read only.

Node name

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

Is read only.


The runtime start state for this server.

Is read only.

Product information

This link under Additional properties, displays the product information for the installation of WAS ND. This information includes WAS ND name, ID, version, build date, and build level.

From the Product Information page, we can click on the following links for additional product information:

>Components for a list of all of the components that are installed.
>e-Fixes for a list of all of the service updates that are installed.
>Extensions for a list of the extensions that are installed.
>History report for a detailed report of all installation events that have occurred since WAS was installed such as the installation of a specific service level.
>Product report for a detailed report of the versions of WAS that are installed.
>PTFs for a list of all of PTFs that are installed.


Ports collection
Custom property collection
Server component collection
Thread pool collection


Related concepts

Class loaders


Related tasks

Administer appservers



Object names: What the name string cannot contain
Administration service settings
Class loader collection
Enterprise application collection
Enterprise application settings
Custom service collection
Debugging Service details
EJB container settings
IBM service log settings
Log and trace settings
Message listener port collection
Object Request Broker service settings
Performance Monitoring Infrastructure settings
Process definition settings
Java virtual machine settings
Diagnostic trace service settings
Transaction service settings
Web container settings
Administrative console buttons
Startup behavior settings
Default Java Persistence API settings