Chapter 3. Using the web console to analyze applications

Procedure

1. In the web console, click Projects.
2. Click Create project.
3. Enter a unique name for the project, an optional description, and click Next.

4. To upload applications, click the Upload tab, click Browse, select the application files you want to upload, and click Close.

   Uploading applications stores them directly on the MTR server.

5. To register a server path, click the Server path tab and enter the Server-side path of the application in the field.

   Registering the server path of an application ensures that MTR always uses the latest version.

6. Click Next.

7. Click one or more transformation targets.

   
8. Click Next.
9. Select packages and click > to include them in the analysis.
10. Click Next.

11. If you want to add a custom rule, click Add rule.

    See the Rule Development Guide for more information.

    • To upload a ruleset file, click the Upload tab, click Browse, select one or more files, and click Close.

      A ruleset file must have a .windup.xml extension. The uploaded file is stored on the MTR server.

    • To register the server path of a ruleset file, click the Server path tab, enter the Rules path, and click Save.

      Registering the server path ensures that the MTR server always uses the latest version of the ruleset files.

12. Click Next.

13. If you want to add a custom label, click Add label.

    • To upload a labelset file, click the Upload tab, click Browse, select one or more files, and click Close.

      A labelset file must have a .windup.label.xml extension. The uploaded file is stored on the MTR server.

    • To register a server path, click the Server path tab, enter the Labels path of the label files in the field, and click Save.

      Registering the server path ensures that the MTR server always uses the latest version of the labelset files.

14. Click Next.

15. Review the following Advanced options and make any necessary changes:

    • Target
    • Source
    • Exclude tags: Rules with these tags are not processed.
    • Additional classpath: Enter a space-delimited list of additional .jar files or directories so that they are available for decompilation or other analysis.
    • Application name
    • Mavenize group ID
    • Ignore path: Enter a path for files to exclude from analysis.
    • Export CSV: Exports the report data as a CSV file.
    • Export Summary: Generates an analysisSummary.json export file in the output directory. The file contains analysis summary information for each application analyzed, including the number of incidents and story points by category, and all of the technology tags associated with the analyzed applications.
    • Export reports zip: Creates a reports.zip file in the output folder. The file contains the analysis output, typically, the reports. If requested, it can also contain the CSV export files.
    • Disable Tattletale: Disables generation of a Tattletale report for each application.

    • Class Not Found analysis: Enables analysis of Java files that are not available on the class path.

      Note

      This option should not be used if some classes are unavailable for analysis.

    • Compatible Files report: Generating a Compatible Files report might take a long time for large applications.
    • Exploded app: The input directory contains the unpackaged source files of an application.
    • Keep work dirs: Retains temporary files, for example, the graph database or extracted archive files, for debugging purposes.
    • Skip reports: HTML reports are not generated. Must be enabled if you enabled Export CSV.

    • Allow network access: Validates any XML files within the analyzed applications against their schema.

      Note

      This option might reduce performance.

    • Mavenize: Creates a Maven project directory structure based on the structure and content of the application.
    • Source mode: Indicates that the application files are raw source files, not compiled binaries. The sourceMode argument has been deprecated. There is no longer the need to specify it. MTR can intuitively process any inputs that are presented to it. In addition, project source folders can be analyzed with binary inputs within the same analysis execution.

    • Analyze known libraries: Analyze known software artifacts embedded within your application. By default, MTR only analyzes application code.

      Note

      This option might result in a longer execution time and a large number of migration issues being reported.

    • Transaction analysis: [Tech Preview] Generates a Transactions report that displays the call stack, which executes operations on relational database tables. The Enable Transaction Analysis feature supports Spring Data JPA and the traditional preparedStatement() method for SQL statement execution. It does not support ORM frameworks, such as Hibernate.

      Note

      Transaction analysis is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

    • Skip source code reports: Adding this option skips generating a Source code report when generating the application analysis report. Use this advanced option when concerned about source code information appearing in the application analysis.
16. Click Next.

17. Review your project and click Save or Save and run.

    The project is displayed in the Projects screen.

Procedure

1. In the web console, click Analysis results.
2. Select a project.
3. Click Run analysis.

Procedure

1. In the web console, click Analysis results.

2. Select a project from the list.

   

   The Analysis Reports can be accessed via the Reports bar chart icon or by the Reports action on the right-hand side of the screen.

3. Click on the number of the analysis you want to review to see details of the analysis configuration settings and the analysis execution statistics.

   The results are displayed in the Results screen, which contains two tabs: Details and Logs.

Procedure

1. In the web console, click Analysis results.

2. Click the Reports icon beside the analysis you want to investigate.

   The All applications screen of the reports is displayed.

   

Procedure

1. In the web console, click Analysis configuration.

   
2. Select a Project.
3. Click the appropriate tabs and make your changes.

4. Click Save or Save and run.

   The project is displayed in the Projects screen.

Procedure

1. In the web console, click Rules configuration.
2. Click Add rules.

3. To upload a ruleset file, click the Upload tab, click Browse, select one or more files, and click Close.

   A ruleset file must have a .windup.xml extension. The uploaded file is stored on the MTR server.

4. To register the server path of a ruleset file, click the Server path tab, enter the Rules path, and click Save.

   Registering the server path ensures that the MTR server always uses the latest version of the ruleset files.

   The Custom rules list displays the rules.

Procedure

1. In the web console, click Labels configuration.
2. Click Add label.

3. To upload a labelset file, click the Upload tab, click Browse, select one or more files, and click Close.

   A labelset file must have a .windup.label.xml extension. The uploaded file is stored on the MTR server.

4. To register the server path of a labelset file, click the Server path tab, enter the Labels path, and click Save.

   Registering the server path ensures that the MTR server always uses the latest version of the labelset files.

   The Custom labels list displays the labels.