Control-M Communication Suite
Communication Suite enables you to automate business messaging and communication over Microsoft Teams, Slack, Telegram, and WhatsApp.
Control-M Communication Suite enables you to:
- Connect to any of the supported communication platforms from a single computer with secure login, which eliminates the need to provide authentication.
- Integrate Communication Suite jobs with other Control-M jobs into a single scheduling environment.
- Send text messages through any of the supported communication platforms.
- Monitor the status, results, and output of Communication Suite jobs in the Monitoring domain.
- Attach an SLA job to your Communication Suite jobs.
- Introduce all Control-M capabilities to Control-M for Communication Suite including advanced scheduling criteria, complex dependencies, Resource Pools, Lock Resources, and variables.
- Run 50 Communication Suite jobs simultaneously per Agent.
Control-M Communication Suite Compatibility
The following table lists the prerequisites that are required to use the Communication Suite 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.200 |
Control-M Web | 9.0.20.200 |
Control-M Automation API | 9.0.20.250 |
Control-M Communication Suite 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 Communication Suite
This procedure describes how to install the Communication Suite plug-in, create a connection profile, and define a Communication Suite job in Helix Control-M and Automation API.
Before you Begin
- Verify that Automation API is installed, as described in Setting up the API.
- Verify that Agent version 9.0.21.080 or later is installed.
Begin
- On the Agent host, set the Java environment variable by running one of the following commands through a command line:
- Linux:
- Bourne shell/bash: export BMC_INST_JAVA_HOME=<java_11_directory>
- csh/tcsh: setenv BMC_INST_JAVA_HOME <java_11_directory>
- Windows: set BMC_INST_JAVA_HOME="<java_11_directory>"
- Linux:
- Run one of the following API commands:
- For a fresh installation, use the provision image command:
- Linux: ctm provision image COM_plugin.Linux
- Windows: ctm provision image COM_plugin.Windows
- For an upgrade, use the following command:
ctm provision agent::update
- For a fresh installation, use the provision image command:
- Create a Communication Suite connection profile in Helix Control-M or Automation API, as follows:
- Helix Control-M: Creating a Centralized Connection Profile with Communication Suite Connection Profile Parameters
- Automation API: ConnectionProfile:Communication Suite
- Define a Communication Suite job in Helix Control- or Automation API, as follows:
- Helix Control-M: Creating a Job with Communication Suite Job parameters
- Automation API: Job:Communication Suite
Was this page helpful? Yes No
Submitting...
Thank you
Comments
Log in or register to comment.