This way a single JasperReportsIntegration can be secured and used
simultaneously by different applications. Using this token approach we
can prohibit application A from using the data source for application
A token will be stored in the schema issueing a reporting request.
The token will be passed to the JasperReportsIntegration.
Before executing the request, the integration will validate
the token using the requested data source with a verification function.
Disabling testing / debugging for production systems
New setting in application.properties to disable the report tester
New setting in application.properties to disable the basic connectivity test (will tell you the installed user objects)
Deploying new reports directly from your APEX application or a shell script
New report definition files (report.rxml) can be deployed to
the JasperReportsIntegration directly without the need to copy the
files to the application server manually.