Using the Java Application Modernization Playbook

Java application modernization is one-size-fits-none. Every customer has their own unique applications, with specific business value for their organization. The tools they use, the teams and skillsets they have, the way they work, and the capabilities they need are all different. Their overall goal, however, is always the same: provide the best service they can for their customers.

The Java Application Modernization Playbook lays out all the options at every stage in the modernization journey so that you can build the path that best suits you for where you are now and where you need to go.

Choosing your path

The Java Application Modernization Playbook is presented as a tree where you can select the options that suits your apps the best.

After every selection, you are presented with a new set of options to choose from. For example, collecting data from JBoss has different options than if you are collecting data from WebSphere Traditional. This approach lets you see at every stage what you can do, so you can select the right option.

Each step in the path is then supported by a combination of documents, videos, or both. The playbook uses IBM Transformation Advisor for many of the steps, as it can collect data from your runtime, provide detailed analysis of your applications, and create new artifacts to assist with modernization.

The playbook is not only a set of instructions, it is also a view on how to solve the challenges you face during your application modernization journey. Think of it as a reference guide to how other people have solved these challenges, from data collection and analysis all the way through to deployment and configuration of real-world scenarios such as clusters, Day 2 monitoring, and integration.

Watch the following video for a tour of how the Java Application Modernization Playbook works.

Video will open in new tab or window

Proving the value of modernization

The playbook is not just about how to do things, but also why they are worth doing in the first place. A key part of any modernization journey is proving the value, showing that there is return-on-investment. The near-final node, “validate modernization effort,” (Blog | Video) gives you the hard numbers and the testimonials shows you how other people have modernized with great success.

Modernizing and deploying your applications

On your modernization journey you will be faced with choices when it comes to updating your Java version, choosing the right runtime target, and building the infrastructure to rapidly deploy and update your modernized applications. The playbook covers these options and suggests ways of working. It can’t possibly cover every scenario and we don’t try to. The point of the playbook is to show how it can be done, so that you will have the knowledge to build the solution that is right for you.

Sharing your path

Once you have chosen your current path (current because it will almost certainly change as you modernize) you can reduce the view down to only the options you have selected.

With every interaction the URL for the playbook updates. So you can simply copy the URL and save it for later use, or share it to get feedback and collaborate with your colleagues.

Giving back

The modernization playbook is an entirely open source project and takes contributions. If you find a different (or better) way of doing something, let us know! If you have a scenario that is not covered, just submit a PR. The playbook is a living changing project that updates as the modernization landscape changes.

Summary and next steps

The Java Application Modernization Playbook is a great new tool to help you in your application modernization journey.

Learn how you can use IBM Cloud Transformation Advisor to modernize a traditional WebSphere app, and try Transformation Advisor for free.

Explore more application modernization tools in the articles and tutorials on IBM Developer.