Overview This document outlines the procedure for deploying the BMC Control-M Workbench (version 9.20.200) within a Docker environment. The Workbench provides a local development sandbox for the Control-M Automation API, allowing users to test workload automation jobs and orchestration flows without connecting to a production Control-M Server. The official BMC distribution currently provides access to the Workbench image without requiring a commercial license for evaluation purposes.

Introduction Last year, I spent some time studying Oracle Banking Microservices Architecture (OBMA), together with enterprise schedulers and orchestration platforms such as Control-M . Part of the work involved understanding how to convert traditional Control-M jobs into Airflow DAGs. During this process, I started to observe an important architectural distinction: Not all workflows are the same. While studying OBMA, I noticed that Netflix Conductor was used as the workflow engine inside the architecture.