Control-M Feature List
Click a tab to view the version's features.
For more information about version features, enhancements, corrected problems, known issues, and compatibility information, see Control-M Release Notes.
Support Status: Out of support
Released: July 2010
End of Support: November 2017
What's new | Description |
---|---|
Dynamic Workload Policies |
Defines a set of rules for a group of jobs that can:
|
Rule-based Calendars |
Define Rule-based Calendars (RBCs) to set the dates that will be scheduled (included RBCs) in a job, sub-folder, and SMART folder, by adding and selecting the RBCs for the Rule-based Calendar list. |
One Installation for all product components |
Installs Control-M/EM, Control-M/Server, Control-M/Agent and all Application Plug-ins. |
Annotation for user actions |
Requires users to write a free text annotation, describing the reason for the action before the action is performed. System administrators can define which user actions require annotation. |
L&F enhancements to Reporting Facility |
|
Conversion tool |
The Control-M Conversion Tool enables you to import data from other schedulers. |
Add-ons |
The following add-ons are available in version 7.0.00:
|
Plug-ins |
The following plug-ins are available in version 7.0.00:
|
Support Status: Out of support
Released: November 2012
End of Support: March 2020
What's new | Description |
---|---|
Simplified User Interface |
Control-M version 8.0.00 has a new simplified user interface that enables you to perform tasks efficiently with less training. The simplified user interface has the following items:
For more information, see Simplified User Interface in Control-M version 8.0.00 Release Notes. |
Workspaces |
Workspaces are used to edit jobs/folders that can be shared by users. They can be checked in and checked out to enable you to lock and edit jobs/folders. This process replaces write and upload. Workspaces are stored in a database which allows collaboration with other users. For more information, see Workspaces in Control-M version 8.0.00 Release Notes. |
Significant performance and capacity improvement |
Control-M/Server’s selector process that is responsible for submission is much more enhanced. The time between job submissions has been reduced significantly, and many more jobs can be submitted by one Control-M/Server. For more information, see What's new in Control-M/Server in Control-M version 8.0.00 Release Notes. |
Linux 64bit |
Control-M 8.0.00 now supports Linux 64bit on Control-M/Enterprise Manager, Control-M/Server, and Control-M/Agent. |
Zero downtime for Control-M/Agent Upgrade |
Control-M/Agent on Unix platforms can now be migrated to Control-M version 8.0.00 without any downtime. For more information, see Control-M/Agent enhancements in Control-M version 8.0.00 Release Notes. |
Trial Mode Installation |
The installation of Control-M version 8.0.00 allows you to install a trial version of the solution with all optional components including:
This version is intended for testing and evaluation, not for use in a production environment. |
Full Installation |
The Control-M 8.0.00 full installation includes the following Application Plug-ins:
|
Application Plug-ins |
Now you can install all Application Plug-ins using the new Control-M Application Plug-in DVD. |
Terminology |
Several terms were changed from previous releases in Control-M version 8.0.00.
|
Support Status: Out of support
Released: July 2015
End of Support: October 2020
Feature | Description |
---|---|
High Availability |
Control-M High Availability enables you to maximize your production environment uptime and prevent data loss in the event of a hardware maintenance or failure. When using an Oracle or MSSQL database, in the case of a hardware issue or if all processes are unexpectedly down, you can perform either an automatic or manual failover for both Control-M/EM and Control-M/Server. Once the problem is fixed, you can fall back to the primary host. When using a Control-M PostgreSQL database, the database can be replicated. If there is a hardware issue, you can perform a manual failover to a secondary Control-M server, and later, when the problem is fixed, you can fallback to the primary Control-M server. |
Automated Agent deployment |
Upgrade one or many agents to 9.0.00 and future versions of fix packs in just a few simple steps. Options are available to transfer the package to agents and deploy at a later time, or automatically transfer and deploy in a single step. |
Automated Client deployment |
The new Client deployment utility replaces the WebLaunch tool in previous Control-M versions. Use the Client deployment utility to easily distribute full client installation packages, fix packs and patches to users. Set policies to force users to apply update packages by a specific date. |
Control-M Configuration Manager (CCM) enhancements |
The CCM user interface has been updated to improve user experience.
The Configuration Agent starts up all the required components. You no longer have to start up the CMS, NS or PostgreSQL database (if installed). |
Promotion between environments |
Promotion between environments is a new capability of the Control-M Workload Change Manager that enables you to move job definitions between environments, such as from a development environment to a production environment. During the promotion process, the job definitions are modified and validated according the Site Standards of the target environment. |
Runtime estimations |
With Control-M Batch Impact Manager, you can now see the estimated runtimes of all the jobs in a regular viewpoint without them being defined as a part of a Batch Impact Manager service. |
Usage Alerts |
Keep an eye on your task usage with Usage Alerts, available from within the CCM. Define task usage alert thresholds across all of your Control-M/EMs. Exceeding a threshold will send an email alert. |
Security enhancements |
The SSL certificate deployment capability extends the packaging and deployment of SSL security certificates with an option to specify an external Certificate Authority. |
Improved security algorithms |
Control-M Enterprise Manager password hashed using SHA-512. SSL support for:
|
NFS support for Control-M Server and Control-M Agent installation |
You can now install Control-M/Server and Control-M Agents on NFS. |
IPv6 communication |
IPv6 support, including support for mixed IPv4 and IPv6 environments, is now available for the following components:
|
Additional options to enhance the power of your enterprise scheduling |
|
What If Host simulation |
New capability for Control-M Batch Impact Manager and Forecast to simulate the influence of the unavailability of a specific Control-M Agent or a group of Control-M Agents on your job flows, and prepare for planned shutdowns and maintenance windows. |
Global Calendars |
You can now save time and reduce the efforts invested in calendar management by creating a single calendar in the Control-M Enterprise Manager that will be distributed to all the Control-M Servers. |
Bookmarks |
You can bookmark the jobs in a workspace or a viewpoint to analyze flows and easily locate jobs. Bookmarks are supported in the Planning, Monitoring, Forecast, and History domains. |
Export flow diagram to a file |
You can now export flow diagrams to a Microsoft Visio-compatible EMF format from any domain. Just click the Save as option in the application File menu. |
Enhanced search when loading jobs to a workspace |
You can now view more fine-tuned search results when loading jobs into a workspace in the Planning domain by filtering folders and jobs with a larger variety of fields. |
Online Help on Web server |
The online help is now available from the Control-M Web server. NOTE: Verify that the Web server is up. |
Multiple Application plug-ins installation |
You can now install Application plug-ins from the Control-M full installation DVD. |
Support Status: Full support
Released: January 2018
End of Support: March 2023
Feature | Description |
---|---|
Control-M upgrade |
Control-M/EM and Control-M/Server software upgrades can now be installed in-place with minimal downtime. The in-place upgrade supports both annual releases and fix packs. In-place upgrade is supported from Control-M version 9 fix pack 1 and later. |
Control-M Managed File Transfer |
|
Version compatibility |
The new in-place upgrade process ensures version compatibility across Control-M components, with the following guiding principles:
|
Client Distribution |
|
Application Pack deployment |
|
Cyclic folders |
Provides a simple setup of cyclic scheduling options at the SMART folder level, including:
|
End folder |
This new attribute can be used to mark one or more completion points in the folder’s flow. When a job that is marked with the ‘end folder’ attribute completes, no additional jobs in this folder are submitted. After all the jobs in the folder are complete, the folder status changes to Completed. This new attribute allows you to define a folder with a flow that has more than one potential logical end. NOTE: This feature is disabled when running with Compatibility Mode turned on. |
Variable simulation |
Provides the ability to simulate variables that are resolved before or during job submission. This eliminates the need to order and execute certain jobs, which for example, check if the Variable Simulation syntax is correct. This ability covers job submission variables, system variables, user-defined variables, global variables and pool variables. NOTE: This feature is disabled when running with Compatibility Mode turned on. |
Control-M Reporting |
Control-M Reports replaces the previously released Reporting Facility. Control-M Reports comes with the following enhancements and capabilities:
For migration instructions (from the existing Reporting Facility to Control-M Reports), see Control-M Reporting Facility migration. |
Protected Field in the Monitoring domain |
Provides the ability to disable editing of the command line and Node ID/Group fields for all non-admin users in the Monitoring domain using the ModifyJobFieldsBlock system parameter. |
Recent Viewpoints |
When starting up Control-M client, after Control-M client closes or crashes, you can see recently opened viewpoints. NOTE: Only applies if you select Auto Open Viewpoint and then select Recent Viewpoints from File ->Options -> Monitoring. |
Control-M Batch Impact Manager (BIM) |
Two new BIM alert types were added:
|
Control-M Web |
The Control-M Workload Change Manager web interface has been rewritten in HTML5, aligning it with industry standards. It now supports multiple browsers on various platforms including Google Chrome, Microsoft Internet Explorer, Microsoft Edge, Mozilla Firefox, and Safari. In addition, the two web interfaces (Workload Change Manager and Self Service) were merged into a single interface containing the following three domains:
|
External PostgreSQL |
Control-M can now work with an external PostgreSQL database owned by the customer. This support covers AWS PG RDS as well. NOTE: This support does not cover Workload Archiving. |
Amazon Linux |
Control-M can now be installed on Amazon Linux. This includes Control-M/EM, Control-M/Server, and Control-M/Agent. |
Live Control-M Help |
Control-M help files are now hosted on the BMC Documentation portal. These help files are generated daily and include the latest content updates, corrections, new videos, and more. Along with this capability is the option to opt out of going online every time you invoke the help and instead use the help that was installed with the release. However, this help remains static and does not contain the content updates that are published in the live hosted help. |
Communication improvements |
The Control-M/EM client now connects to the Control-M/EM server using HTTP/HTTPS standards. All communication between the clients and servers is done on a single port via the Control-M Web Server. Setting up SSL between the Control-M/EM client and Control-M/EM server was simplified even further and now only requires that you set up the Control-M Web server. After the upgrade, if HTTPS was not configured on the Control-M Web Server prior to the upgrade, all the Control-M clients communicate using HTTP (unsecured). To go back to having a secured connection, you must set up the Control-M Web Server. After configuring the Control-M Web Server you need to verify that the Windows keystore includes the certificate authority (CA) you used for the Control-M Web Server configuration. The Control-M Web Server configuration tool, manage_webserver, allows you to configure ports, HTTPS, SSL, and other advanced settings. For more information, see Configuring secure communication between Control-M client applications and the Web Server. |
Self-Conversion – ‘Build your own conversion |
Control-M Self Conversion is a powerful application with an intuitive web interface that allows you to build new conversions from any scheduler, application, or homegrown infrastructure into Control-M folders and jobs. |
Major enhancements in multiple conversion types |
|
Control-M Automation API |
The following are some of the major APIs enhancements:
For additional information, see Automation API services. An additional group of enhancements focuses on the extension of the Automation API JSON code. Some of these major enhancements include:
For additional information, see Automation API Code Reference. Deploy descriptor Control-M Automation API now supports the use of a deploy descriptor file to change job definition properties in JSON format before building, deploying, or running the JSON file. Site standards enforcement Site standards are now enforced on deployed JSON files, based on CCM definitions. The site standards must adhere to those defined in Control-M. |
Support Status: Full support
Released: March 2019
End of Support: March 2024
Feature | Description |
---|---|
Control-M multicloud integration |
Control-M Application Integrator authentication for AWS & Azure Users can now easily leverage Application Integrator to integrate with any AWS & Azure services. This is supported by supplying the authentication credentials to AWS / Azure. There's a new Application Plug-in for AWS and a new Application Plug-in for Azure that enable easy integration from a Control-M job to AWS & Azure services (such as: Lambda / Function, StepFunction /LogicApps, and Batch). |
Control-M for AWS |
|
Control-M for Azure |
NOTE: Using Amazon Web Services (AWS) and/or Microsoft Azure services that are triggered by Control-M may result in additional costs as Control-M triggers APIs that consume resources on the cloud. |
Reporting | We now support the ability to share reports between users. This means that users can create their reports (based on a template) and share them with other users so they can run them. |
Server & Agent | Extended host name – We now support a longer host name (up to 85 characters) which addresses the issue of long host names that are created by AWS. Troubleshoot Agent – Control-M configuration manager now provides additional information on why an agent is not available, such as ping and connectivity status. |
Control-M Web | Control-M version 9.19 continues to expand web functionality. As part of our transition from desktop client to a consolidated web interface, Control-M version 9.19 introduces the 'Tools' domain with extended Site Standards and User Views mechanisms. In addition, Planning and Monitoring were extended with additional functionality. The following major enhancements are introduced in this release: Site Standards Site standards was enhanced to support developers to adhere their organizations’ restrictions when creating and editing jobs in a decentralized environment. This includes new 'conditional rules' and 'must have rules' for complicated scenarios to enforce standardization and efficiency among different organization parties. Viewpoints Starting from V19 users will be able to use Web Viewpoints as part of self-service to display jobs and jobs flows. Viewpoint display can be done on a specific Control-M/Server, jobs that are for a specific user, or according to job status. User Views Site customization was re-written and moved from the WLA client to Control-M web tools. User views allow users to customize Control-M Web's look according to organizational needs and support different user persona views (developer vs. ops). Order (Planning) The ability to order your business flows - jobs, folders, or partially based folders, is now available for checked-in folders on the Planning domain. Control-M Web users will be able to order all or selected jobs, assuming they have the permission to do it. Access to Control-D You can now access z/OS job output in Control-D web access through Control-M web interface (Monitoring domain) Mobile New mobile release is now available in Google Play and App store containing the following: Hold and Release functionality (new) and "service ok" status is now replaced with two statuses, Not started and Executed. |
Control-M Governance, Security & Control | As part of our continuous efforts to improve governance, security, and control in general, we've introduced the following capabilities in Control-M 9.0.19:
|
Control-M Conversion | Introducing a new automatic and simple way for migrating business flows from other schedulers, applications, and homegrown setups, into Control-M.
|
Control-M MFT & Control-M MFT Enterprise (B2B) | Control-M MFT is a fully integrated solution, providing full file management capabilities for both internal (application to application) transfers and transmissions to/from external trading partners.
|
Control-M Automation API | Control-M Automation APIs and Workbench Continue to evolve, enabling customers to give ownership to their developers to modernize and manage current job and workload orchestration as code, integrating it within their existing continuous integration and delivery pipeline (CI/CD) tool chains. Some of the major deliverables are: Automation API: Configuration Service
Automation API: Provision Service
Automation API: Additional Enhancements
Workbench
For additional information, see Automation API services or Automation API Code Reference. |
Control-M Application Pack | Control-M Application Pack was first introduced in version 9.0.18 of Control-M and has since been expanded. The Control-M Application Pack can be distributed and deployed on multiple agents using the Control-M Configuration Manager. Note that these agents must first be upgraded to Control-M version 9.0.18 or later. The latest Application plugin forms are now part of Control-M's latest client and cannot be installed separately. Control-M Application Pack currently includes the following Control-M application plugins:
Additional Application plugins are planned for inclusion in future releases. For additional information, see the Control-M Application Pack Release Notes. |
Support Status: Full support
Released: July 2020
End of Support: July 2025
Feature | Description |
---|---|
Role-based Administration (RBA) |
Role-based Administration introduces a new methodology allowing teams to have full control and autonomy on their stack. Users can install, configure, and monitor assets like Control-M/Agents, Application Plug-ins, and Connection Profiles using Automation API, Control-M Web, and the Control-M client. The new authorizations granularity allows Control-M Administrators to delegate control of administrative tasks to other users. The administrator can set which connection profiles, Agents, Application Plug-ins, and Run As users are available to each user and the level of permission the user/team has (browse/update/full). The pre-existing privileges are still valid while the new RBA privileges work in conjunction with them (an OR relationship). This means that adding RBA privileges to a user that already has access via the old privileges does not have an additional effect. To adopt this new model, Administrators are recommended to set 'Configuration' privileges to 'None' and then set Agent, Plug-ins, and Run As with RBA access. It is also recommended to set 'Security' privileges to None when planning to use Connection Profiles RBA access. This new capability is active only when compatibility mode is off (Compatibility mode is on by default after an upgrade). |
Centralized Connection Profile (CCP) |
A Centralized Connection Profile provides the ability to define connection profiles once on a central location (Control-M/EM) and use it across all available Agents. CCP is supported on Managed File Transfer, Application Integrator, Control-M for Database, Control-M for Informatica, Control-M for AWS, and Control-M for Azure. The connection profiles are stored on the Control-M/EM database and are synchronized with the Control-M/Servers connected to that Control-M/EM. Centralized connection profiles are unique by name and application type. Password encryption is done using AES256. All provisioning activities for centralized connection profiles are available from Control-M Web and automation API. This includes creating, updating, testing, and deleting centralized connection profiles. For these plug-ins, the management of local connection profiles is also available from the Control-M Web, via Plug-in Management. Centralized connection profiles help IT organizations reduce TCO of management connection profiles. In addition to the ease and simplicity of CCP creation and maintenance, the new connection centralized connection profiles help with faster disaster recovery and launching new plug-ins when needed. The information is accessible from a central location and stays available in any case of data migration, upgrade, and disaster recovery. To convert local connection profile to centralized connection profile you can use automation API. A sample script is available in the automation API community GitHub at https://github.com/controlm/automation-api-community-solutions. |
Control-M Web | Control-M Web is now available to all customers using Self Service. Control-M Web provides complete workflow life-cycle support from job planning to running, monitoring, and troubleshooting. You can use Control-M Web from your local web browser to manage the day to day operations for most Control-M users, eliminating the need to install and maintain the desktop client. For a complete list of Control-M Web supported capabilities, click here . New features in version 9.0.20:
Web interface new supported capabilities
|
Java (JDK) support | Control-M components are now verified with Open JDK, Oracle Solaris, and Azul JDKs. The following options are now available:
|
Control-M MFT | Control-M MFT is a fully integrated solution, providing full file management capabilities for internal transfers. This year we addressed some of the major requests of MFT customers and provided more file transfer options. In addition, we enhanced our ability to use S3, including shifting between buckets and remote transfers.
|
Control-M MFT Enterprise (MFTE) |
Control-M MFTE completes the MFT offering and provides the option to transfer files to/from external trading partners and the organization. Our MFTE product continues to evolve and now includes High Availability in active-active (always on) mode, LDAP integration, and Automation API for users and folders provisioning. MFTE is available only on Control-M Web. High Availability MFTE supports High Availability in active-active mode. This includes the ability to work with several Gateways and Hubs to enable uploading/downloading files even if one of the Gateways/Hubs is down. High availability mode ensures that all relevant data (users, virtual folders, rules, settings) are synchronized between cluster nodes. The solution requires a shared storage system (network file system) that must be defined. In addition, a reverse proxy is required and must be configured as part of the overall configuration. All protocols are supported in High Availability mode including FTP/FTPS/SFTP/AS2/HTTPS. LDAP Integration In addition to internal authentication that exists today, MFTE now supports LDAP integration, and also hybrid mode (LDAP and Database authentication). The authentication method should be defined in the Hub settings for MFTE in Control-M Web. Starting from this release users can select one of the following authentication methods:
To use LDAP on B2B, new configuration was added to the Hub settings. Users should be mapped into groups and LDAP groups in order to be authenticated as LDAP users. Multi-selection and download on B2B Hub Users can now select, delete, and download multiple files on the Hub. If multiple files are downloaded, a zip file will be created in the download directory |
Control-M Automation API | Check for the latest monthly release of Control-M Automation API. The following are the new API enhancements:
|
Control-M Multi-cloud Integration | Control-M Application Integrator authentication for Google Cloud Platform (GCP) Users can now easily leverage Application Integrator to integrate with any Google service. Application Integrator is enhanced and now includes native authentication to GCP. The authentication method is Service to Service. Automate SSL (TLS) certificate updates on Control-M agents As an Administrator, you can automate updates to SSL (TLS) certificates on multiple Control-M/Agents by incorporating new API request commands in scripts. A new set of API requests enables you to manage updates of SSL (TLS) certificates on SSL-configured Control-M/Agents. You can use these API commands to return the expiration date of a certificate on a specific agent, to create a Certificate Signing Request (CSR), and to deploy a signed certificate to the agent. These commands can be combined in scripts to automate SSL certificate updates on your Control-M/Agents. |
Application Integrator enhancements | Application Integrator was enhanced by the following:
|
Workload Change Manager Site Standard rules |
Site Standards was enhanced by the following:
|
Control-M Reports | Control-M Reports is now enhanced with additional capabilities:
|
Microservices |
Control-M/Server introduces new services as part of a common infrastructure with Control-M/EM. The common infrastructure is based on Kafka while the services appear in CCM. The services adopt to microservice architecture. The new services in Control-M/Server are:
The new services in Control-M/EM are:
|
Migration | A new migration flow is introduced with this version replacing previous migration flows. Migration is supported only for the same version (V9.0.20 to V9.0.20). Therefore, any hardware update will also involve in-place upgrade as part of the flow. Users can migrate to a new account using one of the options below (option 1 is preferable): Option 1:
Option 2:
|
New Operating systems and Databases support |
Operating systems Control-M Server and Control-M EM now support the following operating systems versions:
Control-M Agent, Control-M application pack and Control-M for MFT now support the following operating systems versions:
Control-M Agent, Control-M application pack now support also the following operating systems versions:
Databases Control-M Server and Control-M EM now support the following databases:
Important considerations when upgrading from Control-M 9.0.18 and below emdef utilities now support Site Standards and use a central validation service. As a result, the output of the validation messages has changed to be consistent with the Control-M client and Control-M Web interfaces. If you have automation using emdef utilities, we strongly recommend that you refer to emdef switches and the emdef example for more information. |
Support Status: Full support
Released: September 2022
End of Support:
For a list of new features in Control-M 9.0.21, see What's New in Control-M 9.0.21.
Comments
Log in or register to comment.