See autoarchive.

In Metrics Management, the user assigned as the owner of an object. By default, the object owner is the user or group who created the object. The object has security settings specific to the object owner.

In Metrics Management, the structure of an object that constrains its characteristics, such as properties and permitted operations. For example, location is an object type, and UK and South America are specific location objects.

In Metrics Management, a set of security permissions defined at the object level. A system specialist or object owner defines object-level security. Acting on an object requires both the appropriate privileges and security settings.

See open data access (ODA).

See synchronous.

An application programming interface (API) that provides a Simple Object Access Protocol (SOAP)-based interface between BIRT iHub and external archive software.

A technology that handles communication between a data source and an application, providing interfaces for creating data drivers to establish connections, access metadata, and execute queries to retrieve data. The Eclipse Data Tools Project plug‑ins provide ODA to Actuate BIRT technology. BIRT iHub System and the Information Object Design perspective can use Eclipse plug-ins to implement ODA capability.

An ODA driver communicates between a data source and an application. An ODA driver establishes a connection to a data source, accesses metadata about the data, and executes queries on the data source. In Actuate BIRT technology, ODA drivers are plug‑in extensions to the Eclipse Data Tools Platform project. BIRT iHub System and BIRT Designer Professional can use ODA drivers implemented as an Eclipse plug‑in to the Data Tools Platform project.

See server processes.

In Metrics Management, the mathematical order of operation used to calculate performance across measures, locations, and periods.

A type of join that returns records from one table even when no matching values exist in the other table. The three types of outer join are left, right, and full outer join. A left outer join returns all records from the table on the left side of the join expression, even if no matching values exist in the table on the right side. A right outer join returns all records from the table on the right side of the join expression, even if no matching values exist in the table on the left side. For example, joining customers and orders tables on customerID with the customers table on the left side of the expression returns a result set that contains all customer records, including customers who have no orders. A full outer join is the union of the result sets of both left and right outer joins.

An Eclipse view that shows all report elements in a report design, report library, or report template. Outline shows the report elements’ containment hierarchy in a tree-structured diagram.

See object owner.