Optional Application Migration

FTM version 3 and IBM® App Connect Enterprise have introduced support for the following concepts that can be used with an application. Adoption of these concepts is optional.

• Libraries You may wish to split up your application actions and maps into library projects or convert existing separated projects to libraries.
• Application projects While FTM does not use application projects, you may decide they are the best option for your FTM application.
• Subflows You may wish to convert your actions and maps from msgflow files to subflow files. This can be done using the by right-clicking the msgflow and then selecting Convert to subflow.
• Native XML schema If you have existing message sets for XML data, you might prefer to package the native schemas as a library.
• DFDL Switching from MRM to DFDL is more likely suited to new projects than migration.
• Graphical data maps Adopting this mapping technology is more likely suited to new projects or maps than migration.
• FTM Workload Priority

• For more information about FTM time zone support, refer to ESQL time zone mapping functions