Displaying items by tag: migration

Monday, 13 December 2021 15:42

An Eye-Opening Experience at AWS re:Invent 2021

Modernization’s hot.

If there’s a single takeaway from TSRI’s experience as a sponsor and exhibitor at AWS re:Invent 2021 in Las Vegas, it’s that enterprises and governments alike have their minds on software modernization. If they haven’t started the process of migrating their mainframes and legacy applications to modern architectures to the cloud, then they will be soon actively moving in that direction.

“Virtually every CIO who has a mainframe application is now looking to migrate,” said Scott Pickett, TSRI’s Vice President of Service Operations and Product Delivery, who attended the conference at the end of November.

“Mainframe modernization was the centerpiece of activity for the conference-goers we interfaced with at AWS re:Invent,” echoed Greg Tadlock, TSRI’s Vice President of Sales. While modernization comes in many different flavors—mainframes can be transformed in multiple ways (replatforming, redevelopment, or refactoring, for example.), software modernization is a niche inside the modernization industry. It’s a niche that TSRI has embraced for over two decades and doubled down on earlier this year through validation and selection as a launch partner of the AWS Mainframe Modernization competency. Mainframe application modernization is clearly a movement that has entered the mainstream. “The validation that we made the right decision to be a launch partner with AWS on their Mainframe Modernization competency was confirmed at the re:Invent conference,” Tadlock said.

René Wagner, left, and Scott Pickett at the TSRI booth
René Wagner, left, and Scott Pickett at the TSRI booth

What TSRI Learned

As a company, TSRI has mainly focused on migrating legacy systems to modern languages and architectures, whether on-premises or on the cloud. One thing that surprised the on-site team at re:Invent were the questions about round-tripping. In essence, a round trip is a refactoring of applications originally written in software languages that most modernizations currently target, Java or C#. Both languages have been in use for two decades (or more) themselves, and the technology landscape has changed significantly during that time.

“They came to us specifically because they saw refactoring and the need to take their older Java or C# apps and get them refactored to targeted cloud services, microservices, and containers,” said Kory Caze, TSRI’s Lead Account Executive. It’s a service TSRI has begun to offer, and will certainly become a focus area in the coming year.

The refactoring or transformation of nearly any legacy language to modern languages is certainly one the core values TSRI offers to the modernization market. The capability to modernize more than standard IBM COBOL applications can be useful for, say, an airline that needs to modernize their FORTRAN applications—an opportunity that actually presented itself at the conference this year.

“There are so many software languages and technologies out there, that you can't have a one-size-fits-all solution for,” Kory said. In fact, TSRI’s Director of Business Development, René Wagner, had three different inquiries about doing a transformation from MUMPS, a relatively obscure mainframe language originally developed for healthcare operations—all within 10 minutes of each other! “It's like the most random language,” said René.

 

The Necessity of AWS Cloud Migration

Knowing that several companies have joined AWS’s Mainframe Modernization competency is reassuring to smaller companies like TSRI. They have a significant role to play in bringing major corporations and public sector agencies to the cloud quickly and efficiently, according to René.

“If you went over to the modernization area [at re:Invent] and you asked Amazon, ‘Who do you use to transform your systems to modernize the mainframe?’” René said, “their answer was, ‘Oh, we have an ecosystem of partners that we utilize to get this work done.’”

Everyone on the TSRI team saw live, in action, that modernization will be important over the next few years. Migration to the cloud, they all said, is not a matter of if, but when.

“That was kind of the feeling that I got,” René said. “Modernization is happening, and these people have bled enough on what they currently have.”

 

TSRI's re:Invent booth, including a few collectibles.
TSRI's re:Invent booth, including a few collectibles.

The Future of Cloud

While TSRI has begun to focus more of its efforts on cloud migrations, with AWS as a leading platform, the re:Invent conference opened the company’s eyes to plenty of opportunities that the company’s leadership might not have considered even a year or two ago. Being on the floor as a first-time sponsor and having the ability to demonstrate what the company can do, through Application Blueprint® demonstrations, or walking booth visitors through case studies, has opened a lot of doors for the TSRI team.

“The AWS mainframe migration announcement validates the tools, capabilities, and shift that TSRI has undergone, as well as in the industry,” said Scott Pickett, TSRI’s Vice President of Service Operations and Product Delivery.

Next year should be even more interesting.

If you were unable attend AWS re:Invent 2021, you can still access the materials TSRI shared that show what we can do to help your organization modernize to the AWS cloud. Download this information to get started!

TSRI COBOL to Java for AWS case study  

Case Study: Modernizing a Critical ILS-S U.S. Air Force System for AWS

   

TSRI’s approach to modernizing mainframe technology for AWS

 

Checklist: Preparing for Cloud Modernization

 

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies

Learn About Our Technology

Get Started on your Modernization Journey Today!

 
 
Published in AWS

PL/1 - Life in COBOL's Shadow

When IBM developed the framework for its PL/1 computing language in the 1960s, the committee of business and scientific programmers that developed the parameters for the language could not have foreseen today’s modern technologies of a phone in every pocket and digital access to anyone on the planet via the internet. They also may have hoped for, but likely did not foresee, how a mainframe language and architecture that survived 60 years would still be in use today.

Though PL/1 never reached the level of popularity of its COBOL competitor, it was still used on multiple government, corporate and defense mainframe systems throughout the years. It is, by many accounts, a very stable and reliable language—it even had more features in some areas than COBOL! However, programmers and organizations had little business or technical incentive to adopt the language. Today, having lived for so long in the shadow of COBOL and Fortran, finding programmers with PL/1 experience has become harder each year making it increasingly difficult to maintain any remaining mainframe applications. Those challenges have made PL/1 a desirable candidate to transform into a modern language like C++, C#, or Java.

 

Modernizing PL/1 - Success is in the Details

When it comes to automated modernization and refactoring, a successful outcome lies in the details. For example, TSRI engineers spend a lot of time prior to transforming any code understanding how a step-wise process could allow a critical system to operate continuously without any disruption or data loss. Going step-wise means that some components of the system such as the login function or other application program interfaces can be modernized, tested, and, if necessary, reverted to the original application without any impact on the rest of the application or the end user. Because an automated modernization creates a like-for-like replica of the functionality in the target language—in this case C# in a Windows environment—the successful migration of each step means that subsequent transformations will be easier because the automated transformation engine continues to learn and adjust.

Following the transformation of PL/1 to the modern computing environment, an automated, iterative refactoring process can find redundant, dead, or unused code and remediate while making the entire codebase more efficient. PL/1 was designed to facilitate programming using human-readable logic so automated refactoring can also reduce code overhead significantly. Furthermore, the transformation from the monolithic environment of early mainframe languages to a multi-tier environment separates the programming from the data and the user interface enabling further functional development while preventing system disruption.

PL/1 is not unique in how the architectures that run this legacy language can be modernized but given the age of the language and lack of business or programmer support, undergoing an automated modernization may be the best way to transform PL/1 applications to modern languages and architectures.

-----

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies

Learn About Our Technology

Get started on your modernization journey today!

 

Published in Languages
Monday, 13 September 2021 14:14

Video: Modernizing Using Layered Architectures

One huge benefit to an automated modernization is the migration from a monolithic architecture to a multi-tier architecture. The multi-tier, or layered, architecture separates the data layer from the logic layer, and also makes the presentation layer—what the end user sees and interacts with—independent of the other two. In this video segment, Scott Pickett discusses how this modern-day style of architecture allows developers to extend the functionality of an application without affecting the data or behavior of an application. Even more important, however, he explains how a modernized application can continue to refer back to legacy databases when organizations migrate to their target environment in smaller steps rather than committing all at once.

Be sure to view our other videos in this series:

Videos 1 & 2: “Setting Project Scope” and “Setting Up Development Sandboxes”

Video 3: Selecting Cloud Vendors and Your Target Language

Video 4: Using Automation to Quickly and Accurately Move to a Multi-Tier Environment

----

{fastsocialshare}

TSRI is Here for You As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies

Learn About Our Technology

Get started on your modernization journey today!

Published in Cloud

As Scott notes in this video, the latest in our Modernizing for the Future series for undertaking a cloud modernization, “One of the benefits associated with using an automated technology is that none of it is done by hand.” In this video Scott introduces the idea of automation when it comes to modernization and how taking this avenue will preserve the functionality and logic of the legacy applications. The benefit is that the application will operate exactly the same way it did previously, but with capabilities to expand into a more tiered approach so the application can take advantage of the best the cloud has to offer.

 

Originally aired live on May 18, 2021.

Additionally, having the automated transformation preserve the functionality means once organizations are ready to put the cloud applications into production, the data layer remains consistent so this can be done gradually with very little downtime in the production environments. That minimal business disruption greatly reduces the risk of data loss and technical failures. And from there, automated and semi-automated refactoring can begin to improve the quality and functionality of the application—all in a cloud environment.

 

Be sure to view our other videos in this series:
Videos 1 & 2: “Setting Project Scope” and “Setting Up Development Sandboxes”
Video 3: Selecting Cloud Vendors and Your Target Language

 

As always, TSRI can help answer any questions you may have about modernization, automation, and making sure your systems are ready to deploy in modern computing environments. 

--- 

TSRI is Here for You 

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years. 

See Case Studies 

Learn About Our Technology 

Get Started on Your Modernization Journey Today! 

Published in Cloud

Using automation to modernize mainframe applications will bring a codebase to today’s common coding standards and architectures. But in many cases, modernization to an application’s functional equivalent isn’t always enough. Organizations can do more to make their modern code more efficient and readable. By building refactoring phases into their modernization projects, organizations can eliminate the Pandora’s box of dead or non-functional code that many developers don’t want to open, especially if it contains elements that just don’t work.

Using TSRI’s automated refactoring engine, remediation was complete in an hour.

What is Refactoring and How is it Used?

Refactoring, by definition, is an iterative process that automatically identifies and remediates pattern-based issues throughout a modernized application’s codebase. For example, unreferenced variables or unnecessary redundant snippets could exist throughout the application. This scan, known as dead/redundant code refactoring, will find repetitions of any of this unusable code to flag, then remove it from the codebase. One of TSRI’s current projects found 25,000 instances of a similar issue that would have required 15 minutes of manual remediation per instance—not including the inevitable introduction of human error that would require further remediation. The number of development hours would take more than a year for a single developer to complete.

Using TSRI’s automated refactoring engine, however, remediation was complete in an hour.

Calling refactoring its own post-modernization phase is, in some ways, misleading. Refactoring typically occurs all the way through an automated mainframe transformation. As an example, in a typical COBOL or PL/1 mainframe modernization, TSRI would refactor the code from a monolithic application to a multi-tier application, with Java or C# handling back-end logic, a relational database layer through a Database Access Object (DAO) layer, and the user interface (screens) modernized in a web-based format. Believe it or not, many legacy applications still run on 3270 green-screens or other terminals, like in the graphic below.

Once the automated modernization of the legacy application is complete, the application has become a functionally equivalent, like-for-like system. However, any deprecated code, functions that may have never worked as planned, or routines that were written but never implemented will still exist. A process written in perhaps 1981—or even 1961—may have taken far more code to execute than a simple microservice could handle today.

Situations like this are where refactoring becomes indispensable.

 

Where to begin?

Before a formal refactoring process can begin, it’s important to understand your goals and objectives, such as performance, quality, cybersecurity, and maintainability. This will typically mean multiple workshops to define which areas of the modernized codebase need attention and the best candidates for refactoring, based upon the defined goals. These refactorings will either be semi-automated (fully automated with some human input) or custom written (based upon feedback from code scanners or subject-matter experts.)

The refactoring workshops can reveal many different candidates for refactoring:

  • Maintainability: By removing or remediating bugs, dead or orphaned code, or any other anomalies the codebase can be reduced by as much as one third while pointing developers in the direction of any bugs in need of remediation.
  •  
  • Readability: Renaming obscure functions or variables for a modern developer to fit within naming conventions that are both understandable and within the context of the code’s functionality.
  •  
  • Security: Third-party tools such as Fortify and CAST can be utilized to find vulnerabilities, but once found they need to be remediated through creation of refactoring rules.
  •  
  • Performance: Adding reusable microservices or RESTful endpoints to connect to other applications in the cloud can greatly improve the efficiency of the application, as can functionality that enables multiple services to run in parallel rather than sequentially.

 

What are the Challenges?

  • Challenge 1: One reason refactoring must be an iterative process is that some functionality can change with each pass. Occasionally, those changes will introduce bugs to the application. However, each automated iteration will go though regression testing, then refactored again to remediate those bugs prior to the application returning to a production environment.
  •  
  • Challenge 2: The legacy architecture itself may pose challenges. On a mainframe, if a COBOL application needs to access data, it will call on the entire database and cycle through until it finds the records it needs. Within a mainframe architecture this can be done quickly. But if a cloud-based application needs to call a single data record out of millions or billions from halfway across the world (on cloud servers), the round trip of checking each record becomes far less efficient—and, in turn, slower. By refactoring the database, the calls can go directly to the relevant records and ignore everything else that exists in the database.
  •  
  • Challenge 3: Not every modernization and refactoring exercise meets an organization’s quality requirements. For example, the codebase for a platform that runs military defense systems is not just complex, it’s mission critical. Armed forces will set a minimum quality standard that any transformation must meet. Oftentimes these standards can only be achieved through refactoring. A third-party tool like SonarQube in conjunction with an automated toolset like TSRI’s JANUS Studio® can be utilized to discover and point to solutions for refactoring to reach and exceed the required quality gate.
  •  

In conclusion, while an automated modernization will quickly and accurately transform legacy mainframe applications to a modern, functionally equivalent, cloud-based or hybrid architecture, refactoring will make the application durable and reliable into the future.

--

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies
Learn About Our Technology
Get started on your modernization journey today!

Published in Education
Friday, 09 July 2021 10:42

Get Started with Your Modernization!

Highlights on “Setting Project Scope” and “Setting Up Development Sandboxes”

TSRI is thrilled to present highlights from Modernizing for the Future, our cloud webinar featuring Scott Pickett, our Vice President of Product Development and Service Delivery. In these first two segments, Scott helps your organization get the mainframe modernization process started.

The first segment, “Setting Project Scope,” helps your organization understand their existing baselines, setting realistic expectations and accomplishments for your migration, and planning your target environment.

In this second segment, “Setting Up Development Sandboxes,” Scott discusses your organization’s development sandbox and why setting up an experimental environment will be critical to the success of your automated modernization. Your sandbox will help validate your target environment as well as understand any complexities in languages, architectures, or databases.

 

Be sure to check out the remaining videos in this series as well:

 

As always, TSRI can help answer any questions you may have about automated modernization, and making sure your systems are ready to deploy in modern computing environments.

-------

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

Get started on your modernization journey today!

Published in Best Practices

capitol buildingModernization of High Value Assets (HVAs) and software systems is more urgent than ever. In the past year, tens of millions of U.S. citizens have leveraged critical online systems to manage their livelihood and health during the COVID-19 pandemic. With such a heavy reliance on these systems, now is the time for the federal government’s critically important HVAs systems to keep up with citizens’ growing needs.

 

The Technology Modernization Fund was established in 2017 to support government and civic agencies to bring their critical software infrastructure into the modern age. On May 12 of this year, President Biden issued a comprehensive executive order that gave direction to federal departments and agencies to strengthen the government’s cybersecurity posture. The order establishes a requirement to modernize systems and implement stronger cybersecurity standards by moving agencies and their contract partners to secure cloud services and a zero-trust architecture, which uses identity management protocols to verify that every user of a system interacts with the appropriate levels of security access. This order also mandated deployment of multifactor authentication and encryption.

 

According to Federal Chief Information Security Officer Chris DeRusha, the White House is pushing federal agencies toward a “zero-trust paradigm.” With the pressure on, many agencies are struggling with the magnitude of such an undertaking and are, justifiably, fearful of the perceived security and down-time risks associated with modernization.

 

Modernizing an HVA doesn’t have to be risky

 

Using a graceful, automated approach to leverage modernization solutions can result in a very low risk modernization. By implementing a step-by-step cloud migration while keeping legacy systems running in parallel, an automated modernization can happen quickly, safely, and reliably.

 

TSRI has over 25 years of experience undertaking migrations of this kind (see below).

 

  • TSRI’s Work is the “Playbook” for Future Government Modernization
    A large percentage of TSRI’s work over the past 25 years has been the modernization of critical government and military software applications. If fact, our recent work with HUD was called the “playbook” for future government modernization.

 

  • Modernize Quickly and Maintain Business-as-Usual in the Process
    Our technology enables HVAs to be modernized rapidly and without business disruption.

 

  • Cloud-Ready, Cloud-certified — AWS & Beyond
    As a certified AWS partner for mainframe modernization, TSRI helps organizations take advantage of the Technology Modernization Fund to transform and secure their applications for cloud deployment on AWS and other leading platforms.

 

 

Ready to modernize? Reach out to us to learn more and get started!

 

 

 

 

 

-----

 

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

 

See Case Studies

Learn About Our Technology

Get started on your modernization journey today!

 

Published in Government
Friday, 30 April 2021 10:44

Ada to C++ - Raytheon - TCS / MCS

Navy Multi-band Terminal (NMT) is a SATCOM terminal, which expands available bandwidth and provides support for ForceNet, the Navy's approach to network-centric operations.  TSRI transformed the legacy Ada code to C++, and refactored the modernized application.

  • Customer & Integrator: Raytheon & US Navy
  • Source & Target Language: Ada to C++
  • Lines of Code: 89,000
  • Duration:  5 months
  • Services: Automated Code Transformation, Transformation Blueprint, System Integration and Test Support, Automated Refactoring

 

Published in Case-Studies
Tuesday, 13 April 2021 12:36

Ada to C++ - US Navy - Modem Control Software

TSRI was engaged to modernize US Navy SATCOM Multi-band Terminal (NMT) Modem Control System (MCS) from Ada to C++. To provide SPAWAR with the best modernization approach, Raytheon selected TSRI to transform the existing MCS Ada code into C++ and to re-factor
the C++ toward the desired target architecture. TSRI's fixed-price "integrator ready" deliverable was selected by Raytheon for its low technical risk,
shortened schedule, and low cost.

  • Customer & Integrator: US Navy & Raytheon
  • Source & Target Language: Ada to C++
  • Lines of Code: 190,000
  • Duration:  5 months
  • Services: Automated Code Transformation, Application Blueprint®, Transformation Blueprint®, Engineering Support, Automated Refactoring

Published in Case-Studies

AWS Mainframe Migration Competency

When companies and governments need to migrate their mission-critical applications to the cloud, they will need a partner to make that transformation as smooth and efficient as possible. And when it comes to modernization, a highly automated process will get them cloud-ready quickly and accurately. TSRI is here to help organizations begin their modernization journey, and we are honored to be named as a Validated Partner in Amazon Web Services’ new Mainframe Migration Competency!

The AWS Competency Program is designed to identify, validate, and promote AWS Partners with demonstrated technical expertise and proven customer success.
The Competency designation helps AWS Partners differentiate their business to customers by showcasing their products and services in specialized areas across industries, use cases, and workloads. AWS Partners are vetted, validated, and verified against a high bar to achieve the AWS Competency designation.

TSRI joins an elite group of integrators and technical specialists in this competency. With more than 25 years of experience and leadership in modernization across multiple platforms and languages, we are perfectly positioned to help organizations with legacy architectures migrate to the cutting edge.

read the announcement

-----

TSRI is Here for You

As a leading provider of software modernization services, TSRI enables technology readiness for the cloud and other modern architecture environments. We bring software applications into the future quickly, accurately, and efficiently with low risk and minimal business disruption, accomplishing in months what would otherwise take years.

See Case Studies

Learn About Our Technology

Get started on your modernization journey today!

 

Published in AWS
Page 5 of 8