Users Create Ad Hoc views interactively in the Ad Hoc Editor by dragging and dropping columns of data onto a table, chart, or crosstab. Users can then explore their data by applying filters and performing pivot operations. An Ad Hoc view can also be saved as an interactive report and shared with other users.

A collection of reports, input controls, graphics, labels, and web content displayed together. Users create dashboards interactively in the Dashboard Designer and save them in the repository.

A metadata layer that selects, joins, and filters tables and fields from your data. A Domain can be the basis for an Ad Hoc report. Domains also support row-level security and localization of labels. Only administrators may create Domains. Domains are further documented in the JasperReports Server Data Management Using Domains.

A report or Domain that has been prepared for use in creating Ad Hoc views. Topics filter and select the fields that are available in the Ad Hoc Editor. Topics are stored in the Ad Hoc Components/Topics folder; they are further documented in the JasperReports Server User Guide.

A JasperReport combines a JRXML file, a data source, and optional components such as input controls. Depending on the use case, both users and administrators create JasperReports in the server. For more information, see JasperReport Structure. Procedures for adding reports to the server are described in the JasperReports Server User Guide.

Reports with input controls allow you to save combinations of input values so that you can run the report again directly. In the repository, report options are always listed under the original report.

Report output of any format, either from running a report in the background or from scheduling a report. A content resource is a simple file that the repository allows users to view or download.

A connection that points to a database or other data store. Data sources define where data is stored for reporting. There are several types of data sources, based on the type of connection or location of the data: JDBC, JNDI, and several others. Only administrators may create data sources. For more information, see Data Sources.

A database query string, for example in SQL. The JRXML doesn't necessarily include the query, in which case, you must define a query resource for use in the JasperReport.

A complex type that specifies the values users can input for a report and how the input field appears when running the report, for example radio buttons or check boxes. Input controls depend on datatypes or lists of values to specify the format of the input.

A basic resource that defines the format for input values, for example text, number, or date. A datatype may also specify a valid range for the input value.

A basic resource that defines a list of arbitrary labels for input. Each label is associated with a value that can correspond to your data. For example, the Month Names List in the sample data associates the name of each month with a value 1 to 12.

A server-side XMLA source definition of a remote client-side XML/A connection.

Specifies how to retrieve data for an OLAP view. An OLAP client connection is either a direct Java connection (Mondrian connection) or an XML-based API connection
(XML/A connection).