Setting Up the Application Server
The application server on the monitoring system requires that the following server processes be enabled:
-
Typical application server processes included in a default configuration.
-
PSPPMSRV.
Default Server Processes
A typical default application server configuration is suitable for Performance Monitor activity.
The PSAPPSRV server process is the main server process of the PeopleSoft Application Server.
At least two PSAPPSRV server processes must be enabled. This ensures that the monitoring system can publish notifications of configuration changes through the PeopleSoft Integration Broker gateway. You can enable more PSAPPSRVs to meet increased demand.
PSPPMSRV
The PSPPMSRV process receives the performance data from the monitor servlet and inserts it into the monitoring database.
The following table describes the ways that you can enable this server process using the PeopleSoft Server Administration interface (PSADMIN).
| Method | Description |
|---|---|
|
Quick Configure menu |
You can use the Quick Configure menu in PSADMIN to enable the PSPPMSRV server process. Enable the Perf Collator option. |
|
Custom Configuration menu |
After you have scrolled through all of the configuration sections of the PSADMIN menu, the system prompts you to enable a variety of options. One of these prompts relates to enabling the PSPPMSRV server process. When prompted with the following: Do you want Performance Collators configured? (y/n) Enter y to indicate Yes. |
To add additional PSPPMSRV server processes, use the [PSPPMSRV] configuration section in PSADMIN and adjust the settings. The [PSPPMSRV] configuration section contains the following parameters.
| Field or Control | Description |
|---|---|
|
Min Instances (minimum instances) |
Enter the minimum number of PSPPMSRV server processes that you want to start when the application server boots. |
|
Max Instances (maximum instances) |
Enter the maximum number of PSPPMSRV server processes that you want to start when the application server boots. |
Note:
For the PSPPMSRV server process, the values assigned to Min Instances and Max Instances must be equal. For example, if you want three PSPPMSRV server processes to start, set Min Instances=3 and Max Instances=3. Unlike PSAPPSRV, Tuxedo does not handle load balancing between PSPPMSRVs. Decide how many PSPPMSRV instances you need operating within the appropriate number of domains and boot all of them.
If you have more than one PSPPMSRV configured, the monitor servlet automatically implements load balancing across the multiple PSPPMSRVs. Also, if you configure multiple application server domains, each with its own PSPPMSRVs, the monitor servlet automatically implements load balancing and failover across the domains.
Note:
If the monitoring system
is configured for multiple IPs, enter the exposed IP address in the
psappsrv.cfg file, under section PSPPMSRV and then bounce your servers.
Enter listening_mach_IP=<IP
Address> in the psappsrv.cfg file.
Collator port is system
generated. You may use the netstat command
or similar commands (for your operating system) to check the status
of the collator port. If the collator port is not free, you can explicitly
specify the collator port by using the listening_port parameter in the psappsrv.cfg file. In a normal scenario, you can
have multiple instances of PSPPMSRV, but when you explicitly configure
a port for collator, you can have only one instance of PSPPMSRV.
Set the Min instances, Max Instances, and listening_port parameters under the PSPPMSRV section of the psappsrv.cfg file as shown in the following example.
Min Instances=1
Max Instances=1
listening_port=<port_num>