Skip to content

WSO2 Integrator: MI 4.6.0-M1 Released!

Pre-release
Pre-release

Choose a tag to compare

View all tags
@wso2-integration-bot wso2-integration-bot released this 06 Feb 11:33
· 448 commits to master since this release
v4.6.0-m1
8d9a0cc

The WSO2 Integration team is pleased to announce the release of the WSO2 Integrator: MI 4.6.0-M1.

The WSO2 Integrator: MI 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.

WSO2 Integrator: MI 4.6.0-M1 consists of the following main components.

Runtime

WSO2 Integrator: MI download

Tooling distributions

WSO2 Integrator: MI VSCode extension download

How to run

(Ignore steps 1 and 2 if you already have JDK 21 or 25 installed on your machine)

  1. Install JDK Version 21 or 25.
  2. Set the JAVA_HOME environment variable.
  3. Download and extract the downloaded ZIP file.
  4. Go to the bin directory in the extracted folder.
  5. 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 WSO2 Integrator: MI 4.6.0-M1

  • JDK 25 Support
  • Bouncy Castle FIPS Crypto Provider Support
  • Enable/disable Support for Scheduled Tasks
  • Prometheus 3.5.0 Compatibility
  • Support to Publish Observability Data to Moesif
  • OpenTelemetry-based Observability in Dataservices
  • OpenTelemetry Span Filtering Support for Mediators

Known Issues

All the open issues pertaining to WSO2 Integrator: MI-4.6.0-M1 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 Integrator:MI through this repository.

Important: Please be advised that the security issues must be reported to security@wso2.com, not as GitHub issues, in order to reach the proper audience. We strongly advise following the security vulnerability reporting guideline when reporting security issues.

~ WSO2 Integration Team ~

Assets 3
Loading