Share:|

Would you like to improve your Control-M Workflow development cycle?

 

Have you heard about the Automation API WorkBench?

 

In this webinar Ruben Villa will explain and demonstrate how to use some of the latest tools and techniques to speed up your implementation of workflows.

 

This is the link on YouTube for the recorded session:

 

Connect with Control-M: Control-M Automation API: Advanced - YouTube

 

Here is the Q&A for this webinar (Connect with Control-M: Control-M Automation API: Advanced)

 

________________________________________________________________

 

Q: Do I need a separate Control-M license for Automation API?

A: No, Automation API is installed with Control-M/Enterprise Manager 9.0.00.200

________________________________________________________________

 

Q: What types of jobs am I able to run using Workbench?

A: The type of jobs are the same available on the last version of Automation API: Hadoop, Manage File transfer, command, etc.

________________________________________________________________

 

Q: What form is the workbench machine in?

A: It can be Windows or UNIX

________________________________________________________________

 

Q: Also, is it intended to run the workbench locally or on a remote hypervisor?

A: The Workbench runs on a Virtual Box, it can be installed locally or in a remote host

________________________________________________________________

 

Q: What level of access is required for building jobs from the JSON?  I see "emuser", which implies administrator.  Can Update users do the same or is special access required?

A: API uses ctmcli and needs to get 2 tokens for login.  One from the GUI Server (GSR) and a second from the Control-M Configuration Server (CMS). 

Because of this it needs login privileges for both as defined in the CCM under Authorizations for the user that is attempting to login.  Specifically in Privileges for "Control-M Configuration Manager" and "Control-M Workload Automation, Utilities........"

________________________________________________________________

 

Q: Where can I get the workbench?

A: Downloads and Installation info are in:

https://docs.bmc.com/docs/display/public/workloadautomation/Control-M+Automation+API+-+Installation#Control-MAutomationAPI-Installation-workbenchControl-MWorkbench

________________________________________________________________

 

Q: In the demo, are the jobs created in the AJF only? Can you save the job definition instead of creating a job?

A:  Yes, with the Deploy Service, once a job is deployed, it will be scheduled by Control-M according to its scheduling criteria and dependencies.

________________________________________________________________

 

Q: How does Workbench Submission affect Task Counts?  If the DevOps is ordering jobs directly into the environment, won't this increase my task count?

A:  No, as the Workbench is a Virtual Environment.

________________________________________________________________

 

Q: How can Automation API be used to deploy jobs to environments, not just for testing?

A:  You can have multiple environments (connections) and after testing your flows, you can submit the requests to a production environment.

________________________________________________________________

 

Q: Can I use automation API for Informatica jobs?

A:  Informatica Job Type is not available at this moment.

________________________________________________________________

 

Q: Is automation API available in Control-M Version 8?

A: No, Available from Control-M/Enterprise Manager 9.0.00.200

________________________________________________________________

 

Q: Can empass be encrypted instead of clear text?

A: The encryption can be done at the application level.

________________________________________________________________

 

Q: Does job actually run in workbench?

A: No, this is just a simulation.

________________________________________________________________