Pull content migration esb mi
Why upgrade to WSO2 API-M 4.1.0?¶
Listed below are some of the advantages of moving to API-M 4.1.0 from the ESB.
-
The Micro Integrator of API-M 4.1.0 is now the most improved version of the battle-tested WSO2 ESB runtime.
Tip
WSO2 ESB 5.0, the ESB profile of WSO2 EI 6.x, the Micro Integrator of WSO2 EI 7.x, as well as the Micro Integrator of WSO2 API-M 4.0.0 and WSO2 API-M 4.1.0 contains the same version of WSO2 ESB runtime.
-
All the ESB runtimes of WSO2 can use the same developer tool (WSO2 Integration Studio) for developing integrations.
-
All the integration capabilities that you used in the ESB can be used in the Micro Integrator with minimal changes.
-
The Micro Integrator contains improvements to ease your product experience.
Note
The Toml-based configuration strategy in API-M 4.1.0 replaces the XML configurations in previous versions of the ESB runtime. Some of the features are removed from WSO2 Micro Integrator as they are not frequently used.
Upgrading to WSO2 API-M 4.1.0 is recommended for the following requirements:
- You need to expose integrations as managed APIs so that integration solutions can be managed and monetized in an API marketplace.
- You need to switch to a microservices architecture from the conventional centralized architecture.
- You need a more lightweight, user-friendly version of the battle-tested WSO2 ESB.
- You need a more lightweight, container-friendly runtime in a centralized architecture.
- You need native support for Kubernetes.
Before you begin¶
Note the following:
- Ports are different in the Micro Integrator of API-M 4.1.0. Find out about ports in the Micro Integrator.
-
The Micro Integrator of API-M 4.1.0 contains changes that impact your migration process. Be sure to read the Comparison: ESB vs the Micro Integrator before you start the migration.
-
Note that API-M 4.1.0 does not allow manual patches. You can use WSO2 Updates to get the latest fixes or updates for this release.
- The BPS profile does not exist in the latest version of MI and we recommend that you use an alternate product for complex long running processes they are running on BPS. Alternately, you can continue to use BPS until it reaches end-of-life.