Appendix A. Reference material

A.1. Additional resources

A.1.1. Getting involved

To help the Migration Toolkit for Applications cover most application constructs and server configurations, including yours, you can help with any of the following items.

  • Send an email to jboss-migration-feedback@redhat.com and let us know what MTA migration rules should cover.
  • Provide example applications to test migration rules.

  • Identify application components and problem areas that may be difficult to migrate.

    • Write a short description of these problem migration areas.
    • Write a brief overview describing how to solve the problem migration areas.
  • Try Migration Toolkit for Applications on your application. Be sure to report any issues you encounter.

  • Contribute to the Migration Toolkit for Applications rules repository.

    • Write a Migration Toolkit for Applications rule to identify or automate a migration process.
    • Create a test for the new rule.
    • Details are provided in the Rules Development Guide.

  • Contribute to the project source code.

    • Create a core rule.
    • Improve MTA performance or efficiency.
    • See the Core Development Guide for information about how to configure your environment and set up the project.

Any level of involvement is greatly appreciated!

A.1.3. Reporting issues with MTA

The Migration Toolkit for Applications uses JIRA as its issue tracking system. If you encounter an issue executing MTA, please file a JIRA Issue.

Note

If you do not have a JIRA user account, you must create an account in order to create a JIRA issue.

A.1.3.1. Creating a JIRA issue

  1. Open a browser and navigate to the JIRA Create issue page.

    If you have not yet logged in, click the Log In link at the top right side of the page and enter your credentials.

  2. Choose the following options and click the Next button.

    • Project

      For core MTA issues, choose Migration Toolkit for Applications (WINDUP).

      For issues with MTA rules, choose: Migration Toolkit for Applications rules (WINDUPRULE).

    • Issue Type: Bug

  3. On the next screen complete the following fields.

    • Summary: Enter a brief description of the problem or issue.
    • Environment: Provide the details of your operating system, version of Java, and any other pertinent information.
    • Description: Provide a detailed description of the issue. Be sure to include logs and exceptions traces.
    • Attachment: If the application or archive causing the issue does not contain sensitive information and you are comfortable sharing it with the MTA development team, attach it to the issue using the browse button.
  4. Click the Create button to create the JIRA issue.





Revised on 2021-01-25 11:55:42 UTC