Manual Migration Process
|
Standard Support for Mule 4.1 ended on November 2, 2020, and this version of Mule reached its End of Life on November 2, 2022, when Extended Support ended. Deployments of new applications to CloudHub that use this version of Mule are no longer allowed. Only in-place updates to applications are permitted. MuleSoft recommends that you upgrade to the latest version of Mule 4 that is in Standard Support so that your applications run with the latest fixes and security enhancements. |
After learning how to prepare for a migration, it is important to understand the high-level migration steps.
- Note
-
For an assisted migration with the Mule Migration Assistant, start instead from the user documentation (on GitHub), which links to the MMA user documentation.
For a completely manual migration:
-
Add all required modules, such as the Database connector, to the Anypoint Studio 7 palette.
Notes:
-
You can add modules through the Studio 7 palette. Other modules are available in Anypoint Exchange.
-
All Mule projects are Mavenized by default when you add the modules to your project.
-
-
Migrate all the global configurations.
-
Migrate configuration properties.
-
Learn how the components work in Mule 4 to see what has changed from Mule 3.
-
Understand how changes to the Mule message structure (attributes, payload, and variables) affect your configurations. See Introduction to Mule 4: The Mule Message.
-
Update your expressions and scripts to DataWeave version 2:
-
Be aware of changes between DataWeave 1 and DataWeave 2, for example, importing specific function modules and understanding syntax changes. See Migrating from DataWeave 1.0 to 2.x.
-
Change MEL expressions to DataWeave 2, for example, in an connector or Choice component. See Migrating MEL to DataWeave.
-
-
Update all exception handling to Mule 4 with the new exception types that are available.
-
If you are working with APIs, understand how to set HTTP status codes.