Changed features and feature capabilities in version 10.1 Fix Pack 1

A list of features changed since the previous release

The following features have changed or have been introduced or removed since the previous release:
REST APIs documentation automatically integrated into the product documentation
Information about REST APIs is automatically extracted from the code and integrated into the documentation at HCL Workload Automation API for easier reading and increased retrievability.
File Proxies now selected randomly in the Managed File Transfer integration
By default, the integration uses the File Proxy specified by the dynamic domain manager. You can also optionally define a list of preferred File Proxies to be used instead of the default list.
The File Proxy is selected randomly in the list provided by the dynamic domain manager. If you provided a custom list, the random selection is performed only on your list.
The random selection mechanism ensures higher tolerance for peaks in workload and workstation failures. For more information, see File Transfer Integration on Automation Hub.
Default storing mechanism of job log changed
When you perform a fresh installation, by default the job log is stored in memory instead of being stored in a file, as in the previous releases. This ensures compliance with the PCI standard. For more information, see Log files and archived files.
Enhanced security with the conn_verify property
You can now optionally set the conn_verify property to 1 or 2, so that the agent must provide valid certificates in order to establish an SSL connection. The default value is 0, which means that no verification is performed on certificates.
Hostname verification for File Proxy
You can now optionally enable a check on the hostname defined for the certificates used by File Proxy. To enable the verification, create the Java system property named wa.fileproxy.enforceSSLhostnameVerify and set it to true.
Hostname verification for the mail sender plug-in
You can now optionally define the MAILPLUGIN_ENABLE_HOST_VERIFICATION property in the TWSConfig.properties file to enable the verification of the hostname of the SMTP server. If you set the property to yes, hostname verification is enabled, if you set it to no, no verification is performed. The default value for fresh installations is yes.
Higher security for job integrations
The Verify host name check box is selected by default in some integrations. Starting from version 10.1 Fix Pack 1, to increase the security standard provided by the product, this selection starts a check on the data contained in the keystore file. Ensure you provide the correct path and credentials to the keystore file in the Certificates section for the following integrations:
  • JSR 352 Java Batch
  • Restful
  • Job Management
  • Job Stream Submission
  • Variable Table
If the information in the Credentials section is not correct, this causes the job to fail with an error similar to the following:
AWKJMJ041E An error occurred during the Job submission. 
The error was "AWKSPI006E Keystore authentication failed. The error message is 
"No certificates provided, cannot verify the hostname."
If your integrations fail after upgrading to Fix Pack 1, you have the following options:
  • deselect the Verify host name check box.
  • provide the correct path and credentials to the keystore file.