Previous Topic
Auditing on Exporting, Printing, and Saving of Reports
You can make use of the two callback APIs - jet.bean.ReportCallback and jet.bean.CallbackInfo - to get the event and user information when a user exports, prints, or saves a report in Designer. The information includes the event (Export, Print, or Save), the time when the event occurs, the report ID, the user name who performs the operation, the parameters and values that are used to run the report if there are any, and the file name that the report is exported to or saved to. This topic describes how to implement the APIs to audit the Export, Print, and Save operations on reports.
- Write a class, for instance, com.yourcompany.callback.CustomCallback, to implement the callback interface jet.bean.ReportCallback.
- Put the class into the
<install_root>\libdirectory of Designer. - Apply the class by adding the following JVM system property in the Designer startup file, JReport.bat/JReport.sh, which is stored in
<install_root>\lib.-Djreport.callback.class=com.yourcompany.callback.CustomCallback - Designer calls your implementation right after a user exports, prints, or saves a report, and passes the information related to the operation to you.