Applications Management
The Applications tab allows listing and managing applications with the current organization’s account.
This tab allows observing the list of applications with their metadata and excluding, downloading, deleting, and declaring applications. The application list is split in conformity with the main project language of applications.
The Application tab overview
General Functionality
The Applications tab displays the table that presents the list of applications associated with the uploaded sources. The table shows:
Name of the application.
Programming language of the application and its version.
Associated database name.
In case of deleting the associated source from mConsole, the field shows the DB engine of the deleted source.Scan date (date/month/year). The date the application was scanned by mMC-CA. If the application was only declared then the field is empty.
Creation mode:
Analyzed – for the applications scanned with the mMC-CA.
Declared – for the applications included manually.
Statuses section showing if any exclusions were made for features or applications.
For searching, filtering, or sorting, use the same options as for Sources | Search-and-Filter.
Actions Panel
Select the application(-s) from the list and click a button on the Actions panel to:
Exclude applications from the analysis.
Download the applications' metadata.
Delete applications from the list of sources.
Declare new applications.
The Declare button leads to the Edit Application page. There, you can manually declare characteristics of a new application connected to your source(-s).
Using the Actions panel to manage applications
Application Management
On the Application Management page, you can:
Exclude specific features of a particular application so that they do not participate in the score calculation.
Declare a new application to include in the list of sources instead of scanning it.
To open the Application Management page, go to Account Data → Applications.
Edit Application
In case you have a new application connected to your source(s), you have to declare it so that mConsole could analyze it.
To declare it, from the Applications tab, click Declare. This will open the Edit Application tab. When you finish the declaring procedure, the new application will be added to the list of applications available by clicking the Applications tab.
The page is divided into various subsections, each of which contains one or more questions.
The Edit Application tab overview
To declare a new application, fill in the form:
In the Identity subsection, fill in the fields:
Application Name.
Associated Database. A dropdown that lists source DB engines and previously analyzed databases used by the application. Select a required item from the list.
In the General subsection, fill in the fields answering the questions:
Source Control. Is the code under source control (Git, SVN, etc.)?
Semantic Version. Does the application have a semantic version?
Screen Count. How many screens or forms does the application have?
Programming Language Version. What programming language is the application written in?
Oldest Code. When was the application first created – specify the date in format month/date/year?
Observable. Is the application instrumented with observability (logging, tracing, monitoring)?
Newest Code. When was the application last modified?
Lines of Code Count. How many lines of code does the application have?
Code Ownership. Was the application code developed all in-house, by a 3rd party, or modified by 3rd party?
Automated Build. Is there build automation for the application (Jenkins, CI environment, or similar)?
Automated Deployment. Is there deployment automation for this application? Are build artifacts promoted to hosting environments by automation?
Automated Test. Are tests automated? Are there unit tests, integration tests, or other test automation running as part of build or deployment?
Stored Procedure Count. What is the number of unique stored procedures the application invokes?
Table Count. What is the number of unique tables the application interacts with?
View Count. What is the number of unique views the application interacts with?
DB Link Count. What is the number of unique views the application interacts with?
Schema Migration Support. Does the application contain schema migration and versioning support?
SQL Read Operation Count. How many
SELECTtype operations are in the application code?SQL Write Operation Count. How many
UPDATE,DELETE,INSERTtype operations are in the application code?
All the questions are optional.
In the Language Specific sections, if available, answer the questions specific for a particular programming language. The questions differ depending on the language.
The Language Specific sections and sub-headings are hidden by default. They are shown only when:A language is entered in the Programming Language field of the General section (view above).
There are language-specific questions for the given language.
In the Database Source & Target section, provide the following details:
Workload Type. What is the primary workload type for this application’s database?
Multi-Region. Does the application’s database require multi-region presence?
Writes Rate. What is the database write rate for this application (write operations per second)?
Read Rate. What is the database write rate for this application (read operations per second)?
All the questions are optional.
Click Save.
If the Save button is disabled, review the edit form and fill in all mandatory fields observing value formats and ranges.
Excluding features in a single application
Below the application name, open the Features tab to see the list of features related to the application.
To exclude features of a selected application:
From the features list, select features subject to exclude.
Click Exclude on the Actions panel.
The excluded features become Excluded in the list.
