You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/migrate/appcat/java.md
+16-9Lines changed: 16 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ The tool discovers application technology usage through static code analysis, pr
18
18
19
19
This tool is open source and is based on [WindUp](https://github.com/windup), a project created by Red Hat and published under the [Eclipse Public License](https://github.com/windup/windup/blob/master/LICENSE).
20
20
21
-
## When should I use Azure Migrate application and code assessment?
21
+
## Overview
22
22
23
23
The tool 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.
24
24
@@ -56,12 +56,10 @@ When the tool assesses for Cloud Readiness and related Azure services, it can al
56
56
* Azure Key Vault
57
57
* Azure Front Door
58
58
59
-
## How to use Azure Migrate application and code assessment for Java
59
+
## Download
60
60
61
61
To use the `appcat` CLI, you must download the ZIP file described in the next section, and have a compatible JDK 11 or JDK 17 installation on your computer. The `appcat` CLI runs on any Java-compatible environment such as Windows, Linux, or Mac, both for Intel, Arm, and Apple Silicon hardware. We recommend you use the [Microsoft Build of OpenJDK](/java/openjdk).
62
62
63
-
### Download
64
-
65
63
> [!div class="nextstepaction"]
66
64
> [Download Azure Migrate application and code assessment for Java 6.3.0.9](https://aka.ms/appcat/azure-migrate-appcat-for-java-cli-6.3.0.9-preview.zip). Updated on 2024-08-06.
67
65
@@ -80,9 +78,18 @@ The following previous releases are also available for download:
80
78
-[Azure Migrate application and code assessment for Java 6.3.0.8](https://aka.ms/appcat/azure-migrate-appcat-for-java-cli-6.3.0.8-preview.zip). Released on March, 2024.
81
79
-[Azure Migrate application and code assessment for Java 6.3.0.7](https://aka.ms/appcat/azure-migrate-appcat-for-java-cli-6.3.0.7-preview.zip). Released on November, 2023.
82
80
83
-
### Get started with appcat
81
+
## Get started
82
+
83
+
To run `appcat`, make sure you have a supported JDK installed. The tool supports the following JDKs:
84
+
85
+
* Microsoft Build of OpenJDK 11
86
+
* Microsoft Build of OpenJDK 17
87
+
* Eclipse Temurin™ JDK 11
88
+
* Eclipse Temurin™ JDK 17
89
+
90
+
After you have a valid JDK installed, make sure its installation directory is properly configured in the `JAVA_HOME` environment variable.
84
91
85
-
Unzip the zip file in a folder of your choice. You then get the following directory structure:
92
+
To continue, download and unzip the package in a folder of your choice. You then get the following directory structure:
86
93
87
94
```
88
95
appcat-cli-<version> # APPCAT_HOME
@@ -122,7 +129,7 @@ The following guides provide the main documentation for `appcat` for Java:
*[Rules Development Guide](https://azure.github.io/appcat-docs/rules-development-guide/)
124
131
125
-
## Discover technology usage and Cloud readiness without an Azure service in mind
132
+
###Discover technology usage and Cloud readiness without an Azure service in mind
126
133
127
134
Discovery of technologies and Cloud readiness targets provide great insight into application replatform and modernization to the Cloud. The tool scans the application and its components to gain a comprehensive understanding of its structure, architecture, and dependencies. It also finds potential issues that might be challenging in a Cloud environment. The `discovery` target in particular is used to create a detailed inventory of the application and its components. This inventory serves as the basis for further analysis and planning. For more information, see the [Discovery report](#discovery-report) section.
128
135
@@ -138,7 +145,7 @@ This type of report is useful when you don't have a specific Azure service in mi
138
145
139
146
The tool always performs the `discovery` whether or not you include that value in the `--target` parameter.
140
147
141
-
## Assess a Java application
148
+
###Assess a Java application
142
149
143
150
The *assessment* phase is where the `appcat` CLI 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 targets.
144
151
@@ -319,7 +326,7 @@ The complete guide for Rules Development is available at [azure.github.io/appcat
319
326
320
327
### 6.3.0.9
321
328
322
-
This release contains the following fixes to the known issues previously on 6.3.0.8, and includes a set of new rules. For more information, see below.
329
+
This release contains the following fixes and includes a set of new rules. For more information, see below.
323
330
324
331
- Resolved an issue with the `localhost-java-00001` rule.
325
332
- Introduced new rules for identifying technologies such as AWS S3, AWS SQS, Alibaba Cloud OSS, Alibaba Cloud SMS, Alibaba Scheduler X, Alibaba Cloud Seata, and Alibaba Rocket MQ.
0 commit comments