Table of Contents

Search

  1. Preface
  2. Informatica Managed File Transfer Welcome Overview
  3. Dashboard
  4. Resources
  5. Workflows
  6. Task Reference
  7. Services Overview
  8. Users
  9. Logs and Reports
  10. Encryption
  11. System
  12. Appendix
  13. Glossary Terms

Session Persistence within Loops

Session Persistence within Loops

By default, when a file transfer task (FTP, FTPS, SFTP or SCP) is finished, the connection with the server (session) will be disconnected and closed. When using a file transfer task in a Loop or as part of a multi-step workflow, the session can be kept open and reused rather than closing and reopening the session for each file transfer task to the same server. To keep a session open or to hand off the open session to the next file transfer task in a Project, use the Input Session ID and Output Session ID variables on the Advanced tab of the file transfer task. If this is the first file transfer session in the Project and other tasks will use this connection, only specify the Output Session ID (for example, FTPSession). The next task that uses the session would specify ${FTPSession} in the Input Session ID field. When no additional tasks in the Project need the open session, it should be closed using the Close Session Task (using the Session ID value of ${FTPSession}).

0 COMMENTS

We’d like to hear from you!