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 the specified versions:

Start adding filters for your table either in the macro settings or on the filtration pane.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...
FeatureVersionPageSection

You can now include an additional header in login requests sent by the CLI using the new additionalLoginHeader property in the environment update command.

This is useful, for example, if your connection with the API server goes through an API Gateway that requires an additional authorization header during login actions.

9.0.19.120Services > Environment serviceenvironment update

File Transfer jobs now support file transfers from the local filesystem to an AS2 server using the AS2 protocol. A new AS2 connection profile is available for use by such File Transfer jobs.

9.0.19.120

Code Reference > Job types

Code Reference > Connection Profiles

Job:FileTransfer

ConnectionProfile:FileTransfer:AS2

File Transfer jobs now support the FTPS (FTP over SSL) communication protocol. A new type of connection profile is available for use by such File Transfer jobs.9.0.19.120Code Reference > Connection ProfilesConnectionProfile:FileTransfer:FTPS
The new config item::recycle command enables you to recycle (that is, restart) a specific Control-M component. Currently, this command supports recycling of Control-M/Agents.9.0.19.120Services > Config serviceconfig item::recycle

The RerunIntervals and RerunSpecificTimes properties now support folders, in addition to jobs.

9.0.19.110Code Reference > Job Properties

RerunIntervals and RerunSpecificTimes

File Transfer jobs now support file transfers from the local filesystem to Amazon S3 storage or S3-compatible storage and vice versa. For such file transfers, the new S3BucketName parameter must be included in the job definitions. New S3 connection profiles are also available for use by these File Transfer jobs.

9.0.19.110

Code Reference > Job types

Code Reference > Connection Profiles

Job:FileTransfer

ConnectionProfile:FileTransfer:S3:Amazon

ConnectionProfile:FileTransfer:S3:Compatible

A new type of If action, Action:CaptureOutput, now enables you to search job output and capture text from the job output into a variable.

9.0.19.100Code Reference > Job PropertiesIf Actions > Action:CaptureOutput
When specifying a Site Standard to enforce on a folder or simple folder, you can now specify values for its Business Fields through the JSON code.9.0.19.100Code Reference > FolderFolder and Simple Folder
The Rerun property now supports cyclic folders, in addition to cyclic jobs. The RerunLimit property now also supports folders, in addition to jobs.9.0.19.100Code Reference > Job PropertiesRerun and RerunLimit
The Confirm property now supports folders, in addition to jobs and subfolders.9.0.19.100Code Reference > Job PropertiesConfirm
When specifying a time period under the When property, you can now use the ActivePeriod parameter to choose between specifying a period of activity (when the job can run) or specifying a period of inactivity (when the job cannot run).9.0.19.100Code Reference > Job PropertiesSpecifying a period when a job can or cannot run
When specifying a time period under the When property, you can now specify a predefined Confirmation calendar to use for validation of scheduling dates and you can indicate how to handle jobs that are scheduled for a non-working day in this calendar.9.0.19.100Code Reference > Job PropertiesSpecifying a Confirmation calendar
SAP BW job for running and monitoring a Process Chain in SAP Business Warehouse (SAP BW). 9.0.19.100Code Reference > Job typesJob:SAP:BW:ProcessChain
Informatica job for automation of Informatica workflows and an Informatica connection profile.9.0.19.100

Code Reference > Job types

Code Reference > Connection Profiles

Job:Informatica

ConnectionProfile:Informatica

File Transfer connection profiles were enhanced with several new optional parameters:

  • WorkloadAutomationGroups — enables you to specify roles (groups of users) that are allowed to access the connection profile.
  • VerifyDestination — Verifies the size of the file at the destination after a successful binary-mode transfer.
  • VerifyBytes — Verifies that the number of bytes sent to the destination during a successful binary-mode transfer is the same as the source file.
9.0.19.100Code Reference > Connection ProfilesConnectionProfile:FileTransfer

The new run job::waitingInfo command enables you to display the reasons why a waiting job has not yet been executed (for example: missing conditions, resources, hosts, users, or workloads).

9.0.19.100Services > Run servicerun job::waitingInfo
The run order command now supports ordering of z/OS type jobs.9.0.19.100Services > Run servicerun order
The new deploy ai:jobtype and deploy ai:jobtypes::get commands enable you to deploy Application Integrator job types to the Control-M/Agent and to get details of such job types.9.0.19.100Services > Deploy service

deploy ai:jobtypes::deploy

deploy ai:jobtypes::get

The deploy service, which enables you to transfer job and configuration definitions to Control-M, now supports the use of a folder definitions XML file. This is in addition to the job definitions XML file, which was already supported.

For the retrieval of existing definitions, the deploy jobs::get command now enables you to choose the job definitions XML format for the output, in addition to the folder definitions XML format and the JSON format (the default).

9.0.19.100Services > Deploy service

Changes

The following changes were made in existing features in the specified versions:

Start adding filters for your table either in the macro settings or on the filtration pane.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...
FeatureVersionPageSection

Responses to API commands of the run service no longer display session tokens in URLs.

To display session tokens in URLs in responses to API commands (as in previous versions of the product), you can use a new setting in the automation_api_config file, as described in the Control-M Administrator Guide.

9.0.19.100

Services > Run service


Values of useextended, a Boolean parameter of the ConnectionProfile:SAP element, were changed from yes/no to true/false.9.0.19.100Code Reference > Connection ProfilesConnectionProfile:SAP

Corrected problems

The following table lists issues that have been corrected in the most recent releases:

Start adding filters for your table either in the macro settings or on the filtration pane.

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

The table is being loaded. Please wait for a bit ...

Tracking #

Description

Version
noneConfiguration actions performed by the config service do not work on Solaris and AIX.9.0.19.120
DRDEV-45

Deployment of a job in XML format times out after a minute, with no user control over the timeout definitions.

To resolve this issue:

  1. In the automation-api.properties file, add the emdef_timeout parameter, and set it to a value that is longer than the default 60000 milliseconds (1 minute).
    For example:   emdef_timeout=180000
  2. For the new setting to take effect, restart the API process (the emrestsrv process).
9.0.19.120
DRDEV-43When deploying a job that uses a site standard with a rerun interval, the job fails to validate and issues an internal validation error.9.0.19.120
DRDEV-41When more than one API session use the same token, after one session logs out, the other sessions might receive a null pointer exception error.9.0.19.110

DRDEV-33

When an order of a folder or job fails, the error message that is returned is empty and does not provide information about the issue.

9.0.19.100

DRDEV-39

The deploy jobs::get command returns an erroneous EndFolder=True (that is, folder set to cyclic folder) when the job type is dummy or RunAsDummy=true.

9.0.19.100

DRDEV-38

Folder deployment fails with error message "String index out of range".

9.0.19.100
CAD-2518

Installation of a plug-in on an agent using the provision upgrade command fails if the first three characters in the name of the installation package include a numerical character (for example, DR1CM*).

9.0.19.100
DRDEV-31When deploying a folder that has an argument that uses the value of a variable, the variables enter the Control-M/Enterprise Manager in the incorrect order and result in an error.9.0.19.100
DRDEV-25Uninstallation of an agent using the provision service fails when the Control-M/Server is on a Windows host and a case mismatch is encountered in the host name specified by the system variable.9.0.19.100
DRDEV-27When the number of GUI sessions is limited in the Control-M environment, the API session is identified as a GUI session and is included in the count of open GUI sessions.9.0.19.100
DRDEV-24Getting job details using the deploy jobs::get command returns an error when the job contains an array of parameters and the first parameter is not defined.9.0.19.100
DRDEV-21

The config server:agent::delete command fails to delete a Control-M/Agent from the Control-M/Server database when the host name contains .com or .org.

9.0.19.100
DRDEV-16Incorrect job status returned by the run jobs:status::get command for a job that was deleted.9.0.19.100
DRDEV-28Deployment of a folder with a rule-based calendar but no when property results in daily execution of the jobs within the folder.9.0.19.100
DRDEV-29

Deployment of an Application Integrator connection profile fails on the most recent version of the Control-M/Enterprise Manager.

9.0.19.100
DRDEV-26

In the XML file returned by the deploy jobs::get command, newline characters erroneously appear as \r\n.

9.0.19.100
DRDEV-18

Deployment of a connection profile fails when more than one Control-M/Server is defined in the environment.

9.0.19.100
CAD-2182The Access-Control-Allow-Origin: * header returns as a vulnerability in CORS security scans.

This header has been removed from all request responses.

9.0.19.100
DRDEV-13Application Integrator (AI) job properties that were defined as mandatory are not validated properly.9.0.19.100
DRDEV-14Deployment failures occur when the Control-M/Server has a patch installed.9.0.19.100
DRDEV-1In a distributed EM environment, the API server fails to find the Application Integrator endpoint for running or deploying AI jobs.9.0.19.100
DRDEV-15The API server fails to start or stop on Solaris 10.9.0.19.100
Was this page helpful? Yes No Submitting... Thank you

Comments