./docs/release_notes-4.2.1/master-docinfo.xml:7: These release notes describe the new features and changes implemented for the {ProductName} (RHAMT) {ProductVersion} release.
./docs/release_notes/master-docinfo.xml:7: These release notes describe the new features and changes implemented for the {ProductName} (RHAMT) {ProductVersion} release.
./docs/release_notes-4.3.0/master.adoc:19://RHAMT extension for VSCode and Eclipse Che (MVP)
./docs/release_notes-4.3.0/master.adoc:20:include::topics/rhamt-extension-vscode-che-mvp.adoc[leveloffset=+2]
./docs/release_notes-4.3.0/master-docinfo.xml:7: These release notes describe the new features and changes implemented for the {ProductName} (RHAMT) {ProductVersion} release.
./docs/topics/web-openshift-access.adoc:4:Once the {WebName} has been xref:deploy_rhamt_app_openshift[deployed on OpenShift], you can access it from a browser. The `deploy.sh` script outputs the link, shown in the example below as `__WEB_CONSOLE_URL__`, to use to open the {WebName}.
./docs/topics/web-openshift-access.adoc:10:-> Deploy RHAMT Web Console ...
./docs/topics/web-openshift-access.adoc:13:Open __WEB_CONSOLE_URL__ to start using the RHAMT Web Console on OpenShift (user='rhamt',password='password')
./docs/topics/web-openshift-access.adoc:16:You can also access the {WebName} from the OpenShift console at `__OPENSHIFT_URL__/console/project/rhamt/overview` by clicking the link in the *RHAMT WEB CONSOLE HTTP* application. If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], be sure to replace `rhamt` in this URL with the name of your project.
./docs/topics/web-openshift-access.adoc:23:Authentication is required in order to access the {WebName}. The default user's credentials are `rhamt` and `password`. See xref:config_auth[Configuring Authentication for the {WebNameTitle}] for more information on configuring authentication for the {WebName}.
./docs/topics/rules-testing-junit.adoc:23:│ │ ├── *__RULE_NAME__.rhamt.xml* _(Custom rule)_
./docs/topics/rules-testing-junit.adoc:25:│ │ │ ├── *__RULE_NAME__.rhamt.test.xml* _(Test rule)_
./docs/topics/cli-args.adoc:56:|--userIgnorePath |Specify a location, in addition to `${user.home}/.rhamt/ignore/`, for {ProductShortName} to identify files that should be ignored. For additional information on formatting these files, see xref:exclude_files_and_packages[Configure {ProductShortName} to Exclude Files and Packages].
./docs/topics/cli-args.adoc:57:|--userLabelsDirectory |Specify a location for {ProductShortName} to look for custom Target Runtime Labels. The value can be a directory containing label files or a single label file. The Target Runtime Label files must use either the [x-]`.windup.label.xml` or [x-]`.rhamt.label.xml` suffix. The shipped Target Runtime Labels are defined within `$RHAMT_HOME/rules/migration-core/core.windup.label.xml`.
./docs/topics/cli-args.adoc:58:|--userRulesDirectory |Specify a location, in addition to `__RHAMT_HOME__/rules/` and `${user.home}/.rhamt/rules/`, for {ProductShortName} to look for custom {ProductShortName} rules. The value can be a directory containing ruleset files or a single ruleset file. The ruleset files must use the [x-]`.windup.xml` or [x-]`.rhamt.xml` suffix.
./docs/topics/web-add-user.adoc:14:.. Navigate to `__OPENSHIFT_URL__/console/project/rhamt/overview` in a browser.
./docs/topics/web-add-user.adoc:16:NOTE: If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], replace `rhamt` with the name of your project.
./docs/topics/web-add-user.adoc:20:. In the upper left corner, select the *Rhamt* realm from the drop down.
./docs/topics/testing-rules.adoc:10:* Test rules should use the `.rhamt.test.xml` extension.
./docs/topics/testing-rules.adoc:13:In addition, it is recommended to create a test rule that follows the name of the rule it tests. For instance, if a rule were created with a filename of `proprietary-rule.rhamt.xml`, the test rule should be called `proprietary-rule.rhamt.test.xml`.
./docs/topics/testing-rules.adoc:57: ../proprietary-servlet.rhamt.xml
./docs/topics/testing-rules.adoc:105: ../proprietary-servlet.rhamt.xml
./docs/topics/testing-rules.adoc:169: ../weblogic.rhamt.xml
./docs/topics/web-enable-auth.adoc:10:$ __RHAMT_HOME__/switch_to_authentication_required.sh
./docs/topics/about-plugin.adoc:8:For more information about link:https://marketplace.visualstudio.com/items?itemName=redhat.rhamt-vscode-extension[the extension], visit the Visual Studio Markteplace.
./docs/topics/create-basic-xml-rule.adoc:19:IMPORTANT: The {ProductShortName} XML rule file must use the `.windup.xml` or `.rhamt.xml` extension, otherwise the rule will not be evaluated.
./docs/topics/mavenize.adoc:16:$ __RHAMT_HOME__/bin/rhamt-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/output --target eap:6 --packages com.acme org.apache --mavenize
./docs/topics/maven-arguments.adoc:35:|userRulesDirectory |Specify a location for {ProductShortName} to look for custom {ProductShortName} rules. The value can be a directory containing ruleset files or a single ruleset file. The ruleset files must use the [x-]`.windup.xml` or [x-]`.rhamt.xml` suffix.
./docs/topics/web-start.adoc:8:$ __RHAMT_HOME__/run_rhamt.sh
./docs/topics/web-start.adoc:11:NOTE: In a Windows environment, use the `run_rhamt.bat` script.
./docs/topics/templates/document-attributes.adoc:13::ProductShortName: RHAMT
./docs/topics/templates/document-attributes.adoc:27::IDEPluginFilename: migrationtoolkit-rhamt-eclipse-plugin-repository
./docs/topics/templates/document-attributes.adoc:63::ProductDistribution: rhamt-cli-{ProductDistributionVersion}
./docs/topics/about-home-var.adoc:2:= Use of RHAMT_HOME in This Guide
./docs/topics/about-home-var.adoc:4:This guide uses the `__RHAMT_HOME__` replaceable variable to denote the path to your {ProductShortName} installation. The installation directory is the `{ProductDistribution}` directory where you extracted the {ProductShortName} ZIP distribution.
./docs/topics/about-home-var.adoc:6:When you encounter `__RHAMT_HOME__` in this guide, be sure to replace it with the actual path to your {ProductShortName} installation.
./docs/topics/openshift-installation-update.adoc:9:link:{ProductDocWebConsoleGuideURL}#deploy_rhamt_app_openshift[Deploy the {ProductShortName} Application].
./docs/topics/plugin-import-custom-ruleset.adoc:10:NOTE: The XML rule file must use the `.windup.xml` or `.rhamt.xml` extension in order to be recognized as an {ProductShortName} rule.
./docs/topics/method-design.adoc:5:image::RHAMT_AMM_Methodology_446947_0617_ECE_Design.png[Red Hat Migration Methodology: Design]
./docs/topics/method-deploy.adoc:5:image::RHAMT_AMM_Methodology_446947_0617_ECE_Deploy.png[Red Hat Migration Methodology: Deploy]
./docs/topics/xml-rule-perform-syntax.adoc:68:a|A reference to a category as defined in `RHAMT_HOME/rules/migration-core/core.windup.categories.xml`. The default categories are `mandatory`, `optional`, `potential`, and `information`.
./docs/topics/xml-rule-perform-syntax.adoc:226:a|A reference to a category as defined in `RHAMT_HOME/rules/migration-core/core.windup.categories.xml`. The default categories are `mandatory`, `optional`, `potential`, and `information`.
./docs/topics/create-first-xml-rule.adoc:86:NOTE: {ProductShortName} identifies files with the `.windup.xml` or `.rhamt.xml` extension as XML-based rules, so be sure to use this naming convention, otherwise the rule will not be evaluated!
./docs/topics/create-first-xml-rule.adoc:193:Copy the `JBoss5-web-class-loading.windup.xml` file to the `__RHAMT_HOME__/rules/` directory.
./docs/topics/create-first-xml-rule.adoc:197:$ cp /home/__USER_NAME__/migration-rules/rules/JBoss5-web-class-loading.windup.xml __RHAMT_HOME__/rules/
./docs/topics/create-first-xml-rule.adoc:207:$ __RHAMT_HOME__/bin/rhamt-cli --sourceMode --input /home/__USER_NAME__/migration-rules/data --output /home/__USER_NAME__/migration-rules/reports --target eap:6
./docs/topics/what-is-the-toolkit.adoc:1:[[about_rhamt]]
./docs/topics/migration-methodology.adoc:7:image::RHAMT_AMM_Methodology_446947_0517_ECE.png[Red Hat Migration Methodology]
./docs/topics/execute.adoc:6:. Open a terminal and navigate to the `__RHAMT_HOME__/bin/` directory.
./docs/topics/execute.adoc:7:. Execute the `rhamt-cli` script, or `rhamt-cli.bat` for Windows, and specify the appropriate arguments.
./docs/topics/execute.adoc:11:$ ./rhamt-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/output --source weblogic --target eap:6 --packages com.acme org.apache
./docs/topics/execute.adoc:38:$ __RHAMT_HOME__/bin/rhamt-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/report-output/ --source eap:5 --target eap:7 --packages com.acme org.apache
./docs/topics/execute.adoc:48:$ __RHAMT_HOME__/bin/rhamt-cli --sourceMode --input /path/to/seam-booking-5.2/ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seam
./docs/topics/execute.adoc:58:$ __RHAMT_HOME__/bin/rhamt-cli --input /path/to/jee-example-app-1.0.0.ear --output /path/to/report-output/ --target eap:7 --target cloud-readiness --packages com.acme org.apache
./docs/topics/execute.adoc:68:$ __RHAMT_HOME__/bin/rhamt-cli -Dwindup.decompiler=procyon --input __INPUT_ARCHIVE_OR_DIRECTORY__ --output __OUTPUT_REPORT_DIRECTORY__ --target __TARGET_TECHNOLOGY__ --packages __PACKAGE_1__ __PACKAGE_2__
./docs/topics/execute.adoc:79:$ __RHAMT_HOME__/bin/rhamt-cli [TAB]
./docs/topics/execute.adoc:90:$ source __RHAMT_HOME__/bash-completion/rhamt-cli
./docs/topics/execute.adoc:103:source __RHAMT_HOME__/bash-completion/rhamt-cli
./docs/topics/execute.adoc:110:# cp __RHAMT_HOME__/bash-completion/rhamt-cli /etc/bash_completion.d/
./docs/topics/execute.adoc:117:To see the complete list of available arguments for the `rhamt-cli` command, open a terminal, navigate to the `__RHAMT_HOME__` directory, and execute the following command:
./docs/topics/execute.adoc:121:$ __RHAMT_HOME__/bin/rhamt-cli --help
./docs/topics/web-execution-config.adoc:43:The *Add* button allows the user to select the rules files ([x-]`.windup.xml` or [x-]`.rhamt.xml`).
./docs/topics/web-execution-config.adoc:59:The *Add* button allows the user to select the rules files ([x-]`.windup.label.xml` or [x-]`.rhamt.label.xml`).
./docs/topics/overriding-rules.adoc:12:Custom rules can be placed in either `__RHAMT_HOME__/rules`, `${user.home}/.rhamt/rules/`, or the directory specified by the `--userRulesDirectory` command-line argument.
./docs/topics/rules-categories.adoc:12:. Edit the rule category file, which is located at `__RHAMT_HOME__/rules/migration-core/core.windup.categories.xml`.
./docs/topics/xml-rule-syntax.adoc:28:{ProductShortName} provides predefined rules for common migration requirements. These core {ProductShortName} rules are located in the {ProductShortName} installation at `__RHAMT_HOME__/rules/migration-core/`.
./docs/topics/plugin-install.adoc:16:For more information about link:https://marketplace.visualstudio.com/items?itemName=redhat.rhamt-vscode-extension[the extension], visit the Visual Studio Markteplace.
./docs/topics/plugin-install.adoc:30:.. In the *Location* field, enter [x-]`http://download.jboss.org/jbosstools/photon/stable/updates/rhamt/` and press *OK*.
./docs/topics/plugin-install.adoc:31:.. Select all of the checkboxes under *JBoss Tools - RHAMT* and press *Next*.
./docs/topics/plugin-install.adoc:46:.. Select all of the checkboxes under *JBoss Tools - RHAMT* and press *Next*.
./docs/topics/plugin-create-custom-ruleset.adoc:11:NOTE: The XML rule file must use the `.windup.xml` or `.rhamt.xml` extension in order to be recognized as an {ProductShortName} rule.
./docs/topics/web-install.adoc:4:. Download the {WebName} from the link:https://developers.redhat.com/products/rhamt/download[{ProductShortName} Download page].
./docs/topics/web-install.adoc:7:The path to the directory created by unzipping this file is referred to as `_RHAMT_HOME_` throughout this guide.
./docs/topics/web-remove-default-user.adoc:4:A default {WebName} user is provided with the {WebName} with the username `rhamt` and password `password`. When you xref:enable_auth[enable authentication] for the {WebName}, you should remove this user so that the {WebName} can only be accessed by authorized users.
./docs/topics/web-remove-default-user.adoc:14:.. Navigate to `__OPENSHIFT_URL__/console/project/rhamt/overview` in a browser.
./docs/topics/web-remove-default-user.adoc:16:NOTE: If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], replace `rhamt` with the name of your project.
./docs/topics/web-remove-default-user.adoc:20:. In the upper left corner, select the *Rhamt* realm from the drop down.
./docs/topics/web-remove-default-user.adoc:22:. From the *rhamt* user's row, click *Delete* and confirm.
./docs/topics/exclude-files-and-packages.adoc:14:* Specify the packages in a file contained within one of the xref:ignored_locations[ignored locations]. Each package should be included on a separate line, and the file must end in `.package-ignore.txt`. For example, see `_RHAMT_HOME_/ignore/proprietary.package-ignore.txt`.
./docs/topics/exclude-files-and-packages.adoc:19:{ProductShortName} can exclude specific files, such as included libraries or dependencies, during scanning and report generation. Files to be ignored are defined inside of a file ending in `.rhamt-ignore.txt` or `.windup-ignore.txt` within one of the xref:ignored_locations[ignored locations].
./docs/topics/exclude-files-and-packages.adoc:34:* `~/.rhamt/ignore/`
./docs/topics/exclude-files-and-packages.adoc:36:* `_RHAMT_HOME_/ignore/`
./docs/topics/plugin-run-windup.adoc:1:[[execute_rhamt]]
./docs/topics/optimize-performance.adoc:15:* Specify a comma-separated list of the packages to be evaluated by {ProductShortName} using the `--packages` argument on the `__RHAMT_HOME__/bin/rhamt-cli` command line. If you omit this argument, {ProductShortName} will decompile everything, which has a big impact on performance.
./docs/topics/method-discover.adoc:5:image::RHAMT_AMM_Methodology_446947_0617_ECE_Discover.png[Red Hat Migration Methodology: Discover]
./docs/topics/web-openshift-troubleshoot.adoc:17:. Access the OpenShift console by navigating to `__OPENSHIFT_URL__/console/project/rhamt/overview`. If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], be sure to replace `rhamt` in this URL with the name of your project.
./docs/topics/web-openshift-troubleshoot.adoc:32:. Access the OpenShift console by navigating to `__OPENSHIFT_URL__/console/project/rhamt/overview`. If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], be sure to replace `rhamt` in this URL with the name of your project.
./docs/topics/web-openshift-troubleshoot.adoc:35:. Click the name of the pod that you wish to examine. To examine the current {WebName} pod, select the `rhamt-web-console-__POD_NAME__` that is in a `Running` state.
./docs/topics/web-openshift-troubleshoot.adoc:48:rhamt-postgresql-1-hfbdn 1/1 Running 0 1d
./docs/topics/web-openshift-troubleshoot.adoc:49:rhamt-sso-1-build 0/1 Completed 0 1d
./docs/topics/web-openshift-troubleshoot.adoc:50:rhamt-web-console-1-build 0/1 Completed 0 1d
./docs/topics/web-openshift-troubleshoot.adoc:51:rhamt-web-console-1-vt7s5 1/1 Running 1 1d
./docs/topics/web-openshift-troubleshoot.adoc:55:In the above example this is `rhamt-web-console-1-vt7s5`.
./docs/topics/web-openshift-troubleshoot.adoc:68:oc logs __POD_NAME__ > ./rhamt-openshift-__POD_NAME__.log
./docs/topics/web-openshift-troubleshoot.adoc:119:error: update acceptor rejected rhamt-web-console-executor-1: pods for rc 'rhamt/__POD_NAME__' took longer than 600 seconds to become available
./docs/topics/install.adoc:4:. Download the {CLIName} from the link:https://developers.redhat.com/products/rhamt/download[{ProductShortName} Download page].
./docs/topics/install.adoc:7:The extracted directory is known as xref:about_home_var[`_RHAMT_HOME_`] in this guide.
./docs/topics/review-reports.adoc:11:$ __RHAMT_HOME__/bin/rhamt-cli --input /home/username/rhamt-cli-source/test-files/jee-example-app-1.0.0.ear/ --output /home/username/rhamt-cli-reports/jee-example-app-1.0.0.ear-report --target eap:6 --packages com.acme org.apache
./docs/topics/web-change-admin-user.adoc:14:.. Navigate to `__OPENSHIFT_URL__/console/project/rhamt/overview` in a browser.
./docs/topics/web-change-admin-user.adoc:16:NOTE: If you renamed the OpenShift project when xref:deploy_rhamt_app_openshift[deploying], replace `rhamt` with the name of your project.
./docs/topics/rhamt-extension-vscode-che-mvp.adoc:1:[[rhamt_extension_for_visual_studio_code_and_eclipse_che]]
./docs/topics/rhamt-extension-vscode-che-mvp.adoc:6:For more information about link:https://marketplace.visualstudio.com/items?itemName=redhat.rhamt-vscode-extension[the extension], visit the Visual Studio Markteplace.
./docs/topics/web-access-console.adoc:4:Once xref:starting_console[started], the {WebName} is accessible from a browser by default on the local host at http://localhost:8080/rhamt-web.
./docs/topics/web-access-console.adoc:9:The {WebName} uses a default user to automatically authenticate. The default user's credentials are `rhamt` and `password`. See xref:config_auth[Configuring Authentication for the {WebNameTitle}] to require individual users to authenticate in order to access the {WebName}.
./docs/topics/manually-test-rules.adoc:8:$ __RHAMT_HOME__/bin/rhamt-cli [--sourceMode] --input __INPUT_ARCHIVE_OR_FOLDER__ --output __OUTPUT_REPORT_DIRECTORY__ --target __TARGET_TECHNOLOGY__ --packages __PACKAGE_1__ __PACKAGE_2__ __PACKAGE_N__
./docs/topics/plugin-identify-resolve-issues.adoc:12:. Click *Run* to xref:execute_rhamt[execute {ProductShortName}].
./docs/topics/add-rule-to-rhamt.adoc:4:A {ProductName} rule is installed by copying the rule to the appropriate {ProductShortName} folder. {ProductShortName} scans for rules, which are files that end with `.windup.xml` or `.rhamt.xml`, in the following locations.
./docs/topics/add-rule-to-rhamt.adoc:8:* The `__RHAMT_HOME__/rules/` directory. xref:about_home_var[`__RHAMT_HOME__`] is the directory where you install and run the {ProductName} executable.
./docs/topics/add-rule-to-rhamt.adoc:10:* The `${user.home}/.rhamt/rules/` directory. This directory is created by {ProductShortName} the first time it is executed and contains rules, add-ons, and the {ProductShortName} log.
./docs/topics/add-rule-to-rhamt.adoc:12:NOTE: For Windows, this directory would be `\Documents and Settings\__USER_NAME__\.rhamt\rules\` or `\Users\__USER_NAME__\.rhamt\rules\`.
./docs/topics/web-openshift-deploy.adoc:1:[[deploy_rhamt_app_openshift]]
./docs/topics/web-openshift-deploy.adoc:4:. Download the {WebName} from the link:https://developers.redhat.com/products/rhamt/download[{ProductShortName} Download page].
./docs/topics/web-openshift-deploy.adoc:7:The path to the directory created by unzipping this file is referred to as `_RHAMT_HOME_` throughout this guide.
./docs/topics/web-openshift-deploy.adoc:16:.. Define a `Project Name`, such as `rhamt`.
./docs/topics/web-openshift-deploy.adoc:19:.. Click the **Browse** button and import the desired {WebName} template. These are included in `__RHAMT_HOME__/openshift/templates`. Once imported, the JSON is visible in the bottom text area.
./docs/rules-development-guide/master.adoc:17:// Use of RHAMT_HOME in this Guide
./docs/rules-development-guide/master.adoc:20:// RHAMT Rules
./docs/rules-development-guide/master.adoc:52:include::topics/add-rule-to-rhamt.adoc[leveloffset=+2]
./docs/rules-development-guide/master.adoc:86:// Review the Existing RHAMT XML Rules
./docs/cli-guide/master.adoc:17:// About the RHAMT_HOME Variable
./CONTRIBUTING.adoc:1:= RHAMT Documentation Contributing Guide
./CONTRIBUTING.adoc:3:Improvements to the RHAMT documentation are welcome.
./CONTRIBUTING.adoc:7:Use the following steps to submit a change to the RHAMT documentation repository.
./CONTRIBUTING.adoc:69:.. A member of the RHAMT documentation team will merge or provide feedback on your request.
./CONTRIBUTING.adoc:83:NOTE: The RHAMT documentation team can use the `buildGuide.sh` script located in each guide's directory. Since this script relies on an internal build tool, other contributors should use the `asciidoctor` command to build the guides.
./CONTRIBUTING.adoc:87:The RHAMT guides are published on the link:https://access.redhat.com/documentation/en/red-hat-application-migration-toolkit/[Red Hat Customer Portal].
./CONTRIBUTING.adoc:90:// Members of the RHAMT documentation team can review the process for publishing the RHAMT guides here: TODO.
./CONTRIBUTING.adoc:92:The RHAMT documentation team handles publishing the guides to the Customer Portal.
./CONTRIBUTING.adoc:217:The RHAMT documentation defines several AsciiDoc attributes in the `docs/templates/document-attributes.adoc` file. This allows you to define the value one place and then used it repeatedly throughout the guides. An example usage of this is defining the RHAMT version.
./CONTRIBUTING.adoc:234:The RHAMT version is {ProductVersion}.
./CONTRIBUTING.adoc:237:This will be resolved as "The RHAMT version is 4.0.0.Final".
./README.adoc:1:= Red Hat Application Migration Toolkit (RHAMT) Product Documentation
./README.adoc:5:This repository holds the official documentation for Red Hat Application Migration Toolkit (RHAMT), which is based on Windup. These guides are published on the link:https://access.redhat.com/documentation/en/red-hat-application-migration-toolkit/[Red Hat Customer Portal].
./README.adoc:11:See the link:https://github.com/windup/windup-documentation/blob/master/CONTRIBUTING.adoc[RHAMT Documentation Contributing Guide] for information on how to contribute to this repository.
./README.adoc:15:To log an issue against the RHAMT documentation, open a link:https://issues.jboss.org/projects/WINDUP/issues[JIRA] with the *Component* field set to *Documentation*.