Run Time behaviour of FTP/SFTP Protocol in OSB

1.      The proxy service polls the input directory at regular intervals. 

Note:

A new connection is created for each poll cycle.

2.      If the proxy service finds a file in the input directory, it renames the file with a .stage extension. This renaming ensures that the service does not pick up the same files during the next polling cycle.

The .stage file exists in the input directory until it is delivered. 

Note:

If the file cannot be retrieved from the input directory (due to network failure, for example), the .stage file is processed during a clean-up cycle. The clean-up cycle is performed every 15 minutes or after 15 polling cycles, whichever occurs later. If a .stage file exists during two consecutive clean-up cycles, it is processed again. 

3.      A JMS task is created for the message and added to the domain-wide JMS queue. 

4.      A domain-wide MDB receives the task and processes the message. 

Note:

The task uses a pooled connection for processing the message. If a connection is not available in the pool, a new connection is created. 

5.      The message is delivered to the pipeline and the .stage file is deleted. 

Note:

If an SFTP business service is configured, the service puts the message in the outbound directory through a pooled connection.

 

If the message is not delivered, the transport attempts to transfer it again and repeats the process up to a predefined number of attempts. If the message cannot be delivered, it is moved to the error directory.