Getting a net.sf.jasperreports.engine.JRRuntimeException When Importing a Report Unit

The Problem

A user is getting the following error when importing a report unit into a new JasperReports Server (JRS) repository:

ERROR Digester:1132 - End event threw exception java.lang.reflect.InvocationTargetException
............
Caused by: net.sf.jasperreports.engine.JRRuntimeException: No query executer factory registered for the ......

This report unit works perfectly in the JRS instance from which the exported repo content file was generated without any problem.

The Cause

This user  uses  their own custom SQL executor class to extend their Oracle PL/SQL function for additional processes before and after the query operations. This user is asking why js-import utility needs the custom class since it "is only applicable at report run time".

JRS import utility process does make a minimum audition on resources for various reasons and this custom class method used in the report execution is indeed needed to pass the import audit to ensure the report unit is correctly deployed with all the integrated components.

The Solution

This user needs to add their custom component jar file containing the missing class to their new JRS deployment before running the import in order to migrate the reports unit successfully.

For command line import utility, user needs to add the jar to:

buildomaticconf_sourceieProlib

For running the import in JRS web UI, user needs to add the jar to:

jasperserver-proWEB-INFlib

=================================================

TTC-20210831-2045704