Azure Migrate application and code assessment for Java
This guide describes how to use the Azure Migrate application and code assessment tool for Java to assess and replatform any type of Java application. The tool enables you to evaluate application readiness for replatforming and migration to Azure.
appcat is a command-line tool from Azure Migrate to assess Java application binaries and source code to identify replatforming and migration opportunities for Azure. It helps you modernize and replatform large-scale Java applications by identifying common use cases and code patterns and proposing recommended changes.
appcat discovers application technology usage through static code analysis, supports effort estimation, and accelerates code replatforming, helping you move Java applications to Azure. With a set of engines and rules, it can discover and assess different technologies such as Java 11, Java 17, Jakarta EE 10, Quarkus, Spring, and so on. It then helps you replatform the Java application to different Azure targets (Azure App Service, Azure Kubernetes Service, Azure Container Apps, and Azure Spring Apps) with specific Azure replatforming rules.
When should I use Azure Migrate application and code assessment?
appcat is designed to help organizations modernize their Java applications in a way that reduces costs and enables faster innovation. The tool uses advanced analysis techniques to understand the structure and dependencies of any Java application, and provides guidance on how to refactor and migrate the applications to Azure.
appcat, you can do the following tasks:
- Discover technology usage: Quickly see which technologies an application uses. Discovery is useful if you have legacy applications with not much documentation and want to know which technologies they use.
- Assess the code to a specific target: Assess an application for a specific Azure target. Check the effort and the modifications you have to do in order to replatform your applications to Azure.
Supported Azure targets
The tool contains rules for helping you replatform your applications so you can deploy to and use the following Azure services.
You can use the following services as deployment targets:
- Azure App Service
- Azure Spring Apps
- Azure Kubernetes Service
- Azure Container Apps
You can use the following services as resource services:
- Azure Databases
- Azure Service Bus
- Azure Storage
- Azure CDN
- Azure Event Hubs
- Azure Key Vault
Use Azure Migrate application and code assessment for Java
appcat, you must download the ZIP file described in the next section, and have a compatible JDK 11+ installation on your computer.
appcat runs on Windows, Linux, or Mac, both for Intel, Arm, and Apple Silicon hardware. You can use the Microsoft Build of OpenJDK to run
appcat CLI is available for download as a ZIP file from aka.ms/appcat/azure-appcat-cli-latest.zip.
Unzip the zip file in a folder of your choice. You then get the following directory structure:
appcat-cli-<version> # APPCAT_HOME
│ ├── appcat
│ └── appcat.bat
│ └── appcat-guide.html
- docs: This directory contains the documentation of
- bin: This directory contains the
appcatCLI executables (for Windows/Linux/Mac).
- samples: This directory contains a sample application and several scripts to run
appcatagainst the sample application.
To run the tool, open a terminal session and type the following command from the $APPCAT_HOME/bin directory:
To run the tool from anywhere in your computer, configure the directory $APPCAT_HOME/bin into your
PATH environment variable and then restart your terminal session.
The following guides provide the main documentation for
appcat for Java:
Discover technology usage without an Azure target in mind
Discovery of technologies is the first stage of application replatform and modernization. During the discovery phase,
appcat scans the application and its components to gain a comprehensive understanding of its structure, architecture, and dependencies. This information is used to create a detailed inventory of the application and its components (see the Discovery report section), which serves as the basis for further analysis and planning.
Use the following command to initiate discovery:
--input ./<my-application-source-path or my-application-jar-war-ear-file> \
The discovery phase is useful when you don't have a specific Azure target in mind. Otherwise,
appcat runs discovery implicitly for any Azure target.
Assess a Java application for a specific Azure target
The assessment phase is where
appcat analyzes the application and its components to determine its suitability for replatorming and to identify any potential challenges or limitations. This phase involves analyzing the application code and checking its compliance with the selected Azure target.
To check the available Azure targets, run the following command:
This command produces output similar to the following example:
Available target technologies:
Then, you can run
appcat using one of the available Azure targets, as shown in the following example:
--input ./<my-application-source-path or my-application-jar-war-ear-file> \
Get results from appcat
The outcome of the discovery and assessment phases is a detailed report that provides a roadmap for the replatforming and modernization of the Java application, including recommendations for the Azure service and replatform approach. The report serves as the foundation for the next stages of the replatforming process. It helps organizations learn about the effort required for such transformation, and make decisions about how to modernize their applications for maximum benefits.
The report generated by
appcat provides a comprehensive overview of the application and its components. You can use this report to gain insights into the structure and dependencies of the application, and to determine its suitability for replatform and modernization.
The following sections provide more information about the report.
Summary of the analysis
The landing page of the report lists all the technologies that are used in the application. The dashboard provides a summary of the analysis, including the number of transformation incidents, the incidents categories, or the story points.
When you zoom in on the Incidents by Category pie chart, you can see the number of incidents by category: Mandatory, Optional, Potential, and Information.
The dashboard also shows the story points. The story points are an abstract metric commonly used in Agile software development to estimate the level of effort needed to implement a feature or change.
appcat uses story points to express the level of effort needed to migrate a particular application. Story points don't necessarily translate to work hours, but the value should be consistent across tasks.
The discovery report is a report generated during the Discovery Phase. It shows the list of technologies used by the application in the Information category. This report is just informing you about the technology that
The assessment report gives an overview of the transformation issues that would need to be solved to migrate the application to Azure.
These Issues, also called Incidents, have a severity (Mandatory, Optional, Potential, or Information), a level of effort, and a number indicating the story points. The story points are determined by calculating the number of incidents times the effort required to address the issue.
Detailed information for a specific issue
For each incident, you can get more information (the issue detail, the content of the rule, and so on) just by selecting it. You also get the list of all the files affected by this incident.
Then, for each file or class affected by the incident, you can jump into the source code to highlight the line of code that created the issue.
You can think of
appcat as a rule engine. It uses rules to extract files from Java archives, decompiles Java classes, scans and classifies file types, analyzes these files, and builds the reports. In
appcat, the rules are defined in the form of a ruleset. A ruleset is a collection of individual rules that define specific issues or patterns that
appcat can detect during the analysis.
These rules are defined in XML and use the following rule pattern:
appcat provides a comprehensive set of standard migration rules. Because applications might contain custom libraries or components,
appcat enables you to write your own rules to identify the use of components or software that the existing ruleset might cover.
To write a custom rule, you use a rich domain specific language (DLS) expressed in XML. For example, let's say you want a rule that identifies the use of the PostgreSQL JDBC driver in a Java application and suggests the use of the Azure PostgreSQL Flexible Server instead. You need a rule to find the PostgreSQL JDBC driver defined in a Maven pom.xml file or a Gradle file, such as the dependency shown in the following example:
To detect the use of this dependency, the rule uses the following XML tags:
ruleset: The unique identifier of the ruleset. A ruleset is a collection of rules that are related to a specific technology.
targetTechnology: The technology that the rule targets. In this case, the rule is targeting Azure App Services, Azure Kubernetes Service (AKS), Azure Spring Apps, and Azure Container Apps.
rule: The root element of a single rule.
when: The condition that must be met for the rule to be triggered.
perform: The action to be performed when the rule is triggered.
hint: The message to be displayed in the report, its category (Information, Optional, or Mandatory) and the effort needed to fix the problem, ranging from 1 (easy) to 13 (difficult).
The following XML shows the custom rule definition:
<description>Recommend Azure PostgreSQL Flexible Server.</description>
<artifact groupId="org.postgresql" artifactId="postgresql"/>
<hint title="Azure PostgreSQL Flexible Server" category-id="mandatory" effort="7">
<message>The application uses PostgreSQL. It is recommended to use Azure PostgreSQL Flexible Server instead.</message>
<link title="Azure PostgreSQL Flexible Server documentation" href="https://learn.microsoft.com/azure/postgresql/flexible-server/overview"/>
After executing this rule through
appcat, rerun the analysis to review the generated report. As with other incidents, the assessment report lists the identified issues and affected files related to this rule.
The complete guide for Rules Development is available at azure.github.io/appcat-docs/rules-development-guide.
Azure Migrate application and code assessment for Java is a free, open source tool at no cost, and licensed under the same license as the upstream WindUp project.
Frequently asked questions
Q: Where can I download the latest version of Azure Migrate application and code assessment for Java?
You can download
appcat from aka.ms/appcat/azure-appcat-cli-latest.zip.
Q: Where can I find more information about Azure Migrate application and code assessment for Java?
When you download
appcat, you get a docs directory with all the information you need to get started.
Q: Where can I find the specific Azure rules?
All the Azure rules are available in the appcat Rulesets GitHub repository.
Q: Where can I find more information about creating custom rules?
See the Rules Development Guide for Azure Migrate application and code assessment for Java.
Q: Where can I get some help when creating custom rules?
The best way to get help is to create an issue on the appcat-rulesets GitHub repository.