Defining a File Transfer job

This procedure describes how to define a File Transfer job, which enables you to watch and transfer files from a local host to a remote host, a remote to a local host, or a remote host to another remote host.

NOTE: Control-M for AFT jobs on Control-M/Agent and Control-M MFT jobs on another Control-M/Agent cannot belong to the same Host group.

Before You Begin

Ensure that you have met the following requirements:

• A configured Control-M Managed File Transfer connection profile, as described for the Control-M for MFT Connection profile management.
• Successful completion of Accessing the Accessing the File Transfer job properties pane.

To define a File Transfer job:

1. In the General tab, from the Connection Profile field, click .

   The Select Connection Profile dialog box appears.

2. In the Connection Profile Type area, select one of the following:
   • Endpoint1 <-> Endpoint2: Shows connection profiles that are defined with two hosts. Select this option if the source and destination locations are defined in the same connection profile.
   • Two Single Endpoints: Shows connection profiles that are defined with one host. Select this option if the source and destination locations are defined in separate connection profiles.

   NOTE:

   • If you are transferring a file to an external user, you must select the connection profile that is connected to the Hub that uses an SFTP protocol.
   • AS2 connection profiles can be paired with Local connection profiles only. FTP and SFTP are not supported.
   • S3 does not support transfers to and from AS2, MVS, OS400, OS2200, OpenVMS, and TANDEM.
   • S3 does not support appending content to S3 objects. Therefore, Rerun from point of failure and Append destination action are not supported.
3. Select the connection profile(s) that you want to use to transfer files, and click OK.
4. (S3 and Azure Blob only) Do one of the following:
   • If you are transferring a file to or from S3, in the Bucket field(s), click and select an Amazon S3 bucket.
   • If you are transferring a file to or from Azure Blob, in the Container fields, click and then select an Azure Blob container.
5. In the Transfers area, do the following:
   1. In the Transfers area, in the first field browse for the file, directory, or library to transfer. You can also type the path manually.

      NOTE: If you are transferring a file to an external user, you must type in the B2B Subfolder home directory (example: /b2bhome) that is defined in MFT Enterprise B2B settings, as described in General Settings.

      NOTE: In AS2, you cannot determine the destination file path. You can override the destination filename, subject, and content type.

   2. In the second field, browse for the file, directory, or library to transfer. You can also type the path manually. If you are transferring a file to multiple hosts, select one of the following:
      • Home Directory: Transfer the file to the home directory on each host.
      • Common Destination Path:Transfers the file to the same location on each host defined here.
      • Different Destination Paths: Transfers the file to different destinations on each host. Click and define each path by browsing to each file in File Selection or modify the locations in one view in Paths List.
   3. Select the transfer option, as described in Transfer options.

   NOTE: You can transfer up to five files at a time, but file transfers within a job are sequential, which means that if a file transfer fails, subsequent file transfer definitions are not performed, unless you select the Continue on failure checkbox, as described in Advanced general parameters.

   NOTE: If a transfer has CJK or Latin-1 characters in the filename, the Control-M/EM server and Control-M/Server databases must be compatible with this format.

6. From the Type drop-down list, select the transfer format.

   EBCDIC format is supported only when transferring files between two MVS FTP hosts.

7. Click Advanced.

   The Advanced dialog box appears.

8. Select the required options, as described in Advanced options, and click OK.
9. Select the optional parameters if required, as described in Optional parameters.
10. Click More.

    The Pre-execution Command and Post-execution Command fields are used to define specific commands to execute at the beginning or at the end of a job. These commands can only be executed on a computer where Control-M/Agent is installed, and the output of the commands (pre or post) appears in the job output.