Our developer wanted a way to count the number of hits to his dashboard that was accessible via the 'Public Access' link. IBI verified that the current release we are on 8.10.5M does not track this level of detail for dashboards we requested it as a future product enhancement.

Our 'Work-Around': 11/4/16 -- In the interim, we have instituted a work-around. We have included only one folder which the Public user has access to which is the Dashboard. We then created a script to count the number of 'public signIn SUCCESS' entries in the log and run the script nightly at 11:30 PM and email to the end user using a CRON job. This at least more closely correlates the Public user login with the Dashboard 'hits' since the Dashboard is now the only resource the Public user has access to upon clicking the 'Public Access' link. We are on 64-bit Linux. The script and CRON job are below:

---------


Shell Script details:

#!/bin/bash
clear

#This shell script pulls the number of hits (successful logins) to the Public Access link which houses the IER Dashboard
#in WebFOCUS. With current version (8.10.5M), there is no mechanism to directly report hits to dashboards created within
#WebFOUCS by the developers. The is a work-around for IBI Ticket #161025054 and TAMUC Ticket # INC0294683


echo "$(grep -o "public signIn SUCCESS" audit.log | wc -l) Public link/IER Dashboard Hit(s) generated for $(date)" | mail -s "Public/IER Dashboard Hits" douglas.dodd@tamuc.edu Jeremy.anderson@tamuc.edu

----------
Cron Job:

30 23 * * * /home/CTIS/tangent/PublicHitsDaily.sh

----------

Example Output:

-----Original Message-----
From: Douglas Dodd
Sent: Thursday, November 03, 2016 11:30 PM
To: Jeremy Anderson; Douglas Dodd
Subject: Public/IER Dashboard Hits

23 Public link/IER Dashboard Hit(s) generated for Thu Nov 3 23:30:02 CDT 2016

This message has been edited. Last edited by: ddoddjr,

If you'd like to track hits at the fex level, -INCLUDE the following fex code into whatever procedure is being ran in your dashboard you want to track. The log file will be updated every time something is ran and give you a bit of information about who ran it as well:

-* To reference this file within a procedure you want to log having been ran, type the
-* following at the top of the procedure:
-* "-INCLUDE IBFS:/EDA/EDASERVE/appFolder/thisLogProcedure.fex"

-* Name your log file:
-DEFAULTH &LOG = 'logFileName.log';

-* File maintenance:
-GOTO setname.&fexname.EXIST;
-setname.0
-SET &fexname = IF &FOCFOCEXEC CONTAINS 'ADHOCRQ' THEN 'ADHOCRQ' ELSE TRUNCATE(&FOCFOCEXEC);
-setname.1
-SET &fexname = TRUNCATE( &fexname );

-* Format time output:
-SET &HOUR = EDIT(&TOD, '99$$$$$$');
-SET &MIN = EDIT(&TOD, '$$$99$$$');
-SET &TIME = &HOUR | ':' | &MIN;

-* Location of log file:
FILEDEF LOGFILE DISK \\serverName\sharedFolderName\&LOG (APPEND
-RUN

-* Contents of the record being appended, etc.:
-SET &LOGGED = &DATEMDYY | ' | ' | &TIME | ' | ' | &IBIMR_user | ' | ' | &fexname;
-SET &OUT1 = PUTDDREC('LOGFILE', 7, &LOGGED, &LOGGED.LENGTH, 'I1');
-SET &OUT1 = CLSDDREC('I1');
-End