Overview

DirX Identity uses TIBCO JasperReports library, “the world’s most popular open source reporting engine” [https://community.jaspersoft.com/project/jasperreports-library] for generating reports on DirX Identity domain entries. It’s the same library that DirX Audit uses for generating its reports. The library can produce pixel-perfect documents including charts of different types and export them in a variety of document formats including HTML, PDF, Excel, CSV, OpenOffice and Word.

For the report design, you can use TIBCO Jaspersoft^® Studio. It presents a graphical user interface and supports you in the layout of visual components, using lots of chart types (most important: bar and pie charts), integrating images and maps, writing complex expressions and integrating subreports to display, for example, the list of roles a user has assigned.

The JasperReports library provides a set of built-in Java functions for evaluating object attributes and producing nice output, for example, for date formats. DirX Identity provides additional utility methods intended to handle situations specific to DirX Identity entries and attributes.

The product supports internationalization. You can display texts and labels in any language and print, for example, dates in language specific format.

The JasperReports library and similar reporting tools are mainly built and described for producing reports on data stored in relational SQL databases. DirX Identity provides a custom data source implementation that lets the Jasper reporting engine fill the reports from DirX Identity Service layer objects (SvcUser, etc.) and especially leverages the use of “virtual attributes”; for example, to retrieve the roles of a user by requesting the attribute “roles_assigned”.

You can produce a report from DirX Identity Web Center, DirX Identity Manager, a DirX Identity workflow and during report design with a command line tool. Unfortunately, it is not possible to run a report from within Jaspersoft Studio: we were not able to solve the class loader problems related to the storage LDAP URLs.

The report and subreport templates are expected to be stored in LDAP entries, the same entries and folders where the classic XSLT-based report definitions are stored. Also, the other artifacts like the referenced images, the styles, and the internationalization messages are held in LDAP. For designing and testing a new report, all the artifacts can be held in local files. When finished, command line tools help you to import them to LDAP.

Find pdf samples of generated reports in folder Additions/SampleReports of the product installation media.