Enabling the Required Elements on the Monitoring System

This section covers the configuration of your monitoring system, and discusses how to enable the required elements.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

The monitoring database requires the use of at least the PeopleSoft database for the production monitoring system. Set this database up using the instructions in the PeopleTools Installation Guide.

Note: For the self-monitoring configuration, use the application database for your system. The application must be running on at least PeopleTools 8.44 for Performance Monitor and on at least PeopleTools 8.51 for Usage Monitor.

See the product documentation for PeopleSoft 9.2 Application Installation for your database platform.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

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

Definition
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>

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

By completing the internet portion of the PeopleSoft Multi-Platform Installer program, you have installed all of the elements that Performance Monitor requires on the web server. No additional installation procedures are required.

Performance Monitor servlets are not activated unless PSPPMSRVs register with them. Agent connections to a monitor are rejected until a PSPPMSRV on the monitoring system registers.

The Performance Monitor servlets that run on the web server of the monitoring system are:

  • Monitor servlet.

  • PPMI servlet.

Note: Make note of the URL of the web server for the monitoring system. On the monitored system, you need to specify the appropriate URL to which to send performance data.

Note: If you elect to implement a production monitoring system, you should set up the monitoring system itself in self-monitoring mode so that you can detect alarm events that are generated from the monitoring web server. That is, while the monitoring system monitors one or more PeopleSoft application systems, it also monitors itself.

If you need to configure multiple web servers for scalability and failover, you need to configure a cluster.

Note: If you notice communication errors in the log files, even though the agents have registered successfully, check the keep-alive setting on the monitoring web server. The keep-alive timeout in the monitoring web server may need to be increased to 660 or higher to resolve these issues. After changing this setting, restart the web server.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

The PSPPMSRV application server process acts as the PPMI client when you record PeopleSoft performance data. To register as a client, the PSPPMSRV requires the appropriate permissions in PeopleTools Security.

Warning! Setting up PSPPMSRV authentication is required.

To set up PPMI authentication:

  1. Create a user profile with the name of your choice using PeopleTools Security.

  2. Add the delivered PeopleTools Perfmon Client role to the user profile.

    The PeopleTools Perfmon Client role contains the PTPMCLNT permission list.

  3. Select PeopleTools > Performance Monitor > Administration > Global Administration and enter the user profile that you created and the associated password in thePPMI User ID andPPMI Password text boxes.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

PSPPMSRV processes must register with the PPMI servlet using the PPMI URL. The PSPPMSRV processes use the PPMI URL that is stored in the monitoring system's database to locate the PPMI servlet for registration.

The PSPPMSRV servers periodically read the PPMI value to determine the PPMI URL. When it is set to NONE, the monitoring system is disabled, which means that the PSPPMSRVs do not insert performance data into the monitoring database.

The PPMI user ID is required to authenticate the PSPPMSRV so that it can subscribe to performance data.

To specify the PPMI URL and PPMI user ID:

  1. Make sure that you have created a PPMI user ID with the appropriate permissions (as described in the previous section).

  2. Select PeopleTools > Performance Monitor > Administration > Global Administration.

  3. On the Global Administration page, enter the appropriate value in the PPMI URL edit box.

    The format is: http://host[:port]/ppmi/[site]/

    For example: http://server1.example.com/ppmi/ps/.

    Where ps is the name of the PeopleSoft site.

  4. Specify the PPMI user ID and password.

  5. Click Save.

  6. Click Ping Test to ensure that the URL that you entered is valid and the URL is available.

If the PPM URLs are set to LOCAL and you want to change them to the appropriate value in the form of a fully qualified HTTP URL, then, after entering the value, you must restart all agents and the PSPPMSRV process.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

Yes

A gateway URL needs to be specified so that the monitoring system can notify the monitor servlet of configuration changes. The monitoring servlet in turn notifies the monitored agents of these changes when they next communicate with the servlet. This communication uses the gateway, which you specify in the Integration Broker administration pages.

When specifying the gateway URL:

  • Select LOCAL gateway.

  • Enter this URL in the following format: http://host[:port]/PSIGW/PeopleSoftListeningConnector.

This step applies to:

Product

Step Required?

Performance Monitor

Yes

Usage Monitor

No

To invoke Performance Monitor Application Engine programs to maintain the performance data, set up a Process Scheduler server that connects to your monitoring database.

To set up a Process Scheduler server, follow the instructions that are provided in your PeopleTools Installation Guide.

See the product documentation for PeopleSoft 9.2 Application Installation for your database platform.

The delivered PeopleSoft Application Engine programs that you schedule to run as part of Performance Monitor administration enable you to:

  • Maintain the current PMU table (the PSPM_REAPER program).

  • Archive or delete historical performance data (the PSPM_ARCHIVE program).

  • Manage the lookup tables in the Performance Monitor interface (the PSPM_LOOKUP program).

See the product documentation for PeopleSoft 9.2 Application Installation for your database platform.