Below is some scenarios for using Datapower S/FTP frontside handler/poller to solve enterprise file transfer requirements.
Scenario 1: Enterprise customers want to bridge legacy S/FTP-based messaging flows with newer HTTP Web Services.
1. A file is retrieved by polling a remote FTP Server
2. Routes the file content to an enterprise HTTP Server for processing
3. Captures the response by the HTTP Server application and places a response file on the remote FTP Server. This is done by creating a predetermined naming pattern.
Scenario 2: Datapower extends the ESB to include an FTP-based client requiring additional security
1. Datapower retrieves file by polling a remote SFTP server
2. It passes binary file through to an enterprise Websphere MQ Queue
3. And captures the response from WebSphere MQ system and places the response file on the remote SFTP sever. This is done by creating a predetermined naming pattern.
Scenario 3: Datapower protects existing enterprise FTP servers.
1. Datapower access FTP connection from remote FTP Clients which allow client to connect to a inbound FTP server transparently and securely.
2. Authentication using username and password is done from incoming FTP Client.
3. Datapower supports the streaming of large file through the appliance.
Scenario 4: Datapower provides additional security for SFTP-based message exchange patterns
1. Datapower acts as an SFTP server to remote client connections.
2. Datapower presents a virtual files system that exists only on the device, proxing the actual back end servers.
3. Datapower dynamically routes files to the desired location on the back end SFTP Server
4. Datapower performs public key authentication on the inbound FTP Clients.