Handling Usage Monitor Data
From PeopleTools 8.60, Usage Monitor data is fetched from different databases and stored in the PUM Usage Monitor table.
When users upload usage data to PUM source, relevant details are added to the PUM Usage Monitor table.
Usage flags are introduced in this table to indicate the usage of Usage Monitor.
|
Flag Value |
Use |
|---|---|
|
X |
Default value, and it indicates that the Usage Monitor is not in use. |
|
Y |
This value is used when user uploads usage data in PUM source and Bug Calculation for Usage Monitor data is not done. |
|
N |
This value is used when user uploads usage data in PUM source and Bug Calculation for Usage Monitor data is done. |
Uploading Usage Data Using Integration Broker
The Usage Monitor data fetched from different databases are uploaded to the PUM Usage Monitor table through the Integration Broker.
To upload the data through Integration Broker, first the PUM source invokes the Usage Instance through REST based APIs.
The APIs import the usage monitor information, which then gets populated into the PUM Usage Monitor table.
You can define a database that can act as a Usage Instance. To define, set the orientation as Usage Monitor in the Define Database page (Update Manager, Administer Metadata, Manage Database).
For details, refer to Defining and Managing Databases Using Update Manager.
Next, users can define an activity of type Synch Usage Repository to fetch the information from this Usage Instance database. You can define this activity on the Define Activity page (Update Manager, Administer Metadata, Manage Activities).
For details, refer to Defining and Managing Database Activities.
Usage History Table
The usage history table maintains information of the database from which Usage Monitor data is imported.
When Usage Monitor data is fetched from any database for the first time, the usage history table populates the data against that database with last update time value as time of upload.
For the subsequent run, the system verifies if the data exists for that database in the usage history table. If the data exists, then it imports the Usage Monitor data collected after the last update time of the history table and this table will be updated with the latest last update time value. Basically, only the latest data is fetched in subsequent runs.