Migration Toolkit for Applications: Use cases and migration paths
Developer-focused assessments of application portfolios
Other use cases
MTA is highly extensible, allowing developers to create their own set of rules and hints or adapt to their own needs. New transformation paths is one example. Many developers use MTA for non-migration use cases as part of their build process (via Maven plugin or Command Line Interface) in order to validate code on a regular basis against organizational standards or to ensure application portability.
Another common use case is the enforcement of certain libraries and frameworks (use a single logging framework instead of pick-your own). Developers also leverage MTA to avoid the usage of proprietary libraries.
The Rules development guide provides instructions about how to customize existing or create new rules and rule-sets.
Ready to migrate your Java apps to containers?
Most Java applications in production today are running on virtual machines (VMs), likely on an application platform that is not container friendly. So, how can you migrate them from the current platform to containers on Kubernetes?