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.
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.
Client Scenario (Splitting into two entities and migrating to SaaS)
6

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.
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
https://www.ibm.com/account/profile/us?page=reg
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.
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

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

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

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

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, ibm.com, 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: www.ibm.com/legal/copytrade.shtml.