Control-M for AWS Step Functions
AWS Step Functions enables you to create visual workflows that can integrate other AWS services.
Control-M for AWS Step Functions enables you to do the following:
- Connect to any AWS Step Functions endpoint from a single computer with secure login, which eliminates the need to provide authentication.
- Integrate AWS Step Functions jobs with other Control-M jobs into a single scheduling environment.
- Execute AWS Step Function state machines (workflows), define state machine parameters, and add job logs to the output.
- Monitor the status, results, and output of AWS Step Functions jobs in the Monitoring domain.
- Attach an SLA job to your AWS Step Functions jobs.
- Introduce all Control-M capabilities to Control-M for AWS Step Functions including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
- Run 50 AWS Step Functions jobs simultaneously per Agent.
Control-M for AWS Step Functions Compatibility
The following table lists the prerequisites that are required to use the AWS Step Functions plug-in, each with its minimum required version.
Component | Version |
---|---|
Control-M/EM | 9.0.20.200 |
Control-M/Agent | 9.0.20.200 |
Control-M Application Integrator | 9.0.20.201 |
Control-M Web | 9.0.20.200 |
Control-M Automation API | 9.0.20.250 |
Control-M for AWS Step Functions is supported on Control-M Web and Control-M Automation API, but not on Control-M client.
To download the required installation files for each prerequisite, see Obtaining Control-M Installation Files.
Setting up Control-M for AWS Step Functions
This procedure describes how to deploy the AWS Step Functions plug-in, create a connection profile, and define an AWS Step Functions job in Control-M Web and Automation API.
NOTE: Integration plug-ins released by BMC require an Application Integrator installation at your site. However, these plug-ins are not editable and you cannot import them into Application Integrator. To deploy these integrations to your Control-M environment, you import them directly into Control-M using Control-M Automation API.
Before you Begin
Verify that Automation API is installed, as described in Automation API Installation.
Begin
Create a temporary directory to save the downloaded files.
- Download the AWS Step Functions plug-in from the Control-M for AWS Step Functions download page in the EPD site.
- Install the AWS Step Functions plug-in via one of the following methods:
- (For version 9.0.21.or later) Use the Provision service of Automation API:
- As an administrator on the Control-M/EM Server, store the downloaded zip file in the following location.
Within several minutes, the zip file is available in all Control-M interfaces associated with the Control-M/EM.- Linux: $HOME/ctm_em/AUTO_DEPLOY
- Windows: <EM_HOME>\AUTO_DEPLOY
- As an application user on the Agent machine, run the provision image command, as follows:
- Linux: ctm provision image ASF _plugin.Linux
- Windows: ctm provision image ASF _plugin.Windows
- As an administrator on the Control-M/EM Server, store the downloaded zip file in the following location.
- (For versions lower than 9.0.21) Use the Deploy service of Automation API, as described in deploy jobtype.
- (For version 9.0.21.or later) Use the Provision service of Automation API:
- Create an AWS Step Functions connection profile in Control-M Web or Automation API, as follows:
- Define an AWS Step Functions job in Control-M Web or Automation API, as follows:
- Web: Creating a Job with AWS Step Functions Job parameters
- Automation API: Job:AWS Step Functions
Comments
Log in or register to comment.