Merge pull request #228 from anarnold97/MTA-6214-8.0.0-Install-guide

MTA-6214: 8.0.0 Install guide still points to 7.3 UI and CLI guides

Author: anarnold97

docs/topics/developer-lightspeed/con_persistent-volumes.adoc

@@ -7,6 +7,6 @@
 = Persistent volume requirements
 
 [role="_abstract"]
-The Solution Server component requires a backend database to store code changes from previous analyses. 
+The Solution Server component requires a backend database to store code changes from previous analyses.
 
-If you plan to enable Solution Server, you must create a `5Gi` `RWO` persistent volume used by the {mta-dl-plugin} database. See link:{mta-URL}/installing_the_migration_toolkit_for_applications/index#persistent-volume-requirements_installing-mta-ui[Persistent volume requirements] for more information.
+If you plan to enable Solution Server, you must create a `5Gi` `RWO` persistent volume used by the {mta-dl-plugin} database. See link:{mta-URL}/installing_the_migration_toolkit_for_applications/index#persistent-volume-requirements_installing-mta-ui[Persistent volume requirements] for more information.

docs/topics/developer-lightspeed/proc_tackle-enable-dev-lightspeed.adoc

@@ -6,32 +6,30 @@
 = Enabling {mta-dl-plugin} in Tackle custom resource
 
 [role="_abstract"]
-Solution Server integrates with the {ProductShortName} Hub backend component to use the database and volumes necessary to store and retrieve the solved examples. 
+Solution Server integrates with the {ProductShortName} Hub backend component to use the database and volumes necessary to store and retrieve the solved examples.
 
 To enable Solution Server and other AI configurations in the {mta-dl-full} VS Code extension, you must modify the Tackle custom resource (CR) with additional parameters.
 
 .Prerequisites
 
 //the hard link must be changed to the same topic in 8.0.0 that has the `{mta-dl-plugin}-database` req.
-. You deployed an additional RWO volume for  the `{mta-dl-plugin}-database` if you want to use {mta-dl-plugin}. See link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/user_interface_guide/mta-7-installing-web-console-on-openshift_user-interface-guide#openshift-persistent-volume-requirements_user-interface-guide[Persistent volume requirements] for more information.
+. You deployed an additional RWO volume for  the `{mta-dl-plugin}-database` if you want to use {mta-dl-plugin}. See link:{mta-URL}/installing_the_migration_toolkit_for_applications/index#persistent-volume-requirements_installing-mta-ui[Persistent volume requirements] for more information.
 
 . You installed the {ProductShortName} operator v8.0.0.
 
 
 .Procedure
 
-. Log in to the Red Hat {ocp-name} cluster and switch to the `openshift-mta` project. 
+. Log in to the Red Hat {ocp-name} cluster and switch to the `openshift-mta` project.
 +
-
 . Edit the Tackle CR settings in the `tackle_hub.yml` file with the following command:
 +
-
 [source, terminal]
 ----
 oc edit tackle
 ----
 
-. Enter applicable values for `kai_llm_provider` and `kai_llm_model` variables. 
+. Enter applicable values for `kai_llm_provider` and `kai_llm_model` variables.
 +
 [source, yaml]
 ----

docs/topics/mta-install/con_mta-rules.adoc

@@ -6,32 +6,32 @@
 = {ProductShortName} rules
 
 [role="_abstract"]
-The {ProductFullName} contains rule-based migration tools (analyzers) that you can use to analyze the application user interfaces (APIs), technologies, and architectures used by the applications you plan to migrate. 
+The {ProductFullName} contains rule-based migration tools (analyzers) that you can use to analyze the application user interfaces (APIs), technologies, and architectures used by the applications you plan to migrate.
 
-{ProductShortName} analyzer rules use the following rule pattern: 
+{ProductShortName} analyzer rules use the following rule pattern:
 
 ----
 when(condition)
  message(message)
  tag(tags)
 ----
 
-You can use the {ProductShortName} rules internally to perform the following tasks: 			
+You can use the {ProductShortName} rules internally to perform the following tasks:
 
-* Extract files from archives. 					
-* Decompile files. 					
-* Scan and classify file types. 					
-* Analyze XML and other file content. 					
-* Analyze the application code. 					
-* Build the reports. 					
+* Extract files from archives.
+* Decompile files.
+* Scan and classify file types.
+* Analyze XML and other file content.
+* Analyze the application code.
+* Build the reports.
 
-{ProductShortName} builds a data model based on the rule execution results and stores component data and relationships in a graph database. This database can then be queried and updated as required by the migration rules and for reporting purposes. 			
+{ProductShortName} builds a data model based on the rule execution results and stores component data and relationships in a graph database. This database can then be queried and updated as required by the migration rules and for reporting purposes.
 
 [NOTE]
 ====
-You can create your own custom analyzer rules. You can use custom rules to identify the use of custom libraries or other components that might not be covered by the provided standard migration rules. 				
+You can create your own custom analyzer rules. You can use custom rules to identify the use of custom libraries or other components that might not be covered by the provided standard migration rules.
 
-For instructions on how to write custom rules, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/rules_development_guide/index[Rules Development Guide]. 
+For instructions on how to write custom rules, see link:{mta-URL}/rules_development_guide/index[Rules Development Guide].
 ====
 
 

docs/topics/mta-install/con_mta-tools.adoc

@@ -6,55 +6,55 @@
 = {ProductShortName} tools
 
 [role="_abstract"]
-Different {ProductFullName} tools provide assistance in the various stages of your migration and modernization efforts. 		
+Different {ProductFullName} tools provide assistance in the various stages of your migration and modernization efforts.
 
-You can use the following {ProductShortName} tools for assessing and analyzing your applications: 		
+You can use the following {ProductShortName} tools for assessing and analyzing your applications:
 
 * *User interface (UI)*
-+	
-By using the user interface for the {ProductName}, you can perform the following tasks: 
++
+By using the user interface for the {ProductName}, you can perform the following tasks:
 
-** Assess the risks involved in containerizing an application for hybrid cloud environments on Red Hat OpenShift. 			
+** Assess the risks involved in containerizing an application for hybrid cloud environments on Red Hat OpenShift.
 ** Analyze the changes that must be made in the code of an application to containerize the application.
 
-+ 	
-For more information about using the MTA user interface, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/user_interface_guide/index[User Interface Guide]. 			
-   
++
+For more information about using the MTA user interface, see link:{mta-URL}/configuring_and_managing_the_migration_toolkit_for_applications_user_interface/index[Configuring and managing the Migration Toolkit for Applications user interface].
+
 * *Command-line interface (CLI)*
 +
 The CLI is a command-line tool in the {ProductName} that you can use to assess and prioritize migration and modernization efforts for applications. It provides numerous reports that highlight the analysis without using the other tools. The CLI includes a wide array of customization options. By using the CLI, you can tune {ProductShortName} analysis options or integrate with external automation tools.
-+ 		
-For more information about using the CLI, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/cli_guide/index[CLI Guide]. 			
-	
++
+For more information about using the CLI, see link:link:{mta-URL}/using_the_mta_command-line_interface_to_analyze_applications/index[Using the MTA command-line interface to analyze applications].
+
 * *{ProductName} Operator*
-+	
-By using the {ProductName} Operator, you can install the user interface on OpenShift Container Platform. 
-+	
-For more information about the prerequisites for the MTA Operator installation, see link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles]. 				
-	
-* *IDE add-ons* 			
 +
-You can migrate and modernize applications by using the {ProductName} add-ons for the following applications: 
+By using the {ProductName} Operator, you can install the user interface on OpenShift Container Platform.
++
+For more information about the prerequisites for the MTA Operator installation, see link:https://access.redhat.com/support/policy/updates/openshift_operators[OpenShift Operator Life Cycles].
+
+* *IDE add-ons*
++
+You can migrate and modernize applications by using the {ProductName} add-ons for the following applications:
 +
-** Eclipse 					
-** Visual Studio Code, Visual Studio Codespaces, and Eclipse Che 	
-** IntelliJ IDEA, both the Community and Ultimate versions 
+** Eclipse
+** Visual Studio Code, Visual Studio Codespaces, and Eclipse Che
+** IntelliJ IDEA, both the Community and Ultimate versions
 
 
 +
-You can use these add-ons to perform the following tasks: 
+You can use these add-ons to perform the following tasks:
 
-** Analyze your projects by using customizable sets of rules. 			
-** Mark issues in the source code. 					
-** Fix the issues by using the provided guidance. 			
-** Use the automatic code replacement, if possible. 		
+** Analyze your projects by using customizable sets of rules.
+** Mark issues in the source code.
+** Fix the issues by using the provided guidance.
+** Use the automatic code replacement, if possible.
 
 
 +
 For more information about using add-ons, see the following documentation:
 
-** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/eclipse_plugin_guide/index[Eclipse Plugin Guide]
-** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/intellij_idea_plugin_guide/index[IntelliJ IDEA Plugin Guide]
-** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/visual_studio_code_extension_guide/index[Visual Studio Code Extension Guide]
+// ** link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/eclipse_plugin_guide/index[Eclipse Plugin Guide]
+** link:{mta-URL}/intellij_idea_plugin_guide/index[IntelliJ IDEA Plugin Guide]
+** link:{mta-URL}/configuring_and_using_the_visual_studio_code_extension_for_mta/index[Configuring and using the Visual Studio Code Extension for MTA]
 
 

docs/topics/mta-install/proc_installing-cli-zip.adoc

@@ -15,7 +15,7 @@ You can install the {ProductShortName} CLI by using the downloadable `.zip` file
 
 * Red Hat Container Registry Authentication for `registry.redhat.io`. Red Hat distributes container images from `registry.redhat.io`, which requires authentication. For more details, see link:https://access.redhat.com/RegistryAuthentication[Red Hat Container Registry Authentication].
 +
-NOTE: This prerequisite is not applicable for the containerless mode. For more information, see link:https://docs.redhat.com/en/documentation/migration_toolkit_for_applications/7.3/html/cli_guide/analyzing-applications-mta-cli_cli-guide#running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing applications in containerless mode]. 
+NOTE: This prerequisite is not applicable for the containerless mode. For more information, see link:{mta-URL}/using_the_mta_command-line_interface_to_analyze_applications/index#running-the-containerless-mta-cli_analyzing-applications-mta-cli[Analyzing an application in containerless mode].
 
 * You installed Java Development Kit (JDK) version 17 or later.
 * You set the `JAVA_HOME` environmental variable.