HCL-TECH-SOFTWARE · francescopuglisi · Nov 28, 2024 · Nov 28, 2024 · Nov 28, 2024 · Nov 28, 2024
diff --git a/README.md b/README.md
@@ -30,7 +30,8 @@ You can access the HCL Workload Automation container images from the Entitled Re
 * hclcr.io/wa/hcl-workload-automation-console:10.2.3.00.20241122
 
 ## Other supported tags
-* 10.2.0.01.20231201
+* 10.2.2.00.20240424
+* 10.2.1.00.20231201
 * 10.2.0.00.20230728
 * 10.1.0.05.20240712
 * 10.1.0.04.20231201-amd64

diff --git a/readmes/readme_CONSOLE.md b/readmes/readme_CONSOLE.md
@@ -14,7 +14,9 @@ Docker adoption ensures standardization of your workload scheduling environment
 
 
 ## Supported tags
-- 10.2.0.01.20231201
+- 10.2.3.00.20241122
+- 10.2.2.00.20240424
+- 10.2.1.00.20231201
 - 10.2.0.00.20230728
 - 10.1.0.05.20240712
 - 10.1.0.04.20231201
@@ -47,7 +49,7 @@ You can access the Console container image from the Entitled Registry:
  The image is as follows:
 
 
-* hclcr.io/wa/hcl-workload-automation-console:10.2.0.01.20231201
+* hclcr.io/wa/hcl-workload-automation-console:10.2.3.00.20241122
 
 ### From HCL Flexera
 
@@ -60,7 +62,7 @@ If you are accessing the images from HCL Flexera, use the following command to u
 
 
 
-Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspizLinuxDeployments.html)
+Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspizLinuxDeployments.html)
 
 
 
@@ -217,7 +219,7 @@ To create new LTPA token, issue the following command:
 
   where:
   - **<host_dir>** is an existing folder on the local machine where docker runs
-  - **<keys_password>** is LTPA keys password ( for further details, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspicfgLDAP.html) documentation).
+  - **<keys_password>** is LTPA keys password ( for further details, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspicfgLDAP.html) documentation).
 
 The "ltpa.keys" and "wa_ltpa.xml" files are created in the local folder \<hostdir>.
 
@@ -330,7 +332,7 @@ Proceed to deploy the product components. After the deployment, you can include
 
 ## Metrics Monitoring
 
-Workload Automation exposes a number of metrics to provide you with insight into the state, health, and performance of your environment and infrastructure. You can access the product APIs for monitoring and retrieving insightful metrics data. The metrics are exposed and can be visualized with tools for displaying application metrics such as, the open source tool Grafana. If you use Grafana, you can take advantage of the preconfigured dashboard that is available with the deployment of the Dynamic Workload Console and the server  components. For more information about the metrics available, see [Metrics monitoring](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_ref/awsrgmonprom.html) documentation. In a Docker environment, by default, access to the metrics does not require authentication. However, if you want to specify a different user that can access the metrics securely using credentials, modify the prometheus.xml file that you will find automatically created in a Docker environment, adding the additional users.
+Workload Automation exposes a number of metrics to provide you with insight into the state, health, and performance of your environment and infrastructure. You can access the product APIs for monitoring and retrieving insightful metrics data. The metrics are exposed and can be visualized with tools for displaying application metrics such as, the open source tool Grafana. If you use Grafana, you can take advantage of the preconfigured dashboard that is available with the deployment of the Dynamic Workload Console and the server  components. For more information about the metrics available, see [Metrics monitoring](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_ref/awsrgmonprom.html) documentation. In a Docker environment, by default, access to the metrics does not require authentication. However, if you want to specify a different user that can access the metrics securely using credentials, modify the prometheus.xml file that you will find automatically created in a Docker environment, adding the additional users.
 
 
 ## Supported Docker versions
@@ -350,7 +352,7 @@ The HCL Workload Automation container has the following limitations:
 
 
 ## Additional Information
-For additional information about how to use the HCL Workload Automation, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
+For additional information about how to use the HCL Workload Automation, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
 
 
 ## License

diff --git a/readmes/readme_DYNAMIC_AGENT.md b/readmes/readme_DYNAMIC_AGENT.md
@@ -14,15 +14,17 @@ Docker adoption ensures standardization of your workload scheduling environment
 
 
 ## Supported tags
-- 10.2.0.01.20231201
+- 10.2.3.00.20241122
+- 10.2.2.00.20240424
+- 10.2.1.00.20231201
 - 10.2.0.00.20230728
 - 10.1.0.05.20240712
 - 10.1.0.04.20231201
 - 10.1.0.03.20230511-amd64
 - 10.1.0.02.20230301
 - 10.1.0.00.20220722
 - 10.1.0.00.20220512
-- 10.1.0.00.20220304
+- .1.0.00.20220304
 - 9.5.0.06.20220617
 - 9.5.0.05.20211217
 
@@ -47,7 +49,7 @@ You can access the Dynamic Agent container image from the Entitled Registry:
  The image is as follows:
 
 
-* hclcr.io/wa/hcl-workload-automation-agent-dynamic:10.2.0.01.20231201
+* hclcr.io/wa/hcl-workload-automation-agent-dynamic:.2.0.01.20231201
 
 ### From HCL Flexera
 
@@ -60,7 +62,7 @@ If you are accessing the images from HCL Flexera, use the following command to u
 
 
 
-Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspizLinuxDeployments.html)
+Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspizLinuxDeployments.html)
 
 
 
@@ -239,7 +241,7 @@ If you want to use custom Agent certificates, uncomment the "BEGIN SECTION - Cer
 
 
 where TWSClientKeyStoreJKS.jks  TWSClientKeyStoreJKS.sth  TWSClientKeyStore.kdb  TWSClientKeyStore.sth are the container keystore and stash file containing your customized certificates.
-For details about custom certificates, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_ad/awsadMDMDAcomm.html) documentation.
+For details about custom certificates, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_ad/awsadMDMDAcomm.html) documentation.
 
     See an example where `release_name` = myname and `namespace` = default: 
 
@@ -279,7 +281,7 @@ On amd64 and Linux on Z platforms.
 
 
 ## Additional Information
-For additional information about how to use the HCL Workload Automation Agent, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
+For additional information about how to use the HCL Workload Automation Agent, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
 
 
 ## License

diff --git a/readmes/readme_SERVER.md b/readmes/readme_SERVER.md
@@ -14,7 +14,9 @@ Docker adoption ensures standardization of your workload scheduling environment
 
 
 ## Supported tags
-- 10.2.0.01.20231201
+- 10.2.3.00.20241122
+- 10.2.2.00.20240424
+- 10.2.1.00.20231201
 - 10.2.0.00.20230728
 - 10.1.0.05.20240712
 - 10.1.0.04.20231201
@@ -46,7 +48,7 @@ You can access the Server container image from the Entitled Registry:
  The image is as follows:
 
 
-* hclcr.io/wa/hcl-workload-automation-server:10.2.0.01.20231201
+* hclcr.io/wa/hcl-workload-automation-server:10.2.3.00.20241122
 
 ### From HCL Flexera
 
@@ -60,7 +62,7 @@ If you are accessing the images from HCL Flexera, use the following command to u
 
 
 
-Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspizLinuxDeployments.html)
+Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspizLinuxDeployments.html)
 
 
 ## Getting Started
@@ -255,7 +257,7 @@ To create new LTPA token, launch the following command:
 
   where:
   - **<host_dir>** is an existing folder on the local machine where docker runs
-  - **<keys_password>** is LTPA keys password ( for further details, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspicfgLDAP.html) documentation).
+  - **<keys_password>** is LTPA keys password ( for further details, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspicfgLDAP.html) documentation).
 
 The "ltpa.keys" and "wa_ltpa.xml" files are created in the local folder \<hostdir>.
 
@@ -281,7 +283,7 @@ Consider the following example:
 
 For more information, see: 
 
-[Running batch reports from the command line interface](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_ref/awsrgbatchreps.html)
+[Running batch reports from the command line interface](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_ref/awsrgbatchreps.html)
 
 
 ## Installing Automation Hub integrations  
@@ -295,7 +297,7 @@ You can also extend Workload Automation with custom plug-ins or integrations tha
 
 ## Metrics Monitoring
 
-Workload Automation exposes a number of metrics to provide you with insight into the state, health, and performance of your environment and infrastructure. You can access the product APIs for monitoring and retrieving insightful metrics data. The metrics are exposed and can be visualized with tools for displaying application metrics such as, the open source tool Grafana. If you use Grafana, you can take advantage of the preconfigured dashboard that is available with the deployment of the Dynamic Workload Console and the server  components. For more information about the metrics available, see [Metrics monitoring](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_ref/awsrgmonprom.html) documentation. In a Docker environment, by default, access to the metrics does not require authentication. However, if you want to specify a different user that can access the metrics securely using credentials, modify the prometheus.xml file that you will find automatically created in a Docker environment, adding the additional users.
+Workload Automation exposes a number of metrics to provide you with insight into the state, health, and performance of your environment and infrastructure. You can access the product APIs for monitoring and retrieving insightful metrics data. The metrics are exposed and can be visualized with tools for displaying application metrics such as, the open source tool Grafana. If you use Grafana, you can take advantage of the preconfigured dashboard that is available with the deployment of the Dynamic Workload Console and the server  components. For more information about the metrics available, see [Metrics monitoring](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_ref/awsrgmonprom.html) documentation. In a Docker environment, by default, access to the metrics does not require authentication. However, if you want to specify a different user that can access the metrics securely using credentials, modify the prometheus.xml file that you will find automatically created in a Docker environment, adding the additional users.
 
 
 
@@ -337,7 +339,7 @@ This limitation applies to only to the stand-alone Docker environment.
 
 
 ## Additional Information
-For additional information about how to use HCL Workload Automation, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
+For additional information about how to use HCL Workload Automation, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
 
 
 ## License

diff --git a/readmes/readme_ZCENTRIC_AGENT.md b/readmes/readme_ZCENTRIC_AGENT.md
@@ -15,7 +15,9 @@ z-centric Agent has the following restriction:
 
 
 ## Supported tags
-- 10.2.0.01.20231201
+- 10.2.3.00.20241122
+- 10.2.2.00.20240424
+- 10.2.1.00.20231201
 - 10.2.0.00.20230728
 - 10.1.0.05.20240712
 - 10.1.0.04.20231201
@@ -49,7 +51,7 @@ You can access the z-centric Agent container image from the Entitled Registry:
  The image is as follows:
 
 
-* hclcr.io/wa/hcl-workload-automation-agent-dynamic:10.2.0.01.20231201
+* hclcr.io/wa/hcl-workload-automation-agent-dynamic:10.2.3.00.20241122
 
 
 ### From HCL Flexera
@@ -61,7 +63,7 @@ If you are accessing the images from HCL Flexera, use the following command to u
   where <tar_name> is the name of the .tar file containing the image.
 
 
-Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1021/distr/src_pi/awspizLinuxDeployments.html)
+Before you deploy HCL Workload Automation components on Linux on Z, see Deploying Docker compose on Linux on Z](https://help.hcltechsw.com/workloadautomation/v1023/distr/src_pi/awspizLinuxDeployments.html)
 
 
 
@@ -199,7 +201,7 @@ On amd64 and Linux on Z platforms.
 
 
 ## Additional Information
-For additional information about how to use the HCL Workload Automation Agent, see the [online](https://help.hcltechsw.com/workloadautomation/v1021/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
+For additional information about how to use the HCL Workload Automation Agent, see the [online](https://help.hcltechsw.com/workloadautomation/v1023/index.html) documentation. For technical issues, search for Workload Scheduler or Workload Automation on [StackOverflow](http://stackoverflow.com/search?q=workload+scheduler).
 
 
 ## License