File Transfer Integration Flow With Websphere Cast Iron V6

I had a great comment from Shashi Kiran on my blog that my previous post on File Transfer with Cast Iron was outdated as the new version of Cast Iron V6 changes the way some configurations when an integration flow is created.

The following is what we want to achieve:

Step 1: When I click on “Select Inputs”, another popup  appears.

Step 2. Clicked on “Data”

Step 3. I had to drag /draw a line from “From” to “to”  for the green line to appear. ( I have to make some sort of a relation I think )

Step 4. Click on Run Test, and then this is where I am lost ! It asks for the test data file and when I enter the data file., it comes back as “Could not process file due to the following error. Content is not allowed in Prolog.”

Above is the new Cast Iron V6 config that Shashi Kiran shared with me, many thanks mate and I know the community appreciate your input.

File Transfer Scenarios with WebSphere Datapower

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.

The following tasks are performed by Datapower:

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

The following task are performed by Datapower:

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.

The following tasks are performed by Datapower:

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

The following tasks are performed by Datapower:

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.

File Transfer Integration flow with Websphere Cast Iron

How to integrate file transfer with Cast Iron

Step 1: Create or start your ftp server (in this case I just use FileZilla Server)

Step 2: In your file server create a user or role and specify the permissions of the user and some username and password

Step 3: Create an FTP endpoint by specifying:

  • FTP Host Name
  • FTP Port Number
  • FTP Username
  • FTP Password

Step 4: Test the connection by clicking on the ‘Test Connection’ button.

Step 5: Create your FTP integration flow

In this flow we will be moving Files from a Cloud Server to a local user machine

Step 6: Specify the folder of the file from origin to destination

Step 7. Test the integration flow by dropping a file into the origin folder and see if it has been move to the destination folder.