WAS v8.5 > Reference > Sets

Application server settings page

A cluster member template is the set of application server configuration settings assigned to new members of a cluster.

IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.

To view this dmgr console page, click...

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.


Name

Logical name for the server. Server names must be unique within a node. However, for multiple nodes within a cluster, you 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 v8.5 uses the server name for administrative actions, such as referencing the server in scripting.
Information Value
Default server1


Run in development mode

Enabling this option might reduce application server 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.

Specifies to use the -Xverify and -Xquickstart JVM properties as startup values. Before selecting this option, add the -Xverify and -Xquickstart properties as generic arguments to the JVM configuration.

If selected, then you must save the configuration, and restart the server before this configuration change takes effect.

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


Parallel start

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

Specifies 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 dmgr console, click Applications > Application Types > WebSphere enterprise applications > 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, you might specify a startup order value of 1 for the most important application, and a value of 2 for the next most important application. You 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.
Information Value
Data type Integer
Default 1
Range 0 - 2147483647


Start components as needed

Select this property if you 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, deployed on the server, are of the same type. For example, using this option works better if all of the applications are web applications that use servlets, and JSP. This option works less effectively if the applications use servlets, JSPs and 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 you are running in conjunction with this product, support this functionality.


Access to internal server classes

Whether the server can run in Restrict or Allow mode.

The Restrict mode is a diagnostic mode used to help determine the suitability of applications for migration. This mode determines whether internal application server classes are accessed. The use of these internal classes might preclude the successful operation of these applications in future releases. However, the Restrict mode is not intended to exclude all classes from general use even if the classes might change. Some classes that might change are unrestricted in order to enable correct operation of the application server. The Restrict mode is not intended to provide complete isolation between an application and application server internal classes. Do not use the Restrict mode in a production runtime environment; use the results for guidance only.

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 the product class loaders is Parent first.

This field only applies if you set the Class loader policy field to S*ingle.

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

This property is read only. The system automatically generates the value.


Cell name

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

This property is read only.


Node name

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

This property is read only.


State

The runtime start state for this server.

This property is read only.


Product information

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

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


Subtopics


Related concepts:

Class loaders


Related


Administer application servers
Troubleshoot applications with HPEL


Reference:

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


+

Search Tips   |   Advanced Search