Skip to content
VSE Control-M Docs Site

On-Demand Helix Demo and POV User Guide

Introduction

Helix 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

Helix On-Demand Demo Code Flow

On-Demand Helix POV Setup Architecture

The On-Demand Helix POV Setup was started as an effort to streamline Helix POVs.

Helix Control-M requires more agility in sales teams’ processes because of expectations that come with a SaaS environment. This automation is a three-step process intended to be used by Control-M presales to streamline the setup, export, and breakdown of a POV agent with workflows. The automation also works well as a demo to highlight an ephemeral Control-M agent running in Kubernetes.

The automation will stand up a namespace and containerized Helix Control-M Agent within our Automated Demos Kubernetes cluster. The agent will be registered with the Helix tenant stood up for the POV and also deploy the selected demos.

Usage Instructions

  1. Login to your desired target environment:
LinkDetails
CTM VSE PRODService will deploy resources into the Helix Control-M Production tenant unless POV is specifed
CTM VSE QAService will deploy resources into Helix Control-M SE-Dev Tenant unless POV is specified

  1. Navigate to the Self-Service Portal in the Monitoring Domain

  2. Select Order Service

  3. Select OnDemand Helix 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.
    • The POV parameter determines what environment to deploy the Demo and Helix Control-M Agent.
      - If this is a demo in Production Helix Control-M, this should be No. Note: if No, please ignore the remaining 3 fields in the form.
      - If this is for a POV, this should be Yes.
    • If POV is Yes, the POV Tenant AAPI Endpoint URL is required in the format https://sample-tenant-aapi.us1.controlm.com/automation-api. For more information on how to generate this value please see the Helix Control-M POV Setup Guide.
    • If POV is Yes, the POV Tenant AAPI Token Value is required. For more information on how to generate this value please see the Helix Control-M POV Setup Guide.
    • If POV is Yes, the POV Tenant Agent Token Tag Name is required. For more information on how to generate this value please see the Helix Control-M POV Setup Guide.

  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, navigate to the Target environment and 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 Helix Demo service once, while the Agent is still available. All of the OnDemand Helix Demo flows can be re-run before the agent is decommissioned.
  • Depending on the selected OnDemand Helix Demo, completion times may vary. Please refer to the Demo Use Case Information section for more information on completion times.