https://github.com/controlm/automation-api-quickstart

Control-M Automation API quickstart
https://github.com/controlm/automation-api-quickstart

automation automation-api control-m controlm jobs-as-code

Last synced: 4 months ago
JSON representation

Control-M Automation API quickstart

• Host: GitHub
• URL: https://github.com/controlm/automation-api-quickstart
• Owner: controlm
• License: other
• Created: 2016-08-09T08:51:58.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2025-04-24T10:10:00.000Z (about 1 year ago)
• Last Synced: 2025-04-24T11:24:45.936Z (about 1 year ago)
• Topics: automation, automation-api, control-m, controlm, jobs-as-code
• Language: Shell
• Homepage:
• Size: 167 MB
• Stars: 98
• Watchers: 30
• Forks: 99
• Open Issues: 8
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Control-M Automation API quickstart

This repository contains code samples and how-to for Control-M Automation API.  

+ [**Download Workbench for Docker**](https://hub.docker.com/r/controlm/workbench) - the latest development Control-M environment. 

+ [**Download Automation API CLI**](https://s3-us-west-2.amazonaws.com/controlm-appdev/release/latest/ctm-cli.tgz) (ctm-cli.tgz).  

+ [**Installation instructions**](https://docs.bmc.com/docs/display/public/workloadautomation/Control-M+Automation+API+-+Installation).  

## Online Documentation

You can find the latest Control-M Automation API documentation, including a programming guide, on the [**project web page**](https://docs.bmc.com/docs/display/public/workloadautomation/Control-M+Automation+API+-+Getting+Started+Guide).

## Contribution guide

To contribute, please follow these guidelines.

### Files, folders and naming conventions

1. Every sample and its associated files must be contained in its own **folder**. Name this folder something that describes what your sample does. Usually this naming pattern looks like **level-sample-purpose** (e.g. 201-automate-corrective-flow). Numbering should start at 101. 100 is reserved for things that need to be at the top.

2. For consistent ordering **create all folders in lowercase**.

3. Include a **README.md** file that explains the sample. A good description helps other community members to understand your sample. The README.md uses [Github Flavored Markdown](https://guides.github.com/features/mastering-markdown/) for formatting text. If you want to add images to your README.md file, store the images in the **images** folder. Reference the images in the README.md with a relative path (e.g. `![alt text](images/sampleImage.png "Sample Image Text")`). This ensures the link will reference the target repository if the source repository is forked.

4. The samples are split into two major categories, Control-M and Helix Control-M. Make sure that you upload the sample under the correct category.