Although Dynamic Agents have been around since TWS 8.6, troubleshooting procedures and checks around Dynamic Agents are not clear yet among majority of the Workload Automation Administrators.
What is a gateway? You can configure a Dynamic Agent as a network gateway to other Dynamic Agents which cannot communicate directly with the Dynamic Workload Broker (DWB) installed on the Master Domain Manager (MDM) or Domain Manager (DM).
This article aims to explore the different types of gateway supported by Workload Automation Dynamic Agent.
IBM Z Workload Scheduler provides a smart interface called Workload Automation Programming Language (WAPL) that allows users simply leverage the full potential of Z Workload Scheduler.
With WAPL it is possible to easily implement scenarios that would normally require a complex programming if implemented through the classic Workload Scheduler Programming Interface Facility (PIF).
Artificial intelligence today is a topic that is cannibalizing the attention of everyone. From the consumers to the industries, it is revolutionizing many aspects of our lives enabling new abilities, before accessible only to human beings.
Developing a Web UI Test Automation battery is usually a challenging project. By nature, a graphical interface of any product tends to evolve and change very quickly, not only to offer the users new features, but also to improve the look and feel of the application. The continuous restyling of web pages is typically reflected in unsustainable Web UI Test Automation code maintenance costs: the frequent rework of the developed test scenarios is driven by failures and analyzing the last test automation execution report consists in a “hunt for defects”.
There are possibly very few industries – if any at all – that can operate without an ERP system, and one of the most successful of such systems is definitely SAP. This is probably also due to the versatility of SAP, being that there are SAP-apps for almost any industry business. It is therefore quite natural to see a solution like HCL Workload Automation (HWA), that makes of the versatility and openness one of its strengths, integrating exceptionally well with SAP. Register for the Widen your SAP landscape with HCL Workload Automation webinar to learn more now!
Although Runcycles and Calendars objects are part of Workload Automation from the beginning, the flexibility of use offered by them compared to other Enterprise Schedulers is not fully understood. This blog aims to present some complex scenarios involving Runcycles and Calendars.
In this blog, we will explore the best architectural practice for Remote Gateway and Local Gateway, for Workload Automation on Cloud (SaaS offer).
If you are a Workload Automation Administrator and you are involved in orchestrating SAP workloads, one of most frequent questions is: How do I control background jobs that are scheduled by end-users?
This is definitely one of the top challenges in the Workload Automation area.
End-user scheduled jobs that bypass a central scheduling are undermining all efforts to control the batch workload on a backend-system and can cause unexpected overloads.
To make things more complicated, company policies often do not permit to limit scheduling authorization for end-user.
There is an enormous amount of Workload Automation Information: it originates from varying sources, with numerous levels of detail, dispersed across product guides, technotes and websites. Information overload makes it difficult when you are trying to find the right piece of Workload Automation information when you need it.