wm.tn.transport:secondaryFtps
Delivers documents through FTP over SSL (also known as FTPS). This service uses the delivery method information that is associated with the secondary FTP delivery method from the receiving partner's profile to determine the host name, port number, user name, password, and directory to use to deliver the document.
Input Parameters
bizdoc | Document The document you want to deliver. The document must be an instance of com.wm.app.tn.doc.BizDocEnvelope. |
retriesRemaining | String The number of retries remaining. The delivery engine passes this information into this server at every attempt of job delivery. |
Output Parameters
serviceOutput |  status String The outcome of the delivery: success or fail. statusMessage String The status message from the last attempt to deliver the document. For example, the status message might be 221. transportTime String Total time (in milliseconds) it took to deliver the document. output Document The header and body that was returned from the FTP “put.” For the structure of output, see
wm.tn.rec:FtpOutput. |
Usage Notes
This service can establish connections only to FTP servers that use SSL; it
cannot establish connections to servers that implement other security facilities.
FTPS requires an SSL handshake, which results in additional processing and additional exposure to network latency. If very large documents are being transmitted, this additional overhead is likely to be negligible. However, if FTPS is used to deliver small documents, the additional overhead may be significant.
The service throws an exception if the receiver identified to receive the document in
bizdoc is a local partner. And the local partner is a host of the network.
This service performs a passive transfer.
The file name of the delivered document is the internal document ID and the extension is either .xml if the content-type is text, xml, or
.bizdoc.