The following table describes the available PPM properties:
Property
What it does
Max processes
Sets the maximum number of VWJs server processes that the PPM can
run at the same time. If all VWJs processes are processing other
requests and the maximum number of VWJs processes is running, PPM
queues new incoming requests and waits for an available process.
The default is 5 processes.
If you lower the current setting for this option and the number
of current VWJs processes exceeds the new maximum you set, the PPM
removes each VWJs process as soon it completes the current request,
until the number of processes equals the new maximum.
The main purpose of having multiple VWJs processes is to take
advantage of multiple processors. Excessive VWJs will be unused
and/or waste resources. Each VWJs process consumes approximately
6 to 8 MB of memory on the Process Engine.
FileNet recommends 1.5 to 2 VWJs processes per CPU. For example,
a single-CPU system should configure PPM for 2 VWJs processes; a
quad-CPU system should configure 6 to 8 VWJs processes.
In Process Task Manager,
this property is available on the PPM General
tab.
Registry port
The RMI port that the PPM runs on. The default port is 32771; it
is only necessary to specify this parameter if the PPM will run
on a different port. See About
the RMI registry for more information about registry ports.
NOTE On
Solaris-based systems, you must take additional steps in order to use port 32771.
See Eliminating port 32771 conflicts
for instructions.
In Process Task Manager,
this property is available on the PPM General
tab.
Return Port
The port number on which the remote PPM object receives calls.
If the return port is 0 (the default value), an anonymous port is
chosen. It is only necessary to enter a value other than 0 if you
are also specifying the Local Host parameter to accommodate a firewall
or Network Address Translator (NAT). See Local
Host below for further details.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
RMI Backlog
The maximum queue length for incoming RMI connection indications
(that is, requests to connect). If a connection indication arrives
when the queue is full, the connection is refused. The default value
is 100.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
Local Host
The fully qualified name of the Process Engine.
NOTE This
parameter is optional unless the Application Engine or web server
or Process Engine
resides behind a firewall or Network Address Translator (NAT). In
such configurations, you may be denied access when you start the
PPM. To resolve this problem, you must enter both the Local
Host and the Return Port
when starting the PPM.
CAUTION RMI
requests to a server with an underscore (_) in the DNS name fail due to a limitation
in JRE 1.4 and greater. If your server has a name containing an underscore, you
must use the IP address or localhost if appropriate.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
VWJs Delay
Automatically starts the total number of VWJs processes specified
in "Max processes" and indicates the delay, in seconds,
between starting each process.
Setting the value to 0 or leaving it blank turns off the automatic
startup of the maximum number of VWJs processes. In this case, a
VWJs process starts whenever the PPM receives a request, until the
maximum number of VWJs processes is reached.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
PPM debugging
Turns on/off debugging for the PPM processes, including all calls
to the RMI registry. Turning this option on creates trace files
called vwppm.trc and vwrmi.log
in the directory from which you start the PPM. New information always
appends to the file. By default, PPM debugging is turned off. You
can periodically archive and delete these files if disk space is
an issue.
The parameter /d turns on/off
debugging for the PPM processes, including all calls to the RMI
registry. Turning this option on creates trace files called vwppm.trc
and vwrmi.log in the directory from
which you start the PPM. New information always appends to the file.
By default, PPM debugging is turned off.
The parameter /s turns on/off
debugging for the VWJs processes. Changing this option affects only
those processes started after you make the change. If you want to
change the debugging setting for existing processes, you must stop
and restart the PPM. If you want to ensure that debugging is on
for all processes, you must stop and restart the PPM, and then immediately
turn on debugging. Turning this option on creates two trace files
called jVWServer#.trc and
jVWServer#.exc, where #
is the number of the server process. The files are created in the
directory from which you start the PPM. New information always appends
to the files. By default, server debugging is turned off.
You can periodically archive and delete these files if disk space
is an issue.
NOTE Do
not turn on debugging unless instructed to by a FileNet support
representative.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
Server debugging
Turns on/off debugging for the VWJs processes. Changing this option
affects only those processes started after you make the change.
If you want to change the debugging setting for existing processes,
you must stop and restart the PPM. If you want to ensure that debugging
is on for all processes, you must stop and restart the PPM, and
then immediately turn on debugging.
Turning this option on creates two trace files called jVWServer#.trc
and jVWServer#.exc, where
# is the number of the server process. The files are created in
the directory from which you start the PPM. New information always
appends to the files. By default, server debugging is turned off.
You can periodically archive and delete these files if disk space
is an issue.
NOTE Do
not turn on debugging unless it is recommended by a FileNet support
representative.
In Process Task Manager,
this property is available on the PPM Advanced
tab.
java_path
The full path to the java executable. The working directory is
the default. This parameter applies only to starting the PPM from
the command line.
pwjar_path
The full path to the pw.jar file. The default location is <drive>\FNSW\BIN\pw.jar,
where <drive> is the drive where the software is installed.
The path and filename must be enclosed in quotes if they contain
any spaces. This parameter applies only to startting the PPM from
the command line.
Enable automatic
startup
Enables automatic startup of the associated process when Process Task Manager
is started from a script. See Enabling
automatic startup for more information.
In Process Task Manager,
this property is available on the PPM General
tab.
The following informational fields are available on the PPM node.
Average calls per minute
The average number of API calls per minute. You can reset the start
time used tor this calculation to the current time by pressing the
Reset button below the PPM tabs.
Average calls per second
The average number of API calls per second, located on the General
tab. You can reset the start time used for this calculation to the
current time by pressing the Reset button below the PPM tabs.
Server processes in use
The number of VWJs processes that are currently servicing a request,
located on the General tab. Note that this may be less than the
total number of currently running VWJs processes.