Chapter 1. Introduction

1.1. About the Rules Development Guide

This guide is for engineers, consultants, and others who want to create custom XML-based rules for Migration Toolkit for Applications (MTA) tools.

For more information, see the Introduction to the Migration Toolkit for Applications for an overview and the CLI Guide for details.

To contribute to the MTA source code base or provide Java-based rule add-ons, see the Core Development Guide.

1.1.1. Use of <MTA_HOME> in this guide

This guide uses the <MTA_HOME> replaceable variable to denote the path to your MTA installation. The installation directory is the mta-cli-5.2.0.Final directory where you extracted the MTA .zip file.

Note

For Windows operating systems, you must extract the MTA .zip file to a folder named mta to avoid a Path too long error.

When you encounter <MTA_HOME> in this guide, replace it with the actual path to your MTA installation.

1.2. About 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. In fact, the MTA analysis process is implemented using MTA rules. 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.

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 rules use the following rule pattern:

when(condition)
  perform(action)
otherwise(action)

MTA provides a comprehensive set of standard migration rules out-of-the-box. 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.