Number of Posts: 7
Filter By:
Number of Posts: 7
Cloud Native, HCL Software | July 20, 2021
HCL Software Unveils HCL Now and SoFy
Five years ago, we imagined a future where our software products could be deployed in minutes into dynamic public, private and hybrid clouds. We harmonized our investments and roadmaps to get cloud-native from the ground up. 5,000+ people-years of investments later, we have: 
Digital Solutions | January 8, 2021
Announcing the HCL Ambassador Class of 2021
We are proud and excited to announce the HCL Ambassador Class of 2021 for HCL Digital Solutions.  The HCL Ambassadors program is an annual recognition program that rewards individuals who go above and beyond in their commitment, advocacy and knowledge-sharing of the HCL Digital Solutions products. HCL Ambassadors gain recognition from us in the following forms  Community calls and social networking forums   Access to exclusive, “invite-only” beta programs and events   Bi-annual calls with senior executives   Fast escalation of support tickets to subject matter expert engineers   Free-of-charge licenses to use HCL Software products   Enhanced exposure of published content through syndication into the HCL Ambassadors blog   HCL Ambassadors-branded merchandise   Access to the program is decided annually following a nomination and judging process. These typically take place in October and November, with the announcement of the next year’s HCL Ambassadors in December.  The HCL Ambassador Class of 2021 term runs from January 2021 through to December 2021. More details can be found on the HCL Ambassadors hub. Congratulations to everyone who has been recognized this year! We are thrilled to be working with you.  
Automation, Innovations | August 11, 2020
Introducing HCL Automation Power Suite Bundle to Automate More, Better and Smarter
HCL Software announced the introduction of HCL Automation Power Suite bundle offering comprising of HCL Workload Automation, HCL Clara and HCL HERO. With Automation Power Suite, customers can automate more, automate better and automate smarter to build an enterprise automation platform.
Automation | August 4, 2020
Unleash the power of HCL Workload Automation in an Amazon EKS cluster
Don't get left behind! The new era of digital transformation of businesses has moved on to new operating models such as containers and cloud orchestration.  Let’s find out how to get the best of Workload Automation (WA) by deploying the solution on a cloud-native environment such as Amazon Elastic Kubernetes Service (Amazon EKS).  This type of deployment makes the WA topology implementation 10x easier, 10x faster, and 10x more scalable compared to the same deployment in an on-premises classical platform. ​   In an Amazon EKS deployment, to best fit the cloud networking needs of your company, you can select the appropriate networking cloud components supported by the WA Helm chart to be used for the server and console components:   Load balancers   Ingresses   You can also leverage the Grafana monitoring tool to display WA performance data and metrics related to the server and console application servers (WebSphere Application Server Liberty Base). Grafana needs to be installed manually on Amazon EKS to have access to Grafana dashboards. Metrics provide drill-down for the state, health, and performance of your WA deployment and infrastructure.  In this blog you can discover how to:  Deploy WA components (Server, Agent, Console) in an Amazon EKS cluster, using one of the available cloud network configurations.  Download the Kubernetes job plug-in from the Automation Hub website and configure it in your AWS EKS cloud environment.   Monitor the WA solution from the WA customized Grafana Dashboard.   Let’s start by taking a tour!!!  Deploy WA components (Server, Agent, Console) in an Amazon EKS cluster, using one of the available network configurations  In this example, we set up the following topology for the WA environment and we configure the use of the ingress network configuration for the server and console components:   1 server   2 dynamic agents   1 console  Let’s demonstrate how you can roll out the deployment...
Automation | July 27, 2020
Enforce Workload Automation continuous operation by activating Automatic failover feature and an HTTP load balancer
How important is that your Workload Automation environment is healthy, up and running, and there are no workload stops or delays? What happens if your Master Domain Manager becomes unavailable or it is affected by downtime?  What manual recovery solution you must do when it happens? How can I distribute simultaneously requests to several application servers in my configurations if my primary server is drowning? How can I hourly monitor the workload automation environment healthy in an easy way? How can I have an alerting mechanism?  The answer is: Workload Automation 9.5 FP2 with Automatic failover feature enabled, combined with NGINX load balancer!  Let start to introduce the components participating to the solution:  = Workload Automation 9.5 FP2 introduces the Workload Automatic failover feature =  When the active master domain manager becomes unavailable, it suddenly enables an automatic switchover to a backup engine and event processor server. It ensures continuous operation by configuring one or more backup engines so that when a backup detects that the active master becomes unavailable, it triggers a long-term switchmgr operation to itself. You can define potential backups in a list by adding preferential backups at the top of the list. The backup engines monitor the behaviour of the master domain manager to detect anomalous behaviour.  = NGINX load balancer = Load balancing across multiple application instances is a commonly used technique for optimizing resource utilization, maximizing throughput, reducing latency, and ensuring fault-tolerant configurations. It is possible to use NGINX as a very efficient HTTP load balancer to distribute traffic to several application servers and to improve performance, scalability and reliability of web applications. Nginx acts as a single-entry point to a distributed web application working on multiple separate servers.   Let continue analyzing our use case solution:  We experiment the solution by defining and using this environment during the formal test phase for 9.5 FP2 project. ...