<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ctm on My learning and diary</title>
    <link>https://jackliusr.github.io/tags/ctm/</link>
    <description>Recent content in ctm on My learning and diary</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 03 Sep 2026 20:00:00 +0800</lastBuildDate><atom:link href="https://jackliusr.github.io/tags/ctm/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Control-M: Setting Up BMC Control-M Workbench 9.20.200</title>
      <link>https://jackliusr.github.io/posts/2026/09/control-m-setting-up-bmc-control-m-workbench-9.20.200/</link>
      <pubDate>Thu, 03 Sep 2026 20:00:00 +0800</pubDate>
      
      <guid>https://jackliusr.github.io/posts/2026/09/control-m-setting-up-bmc-control-m-workbench-9.20.200/</guid>
      <description>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.</description>
    </item>
    
  </channel>
</rss>
