{section}
{column}

{warning}This version must be installed on [Petals ESB 5.3.0|petalsesb530:Petals ESB 5.3.0]+{warning}

h1. Feature

The FTP component is a Binding Component (BC) which supports FTP command.

This component provide a set of 5 operations:

* *put:* Write the received JBI messages in a file with a specified name.
* *mput:* Write the JBI message attachments it receives into files.
* *get:* Retrieve *Xml* file corresponding to a pattern, from a folder. Return it as message payload.
* *getAsAttachment:* Retrieve the first file corresponding to a pattern, from a folder. Return it as message's attachment.(XOP standard)
* *mGet:* Retrieve files corresponding to a pattern, from a folder. Return them as message's attachment.
* *checkFile:* Check the availability of a file.
* *del:* Delete one file.
* *dir:* List the content of a folder.

These operations are available in two modes:
* through a service provider implemented by a service unit. It's the recommended way,
* through an integration service directly provided by the component.

{info}All attachment are processed by using XOP rules (XML-binary Optimized Packaging : [http://www.w3.org/TR/xop10/]).{info}
{column}
{column:width=350px}
{panel:title=Table of contents}{toc:outline=true}{panel}
{panel:title=Contributors}{contributors:order=name|mode=list|showAnonymous=true|showCount=true|showLastTime=true}{panel}
{column}
{section}

h1. Exposing a FTP connection as a service

The component is able to expose an external service in the JBI environment to send FTP commands on an FTP server (*Service-unit mode*).

When the put operation is set on the incoming IN message, the component write the XML message to the FTP server.

The IN message looks like :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:put xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<ver:body>xml body</ver:body>
<ver:filename>file name on the FTP server</ver:filename>
<!--Optional:-->
<ver:connection>
...
</ver:connection>
</ver:put>
{code}

The service does not return a message.

The service might return an error when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOnly*.

h3. MPut Operation

When the mput operation is set on the incoming IN message, the component write the attachments on the FTP server.

The IN message looks like :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:mput xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<ver:attachments>
<ver:filename><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test1.xml"/></ver:filename>
<ver:filename><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test2.xml"/></ver:filename>
</ver:attachments>
</ver:mput>
{code}

The service does not return a message.

The service might return an error when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOnly*.

h3. Get Operation

When the get operation is set on the incoming IN message, the component retrieve ONE file from the FTP server and return it as an XML message content.

The name of the file to retrieve is set in the XML IN content of the message.

The IN message looks like :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:get xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<ver:filename>file name to retrieve</ver:filename>
</ver:get>
{code}

The OUT message returned to the consumer is the content of the XML file.

The service might return a Fault when an element in the request is missing or if the FTP connection failed.

The available exchange patterns is : *InOut*.

{info}Only xml file could be processed otherwise an error will be raised.{info}

h3. GetAsAttachment Operation

When the get operation is set on the incoming IN message, the component retrieve ONE file from the FTP server and return it as an attachment.

The name of the file to retrieve is set in the XML IN content of the message.

The IN message looks like :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:getAsAttachment xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<ver:filename>file name to retrieve</ver:filename>
</ver:getAsAttachment>
{code}

The OUT message returned to the consumer contains the retrieved file, as attachment:
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<tns:getAsAttachmentResponse xmlns:tns="http://petals.ow2.org/components/ftp/version-3">
<tns:attachment>
<tns:filename><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test1.xml"/></tns:filename>
</tns:attachment>
</tns:getAsAttachmentResponse>
{code}

The service might return a Fault when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOut*.

h3. MGet Operation

When the mget operation is set on the incoming IN message, the component retrieves files from the FTP server, according to the file names (or filters) set in the XML request.

There is no recursivity, sub folders are ignored.

Each file is set in the OUT message as an attachment. The IN message looks like:
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:mget xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<!--1 or more repetitions:-->
<ver:filename>*.xml</ver:filename>
<ver:filename>myFile.txt</ver:filename>
</ver:mget>
{code}

The OUT message returned to the consumer contains files, as attachments:
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<tns:mgetResponse xmlns:tns="http://petals.ow2.org/components/ftp/version-3">
<tns:attachments>
<tns:filename><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test1.xml"/></tns:filename>
<tns:filename><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test2.xml"/></tns:filename>
</tns:attachments>
</tns:mgetResponse>
{code}

The service might return a Fault when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOut*.

h3. Dir Operation

When the dir operation is set on the incoming IN message, the component returns the file names listed from the FTP server.

The IN message looks like:
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ver:dir xmlns:ver="http://petals.ow2.org/components/ftp/version-3" />
{code}

The OUT message returned to the consumer is defined as follow :
{code:lang=xml}
<tns:dirResponse xmlns:tns="http://petals.ow2.org/components/ftp/version-3">
<!--Zero or more repetitions:-->
<tns:filename>file1.txt</tns:filename>
<tns:filename>linux.jpg</tns:filename>
</tns:dirResponse>
{code}

The service might return a Fault when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOut*.

h3. Del Operation

When the del operation is set on the incoming IN message, the component delete the remote file.

The IN message looks like :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?><ver:del xmlns:ver="http://petals.ow2.org/components/ftp/version-3">
<ver:filename>?</ver:filename>
</ver:del>
{code}

The service does not return a message.

The service might return an Error when an element in the request is missing or if the FTP connection failed.

The available exchange pattern is : *InOnly*.

h2. Configuration

All needed information must be defined in the service-unit JBI descriptor. This JBI descriptor is configured through parameters divided in following groups:
* *JBI parameters* that defines the service provider identification,
* *CDK parameters* that are parameters driving the service provider implementation at CDK layer,
* *CDK interceptor parameters* that are parameters driving interceptors at CDK layer,
* *Dedicated parameters* that are parameters driving the service provider implementation at component layer.

h3. CDK parameters defining service provider implementation
The following parameters correspond to the CDK configuration of the service provider implementation.

{include:0 CDK SU Provide Configuration 5.8.0}

h3. CDK parameters driving interceptors
The following parameters drive interceptors at CDK layer.

{include:0 CDK SU Interceptor configuration 5.8.0}

h3. Dedicated configuration
The following parameters correspond to the component specific configuration of the service provider implementation.

{anchor:connection-parameters}
{table-plus}
|| Parameter || Description || Default || Required ||
| server | IP or DNS name of the server | {center}\-{center} | {center}Yes{center}{center}except when using FtpService{center} |
| port | the port number of the FTP server | {center}21{center} | {center}No{center} |
| user | the user login name used to connect to the server | {center}\-{center} | {center}Yes{center}{center}except when using FtpService{center} |
| password | the user password | {center}\-{center} | {center}Yes{center}{center}except when using FtpService{center} |
| folder | the folder on the FTP server | {center}\-{center} | {center}No{center} |
| filename | file name for the standard PUT operation (write the XML message content on the FTP server) | {center}content.xml{center} | {center}No{center} |
| connection-mode | In Active mode, the connection port is set by the client. In Passive mode, it is set by the server (default is Active) | {center}active{center} | {center}No{center} |
| transfer-type | transfer mode used for put or get files ascii/binary | {center}ascii{center} | {center}No{center} |
| delete-processed-files | If true, the service delete the files processed by operation get or mget | {center}false{center} | {center}No{center} |
| encoding | Set the encoding encoding value used to process FTP operation | {center}Default JVM Encoding{center} | {center}No{center} |
| max-idle-time | Max idle connection time (milliseconds). Default value is 10000ms | {center}10000 ms{center}\\ | {center}No{center}\\ |
| max-connection | This parameter specifies the maximum number of simultaneous connection allowed by the FTP server. \\ | {center}\-1 (unlimited){center}\\ | {center}No{center}\\ |
{table-plus}

h3. Service unit content

The service unit has to contain the following elements, packaged in the archive:
* the META-INF/jbi.xml descriptor file as described above,
* it is also highly recommended to provide a WSDL description for service provider embeded in the service-unit. The service provider contract must implement the interface "\{http://petals.ow2.org/components/ftp/version-3}Ftp" defined in the abstract WSDL 'FtpServiceInterface.wsdl' available as resource in the component archive.

{code}
service-unit.zip
+ META-INF
- jbi.xml (as defined above)
- service.wsdl (optional)

{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:jbi="http://java.sun.com/xml/ns/jbi"
xmlns:ftp="http://petals.ow2.org/components/ftp/version-3"
xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
version="1.0">

<jbi:services binding-component="true">
<jbi:provides
interface-name="ftp:Ftp"
service-name="ftp:myFTPSUServiceName"
endpoint-name="myFTPSUEndpointName">

<!-- CDK specific elements -->
<petalsCDK:timeout>30000</petalsCDK:timeout>
<petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>
<petalsCDK:wsdl>FtpService.wsdl</petalsCDK:wsdl>
<petalsCDK:retrypolicy>
<petalsCDK:attempts>3</petalsCDK:attempts>
<petalsCDK:delay>20</petalsCDK:delay>
</petalsCDK:retrypolicy>

<!-- Component specific elements -->
<ftp:server>192.168.1.206</ftp:server>
<ftp:port>21</ftp:port>
<ftp:user>user1</ftp:user>
<ftp:password>test</ftp:password>
<ftp:folder>/home/user1/integration</ftp:folder>
<ftp:transfer-type>binary</ftp:transfer-type>
<ftp:connection-mode>active</ftp:connection-mode>
<ftp:delete-processed-files>false</ftp:delete-processed-files>
<ftp:encoding>UTF-8</ftp:encoding>
<ftp:max-idle-time>10000</ftp:max-idle-time>
<ftp:max-connection>-1</ftp:max-connection>
</jbi:provides>
</jbi:services>
</jbi:jbi>{code}

h1. The integration service

The component exposes directly a generic FTP service without deploying a service unit (*Integration service mode*). This generic service can be deactivate removing the file '{{component.wsdl}}' from the component archive.

In integration service mode, parameters for the FTP connection are set in the XML message request in a connection node added to the operation payload as following. See [connection parameters|#connection-parameters] for more details:
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ftp:... xmlns:ftp="http://petals.ow2.org/components/ftp/version-3">
<ftp:connection>
<ftp:server>?</ftp:server>
<ftp:port>?</ftp:port>
<ftp:user>?</ftp:user>
<ftp:password>?</ftp:password>
<!--Optional:-->
<ftp:folder>?</ftp:folder>
<ftp:transfer-type>?</ftp:transfer-type>
<ftp:connection-mode>?</ftp:connection-mode>
<ftp:delete-processed-files>?</ftp:delete-processed-files>
<ftp:encoding>?</ftp:encoding>
</ftp:connection>
</ftp:...>
{code}

Example of a PUT request :
{code:lang=xml}
<?xml version="1.0" encoding="UTF-8"?>
<ftp:put xmlns:ftp="http://petals.ow2.org/components/ftp/version-3">
<ftp:body>xml body</ftp:body>
<ftp:filename>file name on the FTP server</ftp:filename>
<ftp:connection>
<ftp:server>192.168.1.206</ftp:server>
<ftp:port>21</ftp:port>
<ftp:user>user1</ftp:user>
<ftp:password>test</ftp:password>
<ftp:folder>/home/user1/integration</ftp:folder>
<ftp:transfer-type>binary</ftp:transfer-type>
<ftp:connection-mode>active</ftp:connection-mode>
<ftp:delete-processed-files>false</ftp:delete-processed-files>
<ftp:encoding>UTF-8</ftp:encoding>
</ftp:connection>
</ftp:put>
{code}

h1. Configuring the component

The component can be configured through the parameters of its JBI descriptor file. These parameters are divided in following groups:
* *JBI parameters* that have not to be changed otherwise the component will not work,
* *CDK parameters* that are parameters driving the processing of the CDK layer,
* *Dedicated parameters* that are parameters specific to this component.

h2. CDK parameters
The component configuration includes the configuration of the CDK. The following parameters correspond to the CDK configuration.

{include:0 CDK Component Configuration Table 5.8.0}

h2. Interception configuration
{include:0 CDK Component Interceptor configuration 5.8.0}

h2. Dedicated configuration

No dedicated configuration parameter is available.

h1. Business monitoring

h2. MONIT traces

{include:0 CDK BC Business Monitoring Traces 5.8.0}

h2. Flow tracing activation

{include:0 CDK BC Provides Business Monitoring Flow Tracing Activation 5.8.0}

h1. Monitoring the component

h2. Using metrics

Several probes providing metrics are included in the component, and are available through the JMX MBean '{{org.ow2.petals:type=custom,name=monitoring_*<component-id>*}}', where {{*<component-id>*}} is the unique JBI identifier of the component.

h3. Common metrics

{include:0 CDK Component Monitoring Metrics 5.6.0}

h3. Dedicated metrics

No dedicated metric is available.

h2. Receiving alerts

Several alerts are notified by the component through notification of the JMX MBean '{{org.ow2.petals:type=custom,name=monitoring_*<component-id>*}}', where {{*<component-id>*}} is the unique JBI identifier of the component.

{tip}To integrate these alerts with Nagios, see [petalsesbsnapshot:Receiving Petals ESB defects in Nagios].{tip}

h3. Common alerts

{include:0 CDK Component Monitoring Alerts 5.6.0}

h3. Dedicated alerts

No dedicated alert is available.