Migrating from one software solution to another is a reality that all good software developers need to plan for. Having a plan helps to drive innovation at a continuous pace, whether you are developing software for in-house use or you are acquiring software from a vendor. In either case, never anticipating or planning for migration endangers the entire innovation value proposition. And in today’s ever-changing world of software, everyone who wants to benefit from the success of the cloud has to ensure that cloud innovation is continuous. Therefore, maintaining a stack that is changing along with technological advancements is a necessity.
In this article, we will take a look at the impact of moving to OpenJDK and the results will aid in drawing further conclusions and in planning. It’s quite common to be using a proprietary version of JDK, and this article addresses how to use Red Hat Application Migration Toolkit to analyze your codebase to understand the impact of migrating to OpenJDK.
Continue reading “Using Red Hat Application Migration Toolkit to see the impact of migrating to OpenJDK”
For many software modernization projects, it’s all about learning to love, lift, and shift. No, wait. It’s all about learning to love lift and shift. The basic idea behind lift and shift is to modernize how an existing application is packaged and deployed. Because it’s not about rewriting the application itself, lift and shift is typically quick to implement.
Modern development environments rely on containers for packaging and deployment. A modern environment also uses a continuous integration / continuous deployment (CI/CD) system that automatically builds, tests, and deploys an application whenever its source code changes.
Continue reading “Modernize your application deployment with Lift and Shift”
[In case you aren’t following the Red Hat JBoss Middleware blog, we are reposting this article on developers.redhat.com.]
Red Hat Application Migration Toolkit (RHAMT) 4.1.0 has been released, and with it a new feature that I’d like to highlight in this article—Technology Reports.
If you’re not familiar with RHAMT, check out my previous article that introduces RHAMT and describes how you can use it to help with migration existing applications to a modern application platform by analyzing your code base.
This new feature in RHAMT provides an aggregate listing of the technologies used, grouped by function, for the analyzed applications. It shows how the technologies are distributed. After analysis has been performed, using this report hundreds of applications can be quickly compared. In addition, the size, number of libraries, and story point totals of each application are displayed, allowing you to quickly determine each application’s type from a single report, for example:
Continue reading “Announcing Red Hat Application Migration Toolkit 4.1.0: Now with technical reports”
[In case you aren’t following the Red Hat JBoss Middleware blog, we are reposting An Introduction to Red Hat Application Migration Toolkit on developers.redhat.com.]
Application migration and modernization can be a daunting task. Not only do you have to update legacy applications with newer libraries and APIs, but often you must also address new frameworks, infrastructures, and architectures all while simultaneously keeping resources dedicated to new features and versions.
Red Hat Application Migration Toolkit (RHAMT), formerly known as Windup, provides a set of utilities for easing this process. Applications can be analyzed through a command-line interface (CLI), through a web-based interface, or directly inside Eclipse, allowing immediate modification of the source code.
These utilities allow you to quickly gain insights into thousands of your applications simultaneously. They identify migration challenges and code or dependencies shared between applications, and they accelerate making the necessary code changes to have your applications run in the latest middleware platforms.
Continue reading “An Introduction to Red Hat Application Migration Toolkit”
Wanting to become familiar with nftables, I decided to jump in at the deep end and just use it on my local workstation. The goal was to replace the existing iptables setup, ideally without any drawbacks. The following essay will guide you through what I have done in order to achieve that.
Continue reading “Migrating my iptables setup to nftables”
This article describes how an administrator can migrate Red Hat Enterprise Linux 5 or Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 with the help of the Preupgrade Assistant. The Preupgrade Assistant is a tool which assesses your running system for anything that might adversely affect the success of your migration.
As Red Hat Enterprise Linux 5 will have only extended update support after March 2017, administrators will find a tool like that useful to help them migrate their systems to Red Hat Enterprise Linux 7. The migration from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 6 is not covered by the Preupgrade Assistant, nor is it planned.
Note: The Preupgrade Assistant can also be used for the in-place upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 but this is out of scope of this article. The in-place upgrade from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 7 is neither supported nor planned.
Continue reading “Migration of Red Hat Enterprise Linux 5 or 6 to Red Hat Enterprise Linux 7 with the Preupgrade Assistant”