InfoCenter Home >
6: Administer applications >
6.6: Tools and resources quick reference >
6.6.3: Administering application servers >
6.6.3.0: Application server properties

6.6.3.0: Application server properties

Application Server Name
Specifies a name for the application server. The name must unique within the node (physical machine) containing the application server.

Command line arguments
Specifies the command line arguments to pass to the Java virtual machine (JVM) that starts the application server process.

You can find the most updated information about the command line arguments by typing

java
at a command prompt. In case that is not convenient, check this summary list of the arguments.

You might also add a ServiceInitializer parameter or set the server socket queue depth using com.ibm.CORBA.ServerSocketQueueDepth, as described in the administrative server properties.

Current state
Indicates the state the application server is currently in. The next time it is started, it will try to change to its desired state setting.
Debug enabled
Specifies whether the server is running in debugging mode.

When the property is set, the application server will start with the java_g -debug argument, which is necessary to allow the Distributed Debugger, or any Java debugger, to attach to the application server.

Selecting this setting is necessary, but not sufficient, for using the Debugger to debug code running on this application server. You must also select the "Object Level Trace enabled" setting and perform some other steps. See the full InfoCenter for more information.

Desired state
Indicates the state the application server should have the next time it is started.
Environment
Specifies environment variables, and their values, to be used by the application server.

To set variables, click the Environment field to display a dialog box. In the box, enter variable names and values, clicking the Add button after each one.

The value of this property is a list of strings of the form "name=value"

Tips:

Circumstance Property name Property value
When a CMP bean must access DB2 for application data and receives a "No suitable driver" exception, set ... PATH x:\SQLLIB\BIN where x is where DB2 is installed

EPM Specification
Executable in use
Indicates the executable (Java class) representing the application server.

Group ID
Specifies the name of the operating system group under which to run the server.

Note that the operating system group must exist on the machine where the server is to run before the server is started. This group must be assigned the necessary operating system privileges for performing operations such as creating output files on the local file system. Additional information specific to operating system

Group ID in use
Indicates the group ID now in use by the server. Additional information specific to operating system

Maximum startup attempts
Specifies the number of times to try to start the server before discontinuing attempts.
  • Legal Values: Any positive integer

Name
Indicates a name for the application server. The name must unique within the node (physical machine) containing the application server.
Node
Indicates the administrative node on which the application server resides.

Object Level Tracing enabled
Specifies whether Object Level Trace (OLT) and the Distributed Debugger are enabled.

If this option is deselected, this server will not send any trace or debug information to the OLT and the Debugger client interfaces.

Selecting this setting is necessary, but not sufficient, for using OLT/the Debugger to trace or debug code running on this application server.

Parent
Specifies the node on which the application server will reside. Though it is not indicated as such, this property is required.

Ping initial timeout
Specifies the maximum time in seconds after the server starts before a successful ping must occur. After this time elapses, the administrative server attempts to restart the server.

Ping interval
Specifies the frequency of communication attempts between the server and the administrative server to ensure that the server is running.

Adjust this value based on your requirements for restarting failed servers. Decreasing the value detects failures sooner; increasing the value reduces the frequency of pings and thus reduces system overhead.

Ping timeout
Specifies the maximum amount of time in seconds that can elapse after the last successful ping before the administrative server assumes the server has failed.

Adjust this value based on your requirements for restarting failed servers. Decreasing the value shortens the length of time that a server can be down before any attempt to restart it.

Process ID
Indicates the operating system process ID of the server.

Process priority
Specifies the operating system process priority under which to run the server. The lower the number, the greater the importance of the process. Additional information specific to operating system
  • Legal Values: Any positive integer

Process priority in use
Indicates the current process priority of the server. Additional information specific to operating system

Security enabled
Specifies whether to enable WebSphere Application Server security for the application server.

Security enabled in use
Specifies whether WebSphere Application Server security is currently enabled for the application server.

Standard error
Specifies the standard error stream for the operating system.

If the value of this property is set to the null string (""), the stream is set to the null device.

If this property is set to a relative path name, the path is relative to the server's working directory. Any class of trace output can be redirected to this file. By default, the output of the fatal, error, and audit trace classes is sent to this file.

Additional information specific to operating system

  • Default: The file stderr.txt in the server's working directory

Standard error in use
Indicates the standard error stream now in use by the server.

Additional information specific to operating system

Standard input
Specifies the standard input stream for the operating system.

If this property is set to the null string (""), the stream is set to the null device.

If this property is set to a relative path name, the path is relative to the server's working directory.

Additional information specific to operating system

Standard input in use
Indicates the standard input stream now in use by the server.

Additional information specific to operating system

Standard output
Specifies the standard output stream for the operating system.

If this property is set to the null string (""), the stream is set to the null device.

If this property is set to a relative path name, the path is relative to the server's working directory.

Additional information specific to operating system

  • Default: The file stdout.txt in the server's working directory.

Standard output in use
Indicates the standard output stream now in use by the server.

Additional information specific to operating system

Start Time
Indicates the time at which the server was most recently started.

State
Indicates the state the application server is currently in.

Thread Pool Size
Specifies the starting size of the thread pool for the application server.

Each application server has its own thread pool or cache from which it uses threads to process remote method invocations.

The size of a server's thread pool varies throughout the server's lifetime. Threads are created when needed and destroyed when there are too many idle threads.

Trace specification
Specifies the initial trace mask value to use for the server.

A trace mask defines which components are to be traced and allows you control how much trace information is generated.

The format of this property (and tracing in general) is described in the trace properties help.

Trace specification in use

Indicates the trace specification now in use by the application server.
Trace output file
Specifies the file to which to write tracing information.

Trace output file in use
Indicates the trace output file currently in use.

Transaction inactivity timeout
Specifies the number of milliseconds a transaction can remain inactive before it is aborted.

Transaction timeout
Specifies the number of seconds to allow a transaction to proceed before aborting it because it is taking too much time.

Umask
Specifies an octal value that sets the operating system's file creation mask for the server.

The file creation mask specifies permissions that cannot initially be granted for new files. When a new file is created, the system refuses to grant the permissions specified in the file creation mask.

For example, a mask of 022 prevents the granting of the write permission to members of the group that own the file and to all other users who do not own the file.

A mask of 022 allows the owner to be granted all permissions; in other words, it leaves the owner's permissions the way the system specifies them.

If the system would otherwise create a file with privilege values of 777 (read, write, and execute permissions for owner, group, and other), a file creation mask of 022 causes it to create the file with 755 (all permissions for the owner, but only read and execute permissions for group and other).

  • Legal Values: An integer in the octal range 0 through 0777

Umask in use
Indicates the mask now in use by the server.

User ID
Specifies the name of the operating system user under which to run the server.

Note that the operating system user must exist on the machine where the server is to run before the server is started. This user must be assigned the necessary operating system privileges for performing operations such as creating output files on the local file system.

  • Legal Values: A string of 8 or fewer characters
  • Default: The ID used by the administrative server

User ID in use
The user ID now in use by the server.

Working directory
Specifies the local directory in which to run the server.

This directory is used to determine the locations of input and output files with relative path names.

After you start a server, it is recommended that you do not change the server's working directory.

Passivated enterprise beans are placed in the current working directory of the application server on which the beans are running. Make sure the working directory is a known directory under the root directory of the Application Server product.

Workload management selection policy
Specifies the selection method to be used by clients in deciding which server to bind to.

Go to previous article: Administering application servers Go to next article: Administering application servers with the Java administrative console

 

 
Go to previous article: Administering application servers Go to next article: Administering application servers with the Java administrative console