VFS transport Basic Example with WSO2 ESB
"WSO2 ESB has a feature rich file transport which is known as the VFS
transport. This transport is currently used by lot of customers for
implementing various file transfer and processing scenarios. VFS
transport uses the versatile Apache Commons-VFS[1] library as the
underline library for various file system related operations. This
library provided a rich set of features which allows WSO2 ESB's VFS
transport to connect to various types of remote file systems. " [1]
The VFS transport implementation is based on Apache Commons VFS implementation.
Lets try a sample.
<parameter name="transport.vfs.FileURI"></parameter> <parameter name="transport.vfs.MoveAfterProcess"></parameter> <parameter name="transport.vfs.MoveAfterFailure"></parameter>Use the following proxy service.
<proxy xmlns="http://ws.apache.org/ns/synapse" name="StockQuoteProxy2" transports="vfs" statistics="disable" trace="disable" startOnLoad="true">
<target>
<inSequence>
<send>
<endpoint>
<address uri="http://localhost:9000/services/SimpleStockQuoteService" format="soap12" />
</endpoint>
</send>
</inSequence>
<outSequence>
<property name="OUT_ONLY" value="true" />
<send>
<endpoint>
<address uri="vfs:file:///home/achala/supportweek10/failure" />
</endpoint>
</send>
</outSequence>
</target>
<parameter name="transport.vfs.ActionAfterProcess">MOVE</parameter>
<parameter name="transport.PollInterval">10</parameter>
<parameter name="transport.vfs.MoveAfterProcess">file:///home/achala/supportweek10/original</parameter>
<parameter name="transport.vfs.FileURI">file:///home/achala/supportweek10/in</parameter>
<parameter name="transport.vfs.MoveAfterFailure">file:///home/achala/supportweek10/failure</parameter>
<parameter name="transport.vfs.FileNamePattern">.*.xml</parameter>
<parameter name="transport.vfs.ContentType">text/xml</parameter>
<parameter name="transport.vfs.ActionAfterFailure">MOVE</parameter>
</proxy>
Uncomment the VFS transport listener and sender (In the axis2.xml ) . Copy a file to the in folder.
(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)





