EFT.log File

EFT can be instructed to log specific or all HTTP request headers.

Refer to https://kb.globalscape.com/KnowledgebaseArticle11033.aspx for details of configuring an advanced property to log all HTTP request headers.

Capturing AML Workflow Upgrade Errors in EFT Logs

Overview

When upgrading to EFT v8.3.2, the EFT installer and service use the Automate Desktop AML conversion tool to upgrade Automate workflows (AML files) to the newer Automate version.

With this enhancement, EFT now captures Automate AML conversion errors and writes them into the EFT log, making upgrade issues easier to diagnose.

NOTE: The EFT installer only converts AMLs for sample files. Customer workflows are not upgraded until the EFT service is started after installation. Errors for customer workflows will appear when the service performs the upgrade.

What Changed

  • EFT now listens for and captures error output from the Automate Desktop AML conversion tool.

  • When a workflow fails to convert to the upgraded Automate version:

    • EFT records a conversion failure entry in the EFT logs.

    • The log entry includes:

      • The workflow name or identifier that failed to upgrade.

      • The specific line item (step) in the workflow where the failure occurred, as provided by Automate.

NOTE: Some workflows may not be upgraded automatically. Certain Automate workflows use computational logic or dynamically generated configurations that the AML conversion tool cannot analyze during upgrade. When these workflows fail to convert, EFT records the error in the EFT log so administrators can review and update the workflow manually.

Manually Run the Automate Import Tool

To run the import tool manually you first need access to the AML on disk, you can export the AML or access it from the AML backup directory (created on upgrades).

  1. In command line navigate to the Automate installer path, C:\Program Files\Globalscape\AutoMate (default)

  2. Use the following syntax: ImportUtil.exe <path to source> /o <path to new location>

  3. Review any errors outlined by the Import Utility