Skip to content

On-Demand Demo User Guide

Introduction

On-Demand Demo Architecture

The On-Demand demo flows in our Production Demo environment create a pod/replicaset of our high volume flows to demo. In addition to provisioning this environment and registering the agent, it also deploys the connection profiles, job types, and job definitions based off of user codes. This is leveraging an EKS cluster, and terminated the resources created based on a user specified termination date. This is initiated as an orderable service via Control-M, and the user inputs parameters when they order the service to dictate which deployment and flow is created.

Interested in how the On-Demand Demo resources are running? You can access the K8s Operational View here

On-Demand Demo Code Flow

Usage Instructions

  1. Login to your desired target environment:
Link
CTM VSE PROD
CTM VSE QA
  1. Navigate to the Self-Service Portal in the Monitoring Domain

  2. Select Order Service

  3. Select OnDemand Demo

  4. Complete the form

    • The User Code is a 3 letter, lower case, identifier used for Control-M Folder Name, Application, Sub-Application, Job Names, Agent Name, Hostgroup, and Kubernetes Resources.
    • The Email Address must be a valid BMC email address.
    • The Time to Live (days) is a list of duration values in days. This duration defines when the K8s resources created for the demo will be decommissioned.
    • The Selected Demo is a list of the available demos to be created On-Demand.
  5. Once the service is complete, you will recieve an email similar to the screenshot below containing details about the Demo

  6. Once Service is complete, Order the folder beginning with your User Code followed by the name of the Preferred Demo

    • For Example: dba_forecast_flow
  • Please keep in mind, you only have to complete the OnDemand Demo service once, while the Agent is still avaiable. All of the OnDemand Demo flows can be re-run before the Decommission Date.

  • Depending on the selected OnDemand Demo, completion times may vary. Please refer to the Demo Use Case Information section for more information on completion times.