This chapter describes all of the configuration options that are related to an application server domain. Generally, the documentation reflects the order in which the configuration sections appear in the PSADMIN interface or the PSAPPSRV.CFG file.
This chapter discusses:
Workstation listener options.
BEA Jolt listener options.
BEA Jolt relay adapter options.
PeopleCode Debugger options.
Remote call options.
Integration Broker server processes.
Simple Mail Transfer Protocol (SMTP) settings.
Interface driver options.
PeopleSoft Integration Broker options.
Select server process options.
Note. The application server dynamically spawns server processes according to the volume of transaction requests. There is no explicit parameter that you must set to enable spawning. In the following configuration section descriptions, some servers enable you to specify a minimum and maximum number of server processes. To enable spawning, the maximum value must exceed the minimum value by an increment of at least one. As needed, the application server spawns server processes up to the maximum value. As the volume of transactions decreases, the number of spawned server processes decreases, or decays, until the minimum value is reached.
Set database sign-in values in the Startup section.
Enter the PeopleSoft database name, such as FSDMO80 or HRDMO80. This parameter is case sensitive.
Enter the PeopleSoft database type, such as DB2ODBC, DB2UNIX, INFORMIX, MICROSFT, ORACLE, or SYBASE. If you enter an invalid database type, PSADMIN prompts you with a valid list.
Enter the PeopleSoft user ID that is authorized to start the application server. For the application server to boot, the appropriate user ID with the correct authorizations must be assigned to this parameter. This is the ID that the application server passes to the database for authentication and connection. The user ID that you enter here is not related to the actual user (administrator) that carries out the boot command.
The Can Start Application Server permission must be set in the permission list. The authorization to start an application server does not (directly or indirectly) grant any authorizations or privileges beyond the ability to start the application server. Each user who attempts to sign in enters a unique user ID and password, which the application server uses to authenticate each user.
Setting General Permissions
Enter the password that is used by the specified user ID that will gain access to the database. The value that you enter must be specified in uppercase to simplify administration of the system.
Required for all database platforms. Enter the database-level ID that the PeopleSoft system uses to make the initial connection to the database. This user name must have authority to select from PSACCESPRFL, PSLOCK, PSOPRDEFN, and PSSTATUS.
Enter the password for the connect ID. For instance, this might be the UNIX user's password (either uppercase or lowercase).
Required for Sybase and Informix. Enter the name of the server on which the PeopleSoft database is installed. This value is case sensitive.
Use the Database Options section to specify environment variables that may improve the performance of the system. These options do not apply to every database.
Enter a Transmission Control Protocol (TCP) packet size. The minimum value is 512 and the maximum value is 65538. The default packet size is 512. If you change the packet size, make the corresponding changes to the Sybase database server.
See Your Sybase documentation.
Use this option to enable a batch program to initiate a local connection to a PeopleSoft database that is running on the same machine. You should use this option for all PeopleSoft Process Scheduler (batch) and application server configurations that are local (on the same server) to the PeopleSoft Oracle instance. This type of connection enables batch processes to complete significantly quicker. Enter 1 to enable this option, and enter 0 to disable it.
Note. Using the local Oracle connection disables the Query Kill function.
Required for database-level auditing. How this works varies slightly, depending on the platform. Use this option to view more information regarding the clients that are connected to a database server through the application server. For instance, with this enabled, you can view the client machine name or user ID that is associated with a particular connection. Without this option enabled, all connections appear somewhat anonymously, as in PSFT or APPSERV.
The default value is 1 (enabled). Enter 0 to disable it.
Note. This parameter isn't supported on Informix or DB2 LUW platforms.
This parameter enables or disables the inclusion of the Oracle FIRST_ROWS hint on PeopleSoft search pages that use the %First_Rows meta-SQL variable.
For certain SQL constructs, the use of the FIRST_ROWS hint can severely degrade performance to an unacceptable degree. This performance reduction occurs primarily on search pages that are ultimately based on views with multi-table joins.
Specify a value of 1 to apply this parameter and disable the FIRST_ROWS hint. SQL statements generated by search page PeopleCode that includes the %First_Rows meta-SQL variable won't contain FIRST_ROWS.
The default value of this parameter is 0, which enables SQL containing the FIRST_ROWS hint to be generated.
Use the Security section to set an additional layer to the sign-in process.
Use this option to set an additional level of authorization-checking to be performed at the database level. Enter 1 to enable this option, and enter 0 to disable it.
With this option disabled, if a PeopleSoft user attempts to connect to an application server, the application server ensures that the user's PeopleSoft user ID and password exist on PSOPRDEFN. If it does not exist, the request to connect fails. This is PeopleTools-level authentication.
With this option enabled, the application server first attempts to connect to the database by using the user ID and password as part of the database connection string. If the authorization is successful, it disconnects, and then the normal PeopleSoft sign-in procedure occurs.
With this option enabled, to connect successfully to the database, the user must be defined on either the operating system or the database and within PeopleSoft.
Note. For DB2 z/OS (MVS), the user ID and password must be defined as z/OS user logon IDs.
The workstation listener is the component to which PeopleSoft native Windows clients send BEA Tuxedo messages.
%PS_MACH% resolves automatically to the machine name that PSADMIN obtains by using a system application programming interface (API) call. You can also specify the machine's Internet Protocol (IP) address (dotted notation) or its resolvable name (domain name server [DNS] name).
You should not change this value except in the following rare cases. If you are configuring files to run an application server on another machine (that is, you plan to copy PSAPPSRV.CFG and PSAPPSRV.UBB to a domain on another machine), you must overlay %PS_MACH% with the other machine's name.
Enter the 4-digit port number to assign to the WSL. Port numbers are arbitrary numbers between 1000 and 64 K and must not already be in use by another service. The default value is 7000.
Use this option to enable the encryption of data messages between client workstations and the application server. Specify one of the following values:
0 — No encryption.
Important! This is the default value.
40 — 40-bit encryption.
128 — 128-bit encryption.
Note. Because this is a dynamic parameter, you must modify it by selecting Custom Configuration on the Quick-Configure menu, and reboot the application server domain for it to take effect.
Enter the number of workstation handlers (WSHs) to be started at boot time. The default for small and large application server configuration templates are 1 and 10, respectively.
Enter the maximum number of WSHs that can be started for a domain. If the Min Handlers value equals the Max Handlers value, BEA Tuxedo does not automatically spawn incremental WSHs.
Enter the maximum number of client workstation connections that each WSH can manage. Each WSH allows up to around 60 client connections. Numbers vary depending upon the resources of the server. In most cases, you should decrease the default as opposed to increasing it. The default is 40.
Enter the amount of time, in minutes, that a client connection can remain idle (no work requested) before BEA Tuxedo terminates the client connection. Client disconnects are transparent to a client, and a user just clicks the mouse to cause a reconnection. The default value for this setting is 60 minutes.
This value, when multiplied by SCANUNIT (a UBB parameter value that is defined in the PSAPPSRV.UBB file) specifies the amount of time, in seconds, that BEA Tuxedo allows for a client connection request to bind to a WSH before terminating the connection attempt.
Enter the minimum length of a data message for which the application server initiates data compression. While compression results in favorable performance gains for transactions over a wide area network (WAN), testing reveals that compression can degrade performance slightly over a local area network (LAN) due to the compression and decompression overhead.
You should use the default threshold of 5000, which sets a balance between WAN and LAN environments. This means that only network request and response messages over 5000 bytes are compressed, and those 5000 and under are uncompressed. If you support both WAN and LAN users, you can configure a hybrid environment by configuring two application servers: one to support WAN users (with compression set to 100) and another to support LAN users (with compression set to 100000, effectively turning compression off).
Use this section to configure PeopleSoft Internet Architecture connections. The BEA Jolt listener enables BEA Tuxedo to exchange messages with the web server.
See the equivalent parameter for the workstation listener.
Enter the port number that is used for the BEA Jolt server listener (JSL). This value can be any port number that is not already in use by another service on the machine that runs the application server domain. The port number is not used unless you answer Yes to the prompt that asks whether you want to start BEA Jolt.
Use this option to enable the encryption of data messages between client workstations and the web server. Specify one of the following values:
0 — No encryption.
Important! This is the default value. Incoming Jolt requests from the web server (portal, PIA, and Integration Broker) are not encrypted.
40 — 40-bit encryption.
128 — 128-bit encryption.
Note. Because this is a dynamic parameter, you must modify it by selecting Custom Configuration on the Quick-Configure menu, and reboot the application server domain for it to take effect.
Enter the number of BEA Jolt server handlers (JSH) to be started at boot time. Each JSH multiplexes up to 50 connections.
Enter the maximum number of JSHs.
Note. JSHs spawn by using successive port numbers starting at the port number for the JSL in the PSAPPSRV.CFG file. Make sure that the additional ports are free before configuring spawning.
Enter the maximum number of client connections that each JSH can manage.
Enter the amount of time, in minutes, that a client connection can remain idle (no work requested) before BEA Tuxedo terminates the client connection. Client disconnects are transparent to a client, and a user just clicks the mouse to cause a reconnection. The default value for this setting is 10 minutes.
See the equivalent parameter for the workstation listener.
Enter one of these options to control the allowed connection modes from clients:
RETAINED: The network connection is retained for the full duration of a session.
RECONNECT: The client establishes and brings down a connection when an idle timeout is reached and reconnects for multiple requests within a session. The reconnection is transparent to the user.
ANY: (Default) The server allows client code to request either a RETAINED or RECONNECT type of connection for a session. Whereas, with the other two options, the server dictates from which type of client it accepts connections. This option translates to the -c Connection Mode parameter for the JSL section in the PSAPPSRV.UBB file.
BEA Jolt compression can significantly improve performance. BEA Jolt compression enables messages that are transmitted through a BEA Jolt connection to be compressed as they flow over the network. You are likely to see the most significant performance improvements over a WAN.
For compression, the configuration files contain a default compression threshold. This default value should provide the best results for most situations. However, your application server administrator can adjust this value to suit your implementation.
The compression threshold indicates to the server how large a packet must be to require compressing. In other words, the value that you set is the minimum number of bytes that a single packet must be before the server compresses it.
Many of the XML messages being sent around the system are greater than 100,000 bytes. These messages contain HTML in compressed states, so it's generally not required that these messages be compressed. Because of this, the PeopleSoft default is set to 1,000,000 bytes.
Be careful when adjusting compression settings. If you set the threshold too high, then no packets will be large enough to be compressed. If you set the threshold too low, you may greatly reduce network traffic, but be aware that the server will have an increased workload from compressing numerous packets. Typically, you should decrease the threshold according to the bandwidth of the workstation hardware as described in the following paragraphs.
If you are handling only LAN connections, you may want to disable compression by setting the threshold to 99999999 so that only packets larger than 99,999,999 bytes are compressed. Of course, such a large value effectively disables compression so that no packets are compressed. This means no extra work for the server compressing packets.
Alternatively, if you have mostly low bandwidth, as in 56-kilobyte (KB) modem connections over a WAN, then you most likely want to compress the packets as much as possible. When decreasing the compression threshold, keep in mind that the law of diminishing returns applies. Setting the threshold much below 1000 puts an increasing load on the server, and this can nullify any performance increases that you may have gained from reduced network traffic.
After you finish all of the configuration sections, PSADMIN prompts you to configure BEA Jolt which is on by default.
If you are using the PeopleSoft Internet Architecture, you must configure BEA Jolt
The BEA Jolt relay adapter is disabled by default. Unless you have a specific need for JRAD, you should skip this section.
Understanding Jolt Internet Relay
The default is %PS_MACH%. Enter the machine on which the application server is running. See the equivalent parameter for the workstation listener.
This option is for advanced configurations requiring the BEA Jolt internet relay (JRLY). The listener port listens for JRLY requests and must match the JRLY “OUT” port setting in the JRLY configuration file of the sending machine. The port number, as in 9100, is not used unless you enter y at the prompt that asks if you want to configure JRAD.
Use this section to specify general settings for the entire domain—not just for a specific component of the domain.
Enter the name of the application server domain. It does not need to match the name that you specified when you created the domain. This name is important only because the BEA Tuxedo Web Monitor and PeopleSoft Watch Server (PSWATCHSRV) use it to identify application server domains and the processes associated with each machine. It should not exceed 8 characters. Generally, you should use the database name in lowercase.
Enter the directory that contains your database connectivity software, as in /apps/db/oracle/bin, in the path. If the database connectivity directory is not already specified in the path, you can set it by specifying this parameter. The value is added to the path.
On Microsoft Windows, if you don't enter a value, it uses the current path.
On UNIX, if you don't enter a value, it uses the current directory—not the current path. To have it set by default to the current path, enter a period (.).
Note. On Windows, entries that contain a space must be surrounded by quotes.
Enter a parameter that's supplied to BEA Tuxedo for control of process spawning by using the -p command-line option for all server processes. The default setting (1,600:1,1) rarely needs to be changed.
This setting enables the dynamic decay of spawned server processes as the transaction volume decreases. The value can be loosely translated to mean that if, in 600 seconds, there is less than or equal to one job in the queue, the decay process begins. This is described in more detail in the timeout settings appendix of this PeopleBook.
New server processes will be spawned according to the rule defined here. By default, if there is one outstanding request in the queue for one second or more, an additional process is spawned. Additional processes will be spawned all the way up to the Max Instances defined for that server type. If Max Instances and Min Instances are identical, this setting has no effect.
For more information, see servopts(s) in the reference manual of the BEA TUXEDO online documentation.
Note. This parameter applies only if, for PSAPPSRV, the value of Max Instances is greater than that of Min Instances.
Application Server Timeouts
Enter y to have BEA Tuxedo restart server processes (except the BBL process) if the server dies abnormally, as in a kill on UNIX or through the Task Manager on Microsoft Windows. Otherwise, enter n.
Often, administrators must set a trace or performance parameter while the domain is up and running. If you enable this option, then you don't need to reboot the domain for the modified parameter value to take effect.
Enter y or n to enable or disable dynamic changes. When disabled, you must reboot (or cycle the processes) for changes to take effect.
When enabled, the server checks an internal time stamp for a particular service request to see if any values have changed for the parameters for which dynamic changes are valid. If values have changed, the system uses the modified parameter value.
You should enable this option in your test and development domains. For production environments, you should enable dynamic changes selectively.
These parameters allow dynamic changes:
Consecutive service failures.
Trace SQL and Trace SQL Mask.
Trace PC and Trace PC Mask.
Trace PPR and Trace PPR Mask.
Enable DB Monitoring.
Dump Memory Image at Crash.
Dump Managed Objects at Crash.
Log Error Report.
Mail Error Report.
SMTP Settings (all except SMTPGuaranteed, SMTPTrace, and SMTPSendTime).
Analytic Instance Idle Timeout.
Analytic Per Server Log.
Note. The parameters that allow dynamic changes are also identified through comments in the PSAPPSRV.CFG file. Look for the phrase “Dynamic changes allowed for X,” where X is the parameter name. This option does not apply to configuration parameters that BEA Tuxedo relies on, such as the number of processes, whether restart is enabled, the port numbers, the amount of handlers, and so on.
Enter a level of network tracing, ranging from –100 (suppressing) to 5 (all). The default is 3.
The trace file is generated in PS_HOME\appserv\domain\LOGS\psappsrv.log.
This setting is not available through the PSADMIN interface, but can be entered directly into the PSAPPSRV.CFG file.
You can use this parameter to conditionally determine whether you want to do certain logging from your application. You can implement this parameter from PeopleCode using the %AppLogFence system variable, and it's more fully documented in the PeopleCode Developer's Guide.
See Using Application Logging.
Enter the character set (ANSI or UNICODE) of the machine to which you typically write and read the traces and log files. If the character sets are not matched between the file and the machine, the file is unreadable.
Use this section to enable and configure the PeopleCode debugging environment. Configuring PeopleCode debugging is discussed in detail in another section of this PeopleBook.
Setting Up the PeopleCode Debugger
This section enables you to specify the tracing options that you can enable on the application server to track the Structured Query Language (SQL) and PeopleCode of the domains. You can also set all of the trace parameters from the PeopleSoft sign-in page. Just beneath the Sign In button, click the link that opens the trace flags page. This enables you to set the trace options and then sign in to the system.
Note. With many of the following trace options, you need to view the comments in the PSAPPSRV.CFG to understand what to enter to return the trace information you require.
Enter the logging level for SQL tracing for all clients. Traces are written to PS_HOME/appserv/domain/LOGS/domain_user_ID_servername.tracesql. See TraceSQLMask for trace options.
Enter 0 to disable tracing; enter 7 to enable a modest tracing level for debugging. For other levels of tracing, set this option to a value that equals the sum of the needed options. For example, to trace only SQL, enter 1; to trace SQL statements and connect statements enter 7 (1+ 2 + 4 = 7). A setting of 7 is recommended for troubleshooting connection and other basic problems. Tracing can consume large amounts of disk space over time, so be sure to reset this option to 0 when you finish troubleshooting.
Important! The trace file stores elapsed times for SQL events to a precision of one microsecond (six decimal places). However, due to limitations of the operating system, Windows precision is actually in milliseconds (three decimal places), so the last three digits in a Windows trace will always be zero. Elapsed times in UNIX are accurate to one microsecond.
Enter the logging level ceiling for SQL tracing for individual clients. Traces are written to PS_HOME/appserv/domain/LOGS/client_user_ID_servername.tracesql. Clients must specify the necessary SQL tracing level by using the PeopleSoft Configuration Manager on the Trace tab. To prevent clients from turning on the application server trace and consuming resources, the application server uses TraceSQLMask as an administrative control facility.
If a client transmits a request to trace SQL, the application server compares the value that is transmitted to the TraceSQLMask value. If the client value is less than or equal to the TraceSQLMask value, the application server enables the trace. However, if the client value is greater, the application server enables the trace up to the TraceSQLMask value. Trace files are written on the application server; no trace shows up on the client workstation.
Trace values are set in the PSAPPSRV.CFG file. Output files are written to PS_HOME/appserver/winx86/domain/logs.
Enter a level for PeopleCode tracing for activity that is generated by all clients on a domain. Eligible values are defined in the configuration file. TracePC values are displayed in the PeopleSoft Configuration Manager on the Trace tab. You can find the results in PS_HOME/appserv/domain/LOGS/domain.log.
Important! The trace file stores elapsed times for PeopleCode events to a precision of one microsecond (six decimal places). However, due to limitations of the operating system, Windows precision is actually in milliseconds (three decimal places), so the last three digits in a Windows trace will always be zero. Elapsed times in UNIX are accurate to one microsecond.
Enter which PeopleCode trace options that are requested by client machines will be written to the trace file. You can find the results in PS_HOME/appserv/domain/LOGS/client_machine.domain.log.
Use these options to trace the activity in the page processor. Typically, these options are used internally only by PeopleSoft developers; however, you may need to view the results of this trace when troubleshooting.
Tracing-related display processing is useful for seeing when and if related displays are being updated and if they are updating successfully. Some sample output in the log file from setting this flag includes:
Starting Related Display processing Related Display processing - PPR_RELDSPLVALID not set Related Display processing - All Rows Starting Related Display processing for - PSACLMENU_VW2.MENUNAME Related Display processing for - PSACLMENU_VW2.MENUNAME - completed successfully Finished Related Display processing
By using the keylist generation tracing in addition to the related display tracing, you can determine why the related displays have the wrong value. It shows where the keys are coming from. The following is a sample of keylist generation tracing:
Starting Keylist generation Keylist generation - FIELDVALUE is a key FIELDVALUE is low key Low key value was supplied = Key FIELDVALUE = Keylist generation - FIELDNAME is a key Keylist generation - Finding value for USRXLATTABLE_VW.FIELDNAME Not Found in key buffer Seaching for field FIELDNAME in component buffers Scanning level 1 Scanning record DERIVED_USROPTN for field FIELDNAME Field FIELDNAME found in record DERIVED_USROPTN Found in component buffers, value = PT_TIME_FORMAT Key FIELDNAME = PT_TIME_FORMAT Keylist generation - USEROPTN is a key Keylist generation - Finding value for USRXLATTABLE_VW.USEROPTN Not Found in key buffer Seaching for field USEROPTN in component buffers Scanning level 1 Scanning record DERIVED_USROPTN for field USEROPTN Scanning record PSUSROPTLIST_VW for field USEROPTN Field USEROPTN found in record PSUSROPTLIST_VW Found in component buffers, value = TFRMT Key USEROPTN = TFRMT Keylist Generation complete FIELDNAME = PT_TIME_FORMAT FIELDVALUE = USEROPTN = TFRMT
In this example, you can see how the system builds the keylist by first searching in the current record (key buffer), then searching the buffers in the current level, and then searching up a level, and so on. It also indicates exactly what record the key value is taken from. This is useful on complex components where there are often several instances of a particular field; a common problem is that the value is derived from an unexpected location.
Combining the keylist tracing and the related display tracing provides a good view of the system behavior. For example:
Starting Related Display processing Related Display processing - All Rows Starting Related Display processing for - PSACLMENU_VW2.MENUNAME Starting Keylist generation Keylist generation - MENUNAME is a key MENUNAME is low key Low key value was supplied = APPLICATION_ENGINE Key MENUNAME = APPLICATION_ENGINE Keylist Generation complete MENUNAME = APPLICATION_ENGINE Related Display processing for - PSACLMENU_VW2.MENUNAME - completed successfully
Each related display goes through the keylist generation process, and you can see exactly what key values are used to populate the related displays and where those key values came from.
The work record flag is a performance feature. If every field in a level-0 record has a value from the keylist and is display-only, then it is marked as a work record because the values can't be changed. After it is marked as a work record, that affects how the record behaves. For example, PeopleCode for fields in the record but not in the component don't run, data isn't saved, and so on. By enabling this tracing option, you can see which records are flagged as work records. The output looks like this:
Work flag cleared for record PSCLASSDEFN_SRC Work flag cleared for record PSCLASSDEFN_SRC Work flag cleared for record PSCLASSDEFN Work flag cleared for record PSPRCSPRFL Work flag cleared for record SCRTY_QUERY Work flag set for record PSCLASSDEFN Work flag set for record PSPRCSPRFL Work flag set for record SCRTY_QUERY
Because the flag is turned on and off at various points, the last setting (set or cleared) is the most important. In the previous trace, PSCLASSDEFN, which is marked as a work record, is cleared and then set again.
Use these options for tracing PeopleSoft page (PIA page) generation.
Use this parameter to activate specific PeopleSoft Application Engine traces for tracing Application Engine programs.
The bits enable logging for analytic servers beyond the standard LogFence setting.
The Performance Monitor agent is a thread that reports performance metrics for each instrumented server if monitoring is enabled for the database. Select 1 to enable and 0 to disable.
See Working with the Performance Trace.
This parameter determines whether or not a memory image of the failing process is created when a crash occurs. By default, the value is 'NONE' which means that a memory image will not be written during a crash. This value can be set to 'MINI' or 'FULL'. MINI means that a shorter memory image is written. This may be a better option if you are leaving this option turned on permanently. FULL may be appropriate when you are debugging a known issue. Typically, this option is used internally only by PeopleSoft developers.
This parameter assists PeopleSoft in debugging any crash problems at your site by providing insight into the customized object definitions to reproduce the crash on another database.
If you enter y (enabled) and runtime errors are detected (nonfatal error conditions), the system writes a message and information regarding the runtime error to the current log file. If you assign the MailErrorReport parameter an email address, an individual, such as a system administrator, can be alerted whenever the system writes an error to the log. If MailErrorReport is enabled but LogErrorReport is set to n, the system still sends a message for application server crashes, which always cause data to be written to the log. The following is an example of setting this parameter to send notifications to an email address: MailErrorReportemail@example.com.
If the application server shuts down abnormally, you can view the log information that is related to the shutdown. However, because this information can be lengthy, this option enables you to write the information to a file other than the appserv.log file. To enable this option, enter y.
The system writes the crash dump file to PS_HOME\appserv\domain\logs. The system names the crash dump file according to the following convention: server_process_name.process_ID.dmp.
The following example shows what appears in the appserv.log in the event of a crash:
(0) Unhandled exception occurred. Writing crash dump to PSAPPSRV.213.dmp (3) Switching to new log file b:\appserv\test\logs\PSAPPSRV.213.dmp
To disable this option, enter n. If you do not enable this option, crash information appears in the appserv.log by default.
Use this section to specify how to handle caching at your site. Enabling caching on the application server improves performance.
This section has no configuration parameters that need adjusting. In the PSAPPSRV.CFG, you notice that the settings for this section have been commented out. These settings should only be re-introduced pending recommendation from PeopleSoft Support or Engineering.
With EnableServerCaching, you specify what objects the system stores in cache on the application server. To enable application server disk caching the value must be set to 1 or 2.
If you enter 1 the system caches only the most used classes of objects, and if you enter 2, the system caches all object types regardless of the frequency of use. Which option you select depends on internal testing at your site.
To disable application server caching, set this value to 0. In most cases there is no reason to disable server caching. Doing so significantly degrades performance, because it requires the application server to retrieve an object from the database each time the system needs it.
If server caching is enabled on the application server, which is usually the case, there are two modes of caching from which to choose: shared and nonshared cache files.
If you use the nonshared cache mode, each PSAPPSRV server process that starts within a domain maintains its own separate cache file. In this mode, there is one cache file per PSAPPSRV server process.
To set one cache directory and file per server process, enter 0 at the Set ServerCacheMode prompt. By default, nonshared cache files are enabled. With this option enabled, you can find cache files in PS_HOME\appserv\domain\cache\n-1\n.
In the preceding path, n refers to the number of PSAPPSRV server processes that are configured to start within the domain. For example, if you have two PSAPPSRV processes, the system creates two cache directories, \1 and \2, beneath the cache directory.
To set shared caching for the domain, enter 1 at the Set ServerCacheMode prompt. With this option enabled, you can find the cache files in PS_HOME\appserv\domain\cache\share.
The system assumes that a preloaded cache exists in the share directory. The preloaded cache contains most instances of the managed object types that are cached to file. When you boot the application server, if shared cache files are enabled but no cache files exist, the system reverts to unshared caching.
This setting is the location where cache files will be written and stored for this domain.
Note. You must preload your shared cache before you enable shared caching on the application server.
Application Engine processes are independent from application server domains, directories, and configuration files. Therefore, Application Engine processes do not share cache with application server domain processes.
PeopleTools stores application data in a memory cache to increase system performance. However, too large a cache can leave insufficient available memory on your system, which leads to reduced performance.
Use this setting to specify the maximum size of the memory cache. Every time you use an object, its LastUsedDate value is updated. When your system reaches the memory cache threshhold, the system prunes the oldest objects in the cache first — that is, the ones with the oldest LastUsedDate values — and places the pruned data in a disk cache instead. It prunes the cache to keep it 10% below the specified threshhold.
Because using a disk cache can also reduce performance, the default setting might not be optimal for your application. You can adjust this setting to achieve the best trade-off between speed and available memory.
Enter an integer value to specify the maximum size of the memory cache in megabytes. By specifying a value of 0 megabytes you disable pruning altogether, which allows for an unlimited memory cache. The default value of this setting is 10 megabytes.
If you have created a load project, specify the project name. Before booting a domain, you have the option to preload the cache, and this option creates the cache based on the load project you specify.
Configuring an Application Server Domain to Preload Cache
There are two significant Remote Call domain parameters.
You must set the RCCBL Redirect option for remote call through PSADMIN.
Enter 0 to disable redirection and 1 to enable redirection. Redirection causes the server process to retain intermediate work files that are used to pass parameter values between the server process and a RemoteCall/COBOL program for debugging purposes.
Note. Redirect should always be enabled because it contains valuable information for debugging purposes.
The location of the intermediate Remote Call files is $PS_HOME/appserv/<Appserv-Domain-Name>/log_output. The intermediate Remote Call files generated are:
Note. Where <pid> is the Process ID.
Use this parameter to specify where RemoteCall can find the COBOL executables. By default, RemoteCall looks in a predefined location. This might not be the location where you've installed them on your system:
In UNIX, RemoteCall looks in $PS_HOME/cblbin.
In Windows, RemoteCall looks in %PS_HOME%\cblbin%PS_COBOLTYPE%. The %PS_COBOLTYPE% variable contains a single letter that indicates the character encoding for the database platform. It's automatically set to one of the following values when the application server starts:
U — Unicode.
A — Non-Unicode.
E — EBCDIC.
To override this default behavior, set RCCBL PRDBIN to the absolute path of your COBOL executables, for example:
In Windows: RCCBL PRDBIN=c:\pscobol\MYDOMAIN\cblbin
In UNIX: RCCBL PRDBIN=/app/psoft/MYDOMAIN/cblbin
Note. This parameter doesn't appear in the PSADMIN custom configuration interface if it's not already set. You must define it by editing the application server configuration file directly. On the PeopleSoft Domain Administration menu, select Edit configuration/log files menu, then select Edit psappsrv.cfg (current configuration file) to open psappsrv.cfg in a text editor. Define the RCCBL PRDBIN parameter in the RemoteCall section of the file.
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 BEA 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 BEA Tuxedo parameter in the PSAPPSRV.UBB file. Instead, the value is stored in memory and is managed by a PeopleSoft server.
This option makes the recycling of a server process dynamic as opposed to using a static Recycle Count. This parameter works in conjunction with the Recycle Count parameter in that the latter needs to be set to 0 for dynamic recycling to occur. This parameter indicates the percentage of memory growth to reach before the PSAPPSRV process will automatically restart. The default is 20, meaning an additional 20% of memory growth will be incurred after the process has established its memory cache. Uncomment the setting from the PSAPPSRV.CFG file to use this setting in place of the static recycle count. After using dynamic recycling, an administrator can review log files to determine an optimum recycle count and resume static recycling, if desired.
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, but 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.
This parameter determines the threshold for the BEA Tuxedo queue size and is used for Pub/Sub processing only.
See Throttling Dispatched Messages Through the Messaging System.
PSANALYTICSRV relates to the server processes that are associated with the analytic server framework.
Enter the minimum number of analytic server instances that start when you boot the application server domain. There's always at least this number of instances running. The default value of this parameter is 3.
Enter the maximum number of analytic server instances that can result from dynamically spawning new processes. The default value of this parameter is 3.
See Configuring and Starting Analytic Servers.
Enter the number of minutes of inactivity before the analytic instance times out and is unloaded.
This value takes effect only if the PeopleCode AnalyticInstance class Load method specifies a value of -1 for its IdleTimeOut parameter when loading an analytic instance. This includes Load PeopleCode that's launched from an analytic grid, which enables you to avoid having to explicitly specify a timeout.
The default value of this parameter is 0 (no timeout limit) for domains that are configured with a developer template, and 30 minutes for other domains.
The PSSAMSRV server process communicates through the BEA Tuxedo conversational mode. It performs transactional SQL requests (updates).
Enter how many servers are started at boot time. This translates to the PSSAMSRV server's -m (min) parameter in the UBB file.
Enter the maximum number of servers that can be started. This translates to the PSSAMSRV server's -M (Max) parameter in the UBB file.
Enter the number of seconds that the server processes waits for a request before timing out. This stops runaway processes, like an rccbl timeout.
Enter the number of service requests that each server carries out before being terminated (intentionally). Tuxedo immediately restarts the server. 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 BEA Tuxedo parameter in the PSAPPSRV.UBB file. Instead, the value is stored in memory and is managed by a PeopleSoft server.
Enter a number greater than zero to enable dynamic server process restarts 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 cause a recycle of the server process. This is a catchall error handling routine that enables PSAPPSRV, PSQCKSRV, and PSSAMSRV 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 32 (K). Enter the maximum memory that is used by the server to store fetched rows for a transaction before sending results to the client and refilling the memory buffer. When the memory limit is reached, the server sends rows to the client, but then resumes refilling the buffer and sending results to the client until the query is complete. You should leave the default value unchanged.
PSSAMSRV supports conversational transactions, so this parameter enables users to tune performance by adjusting the number of network round-trips that are required for the average transaction. A value of 0 causes unlimited memory to be used, which means one round-trip no matter how large the result set. The memory is not preallocated, but is acquired as needed.
The PSQCKSRV is an optional server process to improve performance. Essentially, the PSQCKSRV, or quick server, is a copy of the PSAPPSRV. It performs quick requests, such as nontransactional (read-only) SQL requests. The PSQCKSRV improves overall performance by enabling the PSAPPSRV process to direct a portion of its workload to PSQCKSRV.
Enter how many servers are started at boot time. This translates to the PSQCKSRV server's –m (min) parameter in the UBB file.
Enter the maximum number of servers that can be started. This translates to the PSQCKSRV server's –M (Max) parameter in the UBB file.
Enter the number of seconds that a PSQCKSRV waits for a request before timing out. This stops runaway processes, like an rccbl timeout. This applies to incremental PSQCKSRV servers that are dynamically started by the Max Instances parameter.
Use the PSAPPSRV specifications.
Enter a number greater than zero to enable dynamic server process restarts 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.
Use the PSAPPSRV specifications.
PSQRYSRV handles the SQL that is generated by PeopleSoft Query (PSQED.EXE). With PSQRYSRV configured, SQL-intensive, complicated, user-defined queries are offloaded to a dedicated server process, thus freeing PSAPPSRV and PSQCKSRV to handle the SQL requests for which they are more suited.
Note. When running PS/nVision reports from a three-tier, Windows client connection, the system also routes the SQL generated by both matrix (ledger-based) and tabular (PS Query-based) reports through PSQRYSRV if it is enabled.
PSQCKSRV also processes SQLRequest services; however, if PSQRYSRV is configured, it processes all SQLRequests that are initiated specifically by PSQuery (SQLQuery:SQLRequest) or PS/nVision.
Like the PSQCKSRV server process, PSQRYSRV is an optional server process. However, if you allow users to initiate queries from PeopleSoft Query, you should take advantage of this server process.
Enter how many servers are started at boot time. This translates to the PSQRYSRV server's –m (min) parameter in the UBB file.
Enter the maximum number of servers that can be started. This translates to the PSQRYSRV server's –M (Max) parameter in the UBB file.
Enter the number of seconds that PSQRYSRV waits for a request before timing out. This stops runaway processes.
Enter the number of service requests that each server carries out before being terminated (intentionally) by BEA Tuxedo and then immediately restarted. Servers must be intermittently recycled to clear buffer areas. The time that is required to recycle a server is negligible, occurring in milliseconds.
If the recycle count is set to 0, PSQRYSRV is never recycled.
Enter a number greater than 0 to enable dynamic server process restarts 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, PSQRYSRV, and PSSAMSRV 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.
Enter the maximum size (in KB) of a result set that is returned from a SELECT query. The default is 10000 KB. Use 0 for no limit.
Enter 1 to enable the application server to read uncommitted data from a table. Enter 0 to disable dirty reads.
This parameter can be used for general reporting and PeopleSoft Query. You can run dirty read queries through the application server, the Process Scheduler, and in a two-tier connection. The Use Dirty-Read setting in the application server configuration controls the behavior of PSAPPSRV, PSQCKSRV, and PSQRYSRV.
Note. Dirty reads are not recommended if you are reading data and doing subsequent processing based on the disposition of the data at the time that it is read. Between the time the data is read by a subsequent process and the time the unit of work is completed by the first process, any activity affecting the table data at the time a subsequent process read could be rolled back, invalidating the accuracy of the data that a subsequent process read.
Dirty Reads in PeopleSoft Query
Setting Parameters for the Application Engine Server
A variety of server processes are devoted to Integration Broker processing. If you are not implementing the Integration Broker technology, skip through these delivered, default server processes:
Publish & Subscribe
These server processes act as brokers, dispatchers, and handlers of the messages in the messaging system.
Administering Messaging Servers for Asynchronous Messaging
You can send electronic mail requests, issued with workflow or PeopleCode, to the application server, and the application server, in turn, passes the requests to the specified mail server (SMTPServer). By having the application server submit the email request, you avoid having to install mail connectivity software on each client, just as you avoid having to install database connectivity software on each client in a three-tier connection. To specify the appropriate SMTP server and port to receive the email requests, you must edit the SMTP Settings section.
When set in the PSAPPSRV.CFG file, these three SMTP settings are not dynamic: SMTPGuaranteed, SMTPTrace, SMTPSendTime. They require a domain reboot to take effect.
Note. You can also control most of these settings using the PeopleCode SMTPSession class, which temporarily overrides them without changing their values in PSAPPSRV.CFG. You use this class primarily when you want to send multiple emails in a single session of the SMTP server, instead of having to change the permanent SMTP settings for every email.
See SMTPSession Class.
Enter the host name and IP address of the mail server machine.
Enter the port number on the mail server machine.
Enter the host name and IP address of the failover mail server machine in case the other specified server is down.
Enter the port number on the failover mail server machine.
Enter the sender's internet address. This must be a valid address, such as firstname.lastname@example.org.
Enter the internet address that you want to be the reply to address for Blackberry email responses. This must be a valid address such as email@example.com.
Enter the sender's source machine name and internet address in the form of MACHINE.XYZCORP.COM. This value is required in some, but not all environments.
Enter the character set that is used on the sender's machine.
Enter the name of a dynamic-link library (DLL) that is used to translate the mail message from the sender's character set (such as latin1, sjis, big5, gb, ks-c-5601-1987, or ks-c-5601-1992) to a 7-bit safe character set for transmission.
Set this parameter to 1 if you want TriggerBusinessEvent email PeopleCode to be delivered through the messaging system, which provides some additional administration capabilities for ensuring delivery of the message.
If the application server isn’t able to make a connection to the SMTP mail server, it attempts to resend the message up to the number of times specified by the Max Retries parameter of the PSSUBHND_dflt or PSMBHND messaging server process.
The system doesn’t try to resend the message indefinitely. When the Max Retries limit is reached without success, the subscription contract for the message is set to a status of Error. You can then manually resubmit the message from the Application Message Monitor.
By enabling this feature you implement a mechanism to ensure that emails get routed to the appropriate place in case SMTP mail fails for reasons such as network timeouts, downed mail servers, invalid parameters, and so on.
Enter 1 to enable the tracing of all email details to the log file when LogFence is set to 5. Enter 0 to disable it. With this option, you can reduce the log file size for high-volume email users.
Enter 1 to have messages contain a send time that is populated by the application server. Enter 0 to leave the send time blank and have it populated by the receiving gateway (depending on the gateway).
Enter the user name to log in to the SMTP server. This applies only when authentication is enabled on the SMTP server.
Enter the password for the user specified by SMTPUserName to access the SMTP server. This applies only when authentication is enabled on the SMTP server.
Enter the user name to log in to the failover SMTP server. This applies only when authentication is enabled on the failover SMTP server.
Enter the password for the user specified by SMTPUserName1 to access the failover SMTP server. This applies only when authentication is enabled on the failover SMTP server.
Enter the time in milliseconds for the mail system to wait for the result of sending each email. If the time is set to 0, the system doesn't wait, and the returned result will be always be %ObEmail_SentButResultUnknown ( = -1). If you set this parameter to -1, the system will wait for the completion of the send process. The default value of this setting is 10000 (ten seconds).
Keep in mind the following considerations:
PeopleSoft mail integration is on the application server only.
Currently, PeopleSoft software does not support VIM/MAPI, because this option is client-side-only integration, and PeopleSoft Internet Architecture applications run on the server-side.
The application server communicates directly with an SMTP server through telnet by using standard SMTP commands with Multipurpose Internet Mail Extensions (MIME) 1.0 messages.
PeopleSoft software currently supports UTF-8 encoding of the email messages out-of-the-box, and you can encode email messages in other ways.
With server-side integration, you do not have to certify any specific email client application. You can use any application to read email.
You can send email using the PeopleCode Mail classes, as well as the SendMail and TriggerBusinessEvent PeopleCode built-in functions. PeopleSoft recommends using the Mail classes for all email sent from a PeopleSoft application.
Outside of PeopleSoft applications, you use PSMAIL.EXE, which is an executable that is for use by advanced developers. PSMAIL.EXE can send email messages through SMTP based on data that is passed as parameters to the executable or from an input file. This executable is primarily used for PeopleSoft Process Scheduler programs.
Set the following parameter for configuring the interface driver for business interlinks.
Enter the RPS_LOCALE string, which the driver sends to the Supply Chain Planning (SCP) server.
You may need to set the following parameters in advanced configurations.
Enter0 to disable the Performance Monitor agent. This setting overrides the value for this parameter that is set in the database. The default value of 1 enables the Performance Monitor agent.
The CLASSPATH environment variable tells the Java Virtual Machine (JVM) and other Java applications where to find the Java class libraries, including any user-defined class libraries. Because PeopleTools automatically generates CLASSPATH entries for core, delivered class libraries, use this field to specify additional class libraries that the PeopleSoft software needs to access.
Specify additional options to be passed to the JVM that's loaded by the PSAPPSRV process. Separate the options with spaces, for example:
-Xrs -Xmx256m -Xms128m
If the domain will run as a Windows service, you must specify at least the default option, -Xrs.
Refer to your JRE documentation for valid JVM options.
If the HTTP destination, such as the gateway or business interlink remote host, is behind a proxy server for security reasons, enter the distinguished name of the proxy server, as in proxy.peoplesoft.com.
Enter the port number on which the proxy server is listening for transmissions. For instance, 80 is a typical default port number.
Enter a list of the hosts that should be connected to directly, not through a proxy server. Separate the hostnames with a pipe symbol ( | ). You can use an asterisk (*) as a wildcard character to specify a pattern of similar hostnames.
For example, localhost|*.peoplesoft.com indicates that the local host and all hosts with names ending in .peoplesoft.com will be accessed directly.
Note. The length of this string cannot exceed 1024 characters.
Enter the character set to use for processing external data on the Unix application server, such as configuration file and log file name and body, and attachment filenames.
The default value is latin1, which supports all Western European languages, including English. If this application server will be used to process only Western European data, you should accept the default for this parameter.
Otherwise, select a character set from the following list corresponding to the languages that this application server will process:
UNIX Character Set
Description (Similar Windows Codepage)
Western Europe (CP1252) (Default)
Central Europe (CP1251)
Japanese Shift-JIS (CP932)
Traditional Chinese (CP950)
Simplified Chinese (CP936)
Korean Wansung (CP949)
Korean Johab (CP1361)
(No USS equivalent)
Unicode (No Windows equivalent)
Note. The character set of the application server and the character set of any Microsoft Windows workstations connecting to that
application server must match.
The utf8 option is valid only when the locale character set is UTF-8.
Enter y to suppress an application error box or message from appearing after an application error occurs. Enter n to view error dialogs and message boxes.
Note. If the system generates an error box for an application server process and this parameter is set to n, BEA Tuxedo can't restart the down process until you close the error box.
The following values are valid for the DbFlags parameter:
Enable the %UpdateStats meta-SQL construct.
Disable the %UpdateStats meta-SQL construct.
Ignore the Truncate command for DB2 UNIX/NT. Use Delete instead.
Disable a secondary database connection (used with the GetNextNumberWithGapsCommit PeopleCode function).
This prevents the creation of a secondary database connection, bundling all SQL into a single unit of work. Without the additional database connection, the database row lock is held for a longer time, reducing concurrency in a multiple-user environment.
Note. Analytic instance processing requires a secondary database connection, so if you're using analytic servers, ensure that this value is not set.
Disable a persistent second database connection (used with the GetNextNumberWithGapsCommit PeopleCode function).
This creates a second database connection in each GetNextNumberWithGapsCommit call, then immediately closes the second connection. This keeps the number of database connections to a minimum, but requires each call to create a new database connection on demand.
Note. The performance impact of making a new database connection is significant, especially in high volume user production environments. Don't use this setting without carefully considering its effect.
DbFlags uses a bit mask so that you can specify one or more of these values. You set this parameter to the total of the values that you want to apply. For example, to disable %UpdateStats and ignore the Truncate command, set DbFlags to 3 (setting bits one and two).
The default is value is 1.
See Using PeopleCode in Application Engine Programs, PeopleCode Built-in Functions and Language Constructs.
This option is not available through the PSADMIN interface, but it exists in the PSTOOLS section of the PSAPPSRV.CFG file for small, medium, and large configurations.
For security purposes, this option has a default value of 1 to prevent SQL error details from being displayed to users. Any SQL errors that occur don't display details, but refer users to consult the system log. The details that were in the SQL message are written to the log file. This helps to prevent SQL injection vulnerabilities.
If you want SQL error details to be visible to users, set this property as follows:
Suppress SQL Error=0
Note. In developer configurations, the Suppress SQL Error option doesn't exist in PSAPPSRV.CFG, and the system assumes a value of 0.
Preventing SQL Injection
The following parameters apply to PeopleSoft Integration Broker.
Administering Messaging Servers for Asynchronous Messaging
Use this parameter to configure the threshold of a message before the system compresses the message.
Set the thread pool size used by the SyncRequest PeopleCode event. The Minimum value is 1 and maximum allowable is 20.
These options enable you to configure PeopleSoft search. These options are documented in detail in another section of this PeopleBook.
Note. If you do not specify a search configuration type, the system assumes the default configuration based on your operating system.
Configuring PeopleSoft Search
Use this option to specify the location of all the files pertaining to the search index. Index name is same as the location. This option is documented in detail in another section of this PeopleBook.
See Specifying the Index Location, Sharing Indexes Between Application Servers and PeopleSoft Process Scheduler.
PSRENSRV is a modified web server designed for real time event notification. The primary purpose of PSRENSRV is to publish events to the browser.
See Configuring REN Servers.
This is the log severity level for the PSRENSRV process. Settings are Error, Warning, Notice or Debug. Default is Warning.
This is the TCP buffer size when serving content. This should not exceed a value of 65536.
This is the REN servers http port. The default value is 7180.
This is the REN servers https port. The default value is 7143.
The fully qualified domain name of the application server. This value should match the value of the web server's authentication token domain.
PSPPMSRV servers subscribe to performance metrics published by the web service at the PPMI URL (entered into the Performance Monitor administration pages) and insert them into the database. If you select Y when you are asked whether you want Performance Collators configured, then the number of PSPPMSRVs specified in Min Instances=1 will be started. Min and Max instances should be set to the same value, as new PSPPMSRV servers are not spawned on demand.
Setting Up the Performance Monitor
The number of servers started at boot time. This translates to the PSPPMSRV server's –m (min) parameter in the UBB file.
The maximum number of servers that can be started. This translates to the PSPPMSRV server's –M (max) parameter in the UBB file.
After you enter all of the previous parameter values for the application server, PSADMIN prompts you for the following server process options. You can use these prompts to reduce the number of server processes that start when the domain boots. This, in turn, makes your configuration simpler while conserving system resources.
For instance, if you enter n for any of the following prompts, the corresponding server process (or a set of server processes) is not configured for the domain. If you enter n to all of the prompts, the domain will contain only the required server processes.
If you want the application messaging server processes to be configured and booted, enter y. If you are not implementing the application messaging technology, enter n.
Note. In addition to setting this option, in PeopleSoft Integration Broker you must also activate the domain on which the pub/sub server resides before you can use the pub/sub system.
See Administering Messaging Servers for Asynchronous Messaging.
Enter n if very few clients access the domain and concurrency is not an issue. Enter y to enable the PSQCKSRV in situations where concurrency and optimal transaction throughput are needed.
If you want all user-generated queries to be initiated by PSQuery and handled by a dedicated server process, enable this option to improve overall performance.
The BEA Jolt listener is required to support the PeopleSoft Internet Architecture by enabling transmission between the web server and the application server.
JRAD applies to specific configurations only. Accept the default unless you are attempting to configure JRAD for use with the BEA Jolt internet relay.
Understanding Jolt Internet Relay
Configures the Workstation Listener for Development Environment (Windows) workstation connections.
Enter y to debug PeopleCode programs with the current domain.
Select Y to start the PSRENSRV servers.
See PSRENSRV Options.
Select Y to start the Multi Channel Framework servers.
See Configuring PeopleSoft MCF Queues and Tasks.
If the domain is servicing a Performance Monitor database, select Y to start the PSPPMSRV servers.
See PSPPMSRV Options.
Configures analytic servers to run in the domain to process PeopleSoft Analytic Calculation Engine requests and to perform optimization processing.
Enable this option of you are configuring a remote , or external, search server to which this domain will send search requests. That is, if you are configuring a Type-3 search option for an application server domain, you need to enable the domains gateway on the application server domain to a communication connection between the application server and its remote search domain.