Posts

Showing posts from 2014

Multi Tenant API Management with WSO2 API Manager - Part 2

Image
In the previous post we discussed what is multi-tenancy, multi-tenancy in API Development and multi-tenancy in API Store(Consumption). In this post we will be discussing how subscriptions can be managed among multiple tenants, how APIs an be published into different tenant domains, multi-tenancy in API Gateway, multi-tenancy in Key Manager and also multi-tenancy in API Statistics. 
Manage subscriptions among multiple tenants
In the previous post we discussed how different tenants can develop and consume APIs in isolated views of API Publisher and API Store.This section describes how API creators can control who can subscribe to an API. In the Add API page, under Subscriptions you can select the Subscriptions Category.
There are 3 subscription categories.
Available to current Tenant Only
The API will be allowed to subscribe for users in current tenant domain only(tenant domain of API Creator).
Available to All the Tenants
The API will be allowed to subscribe for all the tenants in the deplo…

Multi Tenant API Management with WSO2 API Manager - Part 1

Image
Introduction
WSO2 API Manager provides a complete solution for API Management. With Multi-tenancy in WSO2 API Manager, organizations can collaborate and monetize their APIs across multiple entities such as departments, partners or simply between separate development groups. 
Why Multi-Tenancy

The goal of Multi Tenancy is, maximizing resource sharing among multiple tenants while providing an isolated view for each tenant.


One of the main benefits of multi-tenancy is the ability to use a single deployment for multiple tenants which lowers the cost and provides better administration. Further this is ideal for  multi departmental and multi-partner type of business settings.


Multi-Tenancy in API Development
WSO2 API Manager provides a simplified Web interface called WSO2 API Publisher for API Design, Implementation and Management. It is a structured GUI designed for API creators to design, implement, manage, document, scale and version APIs, while also facilitating more API management-related ta…

Troubleshooting Swagger issues in WSO2 API Manager

Image
WSO2 API Manager provides this functionality through the integration of Swagger (https://developers.helloreverb.com/swagger). Swagger-based interactive documentation allows you to try out APIs from the documentation itself which is available as the "API Console" in API Store. 
There are certain requirements that need to be satisfied in order to swagger Try-it functionality to work. First requirement is to enable CORS in API Mananger Store. This documentation describes how that should be done. 
But most of them face many issues in getting the swagger Try-it into work. So this blog post describes common issues faced by users with Swagger and how to troubleshoot them.  
Issue-1 API Console keeps on loading the response for ever as below.
Cause -1
API resource not supporting OPTIONS HTTP verb. 
Solution
Add OPTIONS HTTP verb for API resources as below. Then Save the API and Try again. 


Cause -2 
Backend endpoint not supporting OPTIONS HTTP verb. 
Note: You can verify this by direct…

Customizing workflows in WSO2 API Manager

Image
In WSO2 API Manager, Workflow extensions allow you to attach a custom workflow to various operations in the API Manager for
User SignupApplication CreationApplication RegistrationSubscription

By default, the API Manager workflows have Simple Workflow Executor engaged in them. The Simple Workflow Executor carries out an operation without any intervention by a workflow admin. For example, when the user creates an application, the Simple Workflow Executor allows the application to be created without the need for an admin to approve the creation process.
In order to enforce intervention by a workflow admin, you can engage the WS Workflow Executor. It invokes an external Web service when executing a workflow and the process completes based on the output of the Web service. For example, when the user creates an application, the request goes into an intermediary state where it remains until authorized by a workflow admin.
You can try out the default workflow extensions provided by WSO2…