automation
Number of Posts: 20
Filter By:
Number of Posts: 20
Automation | September 23, 2020
Accelerate your Cloud Transformation! Take advantage from HCL Workload Automation on AWS Marketplace.
"You may not be responsible for the situation you are in, but you will become responsible if you do nothing to change it." Cit. Martin Luther King.   Get ready to accelerate your business by simplifying and automating workloads, improving service level agreements and reducing deployment and management time with your Cloud Transformation!   Could transformation is now the solution to many questions and customer needs to save costs on IT operations and enable faster time to market for new products and capabilities. The real value of cloud transformation is the organization’s new ability to quickly consume the latest technology and rapidly adapt and respond to market needs. A business transformation is not complete if the automation of processes is not also managed at both the IT and application levels. In this context, HCL Software is a real innovator and leader in the workload automation market with the availability of the HCL Workload Automation (HWA) solution which, integrated with an automation Bot, HCL Clara, provides the answer for a complete orchestration, monitoring and reporting of scheduled batch processes both on-premise and on the Cloud.   To respond to the growing request to make automation opportunities more accessible especially on the Cluod, HCL Workload Automation is now offered on the Amazon Web Services cloud as Amazon Elastic Kubernetes Service (Amazon EKS), a fully managed Kubernetes service with high  security, reliability, and scalability values. The strength of the innovation that HCL carry out with continuous and long-term investments is based on enabling the adoption of technology by minimizing the Total Cost of Ownership (TCO) and adopting paradigms such as containerization to facilitate product implementation and facilitate the transition on new releases. With the new release of HWA available on the AWS Catalogue, we are proud to enable the digital transformation of our...
Automation | August 28, 2020
Manage your AWS resources by using AWSCloudFormation with Workload Automation
Let us begin with understanding of AWSCloudformation what it is all about before moving to our AWSCloudformation plugin and how it is benefits to our workload automation users.   AWS CloudFormation provides a common language for you to model and provision AWS and third-party application resources in your cloud environment. AWS CloudFormation allows you to use programming languages or a simple text file to model and provision, in an automated and secure manner, all the resources needed for your applications across all regions and accounts. This gives you a single source of truth for your AWS and third-party resources. Coming to our AWSCloudformation, below diagram summarizes what is our plugin can perform, so our workload customers can make use of this to simplify their infrastructure management as well as easy to implement changes to infrastructure.   To give more clarity on its benefits let us understand with below example,   For a scalable web application that also includes a back-end database, you might use an Auto Scaling group, an Elastic Load Balancing load balancer, and an Amazon Relational Database Service database instance. Normally, you might use each individual service to provision these resources. And after you create the resources, you would have to configure them to work together. All these tasks can add complexity and time before you even get your application up and running.   Instead, you can create or modify an existing AWS CloudFormation template. A template describes all your resources and their properties. When you use that template to create an AWS CloudFormation stack, AWS CloudFormation provisions the Auto Scaling group, load balancer, and database for you. After the stack has been successfully created, your AWS resources are up and running. You can delete the stack just as easily, which deletes all the resources in the stack....
Automation | August 28, 2020
Simplify The Data Loading Using Oracle UCM and HCM Data Loader plugins with Workload Automation
Customers using Oracle Human Resources Cloud face the challenge of continuous bulk loading of large amounts of data at regular intervals. Oracle Human Resources Cloud provides the tools like HCM Data Loader which address this business use case. Now you can automate data loading into Oracle Human Resources cloud using the Oracle UCM and Oracle HCM Data Loader plugins which leverage the HCM Data Loader for the Workload automation users. Business Process automated:       Source: https://docs.oracle.com/en/cloud/saas/human-resources/20a/faihm/introduction-to-hcm-data-loader.html#FAIHM1372446 The above diagram shows the business process automated through these plugins: This process is divided into 2 steps and hence the 2 plugins: A .zip file containing .dat files is placed on the Oracle WebCenter Content server. Here the Oracle WebCenter Content server acts as a staging infrastructure for files that are loaded and processed by the HCM Data Loader. HCM Data Loader imports the data first into its stage tables and then into application tables. Any errors that occur during either the import phase or load phase are reported in the job status and details in job log.   Technical description and workflow Oracle UCM plugin The Oracle UCM enables you to stage data files for processing to HCM Data Loader. It provides easier integration with other business processes by using the Oracle Universal Content Management (UCM) integration. The Oracle UCM Data Loader automates the process of bulk-loading of data. You can load the data files and monitor them from a single point of control. The data is uploaded as zip files to Oracle UCM, which is processed by the HCM Data Loader. This integration helps you save time, resources, and speed up data loading in a secure manner. Prerequisite for the plugins to work: - Oracle Human Resources Cloud service account with correct permissions to access File Import and Export task...
Mainframes | August 17, 2020
Automation using HACL
In continuation to the previous blogs about Automation using PCSAPI and Automation using EHLLAPI API’s, this blog details about the strongest set of ZIEWIN API’s, the HACL (Host Access Class Library) API. Host Access Class Library (HACL) is a set of objects that allows application programmers to access host applications easily and quickly. HCL ZIEWin supports different HACL Layers: [caption id="attachment_8613" align="aligncenter" width="624"] Figure 1 HACL Layers[/caption] Automation Objects (Visual Basic, Word, Excel, etc) : The Host Access Class Library Automation Objects allow ZIEWin to support Microsoft COM-based automation technology (formerly known as OLE automation). The HACL Automation Objects are a series of automation servers that allow automation controllers, for example, Microsoft Visual Basic, to programmatically access ZIEWin Communications data and features. Note: Automation Objects provided by HCL ZIEWin are 64-bit in nature. These can be used only with 64-bit Microsoft Office programs. At present, the following types of automation objects are supported. C++ objects: This C++ class library presents a complete object-oriented abstraction of a host connection that includes: Reading and writing the host presentation space (screen) Enumerating the fields on the screen Reading the Operator Indicator Area (OIA) for status information Accessing and updating information about the visual emulator window Transferring file Performing asynchronous notification of significant events   Java Objects: Java objects provide Java wrappers for all HACL functions. LotusScript Extension: The Host Access Class Library LotusScript Extension (LSX) is a language extension module for LotusScript (the scripting and macro language of Lotus Notes and all the Lotus SmartSuite® products). This LSX gives users of Lotus products access to the HACL functions through easy-to-use scripting functions. ECL Concept - Connections, Handles and Names In the context of the ECL, a Connection is single and unique to a ZIEWin emulator window. Connections are distinguished by their connection handle or connection name. Most HACL objects are associated with a specific connection. Typically, the...
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 7, 2020
Case Study: SAP Factory Calendar Import with HCL Workload Automation
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...
a/icon/common/search Created with Sketch.