This Blog aims to showcase how a Company using HWA and maintaining all its Application Code on GIT alongwith all Scheduling Objects could also promote and manage the entire Code Promotion using HWA while also tracking the Whole Process on Service Now.

In this Blog, we would go through a UseCase to demonstrate a Customer wanting to Track his Application Deployment through Service Now uses HWA to accomplish the same while also orchestrating the entire flow of Application Deployment and Service Now Ticketing Orchestration through HWA :

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.

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.

This blog aims to show how SAP Calendar Import could be done through Workload Automation. Workload Automation as a product has ready made integration with SAP since the 90’s leveraging the SAP RFC Libraries of SAP using the SAP R/3 Batch Access Method.  Now , we would see how we can use this same access method to import Freeday Calendars or Workday Calendars from an SAP R/3 System into Workload Automation.  The r3batch access method can be invoked from TWS/methods Directory(in the older versions) or from the TWSDATA/methods directory in the Newer versions . The export can be for both Freeday Calendars as well as Workday Calendars. The below example is an export of a Freeday Calendar referenced by the Factory Calendar ID 02 exported into a text file /tmp/calendar_03.dat with the name HLI :  wauser@wa-server:/opt/wa/TWS/methods$ ./r3batch -t RSC -c S4HANAR3BW -- " -calendar_id 02 -year_from 2020 -year_to 2021 -tws_name HLI -getfreedays -filename '/tmp/calendar_03.dat' "  Tue Mar 10 09:48:58 2020  -t RSC represents that the import is for an RFC SAP Calendar.  -c CalendarName represents that the Calendar name which is imported from the specific SAP System.  -calendar_id XX denotes a 2 Character identifier of the SAP R/3 Calendar to be imported.  -year_from XXXX denotes the Start year from which to start exporting the dates.  -year_to XXXX denotes the End Year upto which you can export dates.  -getfreedays indicates that the export is for Freedays.  -filename ‘<PATH>/CalendarFileName’ indicates the name of the file to which export is to be done on the Host OS where you are issuing the command.  The exported Calendar can be viewed in the File as shown below :  wauser@wa-server:/opt/wa/TWS/methods$ cat /tmp/calendar_03.dat  $CALENDAR  HLI    ""    01/01/2020 01/04/2020 01/05/2020 01/11/2020 01/12/2020 01/18/2020 01/19/2020    01/25/2020 01/26/2020 02/01/2020 02/02/2020 02/08/2020 02/09/2020 02/15/2020    02/16/2020 02/22/2020 02/23/2020...