Accessing report files

Read(156) Label: report, rpx, report5cli,

esProc can import and export RPX reports via the Report5Cli external library. Below is how to deploy the external library:

 

1. Configuring jars

Copy the following jars from the report designer class path (installation directory\ report5\web\webapps\demo\WEB-INF\lib) into the esProc class path (installation directory\esProc\lib). The Raqsoft core jar for this external library is Report5Cli.jar.

htmlparser-1.6.jar

pdfbox-1.8.14.jar

jsobject.jar

mail.jar

raqsoftReport.jar

commons-codec-1.3.jar

Note: The Report5Cli external library requires the following embedded third-party jars. There’s no need to deploy these jars manually.

batik-anim.jar

batik-awt-util.jar

batik-bridge.jar

batik-codec.jar

batik-css.jar

batik-dom.jar

batik-ext.jar

batik-extension.jar

batik-gui-util.jar

batik-gvt.jar

batik-parser.jar

batik-script.jar

batik-svg-dom.jar

batik-svggen.jar

batik-swing.jar

batik-transcoder.jar

batik-util.jar

batik-xml.jar

poi-3.16.jar

poi-excelant-3.16.jar

poi-ooxml-3.16.jar

poi-ooxml-schemas-3.16.jar

poi-scratchpad-3.16.jar

 

2. Configuring data source

If the to-be-retrieved report involves a data source, esProc needs configuring a namesake data source that has the same structure. If the report doesn’t configure a data source, just ignore this step.

 

3. Configuring raqsoftConfig.xml

Add the following nodes after the <Esproc> node in esProc’s raqsoftConfig.xml file:

<Report>

<license> </license>  // Report license configuration

<home> </home>  // Report main directory configuration

<styleConfig> </styleConfig>  // Report style configuration

</Report>

The <license> node points to the report license file’s absolute or relative path. The report license information must be configured and thus this node shouldn’t be left blank.

The <home> node points to the report’s default storage directory, and can be left blank. It is valid only when retrieving a report through a relative path. It is ineffective when retrieving the report through an absolute path.

The <styleConfig> node configures the path to the report style file. It can be left blank.

esProc also allows reading the report’s configuration file \config\raqsoftConfig.xml through an absolute path. This way esProc’s \config\raqsoftConfig.xml file doesn’t need to be modified.

To perform the dfx file from the command line, users need to set the value of autoConnect property for connecting to the data source in the raqsoftConfig.xml file as true; otherwise the data source can’t be found.

 

4. esProc provides a number of external library functions, including report_config(),  report_open(), report_run() and so on, to access report files. Look up them inHelp-Function referenceto find the uses. When the to-be-retrieved report connects to a data source, esProc needs to configure the data source connection where the data source name should be the same as that configured in the report.

Note: For the time being, the report file access functionality doesn’t support big reports, report populating, report group and parameter form.