In an IBM/HCL Workload Automation (WA) deployment, communication between the MDM (Master Domain Manager) ó DWC (Dynamic Workload Console) and MDM ó DA (Dynamic Agent) is implemented using SSL protocol, TLS v1.2 over TCP/IP. WA provides Self-Signed certificates (signed by IBM) with the product and all components use them by default to establish SSL communication. To enhance security, these certificates must be replaced with commercial CA (Certificate Authority) signed certificate for each server in the environment.
The following sections describe the procedure to replace various certificates.
When designing a workflow into job streams using the HCL Workload Automation solution it may happen that the entire process is not modeled as a simple pipeline and the implementation of the projected flowchart requires some branching and decision logic (IF… THEN.. ELSE…).
Using HCL Workload Automation conditional dependencies feature it’s very easy to solve this design problem, by reading this blog you will learn how to create and use conditional dependencies in many use cases.
Issuing TLS Certificates in PEM Format to be deployed automatically during the installation of HCL Workload Automation
In order to ease the deployment of custom TLS (SSL) certificates to secure the communication between each component of an IBM/HCL Workload Automation (WA) deployment, certificates in PEM (Privacy Enhanced Mail) can be made available in a folder. During the installation, they are used to create and share the KeyStores and TrustStores required for the deployment.
The Automation Hub is a showcase of HCL Workload Automation’s ability to orchestrate both IT and Business workloads.
This is the second part of the 4-part series of blogs covering how HCL Workload Automation can mimic end to end processes on insurance business side.