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:
-
Execute AWS Step Function state machines (workflows), define state machine parameters, and add job logs to the output.
-
Manage AWS Step Functions credentials in a secure connection profile.
-
Connect to any AWS Step Functions endpoint.
-
Introduce all Control-M capabilities to Control-M for AWS Step Functions, including advanced scheduling criteria, complex dependencies, resource pools, lock resources, and variables.
-
Integrate AWS Step Functions jobs with other Control-M jobs into a single scheduling environment.
-
Monitor the status, results, and output of AWS Step Functions jobs.
-
Attach an SLA job to the AWS Step Functions jobs.
-
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.21.300 |
|
Control-M/Agent |
9.0.21.300 |
|
Control-M Application Integrator |
9.0.21.301 |
|
Control-M Automation API |
9.0.21.310 |
Control-M for AWS Step Functions is supported on Control-M Web and Control-M Automation API, but not on the Control-M client.
To download the 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
Integration plug-ins released by BMC require an Application Integrator installation. However, these plug-ins are not editable and you cannot import them into Application Integrator. To deploy these integrations to your Control-M environment, import them directly into Control-M with Control-M Automation API.
Before You Begin
- Verify that Java is installed, as described in Control-M External Java Installation.
-
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.
-
Do one of the following to install the AWS Step Functions plug-in:
-
(9.0.21 or higher) Do the following to run the Control-M Automation API provision service:
-
Log in as an administrator to the Control-M/EM server host and save the downloaded ZIP file to the following location:
-
Linux: $HOME/ctm_em/AUTO_DEPLOY
-
Windows: <EM_HOME>\AUTO_DEPLOY
-
-
Log in to the account where Control-M/Agent is installed and run the following provision image command:
-
Linux: ctm provision image ASF_plugin.Linux
-
Windows: ctm provision image ASF_plugin.Windows
-
-
-
(9.0.20.200 or lower) Run the Control-M Automation API deploy service, as described in deploy jobtype.
-
-
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:
-
Automation API: Job:AWS Step Functions
To remove this plug-in from an Agent, see Removing a Plug-in from the Agent. The plug-in ID is ASF012023.
Change Log
The following table provides details about changes that were introduced in new versions of this plug-in:
|
Plug-in Version |
Details |
|---|---|
|
1.0.05 |
|
|
1.0.03 |
Eliminated redundant validation on the Connection Profile to avoid interference in the job execution. |
|
1.0.00 |
Initial version |
