What is new in this release
The WSO2 API Manager version 2.5.0 is the successor of version 2.2.0. It contains the following new features and enhancements:
- Support for decentralized Gateway capabilities via the WSO2 API Microgateway, a simplified lightweight version of the API Gateway that allows a specific set of APIs to run in isolation on a Microgateway. For more information on the Microgateway, when and how to use it, and how to troubleshoot it, see the relevant sections under Working with the API Microgateway.
- Ability to add a set of custom attributes when creating an application in the API Store.
- Ability to optimize an API-M profile while starting the API Manager server.
- Ability to use REST APIs to retrieve APIs by Microgateway.
What has changed in this release
Removed features and functionalities
No features/functionality have been removed in this release.
Deprecated features and functionalities
This release includes the following features/functionalities that were deprecated, which may be removed in a future release. To view previously deprecated features, see the About this Release page of the previous version.
Gateway Manager profilePrior to WSO2 API Manager 2.1.0, the Publisher and Gateway were required to be on two different cluster domains. However, from WSO2 API Manager 2.1.0 onwards, clustering is no longer a necessity because the Publisher can play the role of the Gateway Manager. Therefore, the Gateway Manager profile (
-Dprofile=gateway-manager)has now been deprecated as it is redundant.
When proper Database Administrative (DBA) practices are followed, the systems (except analytics products) are not granted DDL (Data Definition) rights on the schema. Therefore, maintaining the
-DSetupoption is redundant and typically unusable. As a result, WSO2 has deprecated the
-DSetupoption. Note that the proper practice is for the DBA to run the DDL statements manually so that the DBA can examine and optimize any DDL statement (if necessary) based on the DBA best practices that are in place within the organization.
Analyzing Logs with the Log Analyzer was deprecated from the WSO2 API-M 2.2.0 release onwards and is disabled by default.
This section lists out the features that were updated or introduced newly to WSO2 API-M 2.5.0 via WUM updates.
The following are the features that were updated or newly introduced through WUM updates.
Updated and newly introduced features The date of the update Support for additional extension properties that map a SOAP operations October 4, 2018 Working with Observability November 24, 2018 Defining a custom user claim as the group extractor claim January 8, 2019 Support for any encryption algorithm other than RSA with the cipher tool August 26, 2019
Compatible WSO2 product versions
WSO2 API-M 2.5.0 is based on WSO2 Carbon 4.4.32 and is expected to be compatible with any of the WSO2 products that are based on any Carbon 4.4.x version, except when using WSO2 Identity Server as a Key Manager, you need to specifically use WSO2 Identity Server 5.6.0 when working with WSO2 API-M 2.5.0. If you get any compatibility issues, please contact team WSO2. For information on the third-party software required with API-M 2.5.0, see Installation Prerequisites. For more information on the products in each Carbon platform release, see the Release Matrix.
For a list of fixed issues, see WSO2 API Manager 2.5.0 - Fixed Issues in Github.
For a list of known issues, see WSO2 API Manager 2.5.0 - Known Issues in Github.