Data schemes
When you define a new integration definition, you must select from several options or schemes to define the payload, protocol, and transport for the data.
The database scheme uses database tables to import or export data. The file scheme uses files to import or export data. The DataConnect scheme imports files into DataConnect staging tables. The HTTP post scheme exports data with the HTTP protocol.
Database scheme
When you select the inbound database scheme, you must define the data source and the data map. The data map is used to map the data from the external source to existing IBM® TRIRIGA® fields.
When you select the outbound database scheme, you must define the data source and the outbound query. The outbound query is used to define which fields are exported from your IBM TRIRIGA database.
File scheme
When you select the inbound file scheme, you must define the import file and the data map. The data map is used to map the data from the external source to existing IBM TRIRIGA fields.
When you select the outbound file scheme, you must define the export file and the outbound query. The outbound query is used to define which fields are exported from your IBM TRIRIGA database.
DataConnect scheme
When you select the inbound IBM TRIRIGA DataConnect scheme, you must define the data source, the import file, the DataConnect job, and the data map. The data source is used to access the DataConnect staging tables. The data map is used to map the data from the file to the DataConnect staging tables.
With this scheme, you can use workflows to process and validate data, which gives you more control over error handling.
For information about DataConnect, see Application Building for the IBM TRIRIGA Application Platform: Data Management.
HTTP post scheme
When you select the outbound HTTP post scheme, you must define the server to which the data is sent, the outbound query, and the response map. The outbound query is used to define which fields are exported from your IBM TRIRIGA database. The response map is used to map the response parameters from the HTTP request to your existing IBM TRIRIGA fields.