Job Type Definition

Job type definition enables you to define the operations that communicate with the application through one or more of the following:

You can mix Command Line, Web Services, or REST API operation steps as required.

For more information and practical examples see Control-M Application Hub.

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, Monitoring and Configuration domains. 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 enables you to check issues and fix them without deploying. For errors, you are prevented from deploying the application until you fix them. For Warnings, you can deploy without fixing them.

  • 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 the Agent. For more information about deploying the application, see: Job Type Deployment.