WSO2 Micro Integrator 4.4.0-prealpha
Pre-releaseThe WSO2 Integration team is pleased to announce the release of the WSO2 Micro Integrator 4.4.0-prealpha
The Micro Integrator is a cloud-native, standards-based messaging engine and an integration framework with a configuration based runtime environment for integrating APIs, services, data, SaaS, proprietary, and legacy systems.
How to run
(Ignore steps 1 and 2 if you already have JDK 17 installed on your machine)
- Install JDK Version 17.
- Set the JAVA_HOME environment variable.
- Download and Extract the downloaded ZIP file.
- Go to the bin directory in the extracted folder.
Run the micro-integrator.sh file if you are on a Linux/Mac OS or run the micro-integrator.bat file if you are on a Windows OS.
What's new in Micro Integrator 4.4.0-prealpha
- New mediators
- Scatter-Gather : Clones a message into several and aggregates the responses into a single message. Supports parallel or sequential execution, with output to a variable or message body.
- Foreach v2 : Supports parallel or sequential iteration and allows updating the original array or outputting results to a variable.
- Enhanced mediator functionality
- Inline expression support for PayloadFactory Mediator and Log Mediator.
- UI Enhancements for the commonly used mediators.
- Mediator tryout functionality
- Simplified onboard experience via VSCode Extension
- Simplified Synapse expression
- Environment variable injection for all environment-specific parameters
- JDK 21 support
- Dependency management for connectors
Known Issues
All the open issues pertaining to WSO2 Micro Integrator-4.4.0-prealpha are reported here.
How You Can Contribute
Your feedback is most welcome!
Community
You can use our Discord Channel and Stackoverflow Collective to engage with a wider audience https://wso2.com/community/
Reporting Issues
We encourage you to report issues, improvements, and feature requests regarding WSO2 Micro Integrator through this repository
Important: Please be advised that the security issues must be reported to [email protected], not as GitHub issues, in order to reach the proper audience. We strongly advise following the security vulnerability reporting guideline when reporting security issues.