Application server settings
To change the settings of an application server instance, from the administrative console page, click...Servers | Application Servers | servername
On the Configuration tab, one 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.
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. WAS uses the server name for administrative actions, such as referencing the server in scripting.
Data type String Default server1
- Run in development mode
Enabling this option may reduce the startup time of an application server. This may include JVM settings such as disabling bytecode verification and reducing JIT compilation costs. Do not enable this setting on production servers. This setting is only available on application servers running WAS v6 and later.
Specifies that you want to use the JVM settings -Xverify and -Xquickstart on startup. After selecting this option, save the configuration and restart the server to activate development mode.
The default setting for this option is false, which indicates that the server will not be started in development mode. Setting this option to true specifies that the server will be started in development mode (with settings that will speed server startup 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 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 > appname 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
Specifies 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.
- 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.
The run-time execution state for this server.
The State property is read only.
Ports collectionCustom property collectionServer component collection
Thread pool collection
Administering application servers
WebSphere is a trademark of the IBM Corporation in the United States, other countries, or both.
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.