Network Deployment (Distributed operating systems), v8.0 > Reference > Sets


Application server settings


Overview

To configure an application server or a cluster member template, from the console...

To view the status of applications on a running appserver...


Settings


Name

Logical name for the server. Must be unique within a node. On different nodes within a cluster, we can use identical server names.


Run in development mode

Enabling disables bytecode verification and reduces just-in-time compiler compilation costs. Do not enable on production servers. Only available on an appserver running in a V6.0 or later cell. An appserver restart is required. Default is false

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


Parallel start

Shorten the startup time by specifying that server components, services, and applications start in parallel rather than sequentially. Default is true.

If set to false, the order in which the applications start depends on the assigned weights. Apps with the same weight start in parallel. To set the weight of an application

Important apps should have low values.

Default: 1
Range: 0 - 2147483647


Start components as needed

Have 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.

Start 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 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 that you can use 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. Read only.


Node name

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


State

The runtime start state for this server. Read only.


Product information

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

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


Related

Ports collection
Custom property collection
Server component collection
Class loaders
Administer application servers
Use HPEL to troubleshoot applications
Object names: What the name string cannot contain
Administration service settings
Class loader collection
Enterprise application collection
Enterprise application settings
Custom service collection
Debug Service details
EJB container settings
IBM service log settings
Log and trace settings
Message listener port collection
ORB service settings
PMI settings
Process definition settings
Java virtual machine settings
Thread pool collection
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