The WEB pages mentioned in this article are Java JSP pages.

1. Environment configurations

1.1 Configuring raqsoftConfig.xml

raqsoftConfig.xml is used for configuring the data source(s) used by the report, report design file deployment location, and other information. We can find the file in config directory under ReportLite installation directory and modify the configurations as needed. For example:

<?xml version="1.0" encoding="UTF-8"?>
<Config Version="2">
    <Runtime>
        <DBList encryptLevel="0">
            <DB name="demo">
                <property name="url" value="jdbc:hsqldb:hsql://127.0.0.1/demo" />
                <property name="driver" value="org.hsqldb.jdbcDriver" />
                <property name="type" value="13" />
                <property name="user" value="sa" />
                <property name="password" />
                <property name="batchSize" value="1000" />
                <property name="autoConnect" value="true" />
                <property name="useSchema" value="false" />
                <property name="addTilde" value="false" />
                <property name="dbCharset" value="UTF-8" />
                <property name="clientCharset" value="UTF-8" />
                <property name="needTransContent" value="false" />
                <property name="needTransSentence" value="false" />
                <property name="caseSentence" value="false" />
            </DB>
        </DBList>
        <esProc>
            <charSet/>
            <splPathList>
                <splPath></splPath>
            </splPathList>
            <dateFormat>yyyy-MM-dd</dateFormat>
            <timeFormat>HH🇲🇲ss</timeFormat>
            <dateTimeFormat>yyyy-MM-dd HH🇲🇲ss</dateTimeFormat>
            <mainPath/>
            <tempPath/>
            <bufSize>65536</bufSize>
            <parallelNum>1</parallelNum>
            <cursorParallelNum>1</cursorParallelNum>
            <blockSize/>
            <nullStrings>nan,null,n/a</nullStrings>
            <fetchCount/>
            <extLibsPath/>
            <customFunctionFile/>
        </esProc>
        <Report>
            <reportSerialNo/>
            <home>WEB-INF/reports</home>
            <styleConfig></styleConfig>
            <NaNDisp>NaN</NaNDisp>
            <useOldRule>false</useOldRule>
            <defPaletteName/>
            <defPaletteScope>0</defPaletteScope>
        </Report>
    </Runtime>
</Config>

Under the <DBList> node, configure the list of data sources to be used by the report. Its subnode <DB> is a JDBC data source, where an HSQL source named demo is specified. Property “driver” is the database JDBC driver class name, “url” is the path for accessing the database, and “user” and “password” are username and password for connecting to the database.

Under <esProc> node, there are esProc data source configurations. The configurations can be skipped if the data source won’t be used.

Under <Report> node, <home> is report design file deployment directory, which can be an absolute path or a relative path that is relative to WEB application’s root directory. In the above sample configurations, WEB-INF/reports means that the report file is deployed in reports subdirectory of WEB-INF under WEB application’s root directory.

Find information of the other nodes in ReportLite documentation.

1.2 Configuring web.xml

In web.xml, configure report system initialization under <servlet> and report display under <taglib>. For example:

<servlet>
    <servlet-name>reportServlet</servlet-name>
    <servlet-class>com.raqsoft.reportl.view.ReportLiteServlet</servlet-class>
    <init-param>
        <param-name>configFile</param-name>
        <param-value>/WEB-INF/raqsoftConfig.xml</param-value>
    </init-param>
    <load-on-startup>1</load-on-startup>
</servlet>
  
<servlet-mapping>
    <servlet-name>reportServlet</servlet-name>
    <url-pattern>/reportServlet</url-pattern>
</servlet-mapping>

<taglib>
    <taglib-uri>/WEB-INF/raqsoftReportLite.tld</taglib-uri>
    <taglib-location>/WEB-INF/raqsoftReportLite.tld</taglib-location>
</taglib>

com.raqsoft.reportl.view.ReportLiteServlet class is configured when ReportLite reporting system loads file raqsoftConfig.xml explained in the previous section at WEB application startup. Parameter configFile specifies the configuration file’s deployment location, which can be an absolute path or a relative path that is relative to the WEB application’s root directory.

raqsoftReportLite.tld is the taglib configuration file for displaying the report. It can be copied from ReportLite installation directory’s web directory to WEB-INF directory.

1.3 Deploying jars

Deploy jars of the ReportLite reporting system and the jars of JDBC data source used by the report in WEB-INF/lib directory.

reportlite.jar, esproc-bin-xxxxxxxx.jar and icu4j-60.3.jar are the jars ReportLite uses. They can be copied from ReportLite installation directory’s lib directory.

2. Displaying the report

Use the following statement to import the taglib file into the JSP page:

<%@ taglib uri="/WEB-INF/raqsoftReportLite.tld" prefix="report" %>

Write tags for displaying the report in the page:

<div id=reportContainer style="text-align:center">
    <report:html name="report1" reportFileName="order.rptx"
        params="beginId=10248;endId=10258"
        exceptionPage="myError.jsp"
    />
</div>

“name” is the tag name, which can be freely specified under the JasvaScript naming rule – except that it is of one of the existing tag names in the current page. “reportFileName” is the report design file path, which is relative to the directory configured in raqsoftConfig.xml’s <home> node. “params” specifies parameter values used in the report computation, and can be skipped when no parameters are used; its format is “paramName1=value1; paramName2=value2;……”. “exceptionPage” is path of the page displaying error messages appearing during executing the tags; the path is relative to the directory accommodating the JSP page displaying the report.

Refer to showReport.jsp and myyError.jsp in ReportLite installation directory’s web directory.