What's new in this version
New developments in this version are divided into the following categories:
New features
The following new features were introduced in this version:
Feature | Link to further information | |
|---|---|---|
Page | Section | |
Management of "run as" users for running jobs on an agent | ||
Upgrading an existing Control-M/Agent and deploying certain plug-ins to an existing Agent | ||
Provisioning a Control-M/Server, either as a new server installation or by transferring an existing Control-M/Server from one machine to another (server rehydration) | ||
High Availability (HA) tasks on the Control-M/Server:
| ||
Configuration of authorizations for roles, users, and LDAP groups | ||
Full section (3 pages) | ||
Management of Workload Policies, including retrieval of details regarding defined Workload Policies and activation and deactivation of Workload Policies. | ||
Asynchronous generation of reports from Control-M Reports using two new API commands, as well as support for generation of shared reports. | ||
Support for providing annotations through API commands to justify the action, for when annotation is enabled in Control-M | Annotation input | |
Stored Procedure job (type of Database job) for running a program that is stored on the database | ||
SAP R/3 job with a Copy action (that is, duplication of another SAP R/3 job) and SAP connection profile | ||
Ability to limit incoming traffic into the Automation API server through a gateway, allowing communication only from a specific port. | Control-M Automation API configuration in the Administration section of the Control-M online help | |
Changes
The following changes were made in existing features in this version:
Feature | Link to further information | |
|---|---|---|
Page | Section | |
During setup, a default environment is no longer created for the installed Control-M Workbench. To add an environment for the Workbench, use the new API command environment workbench::add. | ||
The Control-M Automation Command Line Interface (CLI) is now installed on the Control-M/EM on Windows and Linux platforms during installation of Control-M, and it can be run from the bin directory. Manual installation is necessary only on other platforms and host computers. | ||
CLI connections to endpoints no longer require version compatibility. The CLI runs API commands on each endpoint according to the version of the Control-M Automation API installed at the specific endpoint. | — | — |
You can now filter the list of Agents returned by the config server:agents::get command according to a pattern that you specify. | ||
Job status results now include the estimated start times and end times of the next few job runs (up to 50).Estimations are based on run times of previous jobs runs, and are available only if Batch Impact Manager or Control-M Forecast is active in your environment. | ||
Jobs of type FileTransfer now support the use of the RunAsDummy job property, along with all other job types. | ||
Specific default settings defined under the Defaults object are now applied to the relevant types of objects — jobs, folders, or subfolders — and skipped when not relevant. | ||