Note: This tip is for use with SecureFX for Windows.
SecureFX® for Windows provides a command-line utility named SFXCL, a console application that can be used in automated file transfer scenarios.
This document details "best practices" to use in implementing an automated file transfer solution involving SFXCL. Topics covered include SFXCL exit codes, using wildcards, ASCII vs. binary tranfers, and how to generate unique log file names. Example batch files and VBScript code are provided.
1. Introduction 2. Use Correct Command-Line Syntax 2.1. URL Specifications 2.2. Session Specifications 2.3. Local Path Specifications 2.4. File Transfer "Direction" (Upload vs. Download) 2.4.1. Upload Syntax 2.4.2. Download Syntax 2.5. Absolute vs. Relative Paths 3. Use a Log File to Facilitate Troubleshooting 4. Test Manually Before Implementing Automation 4.1. Use the Same Account for Manual Testing and Automation 4.2. Using a Configuration Folder from another Account 4.3. Avoid Hanging SFXCL Processes Needing User Input 5. SFXCL Exit Codes 6. Using Wildcards 7. ASCII vs. Binary Transfers 8. Generating Unique Log File Names 8.1. Generating a Unique Log File Name within a Batch File 8.2. Generating a Unique Log File Name within VBScript Code 9. Example Batch Files 9.1. Upload .CSV Files 9.2. Download .DAT Files 10. Example VBScript Code 10.1. Upload .CSV Files 10.2. Download .DAT Files