WORKLOAD AUTOMATION COMMUNITY

Real Discussion For Real People

Knowledge sharing and discussion platform for automation product experts and users

OUR LATEST POSTS!

HCL Workload Automation is Cloud Native: Introducing HCL Now

HCL Software's cloud-first architecture and deployment make your cloud native journey easy. Unlock the full potential of your software by the technical experts who have created the solution. Our technology choices are guided by the Cloud Native Computing Foundation's definition of cloud native. We enable our software with core cloud native technologies: containers with Kubernetes orchestration and Helm packaging. Request routing, access control and monitoring are provided by broadly adopted open-source solutions: Ambassador, Key cloak, Prometheus and Grafana. A dashboard application provides consistent access to the underlying Kubernetes resources, product log files and more, making it easy to get started with Kubernetes regardless of which cloud provider is used.

Looking for the most innovative chatbot platform? Times are changing and you always look forward to find the most innovative platform. Maybe 5 years ago you would never have imagined that it would be possible to have a "person" by your side, who in every working moment, would tell you what to do, how to do it, and relieve you from all those low value-added activities. Today, I am here to tell you the most beautiful "story" that could radically change your way of working. This story could bring you an unlimited amount of love and tranquility in the workplace, so much that the IT world, and specifically, the products that are part of it, alas, tend to undermine. I'm here to introduce you to HCL Clara, an Intelligent Virtual Assistant.

.This Blog aims to showcase how we can use HCL Workload Automation to Implement a Request Management Workflow for a repeated task for a Service Line and how the complete request can be managed End to End through HWA. The request we are covering here is for a “DB Backup” request being requested by an Application Team of their Application DB . So in a typical scenario, an Application Team would raise a Request on Service Now through a Ticket. The Ticket would be received and acknowledged by the DBA Team and they would go ahead and process this ticket by logging into the specific DB Server in question and would run a manual command to take this adhoc Backup of the Application DB requested in the Ticket to specific location requested. Then go ahead and update the ticket once the Backup is done.

Now that we have talked about the Business User & Scheduler’s Perspective in our previous blog post, this part will focus on the Operator’s perspective and the overall application architecture. As an operator, your mission is to stay in control with custom dashboards and KPIs. With the demo, you will learn to: Monitor the workload from the dashboard; Resolve problems and restart the processing; Easily change the conditions to test alternative business flows. Let’s start to take advantage of a single point of access and control. As a first step, login to the Dynamic Workload Console and modify some parameters on the demo flow to change its behavior. Search for alternate_process job stream and submit it. In the Workload Dashboard you have all the data regarding your workload execution.