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
-[Download](/java/openjdk/download#openjdk-17) and [install Microsoft Build of OpenJDK 17](/java/openjdk/install). Ensure that the **JAVA_HOME** environment variable is set.
100
100
-[Download Apache Maven](https://maven.apache.org/download.cgi) and [install locally](https://maven.apache.org/install.html). Ensure that the Maven binary (`mvn`) is reachable through `PATH` environment variable.
101
-
-[Download and install Python 3](https://www.python.org/downloads/).
102
101
103
102
### Installation
104
103
@@ -123,19 +122,7 @@ Extract the binary from the downloaded file. You should see the following folder
123
122
124
123
### Running the tool
125
124
126
-
#### Option 1: Run appcat from the downloaded folder
127
-
128
-
Change the directory to the extracted folder:
129
-
130
-
```bash
131
-
cd /azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/
132
-
./appcat --help
133
-
```
134
-
135
-
> [!NOTE]
136
-
> The `appcat` binary first looks for its dependencies in the current directory, where it's running from, and falls back to the following scenario if they aren't found.
137
-
138
-
#### Option 2: Add the appcat binary path to your $PATH
125
+
#### Option 1: Add the appcat binary path to your $PATH
139
126
140
127
Move the contents of the folder to the **.appcat** folder in the user's home directory - **$HOME/.appcat** on Linux/Mac and **%USERPROFILE%/.appcat** on Windows.
> In this context, when the `appcat` binary is called from a different folder than where it's installed, it looks for its dependencies in the **.appcat** folder in the user's home directory.
146
+
> When the `appcat` binary is called from a different folder than where it's installed, it looks for its dependencies in the **.appcat** folder in the user's home directory.
147
+
148
+
#### Option 2: Run appcat from the downloaded folder
149
+
150
+
Change the directory to the extracted folder:
151
+
152
+
```bash
153
+
cd /azure-migrate-appcat-for-java-cli-<OS>-<architecture>-<release-version>-preview/
154
+
./appcat --help
155
+
```
156
+
157
+
> [!NOTE]
158
+
> The `appcat` binary first looks for its dependencies in the current directory, and falls back to #Option 1 configration if the dependencies not found.
160
159
161
160
## Usage
162
161
@@ -189,13 +188,13 @@ To analyze application source code, run the following command:
@@ -241,7 +240,6 @@ available target technologies:
241
240
azure-aks
242
241
azure-appservice
243
242
azure-container-apps
244
-
azure-spring-apps
245
243
cloud-readiness
246
244
linux
247
245
openjdk11
@@ -332,34 +330,52 @@ The reports are automatically generated and launched. You can find the reports u
332
330
333
331
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.
334
332
335
-
:::image type="content" source="media/java/report-summary.png" alt-text="Screenshot of the appcat summary report." lightbox="media/java/report-summary.png":::
333
+
:::image type="content" source="media/java/AppCAT7-report-summary.png" alt-text="Screenshot of the appcat summary report." lightbox="media/java/AppCAT7-report-summary.png":::
336
334
337
335
When you zoom in on the **Incidents by Category** pie chart, you can see the number of incidents by category: **Mandatory**, **Optional**, and **Potential**.
338
336
339
337
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.
340
338
341
-
:::image type="content" source="media/java/report-summary-incident.png" alt-text="Screenshot of the AppCAT summary incident report." lightbox="media/java/report-summary-incident.png":::
339
+
:::image type="content" source="media/java/AppCAT7-report-summary-incident.png" alt-text="Screenshot of the AppCAT summary incident report." lightbox="media/java/AppCAT7-report-summary-incident.png":::
342
340
343
341
### Assessment report
344
342
345
343
The assessment report gives an overview of the transformation issues that would need to be solved to migrate the application to Azure.
346
344
347
345
These *Issues*, also called *Incidents*, have a severity (*Mandatory*, *Optional*, or *Potential*), 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.
348
346
349
-
:::image type="content" source="media/java/report-assessment.png" alt-text="Screenshot of the AppCAT assessment report." lightbox="media/java/report-assessment.png":::
347
+
:::image type="content" source="media/java/AppCAT7-report-assessment.png" alt-text="Screenshot of the AppCAT assessment report." lightbox="media/java/AppCAT7-report-assessment.png":::
350
348
351
349
### Detailed information for a specific issue
352
350
353
351
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.
354
352
355
-
:::image type="content" source="media/java/report-assessment-detail.png" alt-text="Screenshot of the AppCAT issue detail report." lightbox="media/java/report-assessment-detail.png":::
353
+
:::image type="content" source="media/java/AppCAT7-report-assessment-detail.png" alt-text="Screenshot of the AppCAT issue detail report." lightbox="media/java/AppCAT7-report-assessment-detail.png":::
356
354
357
355
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.
358
356
359
-
:::image type="content" source="media/java/report-assessment-code.png" alt-text="Screenshot of the AppCAT issue code report." lightbox="media/java/report-assessment-code.png":::
357
+
:::image type="content" source="media/java/AppCAT7-report-assessment-code.png" alt-text="Screenshot of the AppCAT issue code report." lightbox="media/java/AppCAT7-report-assessment-code.png":::
360
358
361
359
## Release notes
362
360
361
+
### 7.6.0.4
362
+
363
+
This release contains the following fixes and enhancements.
364
+
365
+
- Support telemetry collection. `--disable-telemetry` flag to disable telemetry.
366
+
- Refactor CLI command format, make it more clear.
- New `--exclude-paths` flag: Specify paths that should be ignored analysis. Use a comma-separated list for multiple values: `--exclude-paths <path1>,<path2>,...` (default []).
375
+
- New `--packages` flag: Specify application class packages to be evaluated. Use a comma-separated list for multiple values: `--packages <package1>,<package2>,...` (default []).
376
+
- New `--dry-run` flag: Only check if the flags are valid, not running the analysis actually. (default false).
377
+
- Remove `azure-spring-apps` from appcat `--list-targets`.
378
+
363
379
### 7.6.0.3
364
380
365
381
This release contains the following fixes and enhancements.
@@ -438,6 +454,13 @@ GA (Generally Available) release of Azure Migrate application and code assessmen
438
454
439
455
## Known Issues
440
456
457
+
### 7.6.0.4
458
+
459
+
- Rules issues:
460
+
-`azure-system-config-01000` rules aren't being triggered.
461
+
-`azure-password-01000` rule detects only one violation, even when multiple violations exist in the same file.
462
+
- Error in Watcher Error channel on Windows: `Windows system assumed buffer larger than it is, events have likely been missed`. This error message appears on the command line during long-running jobs on Windows.
463
+
441
464
### 7.6.0.3
442
465
443
466
- The flag `--overrideProviderSettings` isn't supported.
0 commit comments