In a later post we'll extend the request used in Parts 1-3, to highlight performance for individual users. Continuing the license review theme, let's clarify overall exposure.
Set this up from the beginning and a business can witness the growing number of licenses used.
1. A saved filter for the definition of 'Active Users' can be changed without affecting dependent requests, so using the Part 2 definition:
(TIMESTAMPDIFF(SQL_TSI_DAY, MAX("Query Time"."Date"), Current_TimeStamp))
Set this up from the beginning and a business can witness the growing number of licenses used.
1. A saved filter for the definition of 'Active Users' can be changed without affecting dependent requests, so using the Part 2 definition:
(TIMESTAMPDIFF(SQL_TSI_DAY, MAX("Query Time"."Date"), Current_TimeStamp))
a filter will look similar to this...
 |
| From DR. OBI |
- Total Available Licenses
- Remaining Available Licenses (Total Available - # Active Users)
 |
| From DR. OBI |
<HTML TITLE="# of Active Users"># of Named Users</HTML>
Add your total number of licenses using a repository variable, database table updated via writeback or other convenient method of your choosing.
Keen-eyed readers will see I'm using the SampleApp available from Oracle. Usage Tracking is available in the RPD supplied in this bundle, just follow the other steps to setup the required tables.
