HCL Workload Automation version 9.5.0 Readme File for Fix Pack 7
- Date
- March 28, 2024
- Fix Pack
- 9.5.0 Fix Pack 7 HCL-IWS-FP0007
- Product
- HCL Workload Automation version 9.5.0 Fix Pack 7
- General Description
- HCL Workload Automation Fix Pack 7 for version 9.5.0
This readme file provides important information about Fix Pack 7 for HCL Workload Automation version 9.5.0 fix Pack 7.
The most up-to-date version of this readme can be accessed at the following URL: Fix Pack readmes.
You can find the readme files for previous Fix Packs here:
It is divided into the following sections:
HCL Workload Automation version 9.5.0 Fix Pack 7 supports all product versions indicated in the Release Notes for HCL Workload Automation.
Review this section thoroughly before installing or using this Fix Pack.
About this Fix Pack
This section contains information specific for this Fix Pack including what has been modified or introduced, what has been fixed, product versions or components to which the Fix Pack applies, and compatibility issues, if any.
- Product versions and components to which the Fix Pack applies
- This Fix Pack can be applied only on top of HCL Workload Automation V9.5.0 and subsequent Fix Packs.
This section includes the following subsections:
Features introduced with Fix Pack 7
- Version 9.5 Fix Pack 7 delivers the following enhancements:
- Changed features and feature capabilities
Problems fixed in HCL Workload Automation Fix Pack 7 for version 9.5.0
This section lists APARs and internal defects solved by Fix Pack 7.
| APAR | ABSTRACT |
|---|---|
| IJ04749 | TWSINST SCRIPT FAILS WITH THE "-HOSTNAME" OPTION |
| IJ12526 | CHANGE IMPLEMENTATION OF AT/EVERY/EVERYENDTIME IN CASE OF SOD DIFFERENT FROM 0000 TO APPLY SOD TO THE AT AND EVERYENDTIME |
| IJ17321 | DA AIX RECONFIG SIGNAL |
| IJ20203 | CONMAN DISPLAYING A CORRUPTED USER NAME AFTER A JOB HAS LAUNCHED AND COMPLETED |
| IJ22130 | SUBMIT JOB FROM DYNAMIC WORKLOAD CONSOLE FAILS BECAUSE VARIABLE WAS NOT FOUND |
| IJ23925 | UPDATE JRE FOR ORACLE CPU JUL 19, OCT 19, JAN 20 |
| IJ26359 | JOBSTREAMINPLAN QUERY DID NOT HAVE THE REQUIRED HOW-MANY FIELD IN THE MANDATORY PARAMETERS |
| IJ29124 | JOIN DEPENDENCIES LOADED INCORRECTLY DURING FINAL EXECUTION |
| IJ31613 | JNEXTPLAN SCRIPT ACCEPTS INVALID OPTIONS |
| IJ31895 | RESTFUL API ON POST HTTP REQUEST THE TASKSTRING AND TASKSTRINGINFO FIELDS ARE TRUNCATED |
| IJ40130 | DEPENDENCY INCONSISTENCY FOR JOB STREAMS |
| IJ40389 | SECURITY FILE WITH A " ' " (SINGLE QUOTE) VIA MAKESEC <TEXT FILE> DOES NOT REPORT AN ERROR |
| IJ40519 | SHADOW JOB BIND AND STATUS CHANGE DURING FINAL EXECUTION |
| IJ40479 | CANNOT ADD SELECTED JOBS IN THE JOB STREAM IN WORKLOAD DESIGNER IN ITALIAN |
| IJ40632 | "AWSTPL002E THE PLANNED START TIME WAS NOT RELOADED" MESSAGE IN LOG FILE EVERY DAY |
| IJ40795 | SEGMENTATION FAULT AFTER OPERATOR COMMAND |
| IJ40824 | OPENSHIFT DYNAMIC AGENT JOB ABEND WITH AWKKUP024I AND AWKKUP020I MESSAGE |
| IJ40991 | AXWAY ST JOBS GO IN ABEND |
| IJ40992 | UNABLE TO USE PREDEFINED USER ID AND PASSWORD IN AXWAY PLUG-IN |
| IJ41037 | THE JOB STREAM END TIME REFLECTED IN THE CONSOLE IS DIFFERENT FROM ITS ACTUAL END TIME BASED ON THE LOGS |
| IJ41305 | TWS 10.1 GA BROKER SSL HANG |
| IJ41345 | RECOVERY OPTION RERUN NOT WORKING AS EXPECTED |
| IJ41481 | EVENT RULE FOR JOBSTREAMSTATUSCHANGED TRIGGERS DUPLICATE ACTION (SENDMAIL) |
| IJ41676 | DELAY IN "CONMAN SJ" REPLY WHEN THE SCHEDTIME IS ADDED TO THE QUERY |
| IJ41705 | DWC DASHBOARD DISPLAYS INCONSISTENT DATA IF MULTIPLE ZOS ENGINES ARE DEFINED BUT ONLY SOME OF THEM ARE USED IN THE DISPLAY |
| IJ41797 | 9.5 ON WINDOWS SUBMIT JOB STREAM FINAL FROM DYNAMIC WORKLOAD CONSOLE CAN CAUSE MASTER DOMAIN MANAGER CRASH |
| IJ42056 | SOMETIMES JOBS SUBMITTED WITH A SUBMIT JOB OPERATION (SBJ) REMAINS IN ADD STATE |
| IJ42139 | AWSJOM200E ERROR WHEN AT AND EVERYTIME ARE DEFINED PAST 0000 AND SOD IS NOT 0000 |
| IJ42610 | RESTART_STARTCOND PUTS IMPLICIT UNTIL |
| IJ43445 | ALL JOBS SUBMITTED TO DAS GET STUCK TO INTRO WHEN RUN NUMBER REACHES 10000 |
| IJ43700 | ISSUE WITH DEPENDENCIES WHEN JOB IS REMOVED FROM A SCHEDULE |
| IJ43774 | ABSOLUTE KEYWORD NO LONGER WORKS IN 9.4 OR 9.5 |
| IJ43801 | A POOL CANNOT BE RECREATED AGAIN ON DATABASE IF IT HAS BEEN RENAMED BEFORE |
| IJ43943 | USEROPTS DECRYPTION DOES NOT WORK WITH FIPS ENABLED |
| IJ44514 | KILL FAILS ONLY TO JOBS DEFINED UNDER FOLDERS |
| IJ44519 | ISSUE EDITING EVENT RULE |
| IJ44601 | SCHEDULE'S END TIME PRINTED EARLIER TIMING THAN THE LAST JOB'S END TIME IN IWS94 FP6 |
| IJ44624 | WHILE BUILDING THE PLAN, PRIORITY TO CARRYFORWARD JOBS COULD BE SET TO 0 AND STATUS TO JOB STREAMS SET TO HOLD |
| IJ44670 | SSMAGENT NOT RUNNING ON DYNAMIC AGENT 9.5.0.X |
| IJ44696 | THE FILETRANSFER PLUGIN IS NOT ABLE TO VALIDATE THE FOLLOWING DESTINATION PATH: "\ALIAS" WHERE "ALIAS" IDENTIFIES A REMOTE PATH |
| IJ44916 | IWS 9.5 FP6 APP SERVER CRASHES ON JOB STREAM SUBMIT |
| IJ44931 | CLARIFICATION REQUIRED- FLEXERA REPORT SHOWS SWIDTAG FILES FOR Z-AGENTS |
| IJ45095 | CONFIGURING TO USE THE SAME LTPA TOKEN_KEYS |
| IJ45111 | JOBSTDL SYNTAX ERROR WHEN JOB OR JOB STREAM NAME HAS HYPHENS |
| IJ45112 | KB0102770 - SAP CHANGED SNC DEFAULT AUTHENTICHATION |
| IJ45138 | ALL RECOVERY JOBS (AFTER THE FIRST) ARE SCHEDULED ALL AT THE SAME TIME |
| IJ45208 | UNABLE TO RETRIEVE LOGS FROM THE FAULT-TOLERANT AGENT DUE TO CORRUPT UNISON_JOB VARIABLE |
| IJ45233 | 127.0.0.1 LOOPBACK IP ADDRESS CANNOT BE RESOLVED IN IPV6-ONLY ENVIRONMENTS |
| IJ45373 | FILETRANSFER JOB REMOTE PASSWORD NOT WORKING WHEN SELECTING USER AS METHOD AND TESTING CONNECTIVITY |
| IJ45753 | WHEN A FAULT-TOLERANT AGENT EMBEDDED IN A WINDOWS CLUSTER (WSFC) IS STOPPED FROM WSFC, ERROR #252 (LINK_STATE=3) IS OUTPUT |
| IJ45754 | RERUN WITH SUCCESSOR FAILS WHEN AGENT COUNT IS MORE THEN 250 |
| IJ45760 | ERROR 415--UNSUPPORTED MEDIA TYPE ERROR FOR THE RESTFUL JOB THROUGH IWA |
| IJ45855 | INCORRECT JOB STATUS FOR DA JOB THAT COMPLETED DURING THE EXECUTION OF THE FINAL JOB STREAM |
| IJ46158 | UNABLE TO REGISTER NEW HP-UX AGENT DUE TO ISSUES WITH WS_WSCANHW.SH SCRIPT |
| IJ46178 | CLIENTSCHED SINTAX IS NOT CORRECT |
| IJ46180 | CENTRALIZED AGENT UPDATE DOWNLOAD FAILS FROM 9.5 FP6 WHEN ENEVENTPROCESSORHTTPSPROTOCOL IS SET TO NO |
| IJ46356 | DOWNLOAD ACTION ON S3 PLUGIN DOES COMPLETE SUCCESSFULLY, BUT THE FILE IS NOT DOWNLOADED |
| IJ46607 | TEST CONNECTION IS NOT WORKING FOR CYBERARK PLUGIN |
| IJ46641 | SUCCESSFUL REMOTE COMMANDS REPORT AS FAILURE AFTER UPGRADE FROM 9.5 FIX PACK 5 TO 9.5 FIX PACK6 |
| IJ46647 | TWS TIMEZONE UPDATE ON 9.5 FIX PACK 7 |
| IJ46692 | EVENT RULE FOR PROMPT STATUS ASKED DOES NOT TRIGGER EVENT ON AD-HOC JOB PROMPT |
| IJ46693 | TWS R3BATCH STOP WORKING WHEN USING THE NEW RFC 7.50 PATCH LEVEL 11 |
| IJ46714 | CHECKSYNC JOB ABEND WITH ERROR AWSJCL075E AFTER CHANGING TWSUSER PASSWORD |
| IJ46960 | WEBSPHERE APPLICATION SERVER LIBERTY BASE SERVICE IS NOT CREATED WHILE THE DOCUMENTATION SAYS THE OTHER WAY AROUND |
| IJ47034 | SERVERINST: WAINST216E --WAPASSWORD CONTAINS INCORRECT CHARACTERS (ASTERISK '*') |
| IJ47035 | SERVERINST: WAINST216E --WAPASSWORD CONTAINS INCORRECT CHARACTERS (EQUAL SIGN '=') |
| IJ47037 | JOB DEPENDENCY MISSING POST DST CHANGE |
| IJ47068 | DOCUMENTATION ABOUT VERIFY_CN_STRING DOES NEED TO BE IMPROVED/ADJUSTED |
| IJ47111 | CENTRALIZED UPDATE FAILS IF WORKSTATION NAME WAS CHANGED |
| IJ47148 | AD HOC PROMPTS CREATED WHEN PREDECESSOR FALLS OFF PLAN CREATED AT TOP LEVEL FOLDER |
| IJ47233 | A CHANGE IN A RESOURCE QUANTITY IN THE DATABASE IS NOT ALSO IMPLEMENTED IN THE PLAN AFTER JNEXTPLAN |
| IJ47235 | CENTRALIZED AGENT UPDATE FAILED ON 9.5 FIX PACK 6 TO 9.5 FIX PACK 6 SECURITY DUE TO INCORRECT VERSION DETECTION |
| IJ47315 | INCORRECT RESULT ON DYNAMIC WORKLOAD CONSOLE FOR USER WITH MODIFY PRIVILEGE |
| IJ47377 | SHLIB_PATH AND LD_LIBRARY_PATH ARE NOT EXTENDED IN TWS_ENV.SH FOR HP-UX |
| IJ47383 | KB0104364 - LIBERTY STALE CONNECTION ISSUE SHOWING SLQ EXCEPTION IN MESSAGES.LOG |
| IJ47471 | NOT ABLE TO ADD DEPENDENCY THROUGH CONMAN USING JOB STREAM ID |
| IJ47481 | DBUSER IS NOT AUTOMATICALLY GRANTED ALL NEEDED ACCESS TO HCL WORKLOAD AUTOMATIONTABLES ON THE DATABASE SERVER |
| IJ47683 | WRONG STEPS LISTED IN "EXAMPLE 10: UPGRADING AGENTS IN A CLUSTER-AWARE CONFIGURATION" DOCUMENTATION |
| IJ47717 | AZURE DATABRICKS PLUG-IN DATA LEAK |
| IJ47952 | DYNAMIC WORKLOAD CONSOLE 9.5 FIXPACK 6 INSTALL ISSUE ON AIX 7.1 |
| IJ47970 | THE AGENT UPGRADE CAUSING MULTIPLE WORKSTATIONS GOING UNLINKED DURING UPGRADE FROM 9.4 TO 10.1 |
| IJ48550 | UNABLE TO ADD NEW AGENT THROUGH COMPOSER IN 9.5 FP3 |
| IJ48417 | AGENTCERTIFICATEDOWNLOADER SCRIPT REQUIRES --DISPLAYNAME PARAMETER |
| IJ48418 | REMOTE COMMAND PLUG-IN RETURNS -1 WHEN THE RETURN CODE IS 1 |
| IJ48491 | DESCRIPTION IS SAME ON V9.5 AND V10.1 IN DOCUMENT, BUT CONTENT IS DIFFERENT FOR 9.5 |
| IJ49034 | FAILING TO GET THE BACKUP VALUE, THE ESTIMATED TIME IS SET TO THE DEFAULT ONE, WHICH IS 0 |
| IJ49064 | POTENTIAL EVENT DRIVEN WORKLOAD AUTOMATION PROXY COMMUNICATION FAILURE WHEN FTA CENTRALIZED UPDATE IS GOING THROUGH DM |
| IJ49106 | SWITCH MANAGER DDM TO BDDM DOES NOT WORK CORRECTLY AT 9.5 FIX PACK 6 SECURITY FIX PACK FIXES (SECURITY-202212 +TS013441722_95FP6SEC_IJ45754 NOV) |
| IJ49416 | COMPOSER HANG ISSUE-QUERYING FOR MORE THAN 1000 DATABASE OBJECTS |
| IJ49545 | TRANSLATION OF "EXCLUSIVE" WAS CHANGED IN JAPANESE VERSION |
| IJ49695 | MULTIPLE JOIN WITH DEPENDENCIES LOADED INCORRECTLY DURING FINAL EXECUTION |
| IJ49718 | AZURE DATA FACTORY PLUG-IN JOBS ARE GETTING TIMEOUT ERROR |
| KB0099406 | CANNOT KILL A SAP JOB DEFINED ON A WINDOWS DA |
| KB0095077 | REST API ISSUES WITH MEMBER WITH A # CHARACTER IN NAME DOES NOT WORK |
| KB0101411 | SAP RETURN CODE MAPPING |
| KB0104652 | MS-SQL JOBS GETTING ABEND AFTER HCL WORKLOAD AUTOMATION VERSION UPGRADE |
| KB0102746 | UNABLE TO SEND DATE PARAMETER FOR STORED PROCEDURE JOBS |
| DEFECT | ABSTRACT |
|---|---|
| WA-87105 | NullPointerException submitting a WebService job on Solaris platform |
| WA-104721 | SAP: -trace generates the trc file in the wrong path instead of DATADIR |
| WA-114734 | 9.5 FP7: Missing DWC license folder |
| WA-117784 | twa_env.sh/command contains references to old paths (wastools) |
| WA-120089 | twsinst -renew fails on linux |
| WA-120803 | conman: poor performance when submitting jobs on fault-tolerant agent |
| WA-124914 | Solaris i386 Agent installation fails at twsinst for syntax error |
| WA-125221 | Windows master domain manager installation fails on waPostConfigure phase due to not using java.exe from JavaExt folder but trying to use it from Windows environment variables. |
| WA-125223 | Solaris SPARC agent installation displays nslookup: not found |
| WA-125682 | Unable to notify scan results to the server because of a resources scanner error on HP Itanium |
| WA-126361 | 9.5 FP7: Centralized update java.lang.NullPointerException |
| WA-126392 | Join condition with multiple external job dependencies does not work |
| WA-126787 | nslookup: print not found after AIX twsinst installation |
| WA-127373 | Composer mod output is not correct: AWSJCL525E The server was unable to load the requested objects within the timeout period of 300 seconds |
Resolved Common Vulnerabilities and Exposures (CVE)
- CVE-2020-27783
- CVE-2020-28975
- CVE-2021-28957
- CVE-2022-45688
- CVE-2022-45689
- CVE-2022-45690
- CVE-2022-46337
- CVE-2023-1370
- CVE-2023-1428
- CVE-2023-2976
- CVE-2023-32731
- CVE-2023-32732
- CVE-2023-34054
- CVE-2023-34062
- CVE-2023-43804
- CVE-2023-44487
- CVE-2023-45803
- CVE-2023-5072
Backward compatibility
This fix pack delivers support for scheduling objects in folders, including workstations. When
monitoring workstations from a back-level agent workstation, the output displays the workstation
unique identifier and not the workstation name for those workstations that were defined in folders
different from the root folder. To identify the corresponding workstation name, run the
conman command using the showid filter, showcpu
;showid, from an updated agent workstation.
Known limitations and workarounds
The following are software limitations and workarounds that affect HCL Workload Automation version 9.5.0 Fix Pack 7.
- WebSphere Liberty minimum required version
- the minimum required WebSphere Liberty version to successfully install the Fix Pack is 22.0.0.3.
- Red Hat OpenShift Container Platform Limitation
- A limitation has been identified in the OCP that affects master domain manager and broker when used in SSL mode within a complete solution deployed on the platform. In this scenario, communication between the master, broker, and dynamic agents may not function properly. To resolve this issue, the environment should be set to "transparent mode" with no SSL communications enabled.
- AIX Dynamic Agent installation fails
-
AIX Dynamic Agent installation might fail due to a previous corrupted installation of the CIT component. The
twsinstcommand fails and thetwsCmdstdOutincludes the following error:Loading file /opt/tivoli/cit/config/Cit.properties error: 2 (No such file or directory)You can perform the following workaround:- Move the CIT component from /opt/tivoli/cit to a backup directory, for example /opt/tivoli/cit _backup .
- Restart the
twsinstcommand.
- APAR IJ44696 - Inability of the File Transfer plug-in to validate "\ALIAS" destination path
-
The File Transfer plug-in is unable to validate the destination path: "\ALIAS" where "ALIAS" identifies a remote path defined via IIS on a Windows operating system. During the job execution, the File Transfer plug-in validates the destination path provided in the job definition. These controls, involve the parent folder of the destination path. By using an ALIAS, the plug-in is unable to resolve the parent folder and all the controls fails. To avoid this issue there are two workarounds available:
- Set the destination path by adding an additional folder after the \ALIAS - \ALIAS\test_folder\
- Change the path pointed by the ALIAS. If it identifies a path like this: \ALIAS
=\\server\Folder1\Folder2\ this should be changed to: \ALIAS =
\\server\Folder1\
In this way the destination path set in the job can change in \ALIAS\Folder2\ and the path validation works fine.
- APAR IJ46693 - Supported RFC 7.50 Patch Level
- HCL Workload Automation version 9.5 supports Remote Function Call (RFC) 7.50 only up to Patch Level 10.
- APAR IJ26545 - Centralized Agent Update failure
- Centralized Agent Update from 9.4.x to 9.5 Fix Pack 7 might fail because the name of the
pools.properties file is replaced by the name of the folder during
the upgrade procedure, and it is not possible to rename the file within a folder that has
the same name.You can perform the following workaround:
- Before starting the upgrade procedure, create a backup of the pools.properties file and save it in a different location.
- Complete the upgrade procedure.
- Move the pools.properties backup file to the original location.
- ITLM tool incorrectly discovering z-centric agents
- After installing a dynamic agent, the ITLM tool might incorrectly discover a z-centric agent. You can find two possible reasons and their workarounds below:
Fix pack structure
This section describes the structure of the images contained in this Fix Pack.
Fix Pack files available for HCL Workload Automation using HCL License Portal
This is the structure of the Fix Pack for the engine on HCL License Portal:
- Readme file and WebSphere Liberty package
- AIX components
- IBM i components
- Linux components
- Linux components on Docker
- Windows components
| Name | Description |
| HWA_9507_readme | Readme file with download instructions |
| WEBSPHERE_LIBERTY_BASE 24.0.0.1 | WebSphere Liberty application server |
| Name | Description |
| HWA_9507_AIX_AGENT |
HCL Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for AIX |
| HWA_9507_AIX_BatchReportCli | HCL Workload Automation 9.5.0.7 2024.03 Batch Reports Command Lines |
| Name | Description |
| HWA_9507_IBM_I_AGENT | HCL Workload Automation Agent 9.5.0.7 for IBM i |
| Name | Description |
| HCL Workload Automation 9.5 LINUX | LINUX distribution |
| HWA_9507_MDM_LINUX_X86_64 | Workload Automation 9.5.0.7 FOR LINUX |
| HWA_9507_LNX_PPC64LE_AGENT | HCL Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Linux on POWER (little endian) |
| HWA_9507_LNX_S390_AGENT | HCL Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Linux on System z9 and System z |
| HWA_9507_LNX_X86_64_AGENT | Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Linux on x86-64 |
| HWA_9507_LINUX_X86_64_BatchReportCli | HCL Workload Automation 9.5.0.7 2024.03 Batch Reports Command Lines |
| HWA_9507_LINUXS390_BatchReportCli | HCL Workload Automation 9.5.0.7 2024.03 Batch Reports Command Lines |
| Name | Description |
| HCL Workload Automation 9.5 LINUX | LINUX distribution |
| HWA_9507_Server_Container | Workload Automation 9.5.0.7 FOR LINUX on x86-64 on Docker |
| HWA_9507_Server_Container_LINUXS390 | Workload Automation 9.5.0.7 for Linux on System z9 and System z on Docker |
| HWA_9507_Agent_Dynamic_Container | Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Linux on x86-64 on Docker |
| HWA_9507_Agent_Dynamic_Container_LINUXS390 | Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Linux on System z9 and System z on Docker |
| Name | Description |
| HCL Workload Automation 9.5 WINDOWS | WINDOWS distribution |
| HWA_9507_MDM_WINDOWS_X86_64 | Workload Automation 9.5.0.7 FOR WINDOWS |
| HWA_9507_WIN_X86_64_AGENT | HCL Workload Automation Agent 9.5.0.7, Remote CLI and Workload Automation for Applications for Windows x64 |
| HWA_9507_WINDOWS_X86_64_BatchReportCli | HCL Workload Automation 9.5.0.7 2024.03 Batch Reports Command Lines |
| Name | Description |
| HWAZ_9507_ZSYSTEM_BatchReportCli | HCL Workload Automation 9.5.0.7 2024.03 Batch Reports Command Lines |
Installing the Fix Pack
This section describes how to apply Fix Pack 7 to HCL Workload Automation.
The section is divided into the following subsections:
Installation notes
When installing the HCL Workload Automation Fix Pack, follow these recommendations:
- Before installing the Fix Pack, ensure you have installed the required prerequisite software. To obtain the latest information about software requirements for HCL Workload Automation, see Product Requirements.
- The minimum required WebSphere Liberty version to successfully install the fixpack is 22.0.0.3 or later.
- Before installing this Fix Pack on AIX® V7.1 operating systems, you must apply the patch for APAR IZ99634. For more information, see: APAR IZ99634.
- On UNIX™ operating systems, before installing the
HCL Workload Automation Fix Pack, ensure that your umask
is set to 022. To verify that umask is set to the correct value, from a command
prompt, run the umask command. If the value is different from 022, modify it by
running the command:
umask 022 - On UNIX operating systems, the database administrator must have read and run privileges for the HCL Workload Automation installation path; otherwise the installation fails. (54367)
After the Fix Pack installation completes, verify the following information:
- This Fix Pack installs a new version of the file tws_env.sh (tws_env.cmd) and also creates a backup file named, tws_env.sh.bk (tws_env.cmd.bk), which are both saved to the TWA_HOME/TWS directory, where TWA_HOME is the HCL Workload Automation installation directory. After installing the Fix Pack, if you have modified the original version, merge the content of the new version with the content of the original version to carry your customized content into the new version.
- Only on Windows operating systems, to correctly display
double-byte character set (DBCS) characters, you must perform the following actions:
- Set the
LANGenvironment variable to the DBCS language code you want to use, for example,set LANG=zh_CN. - Set the
TWS_TISDIRenvironment variable to the HCL Workload Automation home directory, for example,set TWS_TISDIR=C:\FTA\TWS. - Open the Control Panel window and click Clock, Language, and Region.
- Click Region and Language.
- In the Format tab, choose from the Format drop-down list the language you want to use.
- In the Keyboards and Languages tab, under Display Language, click install and follow the steps to install the DBCS language pack you want to use.
- In the Administrative tab, click Change system locale and, from the drop-down list, choose the language (system locale) you want to use.
- Set the
- When installing a dynamic agent or a fault-tolerant agent, ensure that the agent name does not start with a number. If the name of the dynamic agent starts with a number, use the -displayname parameter at installation time to specify a different name. If the name of the fault-tolerant agent starts with a number, use the --thiscpu parameter at installation time to specify a different name.
Interoperability notes
HCL Workload Automation version 9.5.0 Fix Pack 7 supports all product versions indicated in the version 9.5 Release Notes which can be accessed at the following link: Release Notes for HCL Workload Automation.
Disk space requirements
For the most up-to-date information about disk space and memory requirements, see the hardware requirements at the following URL: Hardware Requirements
Before starting the Fix Pack installation, ensure that you have the necessary disk space
available on the file system. Consider that the disk space check calculated by the installation
considers the entire space occupied by the TWA_HOME directory. The space
required by the backup is the sum of the following directories:
TWA_HOME/TWS + TWA_HOME/TDWB + TWA_HOME/wastools + TWA_HOME/propertiesIn addition to the disk space in the following table, the installation requires an additional 600
MB on the file system where the IMShared directory is located.
| Operating System | Installation directory | Temporary directory |
|---|---|---|
| AIX | 2,5 GB | 1,5 GB |
| Microsoft® Windows | 2 GB | 1 GB |
| Linux® | 1,5 GB | 800 MB |
| Operating System | Installation directory | Temporary directory |
|---|---|---|
| AIX | 900 MB | 400 MB |
| Microsoft Windows | 700 MB | 350 MB |
| Linux | 720 MB | 350 MB |
| Operating System | Installation directory | Temporary directory |
|---|---|---|
| AIX | 600 MB | 250 MB |
| Microsoft Windows | 800 MB | 400 MB |
| Linux | 600 MB | 250 MB |
Installation methods
You can install the Fix Pack using one of the following methods:
- For master domain manager or its backup:
- see
- For dynamic domain manager or its backup:
- see
- For fault-tolerant agent, dynamic agent or domain manager:
- see
You can install the Master Domain Manager version 9.5 Fix Pack 7 as fresh install. For further information, see
Installing HCL Work load Automation
Configuring your master domain manager and broker in SSL mode
If you plan to install your master domain manager,
Version 9.5 Fix Pack 7 in SSL mode or plan to upgrade to Version 9.5 Fix Pack 7 and
set up your master domain manager and broker in SSL
mode, perform the following steps:
- Install the master domain manager or upgrade your current master domain manager to version 9.5.0 Fix Pack 7
- Replace the values of the following parameters in the
localopts file with the following values:
- nm SSL full port = 31113
- SSL key =TWA_home/TWS/ssl/OpenSSL/TWSClient.key
- SSL certificate = TWA_home/TWS/ssl/OpenSSL/TWSClient.cer
- SSL key pwd = TWA_home/TWS/ssl/OpenSSL/password.sth
- SSL CA certificate = TWA_home/TWS/ssl/OpenSSL/TWSTrustCertificates.cer
- SSL random seed =TWA_home/TWS/ssl/OpenSSL/TWS.rnd
- SSL Encryption Cipher = TLSv1.2
- Modify the master domain manager
and broker using the composer mod command, as
follows:
CCPUNAME your_master_domain_manager_workstation DESCRIPTION "MANAGER CPU" OS UNIX NODE localhost TCPADDR 31111 SECUREADDR 31113 DOMAIN MASTERDM FOR MAESTRO TYPE MANAGER AUTOLINK ON BEHINDFIREWALL OFF SECURITYLEVEL FORCE_ENABLED FULLSTATUS ON ENDCPUNAME your_broker_workstation DESCRIPTION "This workstation was automatically created." OS OTHER NODE localhost TCPADDR 41114 SECUREADDR 41114 DOMAIN MASTERDM FOR MAESTRO TYPE BROKER AUTOLINK ON BEHINDFIREWALL OFF SECURITYLEVEL FORCE_ENABLED FULLSTATUS OFF END - Modify the Broker.Workstation.PortSSL parameter in the
BrokerWorkstation.properties file from
false to true.
The Broker.Workstation.PortSSL parameter specifies the port used by the broker server to listen to the incoming traffic (equivalent to the Netman port) in SSL mode. It is first assigned at installation time. This port number must always be the same for all the broker servers that you define in your HCL Workload Automation network (one with the master domain manager and one with every backup master domain manager you install) to ensure consistency when you switch masters.
- Stop and start WebSphere Application Server Liberty Base, as described in Application server - starting and stopping.
- Stop and start all HCL Workload Automation processes.
- Run
Jnextplan -for 0000
Before Installing
Before installing the Fix Pack using any of the methods described in the following sections,
perform the following actions:
- If you have jobs scheduled to run on the instance you are upgrading, make sure that
they have completed otherwise some processes, such as
jobmonorjoblnch, might still be active. - Download the appropriate ZIP files for the operating system from HCL License Portal .
- Extract the content of the ZIP files into a directory, using one of the extraction tools
available on your system or downloadable from the Internet. The tool you use must be able
to keep the file permissions on the extracted files, for example, infozip. Note:
- If you want to install the Fix Pack on IBM i, to untar the eImages, see Extract the eImages for the Z Agent and Dynamic Agent on IBM i operating systems.
- To extract the .zip file onto a Windows 64-bit system, ensure that the eImage is not located on the desktop because the Windows operating system extract tool has a problem. Choose another directory into which to extract the Fix Pack eImage.
- If you want to install the fixpack on Rhel 9 zLinux, ensure that the operating system library "libcrypt.so.1" is installed.
Creating or updating the HCL Workload Automation database schema
Before launching any of the installation methods, create or update the database schema.
Before applying the Fix Pack, create the database schema by following the procedure described in the Creating and updating the database tables chapter in the HCL Workload Automation guide.
If the database already exists, update the database by running the following command:
On Windows operating systems-
cscript configureDb.vbs --rdbmstype db_type --dbhostname db_hostname --dbport db_port --dbname db_name --dbuser db_user --dbpassword db_password --dbadminuser db_administrator --dbadminuserpw db_administrator_password - On UNIX operating systems
-
./configureDb.sh --rdbmstype db_type --dbhostname db_hostname --dbport db_port --dbname db_name --dbuser db_user --dbpassword db_password --dbadminuser db_administrator --dbadminuserpw db_administrator_passwordIf a new version of the database is available, update to it by following the procedure described in the Upgrading the database schema chapter in the HCL Workload Automation guide.
Extract the Images for the Agent and Dynamic Agent on IBM i operating systems
The following package is available with this Fix Pack:
- HWA_9507.03IBM_I_AGENT.zip: The dynamic agent on IBM i image. This package also contains an extraction tool executable that can be copied to the IBM i workstation.
To untar or unzip the Fix Pack eImages, you can use the PASE shell or the AIXterm.
- Using PASE shell:
-
- Open the PASE shell.
- Run the command:
"CALL QP2TERM" - Locate the folder where you downloaded the Fix Pack eImage and run the command:
- Dynamic agent
- "unzip HWA95_FP7_IBM_I_AGENT-202403.zip"
- Exit from the PASE shell.
- Using AIXterm:
-
- Start the Xserver on your desktop.
- On the iSeries machine, open a QSH shell and export the display.
- In QSH shell, go to the directory /QopenSys and run the command:
"aixterm -sb" - A pop-up window is displayed on your desktop. Using this pop-up window, unzip the HWA95_FP7_IBM_I_AGENT-202403.zip file, or untar the HWA95_FP7_IBM_I_AGENT-202403.zip.
Rolling back an applied fix pack
This topic describes how to roll back an applied fix pack to a previous version.
You can revert back to an earlier version of an installed Fix Pack or release by
using one of the following methods:
- For master domain manager or its backup:
- see
- For dynamic domain manager or its backup:
Documentation updates for HCL Workload Automation Fix Pack 7 for version 9.5.0
Any additions or changes to the documentation as a result of this Fix Pack have been integrated into the online product documentation available in HCL Workload Automation documentation.
