What's Changed in Control-M 9.0.21

The following sections describe  what's changed in Control-M version 9.0.21:

Control-M External Java

Control-M now requires an external JRE. To ensure that Java remains updated,  JRE deliveries are now decoupled from Control-M and are no longer part of the installation. This reduces installation size and enables you to use the JRE that is common within your organization. You must ensure that Java 11 is available on the Control-M component host machines. For more information, see Control-M External Java Installation.

Authorizations

The Control-M/EM Authorizations functionality is no longer available in the CCM. You must now define Control-M/EM users and roles in Control-M Web.

LDAP

The LDAP configuration functionality is no longer available in the CCM. You must configure LDAP in Control-M Web.

SLA Management, Control-M/Forecast, and Self Service

Control-M/EM installation now includes SLA Management, Control-M/Forecast, and Self Service.

Control-M/Agent

Control-M/Agent installation now includes Application Integrator and Automation API.

Control-M Application Integrator

The plug-in ID attribute of new plug-ins created in Application Integrator now supports only uppercase alphanumeric characters. It cannot contain underscores or any other special character.

Terminology

The following terms are now updated in Control-M Web to align with Control-M SaaS and Automation API terminology:

  • Order is now Run
  • Condition is now Event
  • On-Do is now If-Action
  • Quantitative Resources are now Resource Pools
  • Control Resources are now Lock Resources

CCM Idle Logout

The CCM functionality now includes an automatic logout mechanism for idle users after a specific time, as described in the CCMUserInactivityTimeout parameter in GUI Parameters.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*