This version must be installed on [Petals ESB 5.4.0]+ Features The FileTransfer component is a Binding Component which supports file transfers. This component allows to: Expose a file system access as a service which provide a set of 8 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. Poll a configured directory for incoming files. At a poll, each file retrieved is put into a new JBI message, set as source or attachment. The message is sent to a target JBI service. All attachment are processed by using XOP rules.(XML-binary Optimized Packaging : http://www.w3.org/TR/xop10/ )

Table of contents 1 Features 2 Exposing a file system access as a service (Provides mode) 2.1 Usage 2.1.1 Put Operation 2.1.2 MPut Operation 2.1.3 Get Operation 2.1.4 GetAsAttachement Operation 2.1.5 MGet Operation 2.1.6 CheckFile Operation 2.1.7 Del Operation 2.1.8 Dir Operation 2.2 Configuration 2.2.1 CDK parameters defining service provider implementation 2.2.2 CDK parameters driving interceptors 2.2.3 Dedicated configuration 2.2.4 Service Unit content 2.2.5 Example 3 Invoking service on incoming file (Consumes mode) 3.1 Configuration 3.1.1 CDK parameters defining service consumer implementation 3.1.2 CDK parameters driving interceptors 3.1.3 Dedicated configuration 3.1.4 Service unit content 3.1.5 Example 4 Configuring the component 4.1 CDK parameters 4.2 Interception configuration 4.3 Dedicated configuration 5 Business monitoring 5.1 MONIT traces 5.2 Flow tracing activation 6 Monitoring the component 6.1 Using metrics 6.1.1 Common metrics 6.1.2 Dedicated metrics 6.2 Receiving alerts 6.2.1 Common alerts 6.2.2 Dedicated alerts 7 Known problems 7.1 Encoding problem about filename on a filesystem mounted through Samba Contributors Christophe DENEUX 1 (50 days ago)

Exposing a file system access as a service (Provides mode)

All operations support wild card character.

All operations are in namespace http://petals.ow2.org/components/filetransfer/version-5.

Usage

Put Operation

When the put operation is set on the incoming IN message, the component writes the XML message to the configured directory.

The created file takes the name described in the service unit (filename parameter) otherwise the operation name is taken. For each file created, the system date is appended to this file name.

The IN message looks like :

<?xml version="1.0" encoding="UTF-8"?>
<ver:put xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">?</ver:put>

The service does not return a message.
The available exchange pattern is : InOnly.

MPut Operation

When the mput operation is set on the incoming IN message, the component writes the attachments on the configured directory.
The IN message looks like :

<?xml version="1.0" encoding="UTF-8"?>
<ver:mput xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
    <ver:attachments>
        <!--1 or more repetitions:-->
        <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>

The service does not return a nominal response. It might return fault on following conditions, otherwise an error is returned:

• when no attachment is provided in the request, the fault 'fileAttachmentExpected' is returned.

The available exchange pattern is : InOnly.

Get Operation

When the get operation is set on the incoming IN message, the component retrieves ONE file from the configured directory and return it as an XML message content. By default, the file is moved to the backup directory configured at service unit level.

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

The IN message looks like :

<?xml version="1.0" encoding="UTF-8"?>
<ver:get xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
     <ver:filename>file name to retrieve</ver:filename>
</ver:get>

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

The service might return fault on following conditions, otherwise an error is returned:

• when the element 'filename' is missing in the request, the fault 'filenameMissing' is returned,
• when the expected file is not found, the fault 'noFileFound' is returned,
• when the expected file is not a XML file, the fault 'xmlFileExpected' is returned,
• when the expected file is locked for writing by another process, the fault 'fileLocked' is returned.

The available exchange patterns is : InOut.

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

GetAsAttachement Operation

When the getAsAttachment operation is set on the incoming IN message, the component retrieve ONE file from the configured directory according to the filename(or filter) set in the XML request. By default, the file is moved to the backup directory configured at service unit level.
The retrieved file is set in the OUT message as an attachment.

The IN message looks like:

<?xml version="1.0" encoding="UTF-8"?>
<ver:getAsAttachment xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
     <ver:filename>file name to retrieve</ver:filename>
 </ver:getAsAttachment>

The OUT message returned to the consumer contains file, as attachment:

<?xml version="1.0" encoding="UTF-8"?>
<tns:getAsAttachmentResponse xmlns:tns="http://petals.ow2.org/components/filetransfer/version-5">
  <tns:file-content>
    <xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test1.xml"/>
  </tns:file-content>
</tns:getAsAttachmentResponse>

The service might return fault on following conditions, otherwise an error is returned:

• when the element 'filename' is missing in the request, the fault 'filenameMissing' is returned,
• when the expected file is not found, the fault 'noFileFound' is returned,
• when the expected file is locked for writing by another process, the fault 'fileLocked' is returned.

The available exchange pattern is : InOut.

MGet Operation

When the mget operation is set on the incoming IN message, the component retrieves files from the configured directory, according to the filenames (or filters) set in the XML request. By default, the files returned are moved to the backup directory configured at service unit level.
There is no recursion, sub folders are ignored.

Each file is set in the OUT message as an attachment.
The IN message looks like:

<?xml version="1.0" encoding="UTF-8"?>
   <ver:mget xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
   <\!\--1 or more repetitions:-\->
   <ver:filename>*.xml</ver:filename>
   <ver:filename>myFile.txt</ver:filename>
</ver:mget>

The OUT message returned to the consumer contains files, as attachments:

<?xml version="1.0" encoding="UTF-8"?>
<tns:mgetResponse xmlns:tns="http://petals.ow2.org/components/filetransfer/version-5">
  <tns:file-content><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:test1.xml"/></tns:file-content>
  <tns:file-content><xop:Include xmlns:xop="http://www.w3.org/2004/08/xop/include" href="cid:myFile.txt"/></tns:file-content>
</tns:mgetResponse>

The service might returns error but no fault.

If a file matching request criteria is locked for writing by another process, it will not be returned until it is unlocked.

The available exchange pattern is : InOut.

CheckFile Operation

When the check operation is set on the incoming IN message, the component check
if the specified file exist. The IN message looks like :

<ver:checkFile xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
         <ver:filename>?</ver:filename>
</ver:checkFile>

The OUT message returned to the consumer looks like :

<ver:checkFileResponse xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
         <ver:filename>?</ver:filename>
         <ver:exist>true|false</ver:exist>
</ver:checkFileResponse>

The service might return fault on following conditions, otherwise an error is returned:

• when the element 'filename' is missing in the request, the fault 'filenameMissing' is returned.

The available exchange pattern is : InOut.

Del Operation

When the del operation is set on the incoming IN message, the component deletes the remote files. The IN message looks like :

<?xml version="1.0" encoding="UTF-8"?>
<ver:del xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5">
<ver:filename>?</ver:filename>
</ver:del>

The service does not return a nominal response. It might return fault on following conditions, otherwise an error is returned:

• when the element 'filename' is missing in the request, the fault 'filenameMissing' is returned.

The available exchange pattern is : InOnly.

Dir Operation

When the dir operation is set on the incoming IN message, the component returns the file names listed from the configured directory. A wild card expression can be given to filter files returned. f no wild card expression is given, or if it is empty, all files will be listed:

<?xml version="1.0" encoding="UTF-8"?>
<ver:dir xmlns:ver="http://petals.ow2.org/components/filetransfer/version-5" >
   <ver:filename>*.xml</ver:filename>
</ver:dir>

The OUT message returned to the consumer looks like :

<?xml version="1.0" encoding="UTF-8"?>
<tns:dirResponse xmlns:tns="http://petals.ow2.org/components/filetransfer/version-5">
         <tns:filename>file.xml</tns:filename>
         <tns:filename>file1.xml</tns:filename>
         <tns:filename>file2.xml</tns:filename>
</tns:dirResponse>

The service might return an ioFault.
The available exchange pattern is : InOut.

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.

CDK parameters defining service provider implementation

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

The service provider is defined into the section 'provides' of the JBI descriptor, containing:

CDK parameters driving interceptors

The following parameters drive interceptors at CDK layer.

Interceptors can be defined to inject some post or pre-processing in the service provider processing or service consumer processing.

Using interceptor is very sensitive and must be manipulated only by power users. A non properly coded interceptor engaged in a component can lead to uncontrolled behaviors, out of the standard process.

Example of an interceptor configuration:

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5">
   <jbi:services>
      <jbi:provides|consumes>
         <!--...-->
         <petalsCDK:su-interceptors>
            <petalsCDK:send>
               <petalsCDK:interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
                  <petalsCDK:param name="myParamName2">myParamValue2</petalsCDK:param>
               </petalsCDK:interceptor>
            </petalsCDK:send>
            <petalsCDK:accept>
               <petalsCDK:interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:interceptor>
            </petalsCDK:accept>
            <petalsCDK:send-response>
               <petalsCDK:Interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:Interceptor>
            </petalsCDK:send-response>
            <petalsCDK:accept-response>
               <petalsCDK:Interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:Interceptor>
            </petalsCDK:accept-response>
         </petalsCDK:su-interceptors>
         <!--...-->
      </jbi:provides|consumes>
      <!--...-->
   </jbi:services>
</jbi:jbi>

Dedicated configuration

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 embedded in the service-unit. The service provider contract must implement the interface "{http://petals.ow2.org/components/filetransfer/version-5}FileTransfer" defined in the abstract WSDL 'FileTransferInterface.wsdl' available as resource in the component archive.

service-unit.zip
  + META-INF
    - jbi.xml (as defined above)
  - service.wsdl (recommended)

Example

An example of a Service Unit descriptor to provide an Filetransfer service:

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

    <jbi:services binding-component="true">

        <jbi:provides endpoint-name="myFileTransferSUEndpointName"
            interface-name="filetransfer:FileTransfer" service-name="generateNs:myFileTransferSUServiceName">

            <!-- CDK specific elements -->
            <petalsCDK:wsdl>MyFileTransferService.wsdl</petalsCDK:wsdl>
            <petalsCDK:validate-wsdl>true</petalsCDK:validate-wsdl>

            <!-- Component specific elements -->
            <filetransfer:filename>gettingstarted.xml</filetransfer:filename>
            <filetransfer:backup-directory>${PETALS_HOME}/filetransfer/backup</filetransfer:backup-directory>
            <filetransfer:folder>${PETALS_HOME}/filetransfer/out</filetransfer:folder>
        </jbi:provides>
    </jbi:services>
</jbi:jbi>

Invoking service on incoming file (Consumes mode)

If you want to invoke a service provider in Petals ESB with files, put the files in the configured directory (folder}). At each configured polling period ({{polling-period), the component fetches the incoming files.

For each received files and according to the transfer mode (transfer-mode or base-msg), the component creates a new message exchange and attaches the file, either as source or attachment.

If a file is put as a attachment, the name of the attachment is set to the name of the file, and in the source of the message exchange, the component put a XML structure according to MTOM optimization rules.

The resulted message exchange(s) are sent to the target endpoint.

During the transfer, if the backup directory (backup-directory) is set, the transfered file is moved into it and never deleted by the component. Otherwise the file is moved to the system temporary directory.

A InOut service provider can be exposed to be consumed through files. The content of its reply will be ignored. By default the message exchange pattern used to send messages to the service provider is 'InOnly'. Just set the right value into the parameter mep in the section consumes of the SU JBI descriptor.

When deploying a service unit like in the following code snippet, all the files put in the directory $PETALS_HOME/filetransfer/in would be set as the payload of an invocation to the ftContentNoBaseMsgService service.

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 consumer implementation at CDK layer,
• CDK interceptor parameters that are parameters driving interceptors at CDK layer,
• Dedicated parameters that are parameters driving the service consumer implementation at component layer.

CDK parameters defining service consumer implementation

The following parameters correspond to the CDK configuration of the service consumer implementation.

A service consumer is defined into the section 'consumes' of the JBI descriptor, containing:

CDK parameters driving interceptors

The following parameters drive interceptors at CDK layer.

Interceptors can be defined to inject some post or pre-processing in the service provider processing or service consumer processing.

Using interceptor is very sensitive and must be manipulated only by power users. A non properly coded interceptor engaged in a component can lead to uncontrolled behaviors, out of the standard process.

Example of an interceptor configuration:

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5">
   <jbi:services>
      <jbi:provides|consumes>
         <!--...-->
         <petalsCDK:su-interceptors>
            <petalsCDK:send>
               <petalsCDK:interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
                  <petalsCDK:param name="myParamName2">myParamValue2</petalsCDK:param>
               </petalsCDK:interceptor>
            </petalsCDK:send>
            <petalsCDK:accept>
               <petalsCDK:interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:interceptor>
            </petalsCDK:accept>
            <petalsCDK:send-response>
               <petalsCDK:Interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:Interceptor>
            </petalsCDK:send-response>
            <petalsCDK:accept-response>
               <petalsCDK:Interceptor name="myInterceptorName">
                  <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
               </petalsCDK:Interceptor>
            </petalsCDK:accept-response>
         </petalsCDK:su-interceptors>
         <!--...-->
      </jbi:provides|consumes>
      <!--...-->
   </jbi:services>
</jbi:jbi>

Dedicated configuration

The parameter "transfer-mode" and "base-msg" can not be used at the same time.

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,.

service-unit.zip
  + META-INF
    - jbi.xml (as defined above)

Example

Example 1: use of the parameter 'transfer-mode'

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0"
    xmlns:providerNs="http://petals.ow2.org/filetransfer/my-provider"
    xmlns:filetransfer="http://petals.ow2.org/components/filetransfer/version-5"
    xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
    xmlns:jbi="http://java.sun.com/xml/ns/jbi"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <jbi:services binding-component="false">
        <jbi:consumes
            interface-name="providerNs:ftContentNoBaseMsg"
            service-name="providerNs:ftContentNoBaseMsgService"
            endpoint-name="ftContentNoBaseMsgEndpoint">

            <petalsCDK:timeout>20</petalsCDK:timeout>
            <petalsCDK:mep>InOnly</petalsCDK:mep>
            <petalsCDK:operation>providerNs:simplefiletransfer</petalsCDK:operation>

            <filetransfer:folder>${PETALS_HOME}/filetransfer/in</filetransfer:folder>
            <filetransfer:polling-period>3000</filetransfer:polling-period>
            <filetransfer:transfer-mode>content</filetransfer:transfer-mode>
        </jbi:consumes>
    </jbi:services>
</jbi:jbi>

Example 2: use of the parameter 'base-msg'

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi version="1.0"
    xmlns:providerNs="http://petals.ow2.org/filetransfer/my-provider"
    xmlns:filetransfer="http://petals.ow2.org/components/filetransfer/version-5"
    xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5"
    xmlns:jbi="http://java.sun.com/xml/ns/jbi"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <jbi:services binding-component="true">
        <jbi:consumes
            interface-name="providerNs:ftAttachmentBaseMsg"
            service-name="providerNs:ftAttachmentBaseMsgService"
            endpoint-name="ftAttachmentBaseMsgEndpoint">

            <petalsCDK:timeout>30000</petalsCDK:timeout>
            <petalsCDK:mep>InOnly</petalsCDK:mep>
            <petalsCDK:operation>providerNs:simplefiletransfer</petalsCDK:operation>

            <filetransfer:folder>${PETALS_HOME}/filetransfer/in4</filetransfer:folder>
            <filetransfer:polling-period>1000</filetransfer:polling-period>
            <filetransfer:base-message>
                 <![CDATA[<customMessage><attachments><filein>$attachment</filein></attachments></customMessage>]]>
            </filetransfer:base-message>
        </jbi:consumes>
    </jbi:services>
</jbi:jbi>

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.

CDK parameters

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

• Installation: The parameter can be set during the installation of the component, by using the installation MBean (see JBI specifications for details about the installation sequence). If the parameter is optional and has not been defined during the development of the component, it is not available at installation time.
• Runtime: The paramater can be set during the installation of the component and during runtime. The runtime configuration can be changed using the CDK custom MBean named RuntimeConfiguration. If the parameter is optional and has not been defined during the development of the component, it is not available at installation and runtime times.

Interception configuration

Interceptors can be defined to inject some post or pre-processing in the component during service processing.

Using interceptor is very sensitive and must be manipulated only by power users. A non properly coded interceptor engaged in a component can lead to uncontrolled behaviors, out of the standard process.

Example of an interceptor configuration:

<?xml version="1.0" encoding="UTF-8"?>
<jbi:jbi xmlns:jbi="http://java.sun.com/xml/ns/jbi" xmlns:petalsCDK="http://petals.ow2.org/components/extensions/version-5" ...>
   <jbi:component>
      <!--...-->
      <petalsCDK:component-interceptors>
         <petalsCDK:interceptor active="true" class="org.ow2.petals.myInterceptor" name="myInterceptorName">
            <petalsCDK:param name="myParamName">myParamValue</petalsCDK:param>
            <petalsCDK:param name="myParamName2">myParamValue2</petalsCDK:param>
         </petalsCDK:interceptor>
      </petalsCDK:component-interceptors>
      <!--...-->
   </jbi:component>
</jbi:jbi>

Dedicated configuration

These parameters drive features proposed by the component

Business monitoring

MONIT traces

Each service provider exposed in Petals ESB is able to log MONIT traces with following information:

• on service provider invocation, when receiving an incoming request, with following attributes:
  • traceCode set to provideFlowStepBegin,
  • flowInstanceId set to the flow instance identifier retrieved from the incoming request,
  • flowStepId set to an UUID value,
  • flowStepInterfaceName set to the service provider interface name,
  • flowStepServiceName set to the service provider service name,
  • flowStepOperationName set to the operation of the invoked service provider,
  • flowStepEndpointName set to the service provider endpoint name,
  • flowPreviousStepId set to the step identifier of the previous step, retrieved from the incoming request.
• on external service provider invocation, when sending a request to the external service provider, with following attributes:
  • traceCode set to provideExtFlowStepBegin,
  • flowInstanceId set to the flow instance identifier retrieved from the incoming request,
  • flowStepId set to an UUID value,
  • flowPreviousStepId set to the step identifier of the previous step that is the internal processing of the incoming request into the BC.
• on external service provider termination, when receiving the outgoing response of the external service provider, with following attributes:
  • traceCode set to provideExtFlowStepEnd or provideExtFlowStepFailure,
  • flowInstanceId set to the flow instance identifier retrieved from the incoming request,
  • flowStepId set to the flow step identifier defined for the external service provider invocation.
• on service provider termination, when returning the outgoing response, with following attributes:
  • traceCode set to provideFlowStepEnd or provideFlowStepFailure,
  • flowInstanceId set to the flow instance identifier retrieved from the incoming request,
  • flowStepId set to the flow step identifier defined on incoming request receipt.

Flow tracing activation

The flow tracing (ie. MONIT traces generation) is defined according to the property 'org.ow2.petals.monitoring.business.activate-flow-tracing' of the incoming request. If the property does not exist, the parameter activate-flow-tracing of the service provider definition will be inspected. If no parameter is defined at service provider level, the component configuration parameter 'activate-flow-tracing' is used. Finally, by default, the flow tracing is enabled.

Monitoring the component

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.

Common metrics

The following metrics are provided through the Petals CDK, and are common to all components:

Dedicated metrics

No dedicated metric is available.

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.

To integrate these alerts with Nagios, see Receiving Petals ESB defects in Nagios.

Common alerts

Dedicated alerts

No dedicated alert is available.

Known problems

Encoding problem about filename on a filesystem mounted through Samba

An encoding problem can occurs about filename with Sambe mounts.
Please check that the encoding is correctly configured at Samba level through the parameters 'unix charset' and 'display charset'.