See privilege.

An extension that produces a report in a specific format. For example, BIRT provides rendering extensions for Adobe PDF, Adobe PostScript, HyperText Markup Language (HTML), Microsoft Excel, Microsoft PowerPoint, and Microsoft Word.

A category of documents that presents formatted and structured content from one or more data sources, such as a database or text file.

An Extensible Markup Language (XML) file that contains the complete description of a report. The report design file describes the structure and organization of the report, the constituent report items, data sets, data sources, and Java and JavaScript event handler code. A report developer uses BIRT Designer Professional or Actuate Report Studio to create the report design file and the BIRT Report Engine processes to create a formatted report.

A binary file that encapsulates the report item identifiers and values, and additional information, such as data rows, pagination, table of contents, and Actuate BIRT technology such as HTML buttons and HTML 5 charts. A report user accesses the document on a volume using Dashboards option or Interactive Viewer option. A report user accesses the document on a file system using Interactive Viewer or Viewer. A report developer provides access to a document on a mobile device using Actuate REST API.

In BIRT Designer Professional and Report Studio, the main window where a report developer designs and previews a report. The report editor supplies the following pages: Extensible Markup Language (XML) source editor, layout editor, master page editor, and script editor.

A visual or non-visual component of a report design. A visual report element, such as a table or a label, is a report item. A non-visual report element, such as a report parameter or a data source, is a logical component. Actuate BIRT technology supports additional report elements, such as HTML 5 charts and the report document data source.

A file that contains instructions for generating a report document.

See server processes.

A report element that is a visual component of a report design. A report item displays content in the report output. For example, a data element displays data from a data set and a table element displays content in rows and columns. Actuate BIRT technology provides support for additional report items, such as HTML 5 charts.

A BIRT extension that a Java developer uses to create a custom report item. For example, HTML 5 charts.

See subreport.

The abstract specification for BIRT technology. The ROM defines the visual and non-visual components of a report. The ROM specification is an Extensible Markup Language (XML) document. The complete ROM specification is at:

The deployment file containing the Report Object Model (ROM) specification that BIRT technology uses to generate and validate a report design.

An Extensible Markup Language (XML) element in the BIRT Report Object Model (ROM) that describes a visual or non-visual component of a report. Visual elements include items appearing in a report such as a label, list, or table element. Non-visual elements include data sets, data sources, and report parameters.

The Extensible Markup Language (XML) schema defining the content, semantics, and structure of the components in the BIRT Report Object Model (ROM). The ROM schema is at:

A report element that enables a user to provide a value as input to the execution of the report. Using a parameter to customize a report provides more focused information to meet specific needs. For example, parameters support selecting sales information by country and city.

See Actuate BIRT iHub.

A BIRT iHub System capability that supports managing user information from an external database or security source, such as a Lightweight Directory Access Protocol (LDAP) directory server. A worked example using this API is part of Actuate BIRT iHub Integration Technology.

A tool that supports designing Actuate BIRT reports without requiring knowledge of SQL (Structured Query Language) or a programming language.

A separately licensed BIRT iHub System option that supports business users who design Actuate BIRT reports. BIRT iHub System options are separately purchased products.

See template.

An Extensible Markup Language (XML) file that contains a reusable design providing a start position for developing a new report, including report elements that support Actuate BIRT technology such as Actuate BIRT data object and report document data sources, HTML buttons, and HTML 5 charts.

A Java EE web application servlet that produces a report from a report design (.rptdesign) file or a report document (.rptdocument) file. When deployed to a Java EE application server, the report viewer servlet makes reports available for viewing over the web. The report viewer servlet is also an active component of the report previewer of BIRT Designer Professional.

In Actuate BIRT technology, a portion of a report that can be embedded in a web page.

A location for rich information storage. In BIRT iHub System, the repository is a volume.

A message that an application sends to perform an action. For example, Information Console sends a request to BIRT iHub to provide the list of items in a folder using the following URI:

In a volume, an action to resubmit a failed scheduled job.

An application file, such as a configuration file, image, library, or template.

A text file that contains the mapping from resource keys to string values for a particular locale. Resource files support producing a report having localized values for label and text elements.

A specification for allocating iHub Factory processes to run designs and generate documents. A Factory process reserved for a resource group can only be used for objects specified to run in that group. For example, iHub routes a design to a synchronous resource group to run the design immediately and an asynchronous resource group to run the design as a scheduled job.

A unique value that maps to a string in a resource file. For example, the resource key, greeting, can map to Hello, Bonjour, and Hola in the resource files for English, French, and Spanish, respectively.

A message containing the result of a requested operation.

See Actuate REST API.

In Metrics Management, a security setting which allows a user to only enter measure commentary or data for specific commentary types, comparatives, or locations.

Data rows from an external data source. For example, the data rows that are returned by a SQL SELECT statement performed on a relational database are a result set. A stored procedure can return one or more result sets.

In a volume, settings that specify how many times and at what intervals to resubmit a failed job.

See outer join.

See user group.

See Report Object Model (ROM).

An expression used to collect data rows into row groups and subgroups in a cross tab element.

A job initiated by a request from Information Console that runs immediately and produces a temporary report document.

The period of time in which a computer program executes. For example, a report executable generates a report during run time.

A job initiated by a request from Information Console that runs immediately and saves its output on a volume.

An expression that calculates a value in one pass through the data rows in a data source. For example, an expression that calculates the sum of all orders in a group of data rows is a running aggregate.

A job currently executing on an iHub volume.