Application server settings

Use this page to view or change the settings of an appserver instance.

To view this administrative console page, click...

Servers | Application Servers | server

The Configuration tab provides editable fields and the Runtime tab provides read-only information. The Runtime tab is available only when the server is running.

 

Configuration tab

Name	Specifies a logical name for the server. Server names must be unique within a node. Data type String Default server
Initial State	Specifies the component execution state requested when the server is first started. Data type String Default Started Note that The default setting for Initial State is Started. It is important to note that if you change the Initial State setting for this subcomponent to Stopped, and then start its associated server, this subcomponent will remain in the Stopped state. For example, if you set the Initial State property of the Application Server subcomponent to Stopped, and then start its associated server, only the server and other services such as administration, naming, and security will start. The application services, such as the Web container, EJB container, and applications, will not start. If you are using clusters, note also that the Initial State property is not intended to be used to control the state of individual servers in the cluster at the time the cluster is started. It is intended only as a way to control the state of the Application Server subcomponent of a server. It is best to start and stop the individual servers of a cluster using the Server options of the Administrative Console or command line commands startServer(and stopServer).
Application Class loader Policy	Specifies whether to use a single class loader to load all applications or to use a different class loader for each application. The options are SINGLE and MULTIPLE. The default is to use a separate class loader for each application (MULTIPLE). Data type String Default MULTIPLE
Application Classloading 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 class loaders is PARENT_FIRST. By specifying PARENT_LAST, your application can override classes contained in the parent class loader, but this action can potentially result in ClassCastException or LinkageErrors if you have mixed use of overridden classes and non-overridden classes. The options are PARENT_FIRST and PARENT_LAST. The default is to search in the parent class loader before searching in the application class loader to load a class. Data type String Default PARENT_FIRST

Runtime tab

Process ID	Specifies a string identifying the process. Data type String
Cell Name	Name of the cell for the appserver. Data type String Default host_nameNetwork
Node Name	Name of the node for the appserver. Data type String
State	Indicates whether the appserver is started or stopped. Data type String Default Started