Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.


103 visualizaciones

Publicado el

  • Sé el primero en comentar

  • Sé el primero en recomendar esto


  1. 1. Migration from On-Premises to SaaS IBM Workload Automation Sajjad Kabir ( IBM Certified IT Specialist, IWA SME Senior IT Management Consultant
  2. 2. Agenda Overview of IBM Workload Automation (IWA) Software as a Service (SaaS) IBM Hybrid Cloud Architecture Considerations for migrating to SaaS Client Scenario IBM Cloud Agent User account and roles Migrating Workload from on-prem env to SaaS Cut-over
  3. 3. Overview of IWA SaaS IBM installs and deploys the IWA server infrastructure and provides on going maintenance, e.g. monitoring, upgrade, and backup Utilizes DevOps methodology to release new functions, features, and fixes Guarantees privacy, reliability, scalability, and security Optimizes business processes with flexible workload automation and job scheduling Automates IT and business processes using off-the-shelf components from Application Catalog Clients purchase subscription to SaaS offerings Runs workloads on IBM Cloud Agents locally installed on-prem servers and communicates with the SaaS env through a secured connection Provides a web browser based user interface, Application Lab, for managing simple or Dynamic Workload Console for advanced business processes
  4. 4. IBM Hybrid Cloud Architecture 3 Internet IBM Cloud (SoftLayer) Client Network Gateway Agent Agent https (443) https https (443) https https Master Backup Master WAaaS Controller
  5. 5. Considerations for migrating to SaaS 4 How this offering helps Need to reduce expenses No resources to build an automation infrastructure Lack of technical know-how hinders automation Adopt agile, cloud, mobile, next gen service mgmt Pain points Get time back by automating your processes Deliver results fast by using off-the-shelf components from our Application catalog Eliminate the need of HW for the infrastructure A tiered pricing model with pack size of 1,000 jobs with a monthly measurement period Start small then scale to meet complex challenges User Scenarios Typical buyer & influencer(s) Automate Big Data, Analytics, & ERP processes Run and monitor workloads wherever you are Modernize batch & move from job scheduling to Workload Automation (integrated processes) IT Ops managers - wants to move to a service- centric delivery organization LOB owner – wants low cost solution with immediate benefits, ease of use, ubiquitous, and scalability to grow with evolving needs. App owner – wants immediate integration capabilities with apps to automate processes Questions to ponder IT Ops manager : Am I spending too much money building and managing the infrastructure? LoB owner : Is it taking too much time to automate and monitor our processes?
  6. 6. Client Scenario 5 Benefits Cost savings Software needed to be upgraded as it was going out of support No internal resources with deep TWS skills Allocate budget for a services contract to assist with the upgrade Business Drivers Cost reduction by about 10-15% Software is always up to date and in support Run and maintain existing workloads without hiring skilled TWS resources With the company splitting, SaaS provided an ideal situation for separate accounting
  7. 7. Client Scenario (Splitting into two entities and migrating to SaaS) 6
  8. 8. IBM Cloud Agent 7 IBM Cloud Agent is a Dynamic Agent Windows, Linux, HP-UX, AIX, and iSeries are the supported Operating Systems All communication is established using HTTPS Only the SSL port (443) needs to be opened through the firewall An alternative server can be used as a gateway with SSL connection for servers with no connection to the internet All connections are outbound from on-prem to SaaS env Workstation (Variable Table, Calendars, and Prompt) names are prefixed with a two letter identifier to support multi tenancy A set of plugins and access methods included with the agent Run a wrapper script (installAgent) to launch the installation Flags used to specify unique ports for multiple instances of the agent
  9. 9. User Accounts and Roles 8 The web user interface is provided by IBM Service Engage site. Once the SaaS instances is deployed, user accounts can be created Each user needs to register for an IBM ID The owner of the subscription goes into User Management and adds users There are two roles available: o App Developer – full access to create and run workloads o Administrator – manage subscription and users Additional roles can be requested via support channel
  10. 10. Migration Methodology 9 Workload Applications were introduced in IWA 9.1 It is an object that can package a set of scheduling objects for migration from one env to another SaaS env supports Workload Applications Clients migrating from 9.x to SaaS can easily export Workload Applications and import into SaaS Clients migrating from 8.x to SaaS need a different approach: Export all scheduling objects to text files Import into a 9.x lab env Create and export Workload Applications Import Workload Applications in to SaaS
  11. 11. Migration Methodology (from 8.x) 10
  12. 12. Migration Methodology (from 9.x) 11
  13. 13. Migrating Workload from on-prem to SaaS 12
  14. 14. Migrating Workload from on-prem to SaaS (details) 13 Declare a freeze period with no changes allowed in the on-prom env Export all scheduling objects Make adjustments to Run Cycles for the change in Start of Day, 12:00 AM in SaaS Change the priority of any job or job stream from Go to High Raise the fence on all workstations from 0 to High in the SaaS env. This will hold all jobs from running Import all Workload Application making substitutions as necessary Select a few workloads to test, change the priority from High to Go, so that it can go over the fence and run Upon successful execution, change the priority from Go to High Generate a Forecast plan and compare with the plan in the on-prem env Make necessary adjustment to match the two plans
  15. 15. 14 Cut-over
  16. 16. Cut-over (details) 15 On the day before the cut-over, hold the workloads that run between 12 AM and Start of Day in the on-prem env Before 12 AM in the SaaS env, drop Fences on all workstations to 0 The plan will start executing from the SaaS env on all Agents A few minutes before FINAL runs in the on-prem env, raise the Fence on all Workstations to Go, except the MDM so that only FINAL runs Before FINAL finishes, raise the Fence to Go on the MDM All workload will be on hold in the on-prem env If there are workloads that weren’t migrated to the SaaS env, drop the Fences on the respective workstations As the plan progresses accordingly in the SaaS env, towards the end of the day, cancel all workloads in the on-prem env that ran successfully in the SaaS env and put them in Draft mode Drop the Fence to 0 on all workstations in the on-prem env
  17. 17. Fail-back 16
  18. 18. Fail-back (details) 17 If workloads aren’t running properly in the SaaS env Raise the Fences on all Workstations to Go in the SaaS env Cancel the workloads in the on-prem env that have already run successfully in the SaaS env Drop the Fences on all Workstations to 0 in the on-prem env Determine and solve the cause of failure Schedule a cut-over again
  19. 19. Want to Lean More?
  20. 20. Notices and Disclaimers 19 Copyright © 2016 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM. U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM. Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. THIS DOCUMENT IS DISTRIBUTED "AS IS" WITHOUT ANY WARRANTY, EITHER EXPRESS OR IMPLIED. IN NO EVENT SHALL IBM BE LIABLE FOR ANY DAMAGE ARISING FROM THE USE OF THIS INFORMATION, INCLUDING BUT NOT LIMITED TO, LOSS OF DATA, BUSINESS INTERRUPTION, LOSS OF PROFIT OR LOSS OF OPPORTUNITY. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided. Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice. Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary. References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business. Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation. It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actions the customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law
  21. 21. Notices and Disclaimers Con’t. 20 Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products in connection with this publication and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. IBM does not warrant the quality of any third-party products, or the ability of any such third-party products to interoperate with IBM’s products. IBM EXPRESSLY DISCLAIMS ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. The provision of the information contained h erein is not intended to, and does not, grant any right or license under any IBM patents, copyrights, trademarks or other intellectual property right. IBM, the IBM logo,, Aspera®, Bluemix, Blueworks Live, CICS, Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document Management System™, FASP®, FileNet®, Global Business Services ®, Global Technology Services ®, IBM ExperienceOne™, IBM SmartCloud®, IBM Social Business®, Information on Demand, ILOG, Maximo®, MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower, PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®, PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®, PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®, SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli®, Trusteer®, Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and System z® Z/OS, are trademarks of International Business Machines Corporation, registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at:
  22. 22. Thank You Your Feedback is Important! Access the InterConnect 2016 Conference Attendee Portal to complete your session surveys from your smartphone, laptop or conference kiosk.