The operations are split into the following steps:
Pre-Execution: (Optional) Defines an operation step that needs to execute before the main execution, such as initialization, log in information, creating a file or a database table.
Execution: Defines an operation step that runs during the main execution flow (selected by default). You can define several Execution operation steps, but you must define at least one Execution step, otherwise the job type is not valid and you cannot deploy.
Post-Execution: (Optional) Defines an operation that needs to run after completion, such as clean up, log out and adding completion data to output.
When adding a command line, web service or REST API step, you can add parameters, which appear in the Designer area so you can view how the parameters appear in the Planning and Monitoring domains in Control-M client, Control-M Web, and the Connection Profile in the Control-M Configuration Manager. You can also add parameters directly to the Connection Profile or Job Properties, without adding them first to the Command Line, Web Service or REST API operation step. However, if you add the parameters directly to the Designer area they are not added automatically to the Command Line, Web Service or REST API operation step. For more information, see Job type designer.
After you have finished adding the operations and parameters, you can do one or more of the following:
Save: Saves the application locally.
Validate: Enables you to test the job type before deploying, by clicking Validate from the toolbar. This is useful to use, so you can check errors and fix without deploying. If there are any errors, you cannot deploy the application. If there are issues from the validation (runs automatically before deploy), the following messages may appear:
Errors: Prevents you from deploying as you need to fix the error before deploying. For example, if the Execute operation does not contain a step, an error message is issued which you need to fix.
Warnings: Describes any problems with your application but you can still deploy.
Test: Enables you to test the job type before exposing it to end users. You can see whether each step is valid, a detailed log and start and end times. For more information, see Testing a job type.
Deploy: Sends the Application to Control-M Agent and any Control-M client. For more information about deploying the application, see: Job type deployment.
Export: Enables you to export a .ctmai file to your local list of job types. You can export the file and import it to another Control-M/EM environment. This is can be useful when you want to move your job type from a Test environment to a Production environment. For more information about importing job types, see Importing job from file.
