Reporting module is an optional component, build on top of well known JasperReports library, which can produce pixel-perfect documents in variety of formats based on historical data collected by NetXMS.

Reporting module consist of two main parts: user interface and standalone Reporting Server, which handles all scheduling, execution, and optional document delivery to end users.

Report generation is two step process: first step is to collect and process input data, then render output files in desired format. This separation exist for a reason: unlike rendering step, data collection could take hours to complete and it make no sense to repeat same processing process to render Excel file instead of PDF. When first step is finished, all processed information is saved into intermediate file on the reporting server and available for rendering at any time (e.g. user can render and download report from last year, even if source data is already purged).

Reports execution and rendering can be initiated both manually and on schedule.

User Interface

All reporting-related operations are available in separate Reporting perspective. Perspective contains two main areas – list of available reports on the left and report details view on the right. Details view show information about currently selected report.


Reporting perspective.

Details view contains tree main areas: Parameters, Schedules, and Results.



Execution parameters for report (in this example: Start date)

In this section, user can set all input parameters required for report execution, for example data range or list of objects which should be included in the report. List of required parameters is extracted from report definition file and can be empty, if particular report do not require any input data to operate.


Each report can have one or more schedules, which define when it should be executed, and optionally rendered. Reporting server can also notify users that new report is executed and available for download, or send resulting file as an attachment.


List of scheduled executions

To add new schedule, click on Add Schedule down below, this will open schedule editor.


Schedule editor with two tabs, General and Notifications

General tab contains four scheduling options:

  1. Once - execute report once at specified date and time
  2. Daily - execute report every day at specified time
  3. Weekly - execute report every week on selected days of week at specified time
  4. Monthly - execute report every month on selected days at specified time

Notifications tab of Schedule editor

Notification tab allows to control email notifications and report delivery to list of recipients. To enable notifications, select Send notification on job completion checkbox.

If checkbox Attach rendered report checkbox is enabled, report will be rendered into selected format and attached to notification email.

Results section


List of generated reports

This section contains list of all generated reports, which are stored on the server and can be rendered on request. To render report in desired format, right click on the record and select Render to PDF or Render to Excel.

If report is no longer needed, right click on record and select Delete to completely remove it from server.


NetXMS Server

NetXMS server maintain persistent connection with reporting server on localhost:4710, but if can be changed in configuration.

Configuration Parameter Description Default Value
EnableReportingServer Boolean on/off switch which enable integration 0
ReportingServerHostname IP address or hostname of the reporting server localhost
ReportingServerPort Port number of the reporting server 4710

Reporting Server

Report definitions are loaded from the file system by scanning workspace folder, expected structure: $WORKSPACE/definitions/$REPORT_GUID. Each report folder should contain file main.jrxml, any additional files (images, translation files) should be referenced in main.jrxml with relative paths. Sample directory listing:


Server behaviour is controlled by two files: logback.xml (logger configuration) and

Format of logback.xml is described in Logback manual. is a standard Java property file in key=value format.

Parameter Description
nxreporting.workspace Path to workspace with deployed reports
system.datasource.driverClassName JDBC class name, for example org.postgresql.Driver
system.datasource.url JDBC connection string, for example jdbc:postgresql://
system.datasource.dialect Hibernate dialect, for example org.hibernate.dialect.PostgreSQLDialect. More information in JavaDoc

Access Control

Installation Manual


  1. Unpack into some folder, in this example - /opt/nxreporting

  2. Create directory “conf”

  3. (Optional)Create logger configuration: conf/logback.xml (sample attached), detailed description here:

    <?xml version="1.0" encoding="UTF-8"?>
    <appender name="FILE" class="ch.qos.logback.core.rolling.RollingFileAppender">
        <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy">
        <triggeringPolicy class="ch.qos.logback.core.rolling.SizeBasedTriggeringPolicy">
        <pattern>%d %5p | %t | %-55logger{55} | %m %n</pattern>
  4. Create configuration file for reporting server: conf/nxreporting.xml


    In most cases (when reports are using only single datasource), setting “netxmsdConfig” is enough, database type and credentials will loaded automatically from netxmsd.conf. “netxms” section of the config is required for reports, which load data not from SQL datasource, but using NetXMS API instead (connection is maintained by reporting server).

  5. Create workspace directory (as set by “workspace” parameter), it will contain both report definitions and intermediate report data (in “output” directory).

  6. Put report definition jars into workspace/definitions/:

    AirAlk:~() $ ls -al /opt/nxreporting/workspace/definitions/*.jar
    -rw-r--r--  1 alk  wheel  3729 Mar 11 15:31 /opt/nxreporting/workspace/definitions/alarm-history-1.0.0.jar
    -rw-r--r--  1 alk  wheel  5607 Mar 11 15:31 /opt/nxreporting/workspace/definitions/alarm-resolution-time-1.0.0.jar
    -rw-r--r--  1 alk  wheel  4570 Mar 11 15:31 /opt/nxreporting/workspace/definitions/alarm-resolution-time-statistics-by-users-1.0.0.jar
    -rw-r--r--  1 alk  wheel  4203 Mar 11 15:31 /opt/nxreporting/workspace/definitions/dci-1.0.0.jar
    -rw-r--r--  1 alk  wheel  9968 Mar 11 15:31 /opt/nxreporting/workspace/definitions/epp-1.0.0.jar
  7. Enable reporting server connector, set EnableReportingServer to 1 (either in GUI - server configuration, or using command line: “nxdbmgr set EnableReportingServer 1”), then restart netxmsd.

  8. Create additional tables by executing both scripts from

  9. Start reporting server:

    cd /opt/nxreporting
    java -jar nxreporting-2.0-M2.jar

    When started with “-jar” option, java will automatically find configuration files in conf/ and all libraries in lib/. However, you can run it differently (and omit “cd /opt/nxreporting”):

    java -cp /opt/nxreporting/lib/\*.jar:/opt/nxreporting/conf:/opt/nxreporting/nxreporting-2.0-M2.jar com.radensolutions.reporting.Launcher

    or, if you are running windows:

    java -cp /opt/nxreporting/lib/\*.jar:/opt/nxreporting/conf:/opt/nxreporting/nxreporting-2.0-M2.jar com.radensolutions.reporting.Launcher

    In under 10 seconds, netxmsd should connect to reporting server and list of available reports will be visible in “Reporting” perspective.

Resulting directory structure

total 5728
drwxr-xr-x   6 alk  wheel      204 Apr  7 20:31 .
drwxr-xr-x  14 alk  wheel      476 Apr  3 20:07 ..
drwxr-xr-x   4 alk  wheel      136 Apr  7 20:31 conf
drwxr-xr-x  79 alk  wheel     2686 Jan 23 10:29 lib
-rw-r--r--   1 alk  wheel  2929061 Jan 23 10:29 nxreporting-2.0-M2.jar
drwxr-xr-x   4 alk  wheel      136 Mar 11 15:06 workspace

total 16
drwxr-xr-x  4 alk  wheel   136 Apr  7 20:31 .
drwxr-xr-x  6 alk  wheel   204 Apr  7 20:31 ..
-rw-r--r--  1 alk  wheel  1367 Apr  7 20:21 logback.xml
-rw-r--r--  1 alk  wheel   764 Apr  7 13:21 nxreporting.xml

total 109528

total 0
drwxr-xr-x   4 alk  wheel   136 Mar 11 15:06 .
drwxr-xr-x   6 alk  wheel   204 Apr  7 20:31 ..
drwxr-xr-x  32 alk  wheel  1088 Mar 11 15:43 definitions
drwxr-xr-x   8 alk  wheel   272 Mar 11 15:42 output

total 248
drwxr-xr-x  32 alk  wheel  1088 Mar 11 15:43 .
drwxr-xr-x   4 alk  wheel   136 Mar 11 15:06 ..
-rw-r--r--   1 alk  wheel  3729 Mar 11 15:31 alarm-history-1.0.0.jar
-rw-r--r--   1 alk  wheel  5607 Mar 11 15:31 alarm-resolution-time-1.0.0.jar
-rw-r--r--   1 alk  wheel  4570 Mar 11 15:31 alarm-resolution-time-statistics-by-users-1.0.0.jar

total 0
drwxr-xr-x   8 alk  wheel  272 Mar 11 15:42 .
drwxr-xr-x   4 alk  wheel  136 Mar 11 15:06 ..
drwxr-xr-x   4 alk  wheel  136 Mar 11 15:44 01827cdb-cb23-4b06-b607-fd02c4279add
drwxr-xr-x   4 alk  wheel  136 Mar  7 22:04 52ce4398-a131-4a79-887e-672cc73d5d34
drwxr-xr-x   3 alk  wheel  102 Mar 11 15:44 8a7c025c-84c8-4914-b2bf-3b4cde27a224

Report definitions

On startup, reporting server scan workspace/definitions directory for *.jar files. Each file is unpacked into it’s own folder based on jar name (e.g. “report1.jar” will be unpacked into “report1”). Each archive should contain at least one file – “main.jrxml”, which is main report definition. It can also contain subreports, images – or anything else, supported by Jasper Reports. Any additional resources should be referenced using paths relative to root folder of unpacked report, which is set as addtional paramter “SUBREPORT_DIR” (e.g. “$P{SUBREPORT_DIR}/logo.png”).

Archive can also contain java code, which will be used as data provider (instead of querying SQL database). Reporting server will try to load class “report.DataSource”, which should implement interface “com.radensolutions.reporting.custom.NXCLDataSource” (attached sample: Event Processing Policy). Query string language in jrxml should be set to “nxcl” (default - SQL).

Simplest way to create jar files are using Maven, empty project is provided in samples archive. Running “mvn package” will produce complete jar file in “target” directory.