pfx-api:flush
Â
Properties
Option | Type | Default | Description |
---|---|---|---|
| string | Â | Defines an output target name for the target type header and property. Put here the names of the exchange header and exchange property. |
| string |  | Defines the output target – header/property. |
| string |  | Defines connection to Pricefx. This is an optional parameter and if it is omitted, the connection is taken from the Spring bean named pricefx. |
| Boolean | false | Defines if during fetch null fields should be returned via REST API back to a client. |
| string | Â | Name of the Data Source. |
| string | Â | Name of the Data Feed. |
| date | Â | Incremental date. |
This method uses data from the exchange body.
Examples
<route>
<from uri="direct:start"/>
<setBody>
<constant>type: test</constant>
</setBody>
<to uri="pfx-api:flush?dataFeedName=DMF.Prices&connection=pricefx"/>
<to uri="mock:end"/>
</route>
<!-- using aggregate to avoid triggering flush during multiple file uploads -->
<aggregate strategyRef="recordsCountAggregation" completionFromBatchConsumer="true">
<correlationExpression>
<constant>true</constant>
</correlationExpression>
<log message="calling flush for dataFeedName=DMF.EarnedIncome&dataSourceName=DMDS.EarnedIncome"/>
<doTry>
<to uri="pfx-api:flush?dataFeedName=DMF.EarnedIncome&dataSourceName=DMDS.EarnedIncome&connection={{pfx:import-earned-income.pfx-connection}}"/>
<doCatch>
<exception>java.lang.Exception</exception>
<log message="Flush already PENDING."/>
</doCatch>
</doTry>
</aggregate>
IntegrationManager version 5.8.0