WSO2 API Manager Components
* API Store (Developer Portal): Used by API users. Discover, register and subscribe to APIs. URL = https://localhost:9443/store.
* API Publisher: Used by API owners. Create, Publish and Manage API lifecycle. URL = https://localhost:9443/publisher.
* API Publisher: Used by API owners. Create, Publish and Manage API lifecycle. URL = https://localhost:9443/publisher.
* API Gateway: Used by API consumers. All the requests come here, and security and throttling are enforced here. URL = https://localhost:9443/carbon
* Key Manager: Used by the API Gateway to validate subscriptions, OAuth tokens, and API invocations. Provides a token API to generate OAuth tokens that can be accessed via the Gateway. URL = https://localhost:8243/token
* Traffic Manager: Used by API Gateway to enforce throttling. Features a dynamic throttling engine (Siddhi) to process throttling policies in real-time. URL = https://localhost:9443/admin
* API Manager Analytics: Provides a host of statistical graphs, an alerting mechanism on predetermined events, and a log analyzer.
WSO2 API Manager Users and Roles
* Publisher: Granted permissions to manage the full API lifecycle from creation onward.
* Creator: Granted permissions to create APIs using the API publisher and view APIs in the API Store to understand the feedback given on the developed APIs.
* Consumer: A consumer uses the API Store to discover APIs, see the documentation and forums, and rate/comment on the APIs. Consumers subscribe to APIs to obtain API keys.
* Admin: Super user with all the above privileges and administration capabilities.
Lifecycle of an API
* CREATED: API metadata is added to the API Store, but it is neither yet visible to subscribers, nor deployed to the API Gateway.
* PROTOTYPED: The API is deployed and published in the API Store as a prototype. A prototyped API is usually a mock implementation made public in order to get feedback about its usability. Users can try out a prototyped API without subscribing to it.
* PUBLISHED: The API is visible in the API Store and available for subscription.
* DEPRECATED: The API is still deployed in the API Gateway (i.e., available at runtime to existing users) but not visible to subscribers. You can deprecate an API automatically when a new version of it is published.
* RETIRED: The API is unpublished from the API Gateway and deleted from the Store.
* BLOCKED: Access to the API is temporarily blocked. Runtime calls are blocked, and the API is not shown in the API Store anymore.
API Lifecycle Visibility
Database Configuration for Distributed Deployment
APIM Database configurations across profiles https://goo.gl/N4JGD6 #DataIntegration #ML
