Control-M Agent PAFZ4.9.0.22.001
BMC Software is releasing Control-M/Agent PAFZ4.9.0.22.001 to correct various issues in Control-M SaaS Application Integrator.
Corrected Problems
The following table describes the Control-M Application Integrator problems that are corrected in patch PAFZ4.9.0.22.001:
| Tracking Number | Description | Impacted Integrations |
|---|---|---|
| CTM-13056 | Execution of an Application Integrator job that includes a WSDL step fails when deployed using Control-M Automation API. The following error message appears in the job output: The content of elements must consist of well-formed character data or markup. | Any user-defined Application Integrator plugin |
| CTM-13055 | A connection profile test for a job type that is deployed using Control-M Automation API fails, and the following error message appears: UCM0001 = cant find any operation for Connection profile test | Any user-defined Application Integrator plugin |
| CTM-13018 | The Load button fails to load values for job definitions, and the following error message appears: Error while trying to execute the job load button... Failed to execute REST URL... Missing connection profile... | Any user-defined Application Integrator plugin |
| CTM-13004 | A Retrieve output sub-step fails to retrieve the output of a REST API step while it is executing for display in the job output. |
|
| CTM-12987 | Command Line jobs fail if they are configured to use a connection profile with the Run As field and have the Use as environment variable option enabled. The following message appears in the logs: Cannot invoke "CmAccountDefinitionWrapper.decryptPassword(...)" | Any user-defined Application Integrator plugin |
| CTM-12941 | Data extracted from a Command Line step is printed to the job output even though the Output Handling option Print extracted data to job output is not selected. | Any user-defined Application Integrator plugin |
| CTM-12923 | Job type deployment fails on Windows, and the following exception appears in the logs: java.io.IOException: Cannot run program ""C:\Program": CreateProcess error=2, The system cannot find the file specified | Any user-defined Application Integrator plugin |
CTM-12903 | A load button configured with OAuth2 authentication fails to fetch values. | Any user-defined Application Integrator plugin |
| CTM-12901 | The pre-execution step in a plug-in is executed even though the Perform the Pre-Execute step before load operation option is turned off for the load button in the job definitions. | Any user-defined Application Integrator plugin |
| CTM-12823 | A connection profile that includes AWS authentication fails validation with the following error message: Fail in Execute - Test Flow Secret & Key | Any user-defined Application Integrator plugin |
| CTM-12818 | Output parameters in the SOAP response are not parsed correctly when the response is in XML format and contains the ampersand (&) character. |
|
| CTM-12814 | Jobs fail on Windows if a CLI step name includes one of the following characters: | Any user-defined Application Integrator plugin |
| CTM-12755 | A Control-M Web Services REST job completes with a status of OK even though it should fail, if the response.message.handling property in the aicm.properties file includes the text that appears in the HTTP failure message. |
|
| CTM-12743 | The Verify operation completion sub-step sets the status of the job to failed without retrying to verify according to the Retry in case of failure parameter. | Any user-defined Application Integrator plugin |
| CTM-12706 | Application Integrator procid files are accumulated in the procid directory and are not removed during the New Day procedure. | Any user-defined Application Integrator plugin |
| CTM-12696 | Job deployment using the provision command in the Control-M Automation API CLI fails due to a timeout if deployment does not complete in 60 seconds. To resolve this issue, the new rest.timeout property in aicm.properties is set with a default timeout of 120 seconds. | Any user-defined Application Integrator plugin |
| CTM-12630 | REST API calls over HTTPS do not validate server certificates. As a result, even if the server certificate exists, it is not properly verified. This causes the REST request to fail with the following error message: unable to find valid certification path to requested target | Any user-defined Application Integrator plugin |
| CTM-12592 | A job remains in Executing status even though a Kill command was issued. This occurs if the Kill command is issued after step execution ended and a Verify operation completion sub-step is running. | Any user-defined Application Integrator plugin |
| CTM-12572 | Deployment of a job type to a Control-M/Agent fails if 'localhost' is not resolved correctly. The following error message appears in the logs: "org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 1; Content is not allowed in prolog." | Any user-defined Application Integrator plugin |
| CTM-12542 | The output processed in the Output Handling section is only partial if it contains text surrounded by square brackets. | Any user-defined Application Integrator plugin |
| CTM-12531 | Only the first line is extracted from the Body element in an HTTP response during Output Handling of a REST API step. | Any user-defined Application Integrator plugin |
| CTM-12500 | White-space characters, such as newline or tab characters, are removed from the SOAP response in a Control-M for Web Services SOAP job. |
|
| CTM-12483 | The file that is created when you save content to a file during Output Handling of a REST API step is corrupt if the content is in binary format. | Any user-defined Application Integrator plugin |
| CTM-12400 | The end position for extraction of part of a line in a Command Line step is determined incorrectly. The search begins at the beginning of the line instead of beginning at the specified start position. | Any user-defined Application Integrator plugin |
| CTM-12389 | The proclog directory is filled with AI_DLL_TRACK files when Application Integrator jobs run, and the following error appears in the files: key too long: 72 | Any user-defined Application Integrator plugin |
| CTM-12355 | A REST API call with an empty Body and "Content-Length: 0" in the Header is processed incorrectly during execution. The "Content-Length: 0" setting is removed from the Header. | Any user-defined Application Integrator plugin |
Installing Patch PAFZ4.9.0.22.001 on UNIX
This procedure describes how to install Control-M/Agent patch PAFZ4.9.0.22.001 for Application Integrator on UNIX.
Before You Begin
- Verify that Control-M/Agent 9.0.22 is installed before you install this patch.
- Verify that no Control-M jobs are executing on the Agent.
- If you are using an AIX operating system, remove unused libraries from memory by typing the following command as a root user:
/usr/sbin/slibclean
Begin
- Log in to the Control-M/Agent host where Control-M Application Integrator is installed.
- Create a temporary directory to save downloaded files.
- Download the patch from the following S3 link:
https://control-m-pre-ga.s3.us-east-1.amazonaws.com/PAFZ4.9.0.22.001_GA/PAAIT.9.0.22.001_unix.tar.Z - Save the PAAIT.9.0.22.001_unix.tar.Z file in the temporary directory.
- Run the following command to shut down the Agent:
shut-ag - Extract the patch tar.Z file, using the following command:
zcat PAAIT.9.0.22.001_unix.tar.Z | tar -xvf - - Run the following command
sh setup.sh - Follow the on-screen instructions until the installation is complete.
- Run the following command to start the Agent:
start-ag
Note: After installation is complete, the new Agent version (9.0.22.001) might take several hours to be updated in the Configuration domain. If you want an immediate update of the Agent version, run the ag_ping utility from the Agent machine.
Installing Patch PAFZ4.9.0.22.001 on Windows
This procedure describes how to install Control-M/Agent patch PAFZ4.9.0.22.001 for Application Integrator on Windows.
Before You Begin
- Verify that Control-M/Agent 9.0.22 is installed before you install this patch.
- Verify that no Control-M jobs are executing on the Agent.
Begin
- Log in to the Control-M/Agent computer.
- Create a temporary directory to save downloaded files.
- Download the patch from the following S3 link:
https://control-m-pre-ga.s3.us-east-1.amazonaws.com/PAFZ4.9.0.22.001_GA/PAAIT.9.0.22.001_windows_x86_64.zip - Save the PAAIT.9.0.22.001_windows_x86_64.zip file in the temporary directory.
- Open Windows Services, right-click the Control-M/Agent service, and from the drop-down list select Stop.
- Extract the PAAIT.9.0.22.001_windows_x86_64.zip file.
Navigate to the temporary directory and run the following command:
PAAIT.9.0.22.001_windows_x86_64.exe- Follow the on-screen instructions until the installation is complete.
- Open Windows Services, right-click the Control-M/Agent service, and from the drop-down list select Start.
Note: After installation is complete, the new Agent version (9.0.22.001) might take several hours to be updated in the Configuration domain. If you want an immediate update of the Agent version, run the ag_ping utility from the Agent machine.
Uninstalling Patch PAFZ4.9.0.22.001 from UNIX
This procedure describes how to uninstall Control-M/Agent patch PAFZ4.9.0.22.001 for Application Integrator from UNIX.
Before You Begin
- Verify that no Control-M jobs are executing on the Agent.
- If you are using an AIX operating system, remove unused libraries from memory by typing the following command as a root user:
/usr/sbin/slibclean
Begin
- Log in to the account where Control-M/Agent is installed.
Run the following command to shut down Control-M/Agent:
shut-ag- Run the following command:
/<Agent_Home>/ctm/install/PAAIT.9.0.22.001/uninstall.sh - Run the following command to start up the Agent:
start-ag
Note: After uninstallation is complete, the Agent version (9.0.22.000) might take several hours to be updated in the Configuration domain. If you want an immediate update of the Agent version, run the ag_ping utility from the Agent machine.
Uninstalling Patch PAFZ4.9.0.22.001 from Windows
This procedure describes how to uninstall Control-M/Agent patch PAFZ4.9.0.22.001 for Application Integrator from Windows.
Before You Begin
- Verify that no Control-M jobs are executing on the Agent.
Begin
- Log in, as an administrator, to the host where Control-M/Agent is installed.
- Open Windows Services, right-click the Control-M/Agent service, and from the drop-down list select Stop.
- From the Control Panel, select Program and Features.
- Select Control-M Application Integrator 9.0.22.000 Patch 1 and click Uninstall.
- Open Windows Services, right-click the Control-M/Agent service, and from the drop-down list select Start.
Note: After uninstallation is complete, the Agent version (9.0.22.000) might take several hours to be updated in the Configuration domain. If you want an immediate update of the Agent version, run the ag_ping utility from the Agent machine.