Runtime information for the ExportData GUI

This topic provides runtime information for the ExportData tool's GUI.

Before using the GUI for the first time, review the following list to familiarize yourself with how several key areas of it function:

• Encryption. The tool does not encrypt or compress exported files and handles currently encrypted files as follows:

  • EFS encryption. Files retain EFS encryption if exported to another NTFS device that also uses EFS encryption.

    CAUTION: If exporting files to an NTFS device that uses EFS encryption, the exported files are encrypted under the Windows user account running the tool.

  • Full-disk encryption. Files retain their system-level encryption if exported to a device that also uses full-disk encryption.
  • Third-party application-level encryption. Files retain their encryption and are not accessible after export unless decrypted with the same third-party application and encryption key or password that encrypted them.

• Credentials. The GUI always prompts for credentials.

  Each time you run the GUI, it prompts for Connected credentials. After verifying them, it securely stores the resulting OAuth tokens in a properties file, named dataExport.properties, located in the home directory of your local user account. The tool uses these tokens only while processing requests during the current run and deletes the file when you exit the tool.

  NOTE: The dataExport.properties file contains security credentials. To ensure that you do not compromise the security of your system, do not edit this file or share it with others.

• Multi-instance support. The tool supports multiple instances when installed in different locations.

  You can install the ExportData tool in different locations and run a single instance of each one in parallel. However, to ensure optimal system performance, OpenText recommends that you keep the number of simultaneous instances running to a minimum.

  Multiple instances are semi-independent of each other. They maintain separate request histories and log files but share the same exportData.properties file and therefore the same OAuth token. As a result, if one instance changes or deletes the token, it affects all other instances.

  To perform an action on a particular request, such as to cancel or resume it, you must do so using the instance that ran the request. When running multiple instances of the tool, you can export files to a common destination, such as C:\Export, because the tool exports data to request-specific folders.

  NOTE: If you attempt to run multiple instances of the tool from the same installation, the tool processes only one command at a time.

• Logging. For information about the type and location of the status and error messages that the GUI logs, see Troubleshoot ExportData tool errors.