Application server settings

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

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.

Access to internal server classes

Specifies 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 that might change from general use as certain classes cannot be restricted to enable the proper 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.

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. You cannot change the value that displays 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. 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.

[z/OS] On the z/OS platform, this name is sometimes referred to as the long name.

Data type String
Default server1
Avoid trouble [z/OS] Avoid trouble: [Updated in August 2010] If you are using a global resource serialization (GRS) ring to attach one or more monoplexes to a sysplex environment, the cell name of any servers running in any of the monoplexes must be unique within the entire GRS environment. This requirement means that the cell name of a server running in any of the monoplexes:
  • Must be different than the cell name of any servers running in the sysplex
  • Must be different than the cell name of any servers running in another monoplex that is attached to the sysplex
If you have servers with duplicate cell names within the GRS environment, WebSphere Application Server cannot differentiate between the sysplex cell and the monoplex cell, and treats both servers as part of the same cell, This inaccurate cell association typically causes unpredictable processing results. [Updated in August 2010]
aug2010
gotcha

Short name

[z/OS]

Specifies the short name of the server and must be unique within a cell. This field only applies to the z/OS platform. The short name is also the default z/OS job name and identifies the server to the native facilities of the operating system, such as Workload Manager (WLM), Automatic Restart Manager, SAF (for example, RACF), and started task control.

This field is optional. If you do not specify a value for the short name field, the short name defaults to BBOSnnn, where nnn is the first free number in the cell that can be used to create a unique short name. For example, if default short names are already assigned to two other servers in the cell, the short name BBOS003 will be assigned to this server if you do not specify a short name when you create this server. After the application server is created, you can change this generated short name to a name that conforms to your naming conventions.

The default values for the servant and adjunct jobnames are this short name with either an S, for the servant, or an A, for the adjunct, appended. If you must use an 8-character server short name, the servant and adjunct jobnames become 9-character names. Therefore, you must update the start command arguments for the servant and the adjunct process definitions to use the new 8-character server short name. The topic "Converting a 7-character server short name to 8 characters" describes how to perform this update.

If you specify a short name, the name:
  • Must be one to eight characters in length. By default, the Application Serve assumes you are using a 7-character server short name (JOBNAME). It is recommended that you use a 7-character short name unless your naming standards require an 8-character short name.
  • Must contain only uppercase alphanumeric characters
  • Cannot start with a number.
  • Must be unique in the cell.

Generic short name

[z/OS]

Specifies the generic short name of the server and must be unique within a cell. This field only applies to the z/OS platform. The generic short name for the server becomes either the cluster transition name, if you are creating an unclustered server, or the cluster short name, if you are creating a clustered server.

This field is optional. If you do not specify a value for the generic short name field, the generic short name defaults to BBOCnnn, where nnn is the first free number in the cell that can be used to create a unique generic short name. For example, if default generic short names are already assigned to three other servers in the cell, the generic short name BBOC004 is assigned to this server if you do not specify a generic short name when you create this server.

If you specify a generic short name, the name:
  • Must be one to eight characters in length.
  • Must contain only uppercase alphanumeric characters
  • Cannot start with a number.
  • Must be unique in the cell.

Run in development mode

[z/OS] [AIX HP-UX Linux Solaris Windows]

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.

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

If you select this option, 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 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 them. Applications that have the same weight start in parallel.

To set an application's weight, in the administrative console, click Applications > 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 your 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.

Data type Integer
Default 1
Range 0 - 2147483647

Run in 64 bit JVM mode

[z/OS]

Specifies whether to run the application server in 64-bit mode rather than the default 31-bit mode. If you run the application server in 31-bit mode, the maximum heap size for the deployment manager JVM must be less than 2 gigabytes (GB). Additional virtual storage for customer applications can be obtained by converting the application server to 64-bit mode and increasing the maximum JVM heap size.

If you select this option, you should change the maximum JVM heap size setting to a value that is appropriate for a 64-bit process. For example, you might initially change the maximum heap size for the controller and the servant to 1844m

There is no interdependence between the modes of the servers. Therefore, you can run some of your servers in 31-bit mode and some of your servers in 64-bit mode. However, you should eventually convert all of your servers to 64-bit mode.

See the topic "Running servers in 64-bit mode" for more information on when you should select this option.

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.

This field only applies if you set the Class loader policy field to single.

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.

Initial State

Specifies the initial state of the application server.

The default setting for this option is Started.
Important: Don't set the initial state to Stopped. Application server services may not operate correctly.

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.

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:
  • 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 the product was installed, such as the installation of a specific service level.
  • Product report, for a detailed report of the versions of the product that are installed.
  • PTFs, for a list of all of PTFs that are installed.



Subtopics
[AIX HP-UX Linux Solaris Windows] [iSeries] Thread pool collection
Related concepts
[z/OS] Running servers in 64-bit mode
Class loaders
Related tasks
Administering application servers
[z/OS] Converting a 7-character server short name to 8 characters
Related reference
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
[AIX HP-UX Linux Solaris Windows] [iSeries] IBM service log settings
[AIX HP-UX Linux Solaris Windows] [iSeries] Log and trace settings
Message listener port collection
Object Request Broker service settings
Performance Monitoring Infrastructure settings
Process definition settings
Java virtual machine settings
[AIX HP-UX Linux Solaris Windows] [iSeries] Diagnostic trace service settings
Transaction service settings
Web container settings
Administrative console buttons
Startup behavior settings
Reference topic    

Terms of Use | Feedback

Last updated: Feb 19, 2011 5:25:36 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v610web&product=was-nd-mp&topic=urun_rappsvr
File name: urun_rappsvr.html