Refactoring Toolkit supports three primary categories of refactoring:
This approach processes artifacts at the model level. Refactoring Toolkit reads the outputs generated during the Transform action, converting them into Java beans via the Eclipse Modeling Framework (EMF), which adheres to predefined metamodels.
The schema below illustrates the process of refactoring based on model.
Inputs for Model-Based Refactoring:
For Legacy Programs (e.g., COBOL, PL/I, RPG, ...):
For Legacy Job Control Language (JCL) Scripts:
For Legacy Control Language (CL) Scripts:
Workflow:
This approach works directly on textual artifacts, such as SQL or JSON files, generated during the Transform action.
The schema below illustrates the process of refactoring based on files.
Inputs for File-Based Refactoring:
Workflow:
Global refactoring is the final step in the refactoring process. It is a single-pass operation designed to process results from previous refactorings or to make a global action on the output project. All files from the Transform action are used as inputs, whether they were refactored or not. The schema below illustrates the process of global refactorings.
Inputs for Global Refactorings:
Workflow: