Page History
...
One of the main use cases for this service is to export data using a data mapping from the main application module to a reporting module (both actually Interaction modules) and store this export in a database. An external system can pick up this export, for instance for a data warehouse. Best practices and design considerations with regard to the reporting and sharing of data with other systems can be found in this design guide.
Parameters
Name | Direction | Description | Type | Occurrences | Required |
|---|---|---|---|---|---|
| Connection | Input | Select the connection on which to place the XML export | Connection | Single valued | trueYes |
| DataMapping | Input | Select the data mapping for which the target will be exported (when omitted, the current module will be exported) | Module element DataMapping | Single valued | falseNo |
Exporting
In runtime, the XML profile is exported to the connection, where it is stored as an XML blob in a table called Reports. This table has the following columns:
Column | Type | Description |
|---|---|---|
| Id | Integer | Unique Id of the export |
| Source_application | String | Id of the application where the service was performed (Repository-Branch-Project) |
| Source_service | String | Name of the service that was performed |
| Creation_datetime | Datetime | Exact moment when the service was performed |
| User_name | String | User that was logged in when the service was performed |
| Export_XML | XML Blob | The actual XML |
Events
This service uses default events for a commit and for an exception.
Trace and log
The trace database does not trace the exported data. However, the log file states when the services was called and which datamapping was used.
Configuration
The AQ_Report makes use of the Report SQL Store component. Configuration of this component can be found here, this page also describes how to set up the connection that the service requires.
...
Overview
Content Tools