Merge pull request migtools#20 from johnwilkins/MTA-3131

MTA-3131: [Documentation for] Automatic language and technology discovery for applications

Author: raoradhika

docs/topics/con_automatic-tagging-of-an-application.adoc

@@ -8,8 +8,8 @@
 
 [role="_abstract"]
 
-{ProductShortName} can automatically add tags to the application based on the application analysis. Automatic tagging is especially useful when dealing with large portfolios of applications.
+{ProductShortName} automatically spawns language discovery and technology discovery tasks when adding an application to the *Application Inventory*. When the language discovery task is running, the technology discovery and analysis tasks wait until the language discovery task is finished. These tasks automatically add tags to the application. {ProductShortName} can automatically add tags to the application based on the application analysis. Automatic tagging is especially useful when dealing with large portfolios of applications.
 
-Automatic tagging of applications is enabled by default. You can disable automatic tagging by deselecting the *Enable automated tagging* checkbox in the *Advanced* section of the *Analysis configuration* wizard.
+Automatic tagging of applications based on application analysis is enabled by default. You can disable automatic tagging during application analysis by deselecting the *Enable automated tagging* checkbox in the *Advanced* section of the *Analysis configuration* wizard.
 
 NOTE: To tag an application automatically, make sure that the *Enable automated tagging* checkbox is selected _before_ you run an application analysis.

docs/topics/mta-web-adding-applications.adoc

@@ -52,4 +52,12 @@ NOTE: If you enter any value in any of the Binary section fields, all fields aut
 
 . Click *Create*. The new application appears in the list of defined applications.
 
+.Automated Tasks
+
+After adding a new application to the *Application Inventory*, you can set your cursor to hover over the application name to see the automated tasks spawned by adding the application. The language discovery task identifies the programming languages in the application. The technology discovery task identifies specific technologies in the application. The tasks automatically add appropriate tags to the application, reducing the effort involved in manually assigning tags to the application. After these tasks are complete, the number of tags added to the application will appear under the *Tags* column. To view the tags:
+
+. Click on the application's row entry. A side pane opens. 
+. Click the *Tags* tab. The tags attached to the application are displayed.
+
+You can add additional tags manually as needed. When MTA analyzes the application, it can add additional tags to the application automatically.
 // [Verification]

docs/topics/mta-web-edit-application.adoc

@@ -22,3 +22,7 @@ You can edit an existing application in the *Application Inventory* and re-run a
 . Review the application settings. For a list of application settings, see xref:mta-web-adding-applications_user-interface-guide[Adding an application].
 . If you changed any application settings, click *Save*.
 
+[NOTE]
+====
+After editing an application, {ProductShortName} re-spawns the language discovery and technology discovery tasks.
+====

docs/topics/mta-what-is-the-toolkit.adoc

@@ -17,6 +17,8 @@
 
 {ProductName} ({ProductShortName}) accelerates large-scale application modernization efforts across hybrid cloud environments on Red Hat OpenShift. This solution provides insight throughout the adoption process, at both the portfolio and application levels: inventory, assess, analyze, and manage applications for faster migration to OpenShift via the user interface.
 
+In {ProductShortName} 7.1 and later, when you add an application to the *Application Inventory*, {ProductShortName} automatically creates and executes language and technology discovery tasks. Language discovery identifies the programming languages used in the application. Technology discovery identifies technologies, such as Enterprise Java Beans (EJB), Spring, etc. Then, each task assigns appropriate tags to the application, reducing the time and effort you spend manually tagging the application.
+
 {ProductShortName} uses an extensive default questionnaire as the basis for assessing your applications, or you can create your own custom questionnaire, enabling you to estimate the difficulty, time, and other resources needed to prepare an application for containerization. You can use the results of an assessment as the basis for discussions between stakeholders to determine which applications are good candidates for containerization, which require significant work first, and which are not suitable for containerization.
 
 {ProductShortName} analyzes applications by applying one or more rulesets to each application considered to determine which specific lines of that application must be modified before it can be modernized.

docs/web-console-guide/master.adoc

@@ -164,6 +164,8 @@ include::topics/mta-web-creating-jira-issues-for-migration-wave.adoc[leveloffset
 == Assessing and analyzing applications with MTA
 You can use the {ProductName} ({ProductShortName}) {WebName} to assess and analyze applications:
 
+* When adding to or editing the *Application Inventory*, {ProductShortName} automatically spawns programming language and technology discovery tasks. The tasks apply appropriate tags to the application, reducing the time you spend tagging the application manually.
+
 * When assessing applications, {ProductShortName} estimates the risks and costs involved in preparing applications for containerization, including time, personnel, and other factors. You can use the results of an assessment for discussions between stakeholders to determine whether applications are suitable for containerization.
 
 * When analyzing applications, {ProductShortName} uses rules to determine which specific lines in an application must be modified before the application can be migrated or modernized.