Skip to content
VSE Control-M Docs Site

MFT Watch and Transfer

Introduction

Maintainer: volker_scheithauer@bmc.com & Virtual Team - Control-M MFT

Use Case Overview

File Transfer File Watcher Attributes

Use Case Technical Explanation

The Folder "ZZM_CAP_GENERIC_WXFER" is scheduled to run every hour of the day.
No need to order the folder.
  • Create CTM Viewpoint for ZZM CAP
    • Group by: Application -> Sub Application -> Folder
    • Filter by Application: ZZM*
    • Demo Sub Folder execution: ZZM_CAP_WXFER
      • Higlight: ZZM Data Service Create Temp Files
      • Higlight: ZZM Data Service Watch and Transfer
      • Higlight: Watch and Transfer
        • File Name: /tmp/zzm/%%SMART_ORDERID/data.*
        • File Destination: /%%SMART_ORDERID/
        • Crate directory: /%%SMART_ORDERID on target SFTP server
        • File Watcher maximum time wait: 5 minutes
        • Multiple File Transfer
      • Higlight: Simulate Cyclic Watch and Transfer
        • Multiple File Transfer of files not captured by prior job

Demo Building Blocks: Watch and Transfer

  • Consolidated MFT and WLA together on a single, unified platform

    • A Single Pane of Glass for Business and Data Governance

    • Re-Imagine your MFT Landscape with Improved Service Levels

    • Secure and Reliable MFT for Big Data, Multi-cloud, and DevOps initiatives

      • Scheduled: 🚧

      • Manual oder for now

        • create # of temp files and size based on smart folder variables
        • execute MFT job with “watch and transfer in parallel
        • in case the temp file size exceeds GB size, the inital “watch and transfer” job will not copy all of the temp files
        • simulate a cyclic execution of the “watch and transfer” job by executing a 2nd “watch and transfer” job
        • clean-up temporary files

    Demo Flow

    • Create temp file(s), at least three. Controlled via %%ZZM_FILES_TEMP_COUNT

      • Initial Watch and transfer

      • Simulate Cyclic Job. Catch files that where not yet present when prior job ran. Happens if temp giles are in GB size. Controlled via %%ZZM_FILE_SIZE_UNIT

      • Connection Profiles:

        • ZZM_LFS_AGT
        • ZZM_SFTP_AGT2

      • Hostgroups:

        • ZZM_AGT_01

      • Folder: ZZM_CAP_GENERIC_WXFER

      • Variables:

        • %%SMART_ORDERID
        • %%ZZM_CTM_ENVIRONMENT
        • %%ZZM_USER_RUN_AS
        • %%ZZM_FILE_SIZE_UNIT
        • %%ZZM_FILES_TEMP_COUNT

      • Application: ZZM CAP Demo

      • Sub Application: 20. Watch and Transfer

    Requirements

      markdown title="Requirements and Check-List"
      Requires a local temp file. The temp file will be managed by the job "ZZM Data Service Create Temp Files".
      Based on the smart folder variable "%%ZZM_FILES_TEMP_COUNT" a certain amount of temp files will be created.
      The smart folder variable "%%ZZM_FILE_SIZE_UNIT" defines the size of the temporary file.
    

      "ZZM Data Service Create Temp Files" contains an embedded script "zzm.create.temp.files.sh" that will manegd the temporary files.
    • Local Variables: - VAR_ZZM_SMART_ORDERID - VAR_ZZM_USER_RUN_AS - VAR_ZZM_CTM_ENVIRONMENT - VAR_ZZM_FILE_SIZE_UNIT - VAR_ZZM_FILES_TEMP_COUNT