HCL Workload Automation Version 10.2.0 Release Notes

The Release Notes for HCL Workload Automation, version 10.2.0 contain the following topics:

To download the appropriate package for your operating system and for HCL AI Data Advisor (AIDA), see the HCL License Portal.

For detailed system requirements for all supported operating systems and for HCL AI Data Advisor (AIDA), see the Detailed System Requirements page.

To access the HCL Workload Automation documentation, see the online documentation.

A complete list of new or changed functions in this release are documented in the Summary of enhancements. More information about new features, including helpful demo videos, can be found on the HCL Workload Automation What's New page. See also the V10.2.0 dedicated playlist on the Workload Automation YouTube channel.

Interoperability tables
Top

The level of support provided for the products and components listed in the interoperability tables covers all the shown versions.

On AIX systems, ensure the system library XL C++ Runtime, version 16.1.0.7 or later, is installed.

In the tables in this section the following acronyms are used:

AIDA HCL AI Data Advisor
DA HCL Workload Automation dynamic agent
DDM HCL Workload Automation dynamic domain manager or backup dynamic domain manager
DM HCL Workload Automation domain manager
DWC Dynamic Workload Console
FTA HCL Workload Automation fault-tolerant agent
MDM HCL Workload Automation master domain manager or backup master domain manager
ZWS Agent  HCL Z Workload Scheduler Agent

HCL Workload Automation: compatibility

Compatibility is supported on the latest available fix pack for each HCL Workload Automation release listed in the table:

MDM

DDM

DM

FTA

DA

ZWS Agent
MDM 10.2
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
9.4
DM 10.2
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
FTA 10.2
10.2, 10.1, 9.5, 9.4*
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
DA 10.2
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
DDM 10.2
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4
10.2, 10.1, 9.5, 9.4

HCL Workload Automation no longer supports TLS V1.0 and TLS V1.1. Only TLS V1.2, and TLS V1.3 are supported, by default TLS 1.2 is enabled. This enhancement ensures a higher security level for SSL communication. Ensure that all agents connecting to a master domain manager version 10.2 or later use TLS 1.2 or TLS 1.3.

*Note: The composer command line of the agent at version 10.2 works correctly with master domain managers at version 9.5 and later.

If you are upgrading to version 10.2.0 from versions earlier than or equal to 9.5FP3, you have to upgrade first to 10.2 GA.

If you are upgrading to version 10.2.0 from versions later than or equal to 9.5FP4, you can perform the upgrade as usual.

Dynamic Workload Console: compatibility

Compatibility is supported on the latest available fix pack for each release listed in the table:

MDM
DDM
DWC 10.2
10.2, 10.1, 9.5
10.2, 10.1, 9.5

AIDA: compatibility

Compatibility is supported on the latest available fix pack for each release listed in the table:

MDM
DDM DWC
AIDA 10.2
10.2, 10.1
 10.2, 10.1 10.2, 10.1

Compatibility scenarios and limitations

You are strongly recommended to maintain all HCL Workload Automation components at the latest fix pack level as regular maintenance activity. Keeping your environment consistent also ensures you can implement the new features available with each new release.

If you are upgrading from version 9.5 to version 10.2.0, you can perform both a parallel and a direct upgrade. If you are upgrading from version 9.4 to version 10.2.0, you can perform a parallel upgrade. For more information, see Upgrading from the CLI.

 Environment with agents at version 10.2 

If you are using the composer command line of the agent, the following limitation applies:
•    The composer command at version 10.2 works correctly with master domain managers at version 9.5 and later.

Environment with agents at version 9.4 and master domain managers at version 10.2

The following consideration applies:

•    After renaming resources or prompts from a master domain manager at version 10.2, you cannot reference nor use them on agents at version 9.4.

Fix packs released for this version of the product

To find the fix packs released for HCL Workload Automation, and the Dynamic Workload Console including links to the related readmes files, see HCL License Portal.


Software limitations and problems, and their workarounds
Top

The following are software limitations and problems that might affect HCL Workload Automation, and their workarounds (when available):

 
Centralized update fails on FTA-only due to incorrect SSL cert folder
This issue occurs when the centralized update is performed on a FTA target with no DA installed. It happens during the download phase of the agent image that will be used for the update from MDM to FTA. The transport of the image from MDM to FTA fails due to the incorrect folder (/opt/IBM/IWS/TWSDATA/ITA/cpa/ita/cert) is being referenced on the download command. 
Solution
As a workaround, copy the TWSClientKeyStore files from /opt/IBM/IWS/TWSDATA/ssl/GSKit to 
/opt/IBM/IWS/TWSDATA/ITA/cpa/ita/cert. Then, re-run the centralized update and it will be successful.
*Note: If you are upgrading to version 10.2.0 from versions earlier than or equal to 9.5FP3, you have to upgrade first to 10.2 GA.
For information about performing a centralized update on fix packs or upgrade on releases on a stand-alone fault-tolerant agent, see: Performing the centralized agent update.
Variable passing defect
During variable passing the keyword "Name" as a property key cannot be used for Jira plugin.
Reply Yes/NO not working
The actions REPLY_YES_PROMPT and REPLY_NO_PROMPT are not present for job or jobstream in objects info.
Trivy scan vulnerability 
The scan vulnerability allows an attacker to perform a DoS attack on an arbitrary server, but it is a false positive. The command line will be updated as soon as Kubernetes will release a fix.
Multiple dependencies are not added when a job stream is submitted
If you add multiple dependencies separated by a comma when submitting a job stream, dependencies are not added.
Workaround: Add each dependency separately with the follows keyword and use the semicolumn as a separator. For example:
Ocli plan submit sbs <jobstream> ; follows= <dep1> ; follows=<dep2> ; follows=<dep3>
REST API: time zone in UTC format only
When using REST API, if you run a query defining a time zone for the job in plan, the results are displayed in UTC format even if the defined value is different.
Broker resource fails
The CLI commands of broker resources do not work.
Orchestration Monitor filter on available and unavailable workstations does not work
When you perform a query of unavailable or available workstations using the "old" monitoring and the new Orchestration Monitor, the query results does not show the correct value.

You cannot install the Dynamic Workload Console using a shell in which you previously ran the twa_env command.

This limitation is due to the twa_env command, which sets the data_dir variable to the data dir of the master domain manager. If you need to install the master domain manager and Dynamic Workload Console on the same workstation, you can work around this limitation in one of the following ways:
•    Use the tws_env command instead of the twa_env command.

•    Specify the --data_dir parameter when running both serverinst and dwcinst commands, so that you can specify a different value for the data dir.

If you need to install the Dynamic Workload Console with the default values (without specifying the --data_dir parameter), using a shell from which you previously installed the master domain manager, ensure that the DATA_DIR variable is not set in the shell. To verify this, run the echo $DATA_DIR command.

APARS Fixed in this release
Table 1. APARs addressed in Version 10.2.0
APAR ABSTRACT
IJ31895 RESTFUL API ON POST HTTP REQUEST THE TASKSTRING AND TASKSTRINGINFO FIELDS ARE TRUNCATED
IJ44519 ISSUE EDITING EVENT RULE
IJ44916 IWS 9.5 FP6 APP SERVER CRASHES ON JOB STREAM SUBMIT
IJ45502 INSTALLATION OF 10.2 WITH CUSTOM CERTIFICATES FAILS (PROVIDING INTERMEDIATE CA IN THE ADDITIONALCAS SUBFOLDER)
IJ45889 STEPS DESCRIBED ON THE FOLLOWING TECHNOTE SHOULD BE ADDED INTO OFFICIAL DOCUMENTATION : HTTPS://WWW.IBM.COM/SUPPORT/PAGES/NODE/
IJ46251 USERS.EXE IN IWS 10.2 FOR WINDOWS NOT BE WORKING AS EXPECTED
IJ46607 TEST CONNECTION IS NOT WORKING FOR CYBERARK PLUGIN
IJ46692 EVENT RULE FOR PROMPT STATUS ASKED DOES NOT TRIGGER EVENT ON AD-HOC JOB PROMPT
IJ46850 WHEN TWS SERICES STOP ON ONE OF THE BKM'S, AND THEN ISSUE A LINK TO THAT BKM FROM THE MDM, IT UNLINKS OTHER BACKUP MASTERS AS WELL
IJ46851 CENTRALIZED UPDATE FAILS ON FTA-ONLY DUE TO INCORRECT SSL CERT FOLDER
IJ46960 WEBSPHERE APPLICATION SERVER LIBERTY BASE SERVICE IS NOT CREATED WHILE THE DOCUMENTATION SAYS THE OTHER WAY AROUND
IJ46984 GARBLED COMMAND OUTPUT WHEN LANG SETTING IS JAPANESE IN TWS 10.2
IJ47068 DOCUMENTATION ABOUT VERIFY_CN_STRING DOES NEED TO BE IMPROVED/ADJUSTED
IJ47111 CENTRALIZED UPDATE FAILS IF WORKSTATION NAME WAS CHANGED
IJ47146 POD LABLE IS ALWAYS REMAIN AS BACKUP MASTER
IJ47179 WINDOWS FTA USERS IN AD/LDAP GROUPS NOT AUTHENTICATING IN SECURITY FILE
 

Documentation updates

In the Planning and Installation manual, section Reference, add the following commands:

uninstall
Use this command to uninstall the File Proxy.
fileproxystop
Use this command to stop the File Proxy.

The unistall command syntax is as follows:

UNIX

./uninstall -inst_dir installation_directory [-lang language]

WINDOWS

uninstall.exe -inst_dir installation_directory [-lang language]

where

-inst_dir is the directory where the File Proxy is installed.

-lang is the language in which the messages returned by the command are displayed

The command removes all data related to the File Proxy and leaves the data_dir unchanged.

The fileproxystop command syntax is as follows:

UNIX

./fileproxystop

WINDOWS

fileproxystop.exe

In the Planning and Installation manual, section Reference, File Proxy installation - fileproxyinst script topic, note that the following parameters are required, even though they are documented as optional:

inst_dir
acceptlicense

All other updates to the HCL Workload Automation documentation that are required for version 10.2.0 are included in the editions of the publications in online HCL Workload Automation Publications.

 

Support statements about HCL Workload Automation containers on Amazon Elastic Container Service (ECS)

Users are not entitled to open a case if the issue is related to the configuration and deployment of HCL Workload Automation containers on Amazon ECS.

If an issue occurs on HCL Workload Automation at running time, users can open a case only if all these conditions are met:

  • The user has a container started
  • HCL Workload Automation is running
  • The user can restart the container inside Amazon ECS

If support believes that a user issue is generated by container deployment, support can ask the customer to reproduce the issue in an officially supported environment.

Top

© Copyright International Business Machines Corporation 2006, 2016. All rights reserved. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

© Copyright HCL Technologies Limited 2016, 2023.