MTA-6288 Centralized Configuration for UI

Prabha Kylasamiyer Sundara Rajan · Prabha Kylasamiyer Sundara Rajan · commit 2917c0308d36 · 2026-03-09T13:45:19.000+05:30
Signed-off-by: Prabha Kylasamiyer Sundara Rajan &lt;pkylasam@pkylasam-thinkpadp16vgen1.bengluru.csb&gt;
diff --git a/assemblies/ui-guide/assembly_centralized-configurations-analysis.adoc b/assemblies/ui-guide/assembly_centralized-configurations-analysis.adoc
@@ -0,0 +1,53 @@
+:_newdoc-version: 2.18.5
+:_template-generated: 2025-09-12
+:_mod-docs-content-type: ASSEMBLY
+
+ifdef::context[:parent-context-of-centralized-configurations: {context}]
+
+ifndef::context[]
+[id="centralized-configurations"]
+endif::[]
+ifdef::context[]
+[id="centralized-configurations_{context}"]
+endif::[]
+= Analyzing an application with centralized profiles
+
+:context: centralized-configurations
+
+[role="_abstract"]
+Use standardized configurations across components of {ProductFirstRef} such as the {WebName}, {CLIName}, and the Visual Studio Code {PluginName} by using the centralized configuration management in {ProductFullName}.
+
+As an Architect, you can create, edit, and delete  custom migration targets and configurations. For example, analysis profiles and custom rulesets in the {ProductShortName} {WebName}. The analysis profiles contain the following details:
+
+* Analysis configuration
+.. Mode of analysis (for example, `source code`)
+.. Scope of an analysis (for example, application analysis that includes all dependencies, including known Open Source libraries)
+.. Migration targets (default or custom)
+* Advanced configuration
+.. Custom rules
+.. Rule labels to include or exclude rules for an analysis
+
+As a Migrator, can use these profiles to perform an application analysis. 
+
+The {ProductShortName} Hub stores and syncs the profile configurations. {ProductShortName} components periodically sync with the Hub and pull the analysis profiles that contain the latest updates to the configuration.
+
+
+:FeatureName: Analysis Profile
+[IMPORTANT]
+====
+[subs="attributes+"]
+{FeatureName} 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.
+
+For more information about the support scope of Red Hat Technology Preview features, see link:https://access.redhat.com/support/offerings/techpreview/[Technology Preview Features Support Scope].
+====
+:!FeatureName:
+
+include::topics/mta-ui/proc_configuring-profile-for-an-application-analysis.adoc[leveloffset=+1]
+
+include::topics/mta-ui/proc_creating-custom-migration-targets.adoc[leveloffset=+1]
+
+include::topics/mta-ui/proc_running-an-analysis-using-profile.adoc[leveloffset=+1]
+
+ifdef::parent-context-of-centralized-configurations[:context: {parent-context-of-centralized-configurations}]
+ifndef::parent-context-of-centralized-configurations[:!context:]
+
diff --git a/docs/topics/mta-ui/proc_configuring-profile-for-an-application-analysis.adoc b/docs/topics/mta-ui/proc_configuring-profile-for-an-application-analysis.adoc
@@ -0,0 +1,70 @@
+// Module included in the following assemblies:
+//
+// * docs/web-console-guide/master.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="configuring-profile-application-analysis_{context}"]
+= Configuring an analysis profile
+
+
+[role="_abstract"]
+As an architect, you can configure a profile that has the configuration needed to analyze an application for a specific migration target.
+
+.Procedure
+
+. In the *Migration* view, click *Analysis Profiles*.
+
+. Click *Create new* to open the *Create Analysis Profile* window.
+
+. Enter a unique name for the configuration profile in the *Profile Details* page.
+
+. Click *Next* to go to the *Configure analysis* section. You can configure the analysis source, target platforms, and the scope of the dependency analysis. 
+. Select the *Analysis source* from the list:
+* Binary
+* Source code
+* Source code and dependencies
+* Upload a local binary. This option only appears if you are analyzing a single application. If you chose this option, you must *Upload a local binary*. Either drag a file into the area provided or click *Upload* and select the file to upload.
+. Click *Next*.
+. Select one or more target options in *Set targets* for the analysis:
+
+* Application server migration to either of the following platforms:
+** JBoss EAP 7
+** JBoss EAP 8
+* Containerization
+* Quarkus
+* OracleJDK to OpenJDK
+* OpenJDK. Use this option to upgrade to either of the following JDK versions:
+** OpenJDK 11
+** OpenJDK 17
+** OpenJDK 21
+* Linux. Use this option to ensure that there are no Microsoft Windows paths hard-coded into your applications.
+* Jakarta EE 9. Use this option to migrate from Java EE 8.
+* Spring Boot on Red Hat Runtimes
+* Open Liberty
+* Camel. Use this option to migrate from Apache Camel 2 to Apache Camel 3 or from Apache Camel 3 to Apache Camel 4.
+* Azure App Service
+. Click *Next*.
+. Select one of the following *Scope* options to better focus the analysis:
+
+* Application and internal dependencies only.
+* Application and all dependencies, including known Open Source libraries.
+* Select the list of packages that you want to analyze manually. If you choose this option, type the file name and click *Add*.
+* Exclude packages. If you toggle this option on, type the name of the package and click *Add*.
+
+. Click *Next*.
+. In *Advanced*, you can attach custom rules to the analysis by selecting the *Manual* or *Repository* mode:
+** In the *Manual* mode, click *Add Rules*. Drag the relevant files or select the files from their directory and click *Add*.
+** In the *Repository* mode, you can add rule files from a *Git* or *Subversion* repository.
++
+IMPORTANT: Attaching custom rules is optional if you have already attached a migration target to the analysis. If you have not attached any migration target, you must attach rules.
+
+. Optional: Set any of the following options:
+* Additional target labels
+* Additional source labels
+* Excluded rules labels. Rules with these labels are not processed. Add or delete as needed.
+
+. Click *Next*.
+. In *Review*, verify the analysis parameters.
+. Click *Save*.
++
+{ProductShortName} saves the analysis profile on the *Analysis Profiles* page.
diff --git a/docs/topics/mta-ui/proc_configuring-target-profiles.adoc b/docs/topics/mta-ui/proc_configuring-target-profiles.adoc
@@ -12,7 +12,6 @@ The target profile contains one or more generators. Each generator generates ass
 
 You can configure more than one target profile for the archetype based on the target platforms to which you want to migrate applications of the specific archetype.
 
-//what does priority order mean?
 The generators are run in a priority order, in which manifests generated by lower priority generators do not override manifests generated by other generators.  
 
 .Procedure
@@ -25,7 +24,17 @@ The *Target profiles for <archetype-name>* appears.
 . In the *Name* field in the opened dialogue, enter a unique name for the target profile.
 . Click the *Tag category* field and select the category tag to associate with the tag.
 . Select specific generators and click the right arrow to move the generator from the *Available generators* list to the *Chosen generators* list.
+. (Optional) Select an analysis profile for the application from the list. You can download this profile configuration from the {ProductShortName} {CLIName} only if you select the profile from this list.
 . Click *Create*.
 
+<<<<<<< HEAD:docs/topics/web-console/proc_configuring-target-profiles.adoc
+You can click on the archetype row to open the archetype detail view where the target profiles for the archetype are listed.
+
+[NOTE]
+====
+If you delete a target profile, {ProductShortName} also automatically deletes the analysis profile associated with the target profile.
+====
+=======
 +
-You can click on the archetype row to open the archetype detail view where the target profiles for the archetype are listed.
+You can click on the archetype row to open the archetype detail view where the target profiles for the archetype are listed.
+>>>>>>> 2a7a567 ([DITA] Vale DITA fixes and short descriptions for the UI title (#289)):docs/topics/mta-ui/proc_configuring-target-profiles.adoc
diff --git a/docs/topics/mta-ui/proc_creating-custom-migration-targets.adoc b/docs/topics/mta-ui/proc_creating-custom-migration-targets.adoc
@@ -19,7 +19,7 @@ By using ready-made custom migration targets, you can avoid configuring custom r
 
 .Procedure
 
-. In the *Administration* view, click *Custom migration targets*.
+. In the *Migration* view, click *Custom migration targets*.
 . Click *Create new*.
 . Enter the name and description of the target.
 . Click the *Provider* drop-down menu and choose the language provider.
diff --git a/docs/topics/mta-ui/proc_running-an-analysis-using-profile.adoc b/docs/topics/mta-ui/proc_running-an-analysis-using-profile.adoc
@@ -0,0 +1,55 @@
+// Module included in the following assemblies:
+//
+// * docs/web-console-guide/master.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="profile-application-analysis_{context}"]
+= Using a profile to run an application analysis 
+
+[role="_abstract"]
+As a Migrator, you can use a pre-configured analysis profile to analyze an application for a target platform. 
+
+.Procedure
+
+. In the *Migration* view, click *Application inventory*.
+. Select an application that you want to analyze.
++
+. Review the credentials assigned to the application.
+. Click *Analyze*.
+. In the *Mode* section, select *Use analysis profile*.
+. Select a pre-configured profile from the list for running an analysis. 
+. Click *Next* 
+. *Enable automated tagging*. Select the checkbox to automatically attach tags to the application. This checkbox is selected by default.
++
+NOTE: {ProductShortName} displays automatically attached tags  only _after_ you run the analysis. You can attach tags to the application manually instead of enabling automated tagging or in addition to it.
++
+. *Enable enhanced analysis details*.  
++
+
+//need more information on the above option.
+. Click *Next*.
+. In *Review*, verify the analysis parameters.
+. Click *Run*.
++
+The analysis status is `Scheduled` as {ProductShortName} downloads the image for the container. When {ProductShortName} downloads the image, the status changes to `In-progress.`
++
+NOTE: Analysis takes minutes to hours to run depending on the size of the application and the capacity and resources of the cluster.
++
+NOTE: {ProductShortName} relies on Kubernetes scheduling capabilities to determine how many analyzer instances are created based on cluster capacity. If several applications are selected for analysis, by default, only one analyzer can be provisioned at a time. With more cluster capacity, more analysis processes can be executed in parallel.
+
+. Optional: To track the status of your active analysis task, open the *Task Manager* view by clicking the notifications button.
++
+Alternatively, hover over the application name to display the pop-over window.
+
+.Verification 
+
+To check the report after the analysis is complete: 
+
+. Open the application view by clicking on the application name.
+. Click the *Reports* tab to download the results in *HTML* or *YAML*. 
++
+
+[NOTE]
+====
+You can download the report if the {ProductShortName} Administrator has enabled the option to download reports after running an analysis on the *General configuration* page in the *Administration* view.
+====
diff --git a/docs/web-console-guide/master.adoc b/docs/web-console-guide/master.adoc
@@ -26,7 +26,7 @@ include::assemblies/ui-guide/assembly_tagging-applications.adoc[leveloffset=+1]
 
 include::assemblies/ui-guide/assembly_working-with-archetypes.adoc[leveloffset=+1]
 
-//include::topics/mta-web-applying-assessments-to-other-apps.adoc[leveloffset=+3]
+include::assemblies/ui-guide/assembly_centralized-configurations-analysis.adoc[leveloffset=+1]
 
 include::assemblies/ui-guide/assembly_analyzing-applications.adoc[leveloffset=+1]
 
