WORKLOAD AUTOMATION COMMUNITY

Real Discussion For Real People

Knowledge sharing and discussion platform for product experts and users

OUR LATEST POSTS!

Empowering the intelligent SAP enterprise with HCL Workload Automation

SAP is the backbone of thousands of companies worldwide: its end-to-end suite of applications and services enables business and public customers across 25 industries globally to operate. Enterprise resource planning is one of the strongest areas covered by SAP to take all the core processes needed to run a company – finance, HR, manufacturing, supply chain – and integrate them into a single system. Companies though are complex ecosystems that need to interconnect IT and business processes, while reducing their need for human intervention.
Automation is key to achieve governance, and boost agility.

Automate anything, Run Anywhere is our motto! What better place to start making it real than from our very own Workload Automation test environment? We have been applying it in our Test Lab for Workload Automation version 9.5 since its general availability in 2019, and to all the subsequent fix packs, including the last one, fix pack 3. Let’s start discovering how we can leverage a Workload Automation deployment to run automation jobs that build our code and prepare packages for both our HCL and IBM brand offerings. The automation jobs trigger several automation suites.

To improve productivity and to save IT management costs and time, our customers are starting to move to the cloud environment and are moving heavy workloads from a set of on-premises machines to a resilient cloud infrastructure. So, our principal mission is to facilitate, secure, and support moving a workload automation deployment, from an on-premises infrastructure (minimum WA 95 FP3 version required) to any cloud infrastructure where Workload Automation (WA) is already supported. Link for the video guide: https://youtu.be/7AQHgCnpqLc

A question which everyone would have in mind while Upgrading to WA 9.5 is to manage all the Carryforwards that are present in old Production Plan on the older Version of the Master and to migrate them to the newer Master Server . This Blog aims to sort this problem once and for all to ensure seamless transition to IWS 9.5 without any hassles. As you would already know if you are reading this Blog that WA 9.5 comes with a whole set of New Features and most noticeable Change Architecturally is to move to Liberty as a Middleware in place of Websphere Application Server, JazzSM for both the Engine as well the DWC Profile.