Systems | Development | Analytics | API | Testing

WSO2 API Manager 4.1 offers a new and enhanced user interface called Advanced Configurations through Admin Portal for administrative users to easily configure feature-related central configurations. In previous WSO2 API Manager versions the same configuration, which was previously known as Tenant Configuration, was accessible through the management console using the registry. Now with the introduction of the Advanced Configuration user interface with schema validation capabilities, all the administrative tasks related to API Manager features can be done through the Admin Portal.

This video explains how to expose an integration SOAP service as a managed API through WSO2 API Manager using its Service Catalogue feature. In the video, we talk about where this feature is useful, and then we demonstrate how you can achieve it using WSO2 API Manager 4.1.0, WSO2 MI 4.1.0, and WSO2 Integration Studio.

Third party API support is one of the new features introduced in WSO2 API Manager 4.1.0. Traditionally, the APIs in API Manager are deployed in the API gateway. For instances where the API is deployed elsewhere and there is no requirement to deploy it in the API gateway, third-party APIs can be used. Therefore, the information of the externally deployed API such as the external endpoints and the external developer portal URL (if available) can be exposed to the developers along with a documentation with the use of third-party APIs.