HCL Workload Automation is a containerized product and is Red Hat certified.
HCL Workload Automation container images are Red Hat certified and available in the Red Hat Catalog. Deploy HCL Workload Automation containerized software to take advantage of a scalable Kubernetes-based container platform to automate deployment, scaling and operations of application containers across clusters.
You can access the container images in the Red Hat Catalog at: https://catalog.redhat.com/software/container-stacks/search?q=HCL&p=1.

With the Encryption integration, you can encrypt, decrypt, and sign your files using symmetric or asymmetric encryption.
Data breaches are becoming more and more common in today’s interconnected world and data security is a primary concern. Encryption technology is one of the key methods for protecting information, by scrambling data to make sure unintended recipients are not able to make any sense of the data. To keep your data and information secure, you can use the Encryption integration, which encrypts, decrypts and signs your files using symmetric or asymmetric encryption.
The basic difference between these two types of encryption is that symmetric encryption uses one key for both encryption and decryption, and the asymmetric encryption uses public key for encryption and a private key for decryption.
Because the algorithm behind symmetric encryption is less complex and executes faster, this is the preferred technique when processing bulk data. On the other hand, asymmetric encryption is considered to be more secure than symmetric encryption as it uses two keys for the process: the public key used for encryption is available to everyone, while the private key is not disclosed.
When you use symmetric encryption, you can encrypt and decrypt files. When you use asymmetric encryption, you can encrypt, decrypt, and sign files.
For more information, see Automation Hub.

Shifting your workload from an on-premises to a cloud environment is a simple procedure which grants a number of benefits.
Cloud computing reduces or eliminates the need for businesses to purchase equipment, operate and maintain data centers. This generates a significant savings on hardware, facilities, applications, and other expenses required from on-premises computing. It also aids disaster recovery: hosting systems and storing documents on the cloud provides a smart safeguard in case of an emergency and enables quicker deployment.
Known for flexible scalability, cloud technologies support businesses to do more than just scale up or back when needed. They allow you to better employ smart technology, integrate the cloud footprint across your organization, and adapt strategies for cost control to proactively plan for growth.
For more information, see the Shifting your workload from an on-premises to a cloud environment section in the Planning and Installation Guide.

Entitlement to Db2 Version 11.5 Standard Edition is available with Fix Pack 3.
With Workload Automation V9.5 Fix Pack 3, you are entitled to use Db2 V11.5 Standard Edition.

You can use Amazon Elastic Kubernetes Service (EKS) to run Workload Automation containers on Amazon Web Services (AWS) EKS cloud.

Deploy and manage Workload Automation containerized product components on the Amazon Web Services secure cloud platform. Containers and Kubernetes improve time to value and enable you to more easily scale your environment to meet business needs and at a lower cost. The containers run on a cluster based on the available compute resources and resource requirements of each container. You can run and scale one or more containers as a pod.
The product components are deployed using a chart and the product component container images. By default, a single server (master domain manager), console (Dynamic Workload Console), and dynamic agent are installed.
Workload Automation can be deployed across a single cluster, but you can add multiple instances of the product components by using a different namespace in the cluster. 

For more information, about deploying the containerized product components on the Amazon Web Services secure cloud platform, see the section about deploying with containers on Amazon EKS in the Planning and Installation Guide.

With the file transfer integration, you can transfer files quickly and easily.
With the enhanced version of the File Transfer integration, you are granted a consolidated and coordinated approach to scheduling and automating transfer of files. The highlights of the enhanced integration are as follows:

• Integrated dashboard for monitoring file transfer operations
• Completion time estimate
• Parallel file transfer
• Encryption at REST
• Rerun from point of failure
• Selective re-transfer
• Improved multiple selection
• File transfer status and details on files transferred
• Post-processing of transferred files: delete, rename, move
• File transfer to and from Z systems
  ​
  

Agents at Version 9.3 can run existing file transfer jobs without problems. Jobs you create or edit from the Dynamic Workload Console at Version 9.5, Fix Pack 3 are not supported on agents at Version 9.3, but you can work around this problem by saving the jobs in the composer command line after editing them with the Dynamic Workload Console. The best practice is applying the latest fix pack level to the agents.
For a detailed description about creating a file transfer job, see Automation Hub.

Replicate your dashboard by exporting and importing it on your Dynamic Workload Console.

Now you can easily export your dashboards from your Dynamic Workload Console and import them anywhere, on your environment. For further information, see the Exporting and importing a dashboard section in the Dynamic Workload Console User's Guide.
​
Not enough time to create a customized dashboard? Don’t worry we provide useful dashboards ready to be used as is! Discover all the available dashboards on Automation Hub.

Monitoring your workload is never been so easy!

The new automation command center that empowers your Workload Automation with new amazing integrations.

IBM Workload Scheduler satisfies Requests for Enhancements (RFEs). Requests for Enhancements (RFEs) give customers the opportunity to collaborate directly with the product development team and other users. The team prioritizes and develops new product features based on proposals made by customers. IBM Workload Scheduler V9.5 Fix Pack 2 delivers the following RFEs:

• RFE 138951: Support for an existing Oracle user.
  
• RFE 132029: Add run number check within MakePlan before locking the database.
• RFE: Allow configuration of the value for the global option untilDays.

Folder support has been extended to all scheduling objects. Gain greater business agility by organizing your scheduling objects in a hierarchy of folders. Organize them by lines of business, departments, geographies, or any custom category that makes sense for your business operations.
Move your objects into sub-folders, in batch mode, where the folder names are based on tokens contained in the names of the scheduling objects using the composer rename command.
Filtering for and monitoring your scheduling objects defined in folders means you no longer have to rely on complicated and restrictive naming conventions.
Furthermore, you can associate access control lists to individual folders to manage the security of your scheduling objects.