Running Audit Report fails with error "Group does not exist: JasperserverDataSource_JASPERSERVER.JITENANT AS jitenant"

Issue:

Users can experience the following issues in TIBCO JasperReports® Server v8.0.0:

(1) While running Audit Report, the following error occurs:

Error Message
com.jaspersoft.jasperserver.api.CacheDatasetException: exception getting dataset from cache

(2) While creating an Ad Hoc View from domain "Audit Domain" or "Audit Archive Domain", the "Loading" dialog box appears for a long time before getting "Group does not exist: JasperserverDataSource_JASPERSERVER.JITENANT AS jitenant" error. 

In both use cases, the jasperserver.log records the following errors:

Caused by: org.teiid.api.exception.query.QueryResolverException: Group does not exist: JasperserverDataSource_JASPERSERVER.JITENANT AS jitenant
    at org.teiid.query.resolver.util.ResolverUtil.handleUnresolvedGroup(ResolverUtil.java:880)
    at org.teiid.query.resolver.util.ResolverUtil.resolveGroup(ResolverUtil.java:959)
    at org.teiid.query.resolver.command.SimpleQueryResolver$QueryResolverVisitor.visit(SimpleQueryResolver.java:266)

The environment runs Oracle as the repository database installed using a default_master.properties configured in a way that resulted in the repository database name not being the default 'jasperserver'.

Solution:

This has been reported as a defect with the following incident reference:

JS-61809: Get error running audit report when jasperserver DB is not jasperserver

Until the above defect is formally fixed, the workaround is to modify the Audit and Audit Archive domains to reference the actual repository database name which is not in the default name of 'jasperserver'.

Workaround:

Part 1 - Adding a server attribute to reference the non-jasperserver repository database name

1> Login as superuser and navigate to Manage -> Server Settings -> Server Attributes

2> Add "repositoryDB" to the Name and <the actual name of your repository database> to the Value and click Save

Part 2: Modify the Audit Domain xml to reference the above attribute

1> Navigate to Public -> Audit -> Audit Domains

2> Right Click on Audit Domain and select Export and export to AuditDomain.zip (with Legacy Key option)

3> Extract the AuditDomain.zip content files to folder AuditDomain

4> CD (Change directory) into AuditDomainresourcespublicauditdomainsAuditDomain_files folder and  edit file AuditDomain_schema.data using a text editor (eg notepad++). 

Modify the following (located between lines 13 and 15):

from:

       <entry key="JasperserverDataSource_JASPERSERVER">
          <string>JasperserverDataSource_JASPERSERVER</string>
        </entry>

to:

        <entry key="JasperserverDataSource_JASPERSERVER">
          <string>JasperserverDataSource_{attribute('repositoryDB')}</string>
        </entry>

Save file AuditDomain_schema.data

5> CD into AuditDomain folder and using a zip compression tool (eg 7zip), select all folders and files (resources and index.xml) and archive into AuditDomain_fix.zip

Note: If the archiving is done correctly, the root level of the AuditDomain_fix.zip should contain resources folder and index.xml.

6> In the TIBCO JasperReports® Server UI, navigate to Manage -> Server Settings and click on Import

Select the AuditDomain_fix.zip file to Import as well as "Legacy Key" option and ensure "Update" option remains checked, then click on Import. 

7> Repeat above steps 1 to 6 for the Audit Archive Domain saving the exported file to AuditArchiveDomain.zip instead

After the above steps are done, users should be able to run the Audit reports including the Audit Archive report. Users should also be able to create Ad Hoc Views based off the Audit and Audit Archive Domains without errors. 

ref: 02096591