Open a terminal and run the following command, passing the test file as an input argument and a directory for the output report. $ cp /home//migration-rules/rules/ /rules/ Testing the rule This ruleset looks for the class-loading element in a jboss-web.xml file, which is no longer valid in JBoss EAP 6Īn MTA rule is installed by placing the rule into the appropriate directory.Ĭopy the file to the /rules/ directory. The rule is now complete and should look like the following example. The class-loading element is no longer valid in the jboss-web.xml file. Provide a hint with an informative message and a link to documentation that describes the migration details.
Include database in meta mtasa software#
Because applications may contain custom libraries or components, MTA allows you to write your own rules to identify use of components or software that may not be covered by the existing ruleset.Īdd a classification with a descriptive title and a level of effort of 1. MTA provides a comprehensive set of standard migration rules out-of-the-box. MTA rules use the following rule pattern: MTA builds a data model based on the rule execution results and stores component data and relationships in a graph database, which can then be queried and updated as needed by the migration rules and for reporting purposes. MTA uses rules internally to extract files from archives, decompile files, scan and classify file types, analyze XML and other file content, analyze the application code, and build the reports. In fact, the MTA analysis process is implemented using MTA rules. The Migration Toolkit for Applications (MTA) contains rule-based migration tools that analyze the APIs, technologies, and architectures used by the applications you plan to migrate. Forking and cloning the Migration Toolkit for Applications XML rules Adding a rule to the Migration Toolkit for Applications Reviewing the Migration Toolkit for Applications quickstarts