Job Type Deployment
When you have finished adding Execution steps to your job type, you are now ready to deploy the job type to Control-M Agent and to any Control-M client. Before deploying your job type, you can test the job type before exposing it to end users. You can view the following:
The Connection Profile, Job Definition and Run time parameters you have previously defined
Monitoring field which shows whether the job type ran together with start, run and end time information.
Whether each step is valid with a detailed log
If after deployment you want to change or remove the job type, you can do the following:
Edit the job type after deployment: Enables you to edit the job type in the Application Integrator and redeploy, which overrides the previous deployed version. If you have added new fields, you need to decide how to treat the new fields for existing jobs in Control-M. For more information about redeployment, see Redeploying the Job Type.
Undeploy a job type that has been previously deployed: Removes the job type from all Control-M Agents and clients. The job type is undeployed first and then the job type is deleted. After the job type has been successfully undeployed, the job type is removed from the job palette in Control-M (after the next log in). To undeploy, see Undeploying the Job Type.
If undeployment was unsuccessful for one or more Agents (such as connectivity or permission issues) a warning message appears displaying which Agents are not removed. These Agents may still display the job type but it is not possible to access the job type from the GUI.