MFT Watch Only
Introduction
Maintainer: volker_scheithauer@bmc.com & Virtual Team - Control-M MFT
Use Case Overview
This MFT use case leverages a File Watcher job to watch the necessary SFTP Source and kick off an event driven workflow following the file being found in the proper directory.
Use Case Technical Explanation
File Watcher job
[File Transfer File Watcher Attributes](https://documents.bmc.com/supportu/9.0.21/en-US/Documentation/File_Watcher_Job.htm)
The Folder "ZZM_CAP_GENERIC_AWS" 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 Job execution: ZZM CAP Watch SFTP Source
- Higlight: Watch SFTP Source
- Higlight: If no file is found, bypass MFT job executions
- Higlight: OnDo Action - Event Driven Execution
-
If ended OK: Add event βZZM_CAP_GENERIC_WNLY_FOUND_%%SMART_ORDERIDβ
-
If ended Not OK: Add event βZZM_CAP_GENERIC_WNLY_NOT_FOUND_%%SMART_ORDERIDβ
-
If ended Not OK: Add event βSet to OKβ
-
watch for file on SFTP location, based on global pool variable
-
add event based on file status
-
do not fail the job if no file is found
-
by using Control-M events, govern subsequent automation
-
- File Watcher: Watch only
-
Control-M OnDo action
-
Add Control-M variables
-
Connection Profiles:
- ZZM_LFS_AGT
- ZZM_SFTP_AGT2
-
Hostgroups:
- ZZM_AGT_01
-
Folder: ZZM_CAP_GENERIC_AWS
-
Variables:
-
%%ZZM_CTM_ENVIRONMENT
-
%%ZZM_USER_RUN_AS
-
%%ZZM_COMPANY
-
%%ZZM_USER_ID
-
%%ZZM_USER_EMAIL
-
- Global Variables from pool: ZZM_CAP_INIT
- %%\ZZM_CAP_INIT\FILE_PATH
- %%\ZZM_CAP_INIT\PROJECT_SMART_ORDERID
Requirements and Check-List Requires a local temp file. The temp file will be managed by the folder βZZM_CAP_GENERIC_INITβ. The folder βZZM_CAP_GENERIC_INITβ will set shared pool variables:
- Global Variables from pool: ZZM_CAP_INIT
- %%\ZZM_CAP_INIT\FILE_PATH
- %%\ZZM_CAP_INIT\PROJECT_SMART_ORDERID
Events (previously conditions) are dependencies between jobs or SMART folders on a shared Control-M/Server. Events enable successor jobs or SMART folders (entities) to begin execution once their predecessor entities finish execution. This happens when these entities have fulfilled all other defined prerequisites. An event is a type of prerequisite, along with scheduling criteria and resource requirements, that a job or SMART folder must fulfill before it can execute.
Demo Environment Information
Coming soon!