Power of ONE Automation through Web Services
Download as PPTX, PDF1 like649 views
This document discusses the use of web services for automation through orchestration strategies. It notes that using web services will become necessary for leveraging software as a service solutions, big data solutions, and infrastructure as a service. The Automic web service agent allows orchestration through web services without scripting by supporting REST and SOAP calls and extracting values from responses. The document demonstrates requesting and ticketing through a JIRA API and provisioning servers on Amazon EC2 through web services calls. It provides details on defining web service connections, requests, and parsing responses.
Power of ONE Automation through Web Services
- 1. Automic World 2015 November 2015 Automation through Web Services
- 2. 2 Property of Automic Software. All rights reserved The Challenge of Keeping up with Change.. Distributed World Mutualized World Orchestration Strategies: Command Line Interface APIs Binary Calls OS Commands & Scripts Orchestration Strategies: Web Services
- 3. 3 Property of Automic Software. All rights reserved Using Web Services will become necessary If… You are leveraging any SaaS based solution today or planning it You are adopting big data solutions (Cloudera, Hortonworks) You are using Web Services in your internal development You are using any Software as a Service solution (Salesforce, Jira) You are using Infrastructure as a Services (ex: Amazon EC2) You are using Platform as a Service (ex: OpenShift, Cloud Foundry) You are pulling Data from Partners, Entities, Customers etc.
- 4. 4 Property of Automic Software. All rights reserved What makes the Web Service Agent interesting No Scripting Necessary Support for Rest and SOAP Ability to parse and extract values from Responses Define Custom Variables Get Request and Response as Reports
- 5. 5 Property of Automic Software. All rights reserved Demo: Request Management & Ticketing Open JIRA Ticket upon failure in Workflow Close JIRA Ticket from Job Recovery Add Comments to JIRA Ticket
- 6. 6 Property of Automic Software. All rights reserved Demo: Provisioning Servers Dynamically Provision New Servers via Elastic Cloud Computing (EC2) Easily Identify Instances Automatically Run Maintenance and clean ups Dynamically Deprovision Servers
- 7. 7 Property of Automic Software. All rights reserved Web Service Connection – Object Definition Handles Proxies Handles Authentication Contains the Endpoint (URI / WSDL) Handles Headers and Query Parameters (ex: Version of authentication method) https://ec2.us-east-1.amazonaws.com/finance/?Version=2013-02-01&Action=DescribeInstances&InstanceId=&instanceid
- 8. 8 Property of Automic Software. All rights reserved Web Service - End Point & Curl
- 9. 9 Property of Automic Software. All rights reserved Web Service Request –Variable Query Parameters
- 10. 10 Property of Automic Software. All rights reserved Web Service Request – URL Query Parameters
- 11. 11 Property of Automic Software. All rights reserved Web Service Request – Data
- 12. 12 Property of Automic Software. All rights reserved Web Service Response – Parsing XML / JSON Responses
- 13. 13 Property of Automic Software. All rights reserved Best Practices Use a proxy for better control Install 2 Web Services Agents for High Availability Put all Generic / Common parameters in Connection Objects Run tests with cURL when starting your implementation “Variabilize” as much as possible
- 14. 14 Property of Automic Software. All rights reserved Q&A Thank You!
Editor's Notes
- #3: The Challenge: Coping with innovation is difficult especially as it is accelerating under the influence of new trends and new technologies. The reality now is that any company that isn’t fast enough in adapting to more dynamic / cheaper technologies becomes at risk of losing momentum, business and even in some cases their leadership positions. (Uber, Netflix, Amazon anyone?) “How does Automic fit into this?” => giving part of an answer is the goal of this session today.
- #4: Why Now? All successful companies today race for innovation.. And that is what makes them successful. Companies, and especially tech companies are NO LONGER in the business of running hardware or software. They are in the business of providing Dynamic & Adaptive Services that can scale to the largest audience. A similar pattern goes for other companies too: IT went from being a somewhat cost center to being a Business Unit generating Business Value.. But most companies are still relying on IT that is mostly on premise, cannot easily and elastically scale, and is somewhat dependent on the performance of its members and the solidity of its practice. This shift is the single reason why the AAS family is growing: Netflix will soon no longer run anything on premise, amazon has EC2, Automic runs salesforce..
- #6: Demo time: 1- Log into ECC / AE 2- Trigger a workflow with predicted failures 3- Automatically open tickets into Jira 4- Login to Jira and open corresponding tickets 5- recover from error in AE and relaunch 6- close ticket in Jira from AE
- #7: Demo time: 1- Log into EC2 console, show the different parts 2- Show the instance console and the list of instances running 3- Show how to provision a new server manually using the wizard 4- Login to AE / ECC and trigger the workflow to build an instance 5- check out the instance and logon to it 6- deprovision instance
- #8: Main points: Connection Objects are NOT specific to a service / action / operation, they are specific to an end point and an account Connection Objects can also handle Proxies in case web traffic is routed through a proxy by policy Connection Objects can also contain Resource Parameters and Query Parameters. Ex: Consider URL: https://ec2.us-east-1.amazonaws.com/finance/?Version=2013-02-01&Action=DescribeInstances&InstanceId=&instanceid Finance/ is a Resource in the CONN object Version=2013-02-01 is a Query Parameter in the CONN object => They are common to ALL subsequent calls
- #9: Main points: cURL can be used for testing: convenient when debugging calls URI is built from CONN object AND additional Headers & Query Parameters in the Job definition.. It can however be overridden easily (same as above) Timeout can be set at Job level otherwise take a default value Response can be displayed in Job REPORT, Request and Response can additionally be registered as additional Job Outputs.
- #10: Main Points: Query Parameters usually contain the Action Call itself and all required parameters for the action to work. Here: we use DescribeInstances, which returns information on EC2 instances against certain filters.. Those filters are declared as Parameters The values of Parameters can use Automic Variables
- #11: Main Points: Query Parameters usually contain the Action Call itself and all required parameters for the action to work. Here: we use DescribeInstances, which returns information on EC2 instances against certain filters.. Those filters are declared as Parameters The values of Parameters can use Automic Variables
- #12: Main Points: Response can be filtered for content and shown in Job REPORT. It can also be parsed dynamically for data retrieval and saved in Automic Variables The parsing aspect can be tested directly from the Job Definition Variables can be further processed in POST-PROCESS tab of Jobs
- #13: Main Points: Response can be filtered for content and shown in Job REPORT. It can also be parsed dynamically for data retrieval and saved in Automic Variables The parsing aspect can be tested directly from the Job Definition Variables can be further processed in POST-PROCESS tab of Jobs
- #14: requirements