Plug-ins
Plug-ins bring Control‑M functionality to your external application environment. Control-M provides plug-ins that enable AgentsA Control-M component installed on a host that runs and monitors the jobs on the host to interface with external applications by integrating plug-in jobs with other jobs into a single workflow. Plug-ins are installed on the Agent inside your Control-M environment and connect remotely to the specific application. You do not need to install the plug-in on the same host as the application.
Control-M supports the following plug-ins:
Plug-ins |
Description |
---|---|
Connects to any supported database from a single computer with secure login, which eliminates the need to provide authentication. This enables you to define and monitor Stored Procedure, SQL Script, SQL Server Integration Services (SSIS) Package, and Embedded Query database jobs. |
|
Application Integrator |
Creates custom designed job types that are deployed to the scheduling environment. You can then define and monitor jobs in the Planning and Monitoring domains, using Web Services, REST APIs, or CLI commands. You can integrate to AWS, Azure, and Google Cloud Platform using their native authentication methods. For more information, see Application Integrator. |
Control-M Integrations |
Includes BMC-provided integration plug-ins for a variety of applications and environments. These plug-ins were developed using Application Integrator. To use any of these plug-ins, you must have Application Integrator installed. For more information, see Control-M Integrations. |
Connects to the Hadoop framework, which enables the distributed processing of large data sets across clusters of commodity servers. You can expand your enterprise business workflows to include tasks running in your Big Data Hadoop cluster from one central location using the different Hadoop-supported tools, including Pig, Hive, HDFS File Watcher, Map Reduce Jobs, and Sqoop. |
|
AWS |
Define and run AWS Lambda, Step Functions, and Batch services. For more information, see AWS Job. |
Azure |
Define and run Azure Function, LogicApps, and Batch services. For more information, see Azure Job |
Managed File Transfer |
Operates as an FTP/SFTP client and server solution that enables you to watch and transfer files from a local host to a remote host, a remote host to a local host, a remote host to another remote host, or between Amazon S3 buckets. Control-M MFT uses industry standard protocols, such as FTP (based on RFC 959) and SFTP and does not require installation on remote computers. To configure Control-M MFT, see Control-M MFT Configuration. For more information, see File Watcher Job. |
Enables you to manage both the traditional SAP, planned and automated processes, and the unpredicted real-time, event-driven dynamic job submission. |
|
Enables you to automate Informatica workflows. |
|
Enables you to trigger and monitor Airflow DAG runs. Every Airflow job represents a DAG run in Airflow. From the Monitoring domain, you can view all internal DAG task names, statuses, and view any defined task variables (XCom). Control-M allows direct access to view the DAG run from the Airflow Server interface. |
|
Enables you to define and schedule new Oracle E-Business requests and request sets, extract Oracle E-Business Suite predefined jobs, intercept ad hoc jobs, monitor active Oracle E-Business Suite jobs, trigger Control-M jobs and conditions as a result of ad-hoc events occurring in the Oracle E-Business Suite system. |
|
Enables you to automate report and job generation for pre-defined IBM Cognos reports and jobs. For more information, see IBM Cognos Job. |
|
Enables you to run and execute pre-defined InfoSphere DataStage jobs. For more information, see IBM InfoSphere DataStage Job. |
|
Enables you to enhance the scheduling and job handling capabilities in your PeopleSoft environment and serves as an interface between Control-M and PeopleSoft. |
|
Web Services, Java, and Messaging |
Enables you to expand Control-M job scheduling to on-line and real-time applications and implement effective application integration using three main industry standard technologies to achieve application integration; Java classes and J2EE Enterprise Java Beans (EJBs), Web Services, and Message-Oriented Middleware. For more information, Web Services, Java and Messaging Job. |
Before you can define a Job, you need to create a connection profile in the Configuration domain, which enables you to connect to the required application server. A connection profile contains the connection parameters to a specific application server, such as hostname, username, password, and application specific parameters. This enables your users to connect to the required application server with only the connection profile name. For more information, see Creating a Centralized Connection Profile.
In Control-M, you can manage the following connection profile types:
-
Centralized connection profiles: Enables you to store all connection profiles in the Control-M/EM database and are available to all of your Control-M/Agents in your environment. It saves you time and resources and there is no need to define connection profiles for each Control-M/Agent. For example, instead of updating the username and password for each local connection profile on each Control-M/Agent, update the centralized connection profile, sync, and it’s available to all relevant Control-M/Agents. In addition, if a Control-M/Agent host is no longer available, you don’t need to recreate the connection profile. Connection profiles are synced continuously to Control-M/Server. During job execution, Control-M/Server sends the required connection profile details to the Control-M/Agent. Centralized connection profiles are unique by name and application type.
-
Local connection profiles: Enables you to view and edit existing connection profiles that were created for each Control-M/Agent.