The following guide contains a getting started guide if you’re about to implement the Performance Guard integration to CMS. Note that in this context Performance Guard integration is simply a matter of collecting the “Utilization Index”, “Startup time” and “Logon time” and store them in the CMS database.
1) Obtain a new CMS license with Performance Guard integrations enabled
2) Upgrade the CMS system using the CapaInstaller setup wizard and patch the system.
3) Apply the license using the CMS host
Note it is possible to add the newly obtained license after step 3
4) From tools options define settings
Store detailed data specify the number of day’s detailed data should be kept in the database. The replicator service handles the cleanup task which is executed once a day.
Store average data specify the number of day’s average data should be kept in the database. The replicator service handles the cleanup task which is executed once a day.
Store startup/logon data specify the number of day’s startup/logon data should be kept in the database. The replicator service handles the cleanup task which is executed once a day.
Minutes on startup/logon graph specify the maximum minutes on the y axis where startup/logon data is presented.
5) Create a schedule for the computer job “Performance Guard”. The job is responsible for installing the PG agent and collect data. Therefore it is recommended to schedule the job to be run as an always or alternative “once a day job”
6) Add the computer job “Performance Guard” for the desired test group
7) When the test is complete promote the “Performance Guard” job to production
8) Promote the Agent/Agent service to production
9) Repeat step 5 and 6 for production
10) Start collecting data
Detailed data is collected every time the “Perfomance Guard” job is executed. Data is collected by the replicator and visible from the console immediately.
Currently we recognize high utilization as an U-index between 70 and 80.
Average data is a calculated value based on utilization for previous days. The value is collected once a day.
Startup/Logon data is collected when the used has started the computer and logged on. If the user log’s on within 5 minutes after startup the task is visualized as a single bar else it would be illustrated with 2 bars. If the user log’s off/on it is simply the logon time that is reported.
11) Create Utilization, startup and Logon view in CapaInstaller
12) Report on average data.
Using the reporter it is possible to add information about Utilization, logon and startup to standard report.