Red Hat Summit이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 2. Getting Started
2.1. Prerequisites
Before installing the CLI, verify that you meet the following prerequisites.
- OpenJDK 1.8, OpenJDK 11, Oracle JDK 1.8, Oracle JDK 11
- A minimum of 4 GB RAM; 8 GB recommended
If you are running macOS, it is recommended to set the maximum number of user processes, maxproc, to at least 2048, and the maximum number of open files, maxfiles, to 100000.
2.2. Install the CLI
- Download the CLI from the RHAMT Download page.
- Extract the ZIP file to a directory of your choice.
The extracted directory is known as RHAMT_HOME in this guide.
2.3. Run the CLI
Use the following steps to run RHAMT against your application.
-
Open a terminal and navigate to the
RHAMT_HOME/bin/directory. Execute the
rhamt-cliscript, orrhamt-cli.batfor Windows, and specify the appropriate arguments../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
$ ./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.apacheCopy to Clipboard Copied! Toggle word wrap Toggle overflow -
--input: The application to be evaluated. See the--inputargument description. -
--output: The output directory for the generated reports. See the--outputargument description. -
--source: The source technology for the application migration. See the--sourceargument description. -
--target: The target technology for the application migration. See the--targetargument description. -
--packages: The packages to be evaluated. This argument is highly recommended to improve performance. See the--packagesargument description.
See RHAMT Command-line Arguments for a detailed description of all available command-line arguments.
-
- Access the report.
See RHAMT Command Examples below for examples of commands that use source code directories and archives located in the RHAMT GitHub repository.
RHAMT Command Examples
Running RHAMT on an Application Archive
The following command analyzes the com.acme and org.apache packages of the jee-example-app-1.0.0.ear example EAR archive for migrating from JBoss EAP 5 to JBoss EAP 7.
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
$ 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.apacheRunning RHAMT on Source Code
The following command analyzes the org.jboss.seam packages of the seam-booking-5.2 example source code for migrating to JBoss EAP 6.
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
$ RHAMT_HOME/bin/rhamt-cli --sourceMode --input /path/to/seam-booking-5.2/ --output /path/to/report-output/ --target eap:6 --packages org.jboss.seamRunning Cloud-readiness Rules
The following command analyzes the com.acme and org.apache packages of the jee-example-app-1.0.0.ear example EAR archive for migrating to JBoss EAP 7. It also evaluates for cloud readiness.
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
$ 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.apacheOverride RHAMT Properties
To override the default Fernflower decompiler, pass the -Dwindup.decompiler argument on the command line. For example, to use the Procyon decompiler, use the following syntax:
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
$ RHAMT_HOME/bin/rhamt-cli -Dwindup.decompiler=procyon --input INPUT_ARCHIVE_OR_DIRECTORY --output OUTPUT_REPORT_DIRECTORY --target TARGET_TECHNOLOGY --packages PACKAGE_1 PACKAGE_2RHAMT CLI Bash Completion
The RHAMT CLI provides an option to enable bash completion for Linux systems, allowing the RHAMT command-line arguments to be auto completed by pressing Tab when entering the commands. For instance, when bash completion is enabled, entering the following displays a list of available arguments.
RHAMT_HOME/bin/rhamt-cli [TAB]
$ RHAMT_HOME/bin/rhamt-cli [TAB]Enable Bash Completion
To enable bash completion for the current shell, execute the following command. After the prompt returns, follow the steps in Run the CLI.
source RHAMT_HOME/bash-completion/rhamt-cli
$ source RHAMT_HOME/bash-completion/rhamt-cliEnable Persistent Bash Completion
The following commands allow bash completion to persist across restarts; however, if bash completion is desired for the current shell then the steps in Enable Bash Completion must be followed.
To enable bash completion for a specific user across system restarts, include the following line in that user’s
~/.bashrcfile.source RHAMT_HOME/bash-completion/rhamt-cli
source RHAMT_HOME/bash-completion/rhamt-cliCopy to Clipboard Copied! Toggle word wrap Toggle overflow To enable bash completion for all users across system restarts, copy the Red Hat Application Migration Toolkit CLI bash completion file to the
/etc/bash_completion.d/directory. By default, this directory is only writable by the root user.cp RHAMT_HOME/bash-completion/rhamt-cli /etc/bash_completion.d/
# cp RHAMT_HOME/bash-completion/rhamt-cli /etc/bash_completion.d/Copy to Clipboard Copied! Toggle word wrap Toggle overflow
RHAMT Help
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:
RHAMT_HOME/bin/rhamt-cli --help
$ RHAMT_HOME/bin/rhamt-cli --help2.4. Access the Report
When you execute Red Hat Application Migration Toolkit, the report is generated in the OUTPUT_REPORT_DIRECTORY that you specify using the --output argument in the command line. Upon completion of execution, you will see the following message in the terminal with the location of the report.
Report created: OUTPUT_REPORT_DIRECTORY/index.html
Access it at this URL: file:///OUTPUT_REPORT_DIRECTORY/index.html
Report created: OUTPUT_REPORT_DIRECTORY/index.html
Access it at this URL: file:///OUTPUT_REPORT_DIRECTORY/index.htmlThe output directory contains the following files and subdirectories:
Use a browser to open the index.html file located in the report output directory. See Review the Reports for information on navigating the RHAMT reports.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}