Analyzer Checker

Table of Contents

In the case of a legacy modernization project (mainly Cobol, PL/I, and RPG), this feature helps you start preparing/checking the compliance of the Blu Age Velocity transformation engine within your project assets in order to build and fine-tune your modernization strategy during the calibration phase. To do so, your source code will be explored and parsed using Blu Age Analyzer.

 

Launch

In order to get started with Analyzer Checker, select Toolbox on the left menu and then click on Analyzer Checker.

Analyzer Checker - Launch

Next, you need to select which Blu Age Analyzer version to use and specify your project’s workpackages to be analyzed. If no workpackage is defined the workpackage selection Combobox is not visible and all files will be analyzed. The list of Blu Age Analyzer versions is permanently updated by the team when new releases are available. Click on the launch button to start the analysis. The analysis duration depends on the number of files to be analyzed and their related programming languages. Once  Blu Age Analyzer has finished analyzing your files, you will be notified by email. In the meantime, you can use all the other BluInsights features.

 

Results

When the analysis is done, the results are shown as a table summarizing the main detected specificities of your project that need to be fine-tuned.
Analyzer Checker - Results

On the top of the page, you can visualize general information about the analysis, like how many incompatibilities were found, which Blu Age Analyzer version has been used and when the last analysis took place. The table gives the main information for each file. It can be filtered by file name, total lines, languages, lines of code, workpackages, status, labels, etc. See filters documentation here. In addition, you can take Adjust column settings (select which columns to show or hide).

​In the “…” upper right menu you can also perform the following actions:

  1. Open the results dialog which contains all the selected workpackages and the launch date.
  2. Open the relaunch dialog.
  3. Download artifacts generated by Blu Age Analyzer like the dependencies result and the metadata.ini file used for the analysis.
  4. ​For customers who are used to work with Blu Age Analyzer,  upload a “metadata.ini” file to configure Blu Age Analyzer.

Analyzer Checker - Context Menu

The properties of files shown in the results can be edited (assignation, labels, status…). It is also possible to export those detected errors to a Jira-compliant format. The content of the error is copied in your clipboard thus you can paste it directly in the description field of a Jira ticket.Analyzer Checker - Copy Jira data to clipboard

Dependencies result

​Blu Age Analyzer generates a detailed dependencies analysis that will be leveraged by the Velocity transformation engine in order to perform the modernization. The result of this analysis can be downloaded and imported on the BluInsights ​Dependencies page.