Can you have your desired number of Workload Automation (WA) agent, server and console instances running whenever and wherever? Yes, you can!
Starting from the Workload Automation version 9.5 fix pack 2, you can deploy the server, console and dynamic agent by using Openshift 4.2 or later version platforms. This kind of deployment makes Workload Automation topology implementation 10x faster and 10x more scalable compared to the same deployment in the on-prem classical platform.
If you want to avoid a potential business disruption in your Workload Automation environment, you should leverage the Master/Backup Master configuration. But, what happens if the RDBMS connected to Workload Automation crashes?
In this article, we will describe how to manage both Workload Automation components and DB2 HADR to allow business continuity during a disaster event.
Nowadays, the global marketplace requires systems that can react to fluctuating loads and unpredictable failures, with the end-level agreement (SLA) goal of being available 99.999% of the time. Mitigating the negative impacts of failures, disasters and outages cannot even be contemplated in today’s competitive world. A disaster recovery strategy is too error-prone and resource-consuming: businesses need to operate following an “always on” model.
Workload Automation 184.108.40.206 is here: create an automation center of excellence to drive your digital transformation
HCL and IBM are pleased to announce a new release for Workload Automation, version 220.127.116.11, with enhancements that expand the innovations delivered with version 9.5 and enable the orchestration of new scenarios, particularly for datacenter automation.
A new website, the Automation Hub, has been launched to allow our customers to easily find all the integrations available to orchestrate their business-critical processes.
What is the role of Workload Automation in a disaster recovery mode?
Forewords: coping with a crisis
It is with an intense sense of modesty that we are approaching this topic, since this article is written in the midst of the most severe crisis for humanity our generation ever faced.
Consequently, writing about how an IT solution can help recovering from - and coping with - a planetary health emergency is not an easy task at all.
This Blog aims to showcase a Case Study on how Inventory Management can be managed through Workload Automation .A Company runs a production Plant where Inventory Management is to be Automated using Workload Scheduler. The Production Plant wants to be as close to Balanced plant as possible by reducing Inventory when in excess and increasing Inventory when low .
Workload Automation (WA) simplifies and accelerates application delivery.
It automates and orchestrates application workflows across hybrid environments to satisfy SLAs and improve efficiency and productivity.
You can use the agent for z/OS - aka D-Driven - to schedule work using IBM Workload Scheduler. You install and configure the agent for z/OS in the z/OS system and this work as any other dynamic agent. As soon as it is configured, the agent automatically links with the dynamic domain manager component of IBM Workload Scheduler through the HTTP or HTTPS protocols. With the agent for z/OS you can define jobs and schedules on IBM Workload Scheduler and submit a subset of the jobs to a z/OS system and you run the planning tasks on IBM Workload Scheduler while the execution is demanded to the z/OS system.
“Mainframe essentially keeps the world running."
It may sound bold but it’s true. The quote above, which is from an IBM executive , Philip MacLochlainn, is indeed supported by stunning figures: “85% of all credit cards, 29 billion ATM transactions per year, 92 of the top 100 banks ... 12 billion passenger flights are booked” thanks to mainframe. And it makes no wonder to whom is familiar with mainframe’s history and the story of workload scheduling and management, which we contributed to write.
In the last few years there is a lot of focus around “Mainframe Modernization” … and there are multiple reasons for this focus and great benefit for the enterprises that will embrace this journey. In the journey to Cloud, the market is entering in a new chapter, while in the initial phase, that we call chapter 1, the focus and the plan was to migrate existing workload and application to Cloud, with a modernization of the IT and build new application as Cloud-ready, in the new chapter (Chapter 2) the focus on “migration “ was strongly reduced for multiple reasons.