All Element Summary | ||||||||||||
connector | SFTP connectivity
|
|||||||||||
endpoint |
|
|||||||||||
inbound-endpoint |
|
|||||||||||
outbound-endpoint |
|
Complex Type Summary | ||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
Simple Type Summary | ||||||
|
Attribute Group Summary | ||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
||||||||||
|
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="http://www.mulesoft.org/schema/mule/sftp" xmlns="http://www.mulesoft.org/schema/mule/sftp" xmlns:file="http://www.mulesoft.org/schema/mule/file" xmlns:mule="http://www.mulesoft.org/schema/mule/core" xmlns:schemadoc="http://www.mulesoft.org/schema/mule/schemadoc" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <xsd:import namespace="http://www.mulesoft.org/schema/mule/file" schemaLocation="http://www.mulesoft.org/schema/mule/file/3.3/mule-file.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/core" schemaLocation="http://www.mulesoft.org/schema/mule/core/3.3/mule.xsd"/> <xsd:import namespace="http://www.mulesoft.org/schema/mule/schemadoc" schemaLocation="http://www.mulesoft.org/schema/mule/schemadoc/3.3/mule-schemadoc.xsd"/> <xsd:annotation> <xsd:documentation> The SFTP transport provides connectivity to SFTP servers to allow files to be read and written as messages in Mule. </xsd:documentation> <xsd:appinfo> <schemadoc:short-name>SFTP</schemadoc:short-name> <schemadoc:page-title>SFTP Transport</schemadoc:page-title> <schemadoc:transport-features dispatchEvents="true" receiveEvents="true" requestEvents="true" retries="false" streaming="true" transactions="false"> <schemadoc:MEPs default="one-way" supported="one-way, request-response"/> </schemadoc:transport-features> </xsd:appinfo> </xsd:annotation> <xsd:annotation> <xsd:documentation> SFTP connectivity </xsd:documentation> </xsd:annotation> </xsd:element> <xsd:complexContent> <xsd:sequence maxOccurs="1" minOccurs="0"> </xsd:sequence> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="inbound-endpoint" substitutionGroup="mule:abstract-inbound-endpoint" type="inboundEndpointType"/> <xsd:complexContent> <!-- <xsd:attributeGroup ref="commonAttributes"/> --> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="outbound-endpoint" substitutionGroup="mule:abstract-outbound-endpoint" type="outboundEndpointType"/> <xsd:complexContent> </xsd:extension> </xsd:complexContent> </xsd:complexType> <xsd:element name="endpoint" substitutionGroup="mule:abstract-global-endpoint" type="globalEndpointType"/> <xsd:complexContent> <!-- The only valid exchange-pattern is one-way which is the default. No need to make the exchange-pattern attribute configurable. --> </xsd:extension> </xsd:complexContent> </xsd:complexType> <!-- Various attributes for the connector --> <xsd:annotation> <xsd:documentation> Required: No Default: disabled If specified then Mule tries to create the temp-directory in the endpoint folder if it doesn't already exist. Ensure that the user Mule is configured to use to access the sftp server has privileges to create a temp folder if required! For inbound endpoints: A temporary directory on the ftp-server from where the download takes place. The file will be moved (locally on the sftp-server) to the tempDir, to mark that a download is taking place, before the download starts. NOTE: A file in the tempDir of an inbound endpoint is always correct (has only been moved locally on the sftp-server) and can therefore be used to restart a failing file transfer. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: No Default: disabled If specified then Mule tries to create the temp-directory in the endpoint folder if it doesn't already exist. Ensure that the user Mule is configured to use to access the sftp server has privileges to create a temp folder if required! For outbound endpoints: A temporary directory on the sftp-server to first upload the file to. When the file is fully uploaded the file is moved to its final destination. The tempDir will be created as a sub directory to the endpoint. NOTE: A file in the tempDir of an outbound endpoint might not be correct (since the upload takes place to this folder) and can therefore NOT be used to restart a failing file transfer. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:annotation> <xsd:documentation> Required: no Default: 1000 ms The frequency in milliseconds that the read directory should be checked. Note that the read directory is specified by the endpoint of the listening component. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: true Whether to delete the file after successfully reading it. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled Miniumum age (in ms) for a file to be processed. This can be useful when consuming large files. It tells Mule to wait for a period of time before consuming the file, allowing the file to be completely written before the file is processed. WARNING: The fileAge attribute will only work properly if the servers where Mule and the sftp-server runs have synchronized time. NOTE: See attribute sizeCheckWaitTime for an alternate method of determing if a incoming file is ready for processing. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled Wait time (in ms) between size-checks to determine if a file is ready to be processed. Disabled if not set or set to a negative value. This feature can be useful to avoid processing not yet completely written files (e.g. consuming large files). It tells Mule to do two size checks waiting the specified time between the two size calls. If the two size calls return the same value Mule consider the file ready for processing. NOTE: See attribute fileAge for an alternate method of determing if a incoming file is ready for processing. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled Archives a copy of the file in the specified directory on the file system where mule is running. The archive folder must have been created before Mule is started and the user Mule runs under must have privileges to read and write to the folder. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled If specified then the file to be archived is received in this folder and then moved to the archiveTempSendingDir while sent further on to the outbound endpoint. This folder is created as a subfolder to the archiveDir. NOTE: Must be specified together with the archiveTempSendingDir and archiveDir attributes. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled If specified then the file to be archived is sent to the outbound endpoint from this folder. This folder is created as a subfolder to the archiveDir. After the file is consumed by the outbound endpoint or the component itself (i.e. when the underlying InputStream is closed) it will be moved to the archive folder. NOTE: Must be specified together with the archiveTempReceivingDir and archiveDir attributes. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:annotation> <xsd:documentation> Required: no Default: the message id, e.g. ee241e68-c619-11de-986b-adeb3d6db038 The pattern to use when writing a file to disk. This can use the patterns supported by the filename-parser configured for this connector, by default the [Legacy Filename Parser|http://www.mulesoft.org/display/MULE2USER/File+Transport#FileTransport-LegacyFilenameParser] is used. See section [Child Elements to File Connector|http://www.mulesoft.org/display/MULE2USER/File+Transport] for information on how to override the default parser. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: true If true the file on the inbound-endpoint will not be deleted if an error occurs when writing to the outbound-endpoint. NOTE: This assumes that both the inbound and outbound endpoints are using the SFTP-Transport. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: throwException Determines what to do if a file already exist on the outbound endpoint with the specified name. throwException: Will throw an exception if a file already exists overwrite: Will overwrite an existing file addSeqNo: Will add a sequence number to the target filename making the filename unique, starting with 1 and incrementing the number until a unique filename is found The default behavior is to throw an exception. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:restriction base="xsd:string"> <xsd:enumeration value="throwException"/> <xsd:enumeration value="overwrite"/> <xsd:enumeration value="addSeqNo"/> </xsd:restriction> </xsd:simpleType> <xsd:annotation> <xsd:documentation> A file location. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> A username. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> A password. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> An IP address (eg www.mulesoft.com, localhost, 127.0.0.1). </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> A port number. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:annotation> <xsd:documentation> Required: No Default: disabled If specified then Mule tries to create the temp-directory in the endpoint folder if it doesn't already exist. Ensure that the user Mule is configured to use to access the sftp server has privileges to create a temp folder if required! For inbound endpoints: A temporary directory on the ftp-server from where the download takes place. The file will be moved (locally on the sftp-server) to the tempDir, to mark that a download is taking place, before the download starts. NOTE: A file in the tempDir of an inbound endpoint is always correct (has only been moved locally on the sftp-server) and can therefore be used to restart a failing file transfer. For outbound endpoints: A temporary directory on the sftp-server to first upload the file to. When the file is fully uploaded the file is moved to its final destination. The tempDir will be created as a sub directory to the endpoint. NOTE: A file in the tempDir of an outbound endpoint might not be correct (since the upload takes place to this folder) and can therefore NOT be used to restart a failing file transfer. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <!-- Various attributes both on the endpoints and connectors --> <xsd:annotation> <xsd:documentation> Required: No Default: disabled Used together with the tempDir - attribute to give the files in the tempDir a guaranteed unique name based on the local time when the file was moved to the tempDir. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:annotation> <xsd:documentation> Required: no Default: disabled An identityFile location for a PKI private key. </xsd:documentation> </xsd:annotation> </xsd:attribute> <xsd:annotation> <xsd:documentation> Required: no Default: disabled The passphrase (password) for the identityFile if required. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> <xsd:annotation> <xsd:documentation> Required: No Default: disabled If the number of active connections is specified, then a connection pool will be used with active connections up to this number. Use a negative value for no limit. If the value is zero no connection pool will be used. </xsd:documentation> </xsd:annotation> </xsd:attribute> </xsd:attributeGroup> </xsd:schema> |
XML schema documentation generated with DocFlex/XML RE 1.8.5 using DocFlex/XML XSDDoc 2.5.0 template set. All content model diagrams generated by Altova XMLSpy via DocFlex/XML XMLSpy Integration. |