Exports are based on export definitions. An export definition is basically a collection of settings that advice the Redbex Application Server what data shall be exported and how the data shall be exported. Each export definition is based on one of the supported export types.

Export definitions can be created on-the-fly or can be persisted as stored export definitions within a domain. On-the-fly export definitions are created and executed but the export definition itself is then not persisted. They are best used if you want to export specific data once. Stored export definitions are export definitions that are persisted on the Application Server. You will typically create stored export definitions when you intend to repeatedly execute that export definition or when you plan to automate export using a stored job definition.

An export definition consists of:

•The underlying export type

•Common Settings: Specification of settings common to all export types

•Type specific settings (1): Specification of settings specific to the chosen export type (see documentation of the used export type for details). Type specific settings (1) is a UConfiguration.

•Type specific settings (2): Specification of settings specific to the chosen export type (see documentation of the used export type for details).

•Specification of an observation filter (only available for specific export types)

•Settings for stored export definitions