|
Configuration
of ProcessPoolTest
The default parameters associated with this test are as follows:
- In the PROCESS text box, enter a comma separated list of names:pattern
pairs which identify the process(es) associated with the server being
considered. processName is a string that will be used for display purposes
only. processPattern is an expression of the form - *expr* or expr or
*expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading '*'
signifies any number of leading characters, while a trailing '*' signifies
any number of trailing characters. For example, for an iPlanet application
server (Nas_server), there are three processes named kcs, kjs, and kxs
associated with the application server. For this server type, in the
PROCESS text box, enter "kcsProcess:*kcs*, kjsProcess:*kjs*, kxsProcess:*kxs*,
where * denotes zero or more characters. Other special characters such
as slashes (\) can also be used while defining the process pattern.
For example, if a servers root directory is /home/egurkha/apache and
the server executable named httpd exists in the bin directory, then,
the process pattern is */home/egurkha/apache/bin/httpd*.
To
determine the process pattern to use for your application, on
Windows environments, look for the process name(s) in the Task
Manager -> Processes selection. To determine the process pattern
to use on Unix environments, use the ps command (e.g., the command
"ps -e -o pid,args" can be used to determine the processes
running on the target system; from this, choose the processes of
interest to you).
-
In the PIDFILE text
box, enter a comma separated list of process names:paths to pid files
that contain the process ids of the processes that need to be
monitored. processName
is a string that will be used for display purposes only. For
example, this text box could contain, WebServer:/tmp/pid_file1,
Apache:/tmp/pid_file2, where pid_file1 and pid_file2 are the files
containing the process ids. Note: Each
pid file can contain only one pid.
-
If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.
-
Once the necessary
values have been provided, clicking on the UPDATE button will
register the changes made.
When changing the
configuration for specific servers, a * beside the text box
corresponding to the parameter signifies that these values have to be
manually configured by the user. The parameter values that require to
be configured will typically be prefixed with a $ or contain a
series of *. A value of "none"
in the parameter value indicates that the corresponding parameter
value can be changed if required.
|