In our last blog post, we talked about how the IBM CIO organization approached the modernization of its legacy applications to hybrid cloud and microservices, incrementally unlocking the value from this transformation. In this post, we will focus on modernization tools for Enterprise Java applications and how the tools simplified and accelerated our process.
Since the early 2000s, IBM CIO teams have been using Java™ EE technologies, whether its frameworks like JSF, EJBs or Service Oriented Architectures (SOA) or Aspect-oriented programming frameworks like Spring Boot. Most of these applications were developed when cloud, containers and Kubernetes did not exist, but these applications are still supporting business-critical functions.
Our three-fold modernization objectives are as follows:
When you have hundreds of applications to modernize, it takes a long time to refactor, rewrite and decouple services. So, initially, our focus was runtime and operational modernization to take advantage of all of the native capabilities of our CIO hybrid cloud platform.
The first step for successful modernization is to assess and analyze the application, explore the integrations, identify dependencies and create a pragmatic plan to have minimal disruption for the applications. We quickly realized that we needed an automated tool to discover the dependencies, perform application inventory (Software Bill of Materials) and, most importantly, determine what code/configurations need to be changed for the modernization. That’s where IBM Cloud Transformation Advisor (TA) came to our rescue.
IBM Cloud Transformation Advisor (TA) is a discovery tool that simplifies the containerization of Java applications from traditional app servers like WebSphere, WebLogic or Tomcat to WebSphere/Open Liberty. You can sign up for a trial of TA and find installation instructions here.
Transformation Advisor (TA) uses its Data Collector—a tool that gathers information about middleware deployments in your environment—to provide you with a migration analysis of Java™ EE applications running on IBM WebSphere Application Server, Apache Tomcat or Oracle WebLogic application servers. The tool generates one .zip folder per profile/domain and places analysis results within that directory. Results from the scan are uploaded to Transformation Advisor, where a detailed analysis is provided.
Alternatively, you can easily use the wsadmin tool’s migration commands to generate the reports. See the documentation for more information.
Our approach was as follows:
We were able to instrument 174 WebSphere instances over one weekend. Transformation Advisor helped our containerization journey at these critical stages:
In the next blog post, we will talk about architectural modernization of Java™ EE applications using IBM Mono2Micro—transforming monolithic applications to microservice-based architecture.
IBM web domains
ibm.com, ibm.org, ibm-zcouncil.com, insights-on-business.com, jazz.net, mobilebusinessinsights.com, promontory.com, proveit.com, ptech.org, s81c.com, securityintelligence.com, skillsbuild.org, softlayer.com, storagecommunity.org, think-exchange.com, thoughtsoncloud.com, alphaevents.webcasts.com, ibm-cloud.github.io, ibmbigdatahub.com, bluemix.net, mybluemix.net, ibm.net, ibmcloud.com, galasa.dev, blueworkslive.com, swiss-quantum.ch, blueworkslive.com, cloudant.com, ibm.ie, ibm.fr, ibm.com.br, ibm.co, ibm.ca, community.watsonanalytics.com, datapower.com, skills.yourlearning.ibm.com, bluewolf.com, carbondesignsystem.com