PeopleTools 8.62: Usage Monitor
PeopleTools 8.62: Usage Monitor
April 2025
PeopleTools 8.62: Usage Monitor
Copyright © 1988, 2025, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement
or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute,
exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or
decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you
find any errors, please report them to us in writing.
If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government,
then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,
any programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and
Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users
are "commercial computer software," "commercial computer software documentation," or "limited rights data"
pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,
the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,
and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs
embedded, installed, or activated on delivered hardware, and modifications of such programs), ii) Oracle computer
documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained
in the applicable contract. The terms governing the U.S. Government's use of Oracle cloud services are defined by
the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is
not developed or intended for use in any inherently dangerous applications, including applications that may create a
risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible
to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation
and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous
applications.
Oracle®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD
logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The
Open Group.
This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any
loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as
set forth in an applicable agreement between you and Oracle.
Documentation Accessibility
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program
website at https://docs.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.
To configure the context-sensitive help for your PeopleSoft applications to use the Oracle Help Center,
see Configuring Context-Sensitive Help Using the Hosted Online Help Website.
Your installation documentation includes a chapter with instructions for how to install the online help
for your business environment, and the documentation zip file may contain a README.txt file with
additional installation instructions. See PeopleSoft 9.2 Application Installation for your database platform,
“Installing PeopleSoft Online Help.”
To configure the context-sensitive help for your PeopleSoft applications to use a locally installed online
help website, see Configuring Context-Sensitive Help Using a Locally Installed Online Help Website.
• Application Fundamentals
Most product families provide a set of application fundamentals help topics that discuss essential
information about the setup and design of your system. This information applies to many or all
applications in the PeopleSoft product family. Whether you are implementing a single application, some
combination of applications within the product family, or the entire product family, you should be familiar
with the contents of the appropriate application fundamentals help. They provide the starting points for
fundamental implementation tasks.
In addition, the PeopleTools: Applications User's Guide introduces you to the various elements of the
PeopleSoft Pure Internet Architecture. It also explains how to use the navigational hierarchy, components,
and pages to perform basic functions as you navigate through the system. While your application or
implementation may differ, the topics in this user’s guide provide general information about using
PeopleSoft applications.
Typographical Conventions
The following table describes the typographical conventions that are used in the online help.
. . . (ellipses) Indicate that the preceding item or series can be repeated any
number of times in PeopleCode syntax.
ISO country codes may appear as country identifiers, and ISO currency codes may appear as currency
identifiers in your PeopleSoft documentation. Reference to an ISO country code in your documentation
does not imply that your application includes every ISO country code. The following example is a
country-specific heading: "(FRA) Hiring an Employee."
The PeopleSoft Currency Code table (CURRENCY_CD_TBL) contains sample currency code data. The
Currency Code table is based on ISO Standard 4217, "Codes for the representation of currencies," and
also relies on ISO country codes in the Country table (COUNTRY_TBL). The navigation to the pages
where you maintain currency code and country information depends on which PeopleSoft applications
you are using. To access the pages for maintaining the Currency Code and Country tables, consult the
online help for your applications for more information.
Region Identifiers
Regions are identified by the region name. The following region identifiers may appear in the PeopleSoft
Online Help:
• Asia Pacific
• Europe
• Latin America
• North America
Industry Identifiers
Industries are identified by the industry name or by an abbreviation for that industry. The following
industry identifiers may appear in the PeopleSoft Online Help:
My Oracle Support
Contact Us
Send your suggestions to psoft-infodev_us@oracle.com.
Please include the applications update image or PeopleTools release that you’re using.
Follow Us
Icon Link
Follow @PeopleSoft_Info on X.
From PeopleTools 8.62, the usage monitoring of data is extended to the Process Scheduler and
Application Engine servers.
The data collected by the Usage Monitor for managed objects such as pages, components, and
PeopleCode enables administrators to more accurately understand what definitions in the database are
used in their environment. This information can assist with impact analysis when applying updates or
change packages. Usage Monitor information for managed objects can also be used in conjunction with
the PeopleSoft Test Framework and (or) the LCM Insights feature.
The data collected by the Usage Monitor for ADS objects enables users to understand what ADS
instances are most used in their environment and can assist in impact analysis of how the change package
may modify any used ADS instance in their environment.
See “Application Data Set Overview” (Lifecycle Management Guide) and Enabling Usage Monitor
You can enable usage data collection on the Usage Monitoring Options page. See Enabling Usage
Monitor.
Navigation:
PeopleTools > Lifecycle Tools > Usage Monitoring > Usage Monitoring Options.
By default, this option is not selected. After selecting this option, ensure to restart the application server.
This example illustrates the fields and controls on the Usage Monitoring Options page.You can find
definitions for the fields and controls later on this page.
For example, if you have ten users who use the same ten
objects, then:
Enable Managed Object Usage Monitoring Select to enable the Usage Monitor for managed objects
accessed through application server, Process Scheduler server,
and Application Engine server.
Managed Object Buffer Size Set the buffer limit which determines how much data should
be collected in the buffer before storing the data in the
database. Depending on the pages that are accessed and your
testing needs, you can arrive at an optimum buffer size for
your usage pattern.
Determining the optimal value for the buffer size will likely
take some adjustment once usage collection is up and running
and the volume of data being collected is better known.
If the Buffer Size value is set too high, the buffer may never
fill, causing the process to write collected data to the database
only during the server shutdown event.
Enable ADS Usage Monitoring Select to enable the Usage Monitor for ADS instances
accessed through application server, Process Scheduler server,
and Application Engine server.
The use cases for ADS usage collection include General usage
data collection for custom applications.
The list of ADS instances that are monitored and recorded will
be those identified in the PSADSTRACKITEM PeopleTools
table.
ADS Buffer Size Set the buffer limit which determines how much data should
be collected in the buffer before storing the data in the
database. Depending on the ADS instances that are accessed,
you can arrive at an optimum buffer size for usage pattern.
Determining the optimal value for the buffer size will likely
take some adjustment once usage collection is up and running
and the volume of data being collected is better known.
• Collection mode.
If the Buffer Size value is set too high, the buffer may never
fill, causing the process to write collected data to the database
only during the server shutdown event.
Set Process Names and Process ID for Test Name and Test When you select this option, the process name and process
Case Name ID details get recorded for the usage data monitored by
Application Engine server and Process Scheduler server.
After <N> days N specifies the retention period or the number of days
during which the Usage Monitor data remains in the
PSPTUMPMTAGR table.
Purge Managed Object Data Usage Monitor managed object data older than the retention
period gets deleted when you click the Purge Managed Object
Data button.
Purge ADS Data ADS instance data older than the retention period gets deleted
when you click the Purge ADS Data button.
1. On the Usage Monitoring Options page, set the Managed Object (MO) buffer size to 50.
Note: Until the Buffer Size value is reached, no Usage Monitor data will be written to the database.
Important! This buffer value of 50 is only for verifying the Usage Monitor configuration, ensuring
that data will be quickly written to the Usage Monitor tables. When you are using the Usage Monitor,
you need to increase the Buffer Size value to a more appropriate "production" value. The default is
2500. Refer to the documentation of Managed Object Buffer Size given in the preceding table.
2. Shutdown and restart the application server domain and the PeopleSoft Internet Architecture.
3. Login to that application with your browser and navigate through a few pages and menus in the
application.
4. With your SQL query tool, submit the following query on the monitoring database for managed
objects:
SELECT * FROM PSPTUMPMTAGR
Note: The Usage Monitor managed object data is collected and stored in the PSPTUMPMTAGR
table.
With your SQL query tool, submit the following query on the monitoring database for ADS instances:
SELECT * FROM PS_PTUMADSAGR
Note: The Usage Monitor ADS instance data is collected and stored in the PS_PTUMADSAGR table.
5. Verify that data is present in the table and that the timestamps correspond to the time you verified the
Usage Monitor configuration.
6. Repeat the previous steps when setting the Buffer Size value to your production value.
To associate a test name and test case with usage monitoring managed object data and ADS instance data,
use the Test Usage Monitoring page. This can help to sort the generated usage data, especially for usage
data for PeopleSoft Test Framework tests. As of now, this is only an option when data is collected using
the By UserID option.
PeopleTools > LifeCycle Tools > Usage Monitoring > Test Usage Monitoring.
This example illustrates the fields and controls on the Test Usage Monitoring page to test usage
monitoring for managed objects and ADS instances.
Enter a Test Name and Test Case value to associate specific usage data with individual tests and test
cases.
To view the data collected during the test, you can use the Test Name and Test Case value to retrieve
information specific to a particular test case.
Where PTTST_NAME is the Test Name value, and PTTST_CASE_NAME is the Test Case value.
For this integration, we need to enable Managed Object usage monitoring and use the By UserID data
collection option.
In the PeopleSoft Test Framework (PTF), a test coverage report for managed objects correlates
PeopleTools project data with PTF test metadata to identify components, menus, pages, records and fields
that are referenced in PTF tests. When used in conjunction with Usage Monitor, test coverage correlations
can be extended to include information on all definitions (including PeopleCode, Application Engine
programs, and so on) from a usage perspective. A test coverage report identifies which managed objects
included in the change project are referenced by which PTF test. Definitions included in the change
project that are not referenced in the PTF test metadata or Usage Monitor data appears in the report
identified as a coverage gap.
For this integration, we need to enable Managed Object usage monitoring and use the Anonymous data
collection option.
In LCM Insights, the usage data combines with the customization data to provide information such as the
percentage of customizations in the environment, details of which customizations are used and which are
not.
This information helps to identify the customized objects that are regularly impacted by application
maintenance.