Astadia IBM Mainframe To AWS Reference Architecture
Astadia IBM Mainframe To AWS Reference Architecture
Reference Architecture
Abstract
In businesses today, across all market segments, cloud computing has become the focus of current and
future technology needs for the enterprise. The cloud offers compelling economics, the latest
technologies and platforms, and the agility to adapt your information systems quickly and efficiently.
However, many large organizations are burdened by much older, previous generation platforms,
typically in the form of a mainframe computing environment.
Although old and very expensive to maintain, the mainframe platform continues to run the most
important information systems of an organization. The purpose of this reference architecture is to assist
business and IT professionals as they prepare plans and project teams to start the process of moving
mainframe-based application portfolios to Amazon Web Services (AWS). We will also share various
techniques and methodologies that may be used in forming a complete and effective Legacy
Modernization plan.
This document is part of the Astadia Mainframe to Cloud Modernization Series that leverages Astadia’s
25+ years of mainframe platform modernization expertise.
All other copyrights and trademarks the property of their respective owners.
IBM Mainframe to AWS Reference Architecture
Contents
Introduction ............................................................................................................................ 1
Why Should We Migrate Our Mainframe Apps to AWS? ................................................................. 2
Benefits of Mainframe Modernization ..................................................................................................... 2
Approaches to Mainframe Modernization ............................................................................................... 2
Challenges of Mainframe Modernization ................................................................................................. 3
Why AWS?................................................................................................................................................. 4
Achieving the Positive Impact of Change.................................................................................................. 5
Understanding Typical IBM Mainframe Architecture ...................................................................... 6
IBM Mainframe Heritage .......................................................................................................................... 6
IBM Mainframe Components ................................................................................................................... 6
IBM Mainframe to AWS Reference Architecture ............................................................................ 8
Understanding Amazon Web Services (AWS) ..............................................................................12
Ensuring Project Success .........................................................................................................15
Astadia Mainframe-to-AWS Success Methodology ................................................................................ 15
Conclusion .............................................................................................................................17
IBM Mainframe to AWS Reference Architecture
Introduction
The Amazon Web Services (AWS) cloud computing platform is an excellent target environment for
transitioning from an IBM mainframe workload to a cloud implementation. With the security features of
AWS and the ability to scale based on demand for the services, AWS offers a complete operational
environment in support of mainframe workloads that have been migrated to the cloud. In addition, AWS
supports new innovation of the application portfolio, previously held captive by the inflexible nature of
a mainframe computing model, improving the productivity of application developers and support
personnel.
Even more than a typical IT project, planning to modernize mainframe applications is the most important
phase of the total project effort. A good place to begin is with a thorough assessment of the existing
overall mainframe application portfolio. Through the assessment process, all aspects of the existing
portfolio will be inventoried and examined in detail, resulting in a catalog of each application, database,
technology platform and business user profile currently in use. Once completed, the results of this
application rationalization will then guide the sequence of application migration, as well as the different
modernization strategies and techniques that may be called upon over the course of the entire project.
We’ve included an overview of how Astadia tackles Legacy Modernization projects with our Success
Methodology to give you an idea of what’s involved.
Don’t let the enormity and importance of a mainframe modernization project deter you from getting
started. The skilled individuals needed to continue to maintain mainframes are increasingly leaving the
workforce through retirement and are not being replaced. Hardware and software maintenance costs
continue to escalate and the demands of customers, employees and partners require greater innovation
than mainframe platforms can support.
About Astadia
Astadia has been in the legacy modernization business since 1994 and has successfully completed more
than 200 mainframe modernization projects. Our repeated success has allowed us to develop a
comprehensive methodology, proprietary software tools and techniques, as well as the “know how” that
comes with more than 25 years of experience handling mission critical applications and data. We’re
pleased to share some of that experience with you through our Mainframe to Cloud Modernization Series
of reference architectures, webinars, whitepapers and more. Visit our website at www.astadia.com for
additional information.
So, why should you migrate your mainframe workloads, why migrate them to AWS and why is now the
right time?
Benefits of Mainframe Modernization which ones will be determined during the critical
application portfolio rationalization step of the
The specific benefits in moving any mainframe
project’s assessment phase. Here are three of the
workload will vary between organizations and
most common approaches:
even at the application and database level. In
general, here are three of the top reasons driving
Reuse – Often called “lift and shift”, this is a
legacy modernization projects today:
process that reuses the existing
code/program/applications, typically written in
Cost – The economics of cloud computing are
COBOL, by moving them off the mainframe, and
compelling when compared with the status quo of
recompiling the code to run in a mainframe
maintaining a mainframe environment. A total
emulator hosted in a cloud instance. This approach
cost of ownership (TCO) evaluation of the
minimizes the upfront risks and the length of the
subscription-based, consumption driven cost
project, realizing hardware and software cost
model of the cloud versus the exorbitant hardware
savings soonest.
& software maintenance costs of mainframes will
show a very appealing and short-term achievable
Running mainframe applications in an AWS-hosted
ROI (potentially less than 12 months from project
emulator also opens the possibility of new
completion).
innovation leveraging APIs to previously
inaccessible programs and data.
People – Mainframe-specific technical skills are
not being replaced by today’s college or
Rewrite – It may be tempting to say, “Let’s just
technology trade school graduates. The pool of
write new programs from scratch,” to modernize
available talent with relevant knowledge and
the mainframe applications. This approach is
experience is shrinking exponentially each year.
extremely risky and fails a vast majority of the
The cloud leverages modern technology and its
time. It is complex, costly, and time consuming.
use is ingrained into young software engineers
The resources and investment required tends to
worldwide.
greatly exceed the forecast.
Flexibility – The cloud offers an Open Systems
A new, modern codebase may still be the correct
environment in which high productivity and rapid
end objective, but a better approach would be to
innovation happen at a tremendous rate. A
first move the applications to a cloud-based
properly designed implementation of a cloud
emulator, migrate the database to a cloud-based
infrastructure scales easily and quickly, both
database, then focus on replacing modules/code
expanding and collapsing to synchronize with
over a deliberate, multi-phased approach. When
business demand. Backup, redundancy and
it is time to rewrite, there are several code
disaster recovery is seamless. Support for multiple
transformation engines you can choose from to
end-user platforms and devices is inherent.
reduce the effort and minimize the risk.
Database sharing across the enterprise with high
performance is achievable.
Replace – Another mainframe modernization
approach is to completely replace the mainframe
Approaches to Mainframe Modernization functionality with a program or suite of programs,
You may notice throughout this document that we typically a Software-as-a-Service (SaaS)
use the terms “Mainframe Modernization” and application. You typically see this with purpose-
“Mainframe Migration”. Migration is a type of built solutions for finance, human resources,
modernization, whereas modernization manufacturing, enterprise resource planning, etc.
encompasses a broader set of strategies or There are also industry specific apps that may
options. In many cases, you will employ a solve the problem that a custom mainframe
combination of these strategies, the right mix of solution was needed for decades ago.
Paying for a continuation of the primary production range of use cases. They also have the largest
system and funding the development efforts of the compute capacity in use by paying customers. This
new system at the same time will have a attracts open source and application developers as
temporary financial impact for as long as that well as service providers to make their applications
duality continues. Getting to a “go live” status compatible or add their services to AWS.
quickly and efficiently with the new system, and
retiring the old system, will keep unexpected costs The benefits of migrating your mainframe to
to a minimum. AWS are:
encryption in transit, and private or dedicated the road, which are likely not available to
network connections. mainframe users today.
Achieving the Positive Impact of Change The overall impact of a successful mainframe
migration project is a positive one for the entire
In any mainframe migration project, the results of
organization. A new and better application
a cloud-based application set may be daunting.
portfolio, a cloud platform to enable innovation,
The change will impact the technical staff, as they
and a large cost savings in the operational and
will likely need to learn new skills.
systems software maintenance categories will be
realized. It’s not unusual to repurpose IT staff
The end-user community may not notice too many
after redeploying the mainframe portfolio to the
changes using a new system if the interfaces are
cloud. The cloud platform has many other benefits,
preserved. In fact, the move to the cloud could
but flexibility and cost takeout are at the top of the
fuel innovation resulting in new capabilities down
list.
Below, you will see a design that includes details such as AWS components, batch requirements,
programming language conversions and replacements, integration with external systems, 3rd-party
software requirements, and planning for future needs.
In an actual project, you would also consider any unique features that would necessitate custom-made
solutions. We would recommend proof-of-concept conversions on application subsets to test the model
selected, discover any weaknesses, and prove the viability of the design.
Code Modification
As part of any mainframe modernization project,
there will be a need for partial or, in some cases, Astadia employs an iterative, hybrid process of
extensive code modification. Leveraging our past automated code conversion and human
experience in migrating IBM mainframes to on- intervention. The technology behind the
premises open-systems platforms, Astadia has automation is our Rules-Based Transformation
developed an extensive set of code transformation Engine.
technologies and processes to successfully re-
platform mainframe workloads. We use these in This tool preserves the business logic and rules of
concert with trusted third-party products to modify legacy applications while removing proprietary
source code for deployment to AWS. What follows code that can only execute in the source
is a description of our approach. environment and not in AWS. Its code migration
filters ensure the preservation of mission-critical intervention ensures that legacy applications will
applications and back-end components such as work in AWS without sacrificing their original
trancodes, security policies, and message routing. functionality.
Though the Rules-Based Transformation Engine Although every mainframe migration is unique,
(RBTE) is a proven technology, Astadia augments there are general source-to-target mappings for
our technology with years of hands-on migration application components that apply to most
experience and collaboration with partners. The projects, as shown in the following table.
combination of automation and human
Source Target
These mappings are only a guideline for the most common mainframe technologies. Other technologies are addressed on
an as-needed basis.
Database Migration
In parallel with code modification, data specialists address unique technical requirements or
will need to perform a thorough analysis of the preferences.
legacy databases and files, and develop a detailed
data migration strategy. After the target database and file structures have
been created and validated, static data can be
We recommend an iterative extract, transform and migrated to the AWS production environment. For
load (ETL) process to identify potential data-typing dynamic or other data that is created and/or
issues, develop fixes, and collaborate with the modified frequently, a data migration strategy
application subject matter experts to validate their must be implemented as part of production
efficacy. This iterative process continues until cutover process.
every issue is eliminated.
Like the application component mapping above,
In most cases, hierarchical and flat file data there are general source-to-target data mappings
structures will be replaced with RDBMS solutions, employed by most mainframe-to-AWS migrations:
but other solutions may be implemented to
Source Target
VSAM, other flat files ISAM, flat files, Aurora, SQL Server, DB2 LUW, Oracle, etc.
GDGs GDGs
These mappings are only a guideline for the most common mainframe database and file technologies. Other technologies
are addressed on an as-needed basis.
There may also be organizations who prefer to There’s good news here - it is possible to do a
move applications one at a time or in smaller phased rollout of migrated applications and still
groups as a way of gradually embracing AWS as a have ongoing communication and integration with
solution for their big-iron applications. applications residing on the IBM mainframe. This
kind of mixed environment can be achieved with
Still others may intend to keep their mainframes the proper planning, and will generally resemble
indefinitely for a subset of strategic, mission the image below.
critical applications while migrating less critical
IBM mainframe integration with applications & data already migrated to AWS
There are specific elements of AWS that are relevant to a mainframe modernization project. Below, we
address some of these – this is not the extent of all AWS services nor is it meant to exclude the use of
other AWS service offerings.
Let’s begin with the following description from AWS’ “Overview of Amazon Web Services,” April 2017:
The AWS Cloud provides a broad set of ability to operate production applications and
infrastructure services, such as computing databases that are more highly available, fault
power, storage options, networking and tolerant, and scalable than would be possible
databases that are delivered as a utility: on- from a single data center. The AWS Cloud
demand, available in seconds, with pay-as- operates 42 AZs within 16 geographic Regions
you-go pricing. From data warehousing to around the world, with five more Availability
deployment tools, directories to content Zones and two more Regions coming online in
delivery, over 90 AWS services are available. 2017.
The AWS Cloud infrastructure is built around In addition to discrete uninterruptable power
Regions and Availability Zones (AZs). A Region supply (UPS) and onsite backup generation
is a physical location in the world where we facilities, they are each fed via different grids
have multiple AZs. AZs consist of one or more from independent utilities to further reduce
discrete data centers, each with redundant single points of failure. AZs are all redundantly
power, networking, and connectivity, housed connected to multiple tier-1 transit providers.
in separate facilities. These AZs offer you the
In the following section, we’ll take a deeper look at the AWS portion of the Reference Architecture and
the components identified.
migrate your data to Aurora or any other RDBMS infrastructure security rather than application-
running in AWS. level security.
Hosting LDAP services on a smaller separate EC2 AWS CodeCommit is a fully-managed source
instance often makes it easier to maintain control service providing secure and private Git
independently of applications. However, a full repositories. It eliminates the need to operate your
analysis of your legacy security environment is own source control system or worry about scaling
required to determine how to best architect and its infrastructure.
configure security in the migrated system.
CodeCommit is where you’ll store your migrated
AWS Identity and Access Management (IAM) application source code and binaries, new source
enables you to create and manage AWS users and and binaries, an anything else you want to archive.
groups, and use permissions to allow and deny
their access to AWS resources. This is for AWS
Astadia’s methodology recognizes the organizational impact that any project of this nature will have on
day-to-day operations, as well as the financial and business implications for organizations in both the
short and long term. Return on Investment (ROI), and Total Cost of Ownership (TCO), are carefully
calculated during this process, and are closely managed throughout the project lifecycle.
Astadia’s Mainframe-to-AWS Success Methodology has been refined over the course of 200+ successful
legacy migration projects, and has become an industry leading approach for our medium and large-
scale mainframe clients.
Discover
code, data, software,
processes, requirements
Design
architecture, databases,
interfaces, customizations
Modernize
code, static data, application
components
Test Mainframe
functions, data, interfaces, Application
performance, load-balance Deployment
Implement
deploy, migrate dynamic data,
system cutover, monitor
Manage
manage AWS environment,
maintain & enhance apps
Discover Design
Catalog and analyze all applications, databases, Astadia’s project team analyzes source code, data
networks, platforms, and processes in the client’s structures, end-state requirements, and AWS
portfolio. Document the interrelationships cloud components to design and architect the
between applications, and all external integration solution. The design includes details such as types
points in the client’s configuration. This is a key and instances of AWS components, transaction
input to Application Portfolio Management and loads, batch requirements, programming
Application Rationalization. language conversions and replacements,
integration with external systems, 3rd-party
Test Manage
Since most mainframe-to-AWS projects are Astadia offers a full range of managed services
typically an as-is migration of applications, testing solutions. Having gained significant application
can focus primarily on two areas: the components knowledge from the architecting and
that have been changed or replaced, and implementing the AWS solution, Astadia is well
application performance. For the most part, suited to take on the burden of managing and
“parallel” testing is sufficient; that is, the results maintaining the migrated applications and their
of operations in the source environment must AWS environments, or the dual environment in the
produce the same values in the target case of a partial migration. This offers clients an
environment, except where differences are opportunity to focus their development efforts on
expected due to platform changes. For strategic initiatives as well as address concerns of
performance testing, the focus is on ensuring the finding programmers skilled in maintaining the
user experience is as good or better than the legacy components still in use.
legacy environment and batch processes complete
within acceptable timeframes.
Conclusion
Amazon Web Services and Astadia combine to create a perfect next generation platform for your
mainframe applications portfolio.
Once the mainframe application set has been fully deployed on AWS, you will have the freedom to re-
engineer traditional applications in to a more contemporary computing style, modernize legacy
interfaces and integrate with other applications. In addition, many new services, like mobile and
wireless, can be easily connected to the cloud platform, thus enhancing the overall power of your new
cloud computing environment. Your investment will serve to support all the needs of your enterprise
and the future requirements of your business.
You don’t have to tackle this alone. Astadia has the experience, skilled experts and the technology to
successfully help you complete Legacy Migration projects of all scopes and sizes.
Astadia would be happy to hear from you about your specific Legacy Migration needs and how we may
be of service to you as you prepare to leverage AWS.