AutoSys Workload Automation Is Cloud Ready

by July 11, 2019

What does it mean to be cloud-ready? If you do a Google search you will find 979M results with all kinds of websites explaining cloud readiness. Regardless, we are not trying to explain the term. We want to give information on how to make the best out of your AutoSys environment as you plan your cloud readiness approach.

First, let’s define two areas of cloud readines

  • Deployment environment. This is where you want the solution to reside. The AutoSys solution, either entirely or partially, may be deployed in a private/public cloud, traditional on-premise or in a hybrid environment.
  • Application architecture.  The way the application was architected to run (e.g. classic command line or cloud-enabled). AutoSys is capable of executing cloud-deployed applications using a variety of methods. The way these are automated depends on the type of application (e.g. command-line, SaaS/PaaS, containerized, etc.).

Do you have cloud initiatives? If so, offer your AutoSys solution to ensure it is automated. Despite what other competitors may say, AutoSys is future-ready, proven, and able to cover your cloud needs as well.

What are the steps to get to the Cloud?

  • Determine where you want to deploy the solution. If you choose to continue running AutoSys on-premise, nothing else is required from the solution perspective. If you wish to deploy AutoSys itself to the cloud, select your preferred cloud platform (e.g. Amazon, Microsoft Azure, and Google) and determine whether you want to utilize a consumption-based cloud database services such as Amazon Relational Database Service (RDS), Azure SQL Server, or a bring your own license (BYOL) deployment of a supported database (i.e. MS SQL Server, Oracle, Sybase).  AutoSys licensing is the same regardless of your deployment choice. 
  • Identify the application types you wish to automate. Classic command-line applications that have been moved to the cloud, typically referred to as lift-and-shift, where the existing on-premise environments were merely migrated to a cloud infrastructure can continue to run as they have been. Conceptually, the only thing that is changing is the hostname where the agent is deployed. Applications designed to run in the cloud (e.g. SaaS/PaaS, containerized) require different techniques. Typically, these applications are executed using web services. AutoSys natively provides support for both SOAP and REST web service protocols. The current REST implementation provides basic functionality. (The AutoSys 12.0 release will make this much easier.) This may present some challenges, all of which are relatively easily overcome. Let’s start by considering the various ways of invoking web services. For SOAP web service implementations, typically the WSDOC (SOAP document literal) job type is used to define the web service. For REST, the HTTP job type is used. Other options include calling the web services using applications written in various programming languages (e.g. Java, PERL, Python, etc.) or even using a generic command-line interface (CLI) such as cUrl. It should also be noted that response or payload data of one job can be shared or consumed by another.  Containerized applications can also be executed in multiple ways. All of the container managers provide REST interfaces as well as robust thin command-line interfaces. These applications could be called using the HTTP job types or even easier as command jobs via the respective CLIs. Some examples of these include docker, kubectl, oc, pcf respectively for Docker, Kubernetes, OpenShift, and Pivotal Cloud Foundry).

Some examples of cloud-based applications we have worked with customers to automate include SAP Integrated Business Planning (IBP), SAP Data Services on Demand (DSoD), Oracle HCM, and container-based applications (e.g. Docker, Kubernetes, Pivotal Cloud Foundry, OpenShift, etc.)

This is what you would expect from a modern automation product and AutoSys is able to cover your needs. It is not legacy. It is moving forward and does have a long and robust roadmap in place.

There’s no reason to delay exploiting the cloud today. Whether you’re just beginning to migrate your on-premise environments to the cloud or taking the next step to automate applications architected for the cloud, there’s no need to wait further. Let us help you get started today. 

Want to know more? Join us on July 25th for a free webinar on AutoSys Workload Automation in a Cloud Environment. Register here

If you have questions, please feel free to reach out to our AutoSys product manager, Daniel Shannon (daniel.shannon -at- broadcom.com). He is happy to discuss your needs for AutoSys in a Cloud environment.