PeopleSoft Usage Monitor – Made easy to use

November 23, 2022 | 3 minute read
Text Size 100%:

The Usage Monitor (UM) is a tool provided by PeopleSoft to collect the definitions (Managed Objects such as pages, components, PeopleCode etc.) accessed by users through PIA. The data collected can be used in PeopleSoft Test Framework (PTF) to generate test coverage report, and for Change Package impact analysis. In this blog we will focus on what changed in PeopleTools 8.60 with respect to set up, data collection and how the data can be used.

Beginning with PT 8.60, UM is now a standalone utility which has no dependence on Performance Monitor framework (PPM). The standalone UM works as a self-monitoring tool to collect UM data on any PeopleSoft system.

Prior to 8.60, in a typical production environment, a separate Monitoring system was required which would monitor all the Monitored systems. Thus, to collect and leverage usage monitor information, first PPM should be set up and configured properly. After data is stored on the Monitoring system, user should run PTUMAGR AE program to generate more suitable data for analysis by other tools.

The PPM framework used by UM for data collection is shown in below diagram taken from PeopleBooks. As you can see it has many components to setup and configure which are not required in PeopleTools 8.60.

Performance Monitor architecture

To make it simpler to use without the need of a separate monitoring system and an elaborate PPM setup, UM has been redesigned in PeopleTools 8.60 release. Let’s see how UM can be enabled.

Navigate to Main Menu -> PeopleTools -> Lifecycle Tools -> Lifecycle Tools Options page and check “Enable Usage Monitoring” parameter. Also set the appropriate “buffer size” and choose the data collection method whether “By UserId” or “Anonymous”. After saving the changes, reboot the application server domain. Usage monitor will start to collect the data. The data collected is stored in the PSPTUMPMTAGR table which is ready for consumption by other tools.

 

User can choose to remove the historical UM data by providing number of days and clicking “Purge Data”. Based on number of days, historical data will be removed from PSPTUMPMTAGR table. For example, if days is set to 30, then any UM data beyond 30 days from current date will be removed from PSPTUMPMTAGR table.

Disabling UM is also made easy.  Just, navigate to Main Menu -> PeopleTools -> Lifecycle Tools -> Lifecycle Tools Options page and uncheck the ‘Enable Usage Monitoring’ parameter. Save the changes and reboot the application server domain.

Now let’s move to see how UM data can be used. As you already know UM data is used in conjunction with PTF test coverage report that tells if all your test cases are covered for most used objects. In addition to it, UM data can be used to analyze impact of a change package. For this usage monitor data is fetched from different monitored system databases and stored in the PUM UM table. While reviewing the change package, “Is Used“ field indicates whether the managed objects in change package is referenced in usage repository or not. Based on this user can analyze if change package modifies any used MO objects.

For more details, refer following links:

Usage monitor overview

Using usage monitor data with PTF

Reviewing change package

Shreeman Narayan

PeopleSoft Developer working on ADS, Usage Monitor


Previous Post

PeopleTools Infrastructure DPKs: October 2022 Availability and the Story Behind Them

Mark Hoernemann | 3 min read

Next Post


Legislative Update for PeopleSoft HCM Global Payroll GPUK - SOY 2023-2024

Ravikanth Pandikunta | 1 min read