WebSphere Application Server Network Deployment, Version 6.0.x   Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
             [TIP: Focusing the table of contents and search results]

Defining application server processes

To enhance the operation of an application server, you can define command-line information for starting or initializing an application server process. Such settings define runtime properties such as the program to run, arguments to run the program, and the working directory.

About this task

A process definition can include characteristics such as Java virtual machine (JVM) settings, standard in, error and output paths, and the user ID and password under which a server runs.

You can define application server processes using the administrative console or the wsadmin tool.

Procedure

  1. In the administrative console, click Servers > Application Servers and click on an application server name. Then, under Server Infrastructure, click Java and Process Management > Process Definition.
  2. On the settings page for a process definition, specify the name of the executable to run, any arguments to pass when the process starts running, and the working directory in which the process will run. Then click OK.
  3. [AIX HP-UX Solaris] Specify process execution statements for starting or initializing a UNIX process.
  4. Specify monitoring policies to track the performance of a process.
  5. Specify process logs to which standard out and standard error streams write. Complete this step if you do not want to use the default file names.
  6. Specify name-value pairs for properties needed by the process definition.
    Important: Each custom property name must be unique. If the same name is used for multiple properties, the process uses the value specified for the first property that has that name.
  7. Optional: Prevent the application server from creating javacore dumps.

    A javacore dump, or a thread dump as it is also called, is one of the primary problem determination documents that an application server creates. Also, the performance impact of creating a javacore dump is usually ignorable. Therefore, in most WebSphere Application Server environments, you should not suppress the creation of a javacore dump.

    In certain circumstances, such as when there are security consideration, you might want to prevent the application server from creating javacore dumps. To disable the javacore dump function:

    1. In the administrative console, click Servers > Application servers > server_name > Java and Process Management > Process Definition > Custom Properties > New
    2. In the Name field enter DISABLE_JAVADUMP and in the Value field, enter true to prevent the application server from creating javacore dumps.
  8. Stop the application server and then restart the server.
  9. Check the application server to ensure that the process definition runs and operates as intended.



Sub-topics
Automatically restarting server processes
Related tasks
Running application servers from a non-root user
Running an application server from a non-root user and the node agent from root
Running an Application Server and node agent from a non-root user
Running the deployment manager with a non-root user ID
Configuring processes using scripting
Task topic    

Terms of Use | Feedback

Last updated: Mar 8, 2007 8:14:28 PM CST
http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/trun_processdef.html

© Copyright IBM Corporation 2002, 2006. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)