Control-M Demo System Overview

Introduction

Our focus is to continue to make Control-M easier to use and more accessible for ALL VSE and Marketing DBA users. We invested a big effort in the shift to Cloud, making it as easy to use as possible and enabling a demo environment for everyone to use that does not require VPN access.

Our new deployment leverages a new AWS subscription provided by IS&T, that allows us to integrate with OKTA for an iDP. This also will allow users to consolidate the internal and external demo environments down to 1 environment that is accessible without VPN through iDP, and allows access to internal resources as well as external cloud resources.

Having ONE demo system will foster collaboration and creativity – by consolidating all of the current environments into ONE, that everyone has access to. This will eliminate cloud costs of users creating their own individual environments, and duplicated efforts of maintaining all of these satellite demo systems. This shared single environment will truly display “BMC on BMC” as we will have 3 environment regions for Dev, QA, and Prod like our customers deploy.

We will also integrate this environment with github for us to easily demonstrate and convey messaging about the agility the Automation API affords and be able to do it with an Enterprise repo rather than the free gitlab environment that has challenges due to the capabilities of that free offering.

Access the Control-M Demo Environments

Link
CTM VSE PROD
CTM VSE QA
CTM VSE DEV

For additional details on environment access please visit: Environment Access

Architecture

Prod Architecture

QA Architecture

BMC Enterprise Github Cloud

All of our demos as well as this documentation rely on projects in github, where we store and update artifacts. All of these artifacts are created and deployed to Control-M through Git CI/CD pipelines, maintaining Git as the source-of-truth.