Transfer file

Description

file_transfer

The Transfer file activity allows you to receive or send files, test whether there are files present, or list files in Adobe Campaign.

Context of use

The way in which the data will be extracted is defined when the activity is configured. The file to load may be a list of contacts, for example.

You can use this activity to recover data that will then be structured with the Load file activity.

Configuration

  1. Drop a Transfer file activity into your workflow.

  2. Select the activity, then open it using the button from the quick actions that appear.

  3. Use the drop-down list in the Action field to select one of the following activity actions:

    wkf_file_transfer_01
    • File download: allows you to download a file.

    • File upload: allows you to upload a file. Uploading a file from Adobe Campaign file generates a log entry in the Export audits menu. For more information on export audits, refer to the Auditing exports section.

    • Test to see if file exists: allows you to check whether there is a file.

    • File listing: allows you to list the files present in Adobe Campaign.

    Depending on the action selected, one or several protocols are available:

    • HTTP: this protocol allows you to start downloading a file from an external account or from a URL.

      • Click the Use connection parameters defined in an external account option, then select the account you would like and specify the path of the file to download.

        wkf_file_transfer_03

        Cuidado:

        Wildcards are not supported.

      • Click the Quick configuration option, then enter the URL in the field that appears.

        wkf_file_transfer_04
    • S3: this protocol allows you to start downloading a file from a URL or an external account via Amazon Simple Storage Service (S3).

      • Select the external account and specify the path of the file to download.

        wkf_file_transfer_08
    • SFTP: this protocol allows you to start downloading a file from a URL or an external account.

      • Click the Use connection parameters defined in an external account option, then select the account you would like and specify the path of the file to download.

        wkf_file_transfer_07

        Cuidado:

        Wildcards are supported.

      • Click the Quick configuration option, then enter the URL in the field that appears.

    • File(s) present on the Adobe Campaign server: this protocol corresponds to the repository containing the file(s) to recover.

      Metacharacters, or wildcards (for example * or ?) can be used to filter files.

      Fill in this field and confirm your activity to use this protocol.

      Observação:

      The path must be relative to the storage space directory of the Adobe Campaign server. Files are located in the sftp<yourinstancename>/ directory. You also cannot browse the directories above the storage space. For example: user<yourinstancename>/my_recipients.csv is correct. ../hello/my_recipients.csv is incorrect. //myserver/hello/myrecipients.csv is incorrect.

    Select your protocol and complete the associated fields.

  4. The Additional options section, available depending on the protocol selected, allows you to add parameters to your protocol. You can:

    • Delete the source files after transfer

    • Disable passive mode

    • List all files: this option is available when selecting the File listing action. It allows you to index all the files present on the server in the vars.filenames event variable in which the file names are separated by the 'n' characters.

  5. The If no files are found section of the Advanced options tab allows you to configure specific actions if any errors or inexistent files are detected when the activity is started.

    You can also define retries. The different retries appear in the workflow execution log.

  6. Confirm the configuration of your activity and save your workflow.

Historization settings

Every time a Transfer file activity is executed, it stores the uploaded or downloaded files in a dedicated folder. One folder is created for each Transfer file activity of a workflow. Therefore, it is important to be able to limit the size of this folder in order to preserve physical space on the server.

To do that, you can define Historization settings in the Advanced options of the Transfer File activity.

Historization settings allow to define a maximum number of files or total size for the activity's folder. By default, 100 files and 50 MB are authorized.

Every time the activity is executed, the folder is checked as follows:

  • Only files created more than 24 hours before the execution of the activity are taken into account.

  • If the number of files taken into account is greater than the value of the Maximum number of files parameter, the oldest files are deleted until the Maximum number of files allowed is reached.

  • If the total size of files taken into account is greater than the value of the Maximum size (in MB) parameter, the oldest files are deleted until the Maximum size (in MB) allowed is reached.

Observação:

If the activity is not executed again, its folder will not be checked nor purged. With this in mind, be cautious when transferring large files.

Example

The following example shows the configuration of a File transfer activity which will then be followed by a Load file activity then an Update data activity. The goal of this workflow is to add or update the Adobe Campaign database profiles with the data recovered by the workflow.

  1. Drag and drop a Transfer file activity into your workflow.

  2. Select the activity, then open it using the button from the quick actions that appear.

  3. In the Protocol tab, select SFTP.

  4. Select the Use connection parameters defined in an external account option.

  5. Enter the name of the external account.

  6. Enter the File path on the remote server.

    wkf_file_transfer_07
  7. Confirm your activity and save your workflow.

Esta obra está licenciada sob uma licença não adaptada da Creative Commons Attribution-Noncommercial-Share Alike 3.0  As publicações do Twitter™ e do Facebook não são cobertas pelos termos do Creative Commons.

Avisos legais   |   Política de privacidade online