Code Reference
Control-M Automation API enables you to manage jobs through JSON code.
The following topics provide code samples that describe how to define Control-M objects using JSON notation:
- Folder
- Job Properties
- Job types
- Calendars
- Connection Profiles
- Site Standards
- Site Standard Policies
- Secrets in Code
- Defaults
Control-M objects in JSON code
Each Control-M object begins with a "Name" and then a "Type" specifier as the first property. All object names are defined in PascalCase notation with first letters in capital case. In the examples below, the "Name" of the object is "ObjectName" and the "Type" is "ObjectType".
"ObjectName" : {
"Type" : "ObjectType"
}
The following object types are the most basic objects in Control-M job management:
Object type | Description |
---|---|
Folder | A container of jobs. The following types of folders are available:
You can use a Flow to define order dependency between jobs in a folder. |
Job | A business process that you schedule and run in your enterprise environment. |
Calendar | A set of scheduling criteria that you can apply to multiple jobs (instead of having to define scheduling criteria in each individual job). |
Site Standards | A set of rules that enable you to control job definition by enforcing restrictions on job parameters. |
Site Standard Policies | Site Standard Policies enable you to enforce Site Standards on folders. |
Connection Profile | Access methods and security credentials for a specific application that runs jobs for an installed plug-in. |
Defaults | Definitions of default parameter values that you can apply to multiple objects, all at once. |
Related information
For more information about Control-M, use the following resources.
Comments
Log in or register to comment.