QXchange is architected for robustness and ease of use. The use of profiles allows the preservation of integration instructions and reuse. The user interface is largely designed to be a profile manager to manage the setup of these instructions.

The different data formats and application types are segregated from the core application and made into plug-and-play modular entities called Data Access Plug-ins (DAP). Internally the DAPs understand the unique nature and constraints of the particular application or data format, but the DAP presents a similar interface back to the engine and the user interface. This minimizes complexity for the user. It also allows the easy addition of additional DAPs to the system.

The execution engine is the controlling entity for the entire tool. It uses the profile as the instruction set and calls on appropriate modules to execute the data integration tasks. The execution engine has three sections, extraction, transformation and loading .Extraction and Loading can both call on the DAP modules to access the specific data format in consideration. The transformation module can use the Data Conversion Plug-in to do additional data conversions than is already available in the tool. An internal staging data set is used for data conversions.

A scheduling module allows the selection of a single or a set of profiles to be executed at a specific time, in addition to on-demand. Scheduling can be one-time or recurring.

Architecture