...
An HTTP Exporter exports data held in a Stream to a HTTP Datasource.
For an overview of how HTTP Exporters can be used when creating models, see Exporting Data to HTTP.
Form: HTTP Exporter Details
...
| Field | Description |
|---|---|
| Check if the response indicates successful export | Expression to evaluate the response from the HTTP datasource, where a connection was made. countElements($errors = xmlToItems(_response,"//ERROR")) == 0 |
| Result to record on the Stream | Expression to evaluate the value to put on the stream. if(_success, _response, listToString($errors._MSGTEXT)) |
| Result to record on the Stream after a connection failure | Value to put on the Stream in the event that the HTTP connection attempt failed. _error |
...
| Parallel Exporters | If required, you can specify that the exporter should use a number of parallel exporters. Each buffer of records read from the input pipe will be divided across the parallel exporters. The restriction applied to this is that if Group By fields are specified in the input Pipe to the exporter, all records with the same Group By key will be exported by the same exporter. If no value is specified here then only a single exporter will be used. |
| Commit Size | Tells the exporter to commit records in batches of the specified size. |
| Timeout (secs) | Tells the exporter to timeout each export operation after a number of seconds. If an export operation does time out, the operation will be abandoned and an error will be reported. Each record that is timed out is considered to be a single error when assessing whether the entire export should be stopped and/or rolled back - see Errors Before Rollback below. If no value is specified, the duration of an export operation is unlimited. |
| Errors Before Rollback | If required, you can set the maximum number of errors found, while exporting across all exporters, before the exporter will rollback all uncommitted transactions from all exporters. If no value is specified, the exporter will never rollback, no matter how many errors are found. If 1 is specified, a single error will cause a rollback. |
| Errors Before Stopping | If required, you can set the maximum number of errors found, while exporting across all exporters, before the exporter will stop attempting to export records to the datasource. This is useful where you have set Errors Before Rollback (also configured on this tab), but wish to continue to try to export records to get view of how successful the remaining export would have been. Any records that the exporter attempts to export after the Errors Before Rollback limit has been passed will always be rolled back, even if they are successful. If no value is entered, the exporter will stop when the Errors Before Rollback limit is reached. |
| Icon | Path name for image file. |
| Input Multiplier | This expression works in the same way as the Input Multiplier Expressions on Streams and Database Exporters. A complete export is carried out for each value in the list of values returned by the Input Multiplier Expression. If the Input Multiplier Expression evaluates to an empty list then no export will be carried out. If no Input Multiplier Expression is set, a single export will be carried out. |
| Datasource Instance Expression | The target datasource for this exporter may list multiple HTTP Datasource instances. Each datasource instance is identified by a unique string. This expression should evaluate to a string which allows the HTTP Exporter to determine the instance to use. If no value is entered then the exporter will assume that there is only one instance and will use that one by default. If there is more than one instance and no expression is provided here then an error will be thrown during analysis. |
See Also