PSAPPSRV Options

The PSAPPSRV server process performs the functional requests, such as building and loading panel groups. It also provides the in-memory-caching feature for PeopleTools objects on the application server. Each server process maintains its own cache.

Enter the minimum number of application server instances that start when you boot the domain. There's always at least this number of instances running. This translates to the PSAPPSRV server's -m (min) parameter in the UBB file.

Enter the maximum number of server instances that can be started. This translates to the PSAPPSRV server's -M (Max) parameter in the UBB file.

Enter the number of seconds that a PSAPPSRV waits for a service request, such as MgrGetObj or PprLoad, to complete before timing out. Service timeouts are recorded in the TUXLOG and APPSRV.LOG. In the event of a timeout, PSAPPSRV is terminated and a replacement process is started by Tuxedo.

Enter the number of service requests that each server has carried out before being terminated (intentionally) and then immediately restarting. Servers must be intermittently recycled to clear buffer areas. The time that is required to recycle a server is negligible, occurring in milliseconds. The recycle count does not translate into a native Tuxedo parameter in the PSAPPSRV.UBB file. Instead, the value is stored in memory and is managed by a PeopleSoft server.

Note: The default value for the small, medium, and large templates is 10,000.

Note: Serial Recycle or Dynamic Recycle parameters can delay the recycle even if the number of the requests is greater than or equal to the Recycle Count value.

This parameter can be set at the individual server process level or the domain level.

See ProcessRestartMemoryLimit.

Enter a number greater than 0 to enable dynamic server processes to restart for service failures. To disable this option, enter 0. The default is 2. The value that you enter is the number of consecutive service failures that will cause a recycle of the server process. This is a catchall error handling routine that enables PSAPPSRV, PSQCKSRV, and PSAMSRV to terminate themselves if they receive multiple, consecutive, fatal error messages from service routines. Such errors should not occur consecutively, but if they do, the server process must be recycled or cleansed. A retry message appears on the client browser when this occurs.

The default is 5000 (K). Enter the maximum memory that is used by the server to store fetched rows for a transaction before sending the result set back to a client. If the memory limit is exceeded, the client receives the rows retrieved with a memory buffer exceeded warning. You should use the default value. PSAPPSRV supports nonconversational transactions, so this parameter provides a way to balance high-volume throughput with the needs of users working with large volumes of data. A value of 0 means unlimited memory is used. The memory is not preallocated—it is acquired as needed for each transaction.

Enter 1 (the default) to enable automatic prompting on lookup pages. When the user selects the prompt lookup button, the application server automatically returns all values for that field, up to 300 rows. If necessary, the user can refine the search further by entering partial data in the Search By field.

Enter 0 to require the user to enter a partial value before the automatic prompt list appears.

You can add this parameter, if needed, manually to the [PSAPPSRV] section of the PSAPPSRV.CFG file. AutoLoad JVM controls whether the JVM gets loaded automatically when the domain boots.

By default, domain behavior reflects a setting of AutoLoad JVM=0 (not enabled).

If you have configured EnablePPM Agent=1, then JVM will be loaded at the domain boot time. If you have configured EnablePPM Agent=0, then to load JVM when the domain boots, you need add AutoLoad JVM=1 to the [PSAPPSRV] section of the PSAPPSRV.CFG file.

When serial recycling is enabled for a server process, the system recycles server processes of that type within a domain on a serial basis–one after another–to allow processing to continue uninterrupted. By default, the domain behavior reflects Serial Recycle=Y (enabled).

When Serial Recycle=Y for PSAPPSRV, for example, then only one PSAPPSRV process will recycle during the recycle time of 60 seconds when the Recycle Count limit is reached. Then the next PSAPPSRV will recycle.

When serial recycling is not enabled, all the server processes of that type recycle simultaneously when the Recycle Count limit is reached, which can cause throughput to pause.

Serial recycling applies to these server process types: PSAPPSRV, PSQCKSRV, PSQRYSRV, and the Integration Broker server processes.

To disable serial recycling, manually add the Serial Recycle parameter, and assign the value N. For example:

Serial Recycle=N

The recycle time is 60 seconds.

The Integration Broker messaging system uses the Tuxedo queue size indicated in the application server domain section of PSADMIN to determine when the Tuxedo queue size has reached its maximum.

For more details on this setting, seeSetting the Oracle Tuxedo Queue Size.