In this blog, we are going to walk you through enabling session affinity for the Dynamic Workload Console (console) deployed in a Google Kubernetes Engine (GKE) cluster that uses an HTTP(S) load balancer network service that leverages an instance of Google Cloud SQL for SQL Server managed database. In a GKE cluster environment, a backend service defines how the HTTP(S) cloud load balancing network service distributes incoming traffic. By default, the method for distributing new connections uses a hash calculated based on five pieces of information: The client's IP address.The source port.The load balancer's internal forwarding rule IP address.The destination port.The protocol. You can modify the traffic distribution method for HTTP(S) traffic by specifying a session affinity option.
We, the Workload Automation family, love to take care of every detail. Indeed, we strongly believe that to deliver a good quality product we need to increase our knowledge every day more by discovering and studying new technologies.But the technical part is not the only important thing, we take care of the whole product, which means presentations, blogs, videos, documentation, client advocacy, design thinking, skill transfer, etc.To achieve these goals, effective collaboration and knowledge sharing are at the core. Thus, we arrange a lot of knowledge sharing programs, such as “WA Talks” and “Lunch&Learn”.
As a matter of fact, the deployment of Workload Automation (WA) to a Microsoft Azure cluster makes the implementation of the WA topology 10 times faster and 10 times more scalable compared to the same deployment to the classic on-premises platform, as is the case for Red Hat OpenShift, AWS EKS, Kubernetes and so on. The WA deployment to an Azure cluster can leverage all well-known cloud benefits.
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, boost agility and enable a true digital transformation process, impacting all the business units.
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
Zowe and its major components Web UI, API Mediation Layer, and CLI, are likely to become the new interface for the next generation of mainframers.The Zowe framework is the bridge that connects modern applications with the mainframe by providing easier interoperability and scalability among products and solutions offered by multiple vendors. Developers, testers, operators, and any other professional in the mainframe realm can easily create their tools to automate those tasks that usually would be done manually or through mainframe-native tools. They can build, modify, and debug z/OS applications even with limited z/OS expertise.
The SAP batch access method enables communication between an external SAP system and Workload Automation and provides a single point of entry for automating the launching of jobs, monitoring the status of jobs, and managing exceptions and recovery.“ …Which are the steps you need to follow to setup faster your Workload Automation environment to the target SAP system?...”