Paths

The Paths tab includes the following panes:

  • Folders: Locations of the primary components of the MOVEit system.
  • URLs: Addresses used to access MOVEit services.

Folders and their Contents

The Folders panel provides access to data and application file paths.
Note: Web App, Non Web, and ISAPI are paths that MOVEit Transfer expects to be on the local machine.
Warning: External application and data Folder values can be controlled apart from the MOVEit TransferConfig utility. For example, before you move the MySQL database to another location or move the encrypted filesystem to another location, first check the current recommendation in the PSC/MOVEit Support Site Knowledge Base.
  • Web App: All of the local web application files needed for this MOVEit Transfer node to run.
  • Non-Web: MOVEit Transfer specific files that are needed for the internal function and utilities of the local MOVEit Transfer node.
  • Files: The root filesystem for MOVEit Transfer. If the root filesystem is stored on a remote location click Advanced to configure the UNC path of the remote location, and the username (<Server-name>\<username>) and password needed to access it.
    Note: It is best practice to include the server name when you enter the username associated with the shared folder, here is the expected syntax: <Server-name>\<username>. For example, FileNode01\webfarmuser. Otherwise, MOVEit Transfer services on the current node will be unable to mount the fileshare.

    For more information about using a remote location for the root filesystem, see System Internals - Remote Filesystem.

  • Logs: Root folder for MOVEit Transfer logs. Files include user activity logs, system status, server logs (FTP, WebUI, API), tampercheck logs, files rolled to archives, and so on. (Targeting a logs folder located on the local server machine is best practice.)
    Important: In general, sites (or Web Farm nodes) with higher transaction volumes or aggressive log settings (common when debugging) should not target remote UNC shares as a log file destination. High volumes of message handling hitting a single UNC can cause resource and performance bottlenecks.
  • ISAPI: The MOVEit ISAPI files and object dependencies on this local MOVEit Transfer node, which are needed for making secure transfers.
  • Database: Specifies the location of MySQL, if MySQL is the database engine being used by MOVEit Transfer.

URLs

  • Machine: Used to access authentication and other services from MOVEit Transfer. This URL should refer to the local machines (localhost). The Machine URLs are generated during installation of MOVEit and rarely need to be changed, except in cases where IIS access rules have been changed.
  • Machine2: is derived from the Machine URL.
  • Ignore certificate problems on machine URLs: if selected, allows the use of Machine URLs starting with https even if the certificate on this webserver was not issued by a trusted Certificate Authority. This setting lets you set the IIS setting of Require Secure connection. In this case, you must use https for the Machine URL.
  • Base: The URL that is used to connect users to the interface of MOVEit Transfer.
    • If there is no DNS name available or the DNS name is not resolved, you must use an IP address.
    • If you have installed an SSL certificate, specify the HTTPS protocol.

      This property can allow the secure connection with MOVEit Transfer with a test certificate that might not be able to be confirmed from a trusted source. Where Machine URLs are usually set to the localhost, they do not typically need to use https encryption.

      If machine URLs must use https encryption, and if the certificate is not trusted, you must set this field so that FTP can communicate with the machine URLs.