SQL Server Requires Chilkat v10.1.2+

Upload to Tumbleweed SecureTransport FTPS Server

See more FTP Examples

Demonstrates how to connect, authenticate, and upload file to a Tumbleweed Secure Transport SSL FTP Server. Instead of providing a login name and password, you pass the string "site-auth" for the username, and an empty string for the password. You must also provide a client-side digital certificate -- as the certificate's credentials and validity are used to authenticate. SQL Server

-- Important: See this note about string length limitations for strings returned by sp_OAMethod calls.
--
CREATE PROCEDURE ChilkatSample
AS
BEGIN
    DECLARE @hr int
    DECLARE @sTmp0 nvarchar(4000)
    DECLARE @success int
    SELECT @success = 0

    --  This example requires the Chilkat API to have been previously unlocked.
    --  See Global Unlock Sample for sample code.

    DECLARE @ftp int
    EXEC @hr = sp_OACreate 'Chilkat.Ftp2', @ftp OUT
    IF @hr <> 0
    BEGIN
        PRINT 'Failed to create ActiveX component'
        RETURN
    END

    --  This code has been tested with the Tumbleweed server
    --  at sft.wellsfargo.com
    EXEC sp_OASetProperty @ftp, 'Hostname', 'sft.wellsfargo.com'

    --  Use these exact strings for the username and password:
    EXEC sp_OASetProperty @ftp, 'Username', 'site-auth'
    EXEC sp_OASetProperty @ftp, 'Password', ''

    --  Establish an AUTH SSL secure channel after connecting.
    --  Your client-side certificate is used for authentication when
    --  the SSL channel is established.
    EXEC sp_OASetProperty @ftp, 'AuthSsl', 1

    --  The Ssl property is for establishing an implicit SSL connection
    --  on port 990.  Do not set it.
    EXEC sp_OASetProperty @ftp, 'Ssl', 0

    --  Load a certificate from a .pfx
    --  A PFX may contain several certs, including the certificates
    --  in a chain of authority.
    DECLARE @certStore int
    EXEC @hr = sp_OACreate 'Chilkat.CertStore', @certStore OUT

    DECLARE @password nvarchar(4000)
    SELECT @password = '***'
    --  Load the certs from a PFX into an in-memory certificate store:
    EXEC sp_OAMethod @certStore, 'LoadPfxFile', @success OUT, 'my.pfx', @password
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @certStore, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        RETURN
      END

    --  Find the desired certificate.
    DECLARE @jsonCN int
    EXEC @hr = sp_OACreate 'Chilkat.JsonObject', @jsonCN OUT

    EXEC sp_OAMethod @jsonCN, 'UpdateString', @success OUT, 'CN', 'cert common name'

    DECLARE @cert int
    EXEC @hr = sp_OACreate 'Chilkat.Cert', @cert OUT

    EXEC sp_OAMethod @certStore, 'FindCert', @success OUT, @jsonCN, @cert
    IF @success = 0
      BEGIN

        PRINT 'Certificate not found!'
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    --  Tell the Chilkat FTP2 component to use the client-side
    --  cert for the SSL connection:
    EXEC sp_OAMethod @ftp, 'SetSslClientCert', @success OUT, @cert

    --  Connect and authenticate with the FTP server.
    EXEC sp_OAMethod @ftp, 'Connect', @success OUT
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END
    ELSE
      BEGIN
        --  LastErrorText contains information even when
        --  successful. This allows you to visually verify
        --  that the secure connection actually occurred.
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
      END


    PRINT 'Secure FTP Channel Established!'

    --  Change to the remote directory where the file will be
    --  uploaded.  If your file is to be uploaded to the FTP user 
    --  account's home directory, this is not necessary.
    EXEC sp_OAMethod @ftp, 'ChangeRemoteDir', @success OUT, 'someSubDir'
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    --  You may include an absolute or relative path with the 
    --  local filename.  If no path is included, the file should 
    --  be present in the current working directory of the calling
    --  process.
    DECLARE @localFilename nvarchar(4000)
    SELECT @localFilename = 'someFile.dat'
    DECLARE @remoteFilename nvarchar(4000)
    SELECT @remoteFilename = 'someFile.dat'

    --  Upload the file.
    EXEC sp_OAMethod @ftp, 'PutFile', @success OUT, @localFilename, @remoteFilename
    IF @success <> 1
      BEGIN
        EXEC sp_OAGetProperty @ftp, 'LastErrorText', @sTmp0 OUT
        PRINT @sTmp0
        EXEC @hr = sp_OADestroy @ftp
        EXEC @hr = sp_OADestroy @certStore
        EXEC @hr = sp_OADestroy @jsonCN
        EXEC @hr = sp_OADestroy @cert
        RETURN
      END

    EXEC sp_OAMethod @ftp, 'Disconnect', @success OUT

    EXEC @hr = sp_OADestroy @ftp
    EXEC @hr = sp_OADestroy @certStore
    EXEC @hr = sp_OADestroy @jsonCN
    EXEC @hr = sp_OADestroy @cert


END
GO