Bot releases are visible (Hide)
Published by Rajith90 almost 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG300/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda about 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG300/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG301/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG301/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Contributing Code
Read through project Contribution Guidelines to learn how to contribute with code.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG301/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://github.com/wso2/product-microgateway#microgateway-quick-start
https://docs.wso2.com/display/MG301/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://github.com/wso2/product-microgateway#micro-gateway-quick-start
https://docs.wso2.com/display/MG300/
Reporting Issues
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the Github Issues.
Mailing Lists
Join our mailing list and receive updates on product development. Developer List: [email protected]
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://docs.wso2.com/display/MG300/
The Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway with characteristics below:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
The following diagram illustrates an overview of how API Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). Running Microgateway has two main steps.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required.
GitHub Fixed Issues
All the open issues pertaining to WSO2 API Microgateway are reported at the following location:
GitHub Open Issues
Join our mailing list and correspond with the developers directly.
Developer List: [email protected]
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the public (API Microgateway Git Repo).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://docs.wso2.com/display/MG300/
The Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway with characteristics below:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
The following diagram illustrates an overview of how API Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). Running Microgateway has two main steps.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required.
GitHub Fixed Issues
All the open issues pertaining to WSO2 API Microgateway are reported at the following location:
GitHub Open Issues
Join our mailing list and correspond with the developers directly.
Developer List: [email protected]
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Microgateway through the public (API Microgateway Git Repo).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://docs.wso2.com/display/MG300/
The Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway with characteristics below:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). Running Microgateway has two main steps.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required.
GitHub Fixed Issues
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub Open Issues
Join our mailing list and correspond with the developers directly.
Developer List: [email protected]
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://docs.wso2.com/display/MG270/
The API Manager Microgateway provides the capability to create specialized gateway distributions (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Its ability to execute in isolation without mandatory connections to other components (Key Manager, Traffic Manager, etc).
Ability to host a subset of APIs of choice (defined on the API Publisher) instead of all.
Immutability - if you update an API you need to re-create the container/instance, no hot deployment.
Microgateway offers you a proxy that is capable of performing security validations (OAuth, Basic Auth, Signed JWT), in-memory (local) rate limiting and operational analytics.
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
GitHub (Product-Microgateway)
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub (Product-Microgateway)
Join our mailing list and correspond with the developers directly.
Developer List: [email protected]
User List: [email protected]
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).
--WSO2 API Manager Team--
Published by praminda over 5 years ago
https://docs.wso2.com/display/MG270/
The API Manager Microgateway provides the capability to create specialized gateway distributions (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Its ability to execute in isolation without mandatory connections to other components (Key Manager, Traffic Manager, etc).
Ability to host a subset of APIs of choice (defined on the API Publisher) instead of all.
Immutability - if you update an API you need to re-create the container/instance, no hot deployment.
Microgateway offers you a proxy that is capable of performing security validations (OAuth, Basic Auth, Signed JWT), in-memory (local) rate limiting and operational analytics.
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
GitHub (Product-Microgateway)
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub (Product-Microgateway)
Join our mailing list and correspond with the developers directly.
Developer List: [email protected]
User List: [email protected]
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).
--WSO2 API Manager Team--
Published by fazlan-nazeem over 5 years ago
https://wso2.com/api-management/api-microgateway/
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
The API Manager Microgateway provides the capability to create specialized gateway distributions (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Its ability to execute in isolation without mandatory connections to other components (Key Manager, Traffic Manager, etc).
Ability to host a subset of APIs of choice (defined on the API Publisher) instead of all.
Immutability - if you update an API you need to re-create the container/instance, no hot deployment.
Microgateway offers you a proxy that is capable of performing security validations (OAuth, Basic Auth, Signed JWT), in-memory (local) rate limiting and operational analytics.
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
GitHub (Product-Microgateway)
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub (Product-Microgateway)
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).
Published by Rajith90 about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distributions (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Its ability to execute in isolation without mandatory connections to other components (Key Manager etc).
Ability to host a subset of APIs of choice (defined on the API Publisher) instead of all.
Immutability - if you update an API you need to re-create the container/instance, no hot deployment.
Microgateway offers you a proxy that is capable of performing security validations (OAuth, Basic Auth, Signed JWT)
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
GitHub (Product-Microgateway)
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
GitHub (Product-Microgateway)
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).
Published by Rajith90 about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
https://docs.wso2.com/display/AM300/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
Published by chamilaadhi about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
Published by tharikaGitHub about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
Published by chamilaadhi about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
Published by tharikaGitHub about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.
Published by tharikaGitHub about 6 years ago
The API Manager Microgateway provides the capability to create specialized gateway distribution (Microgateway distributions) where only a single API or a group of APIs are included. Once a Microgateway distribution is started, it will start serving those specific API(s) right away.
In summary, a Microgateway is a specialized form of the WSO2 API Gateway by having below main characteristics:
Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.
https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway
Following are some of the main expectations of Microgateway
The following diagram illustrates an overview of how API Manager Microgateway works.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The Microgateway will have two main responsibilities.
These two steps will be treated as two phases. One will first complete the "setup" phase and move on to the "build" phase. The reason for treating them as phases is to make it possible for developers to take control of the runtime if and when required. For example, what gets run as default on a Microgateway is a simple API proxy. If a developer needs to perform some sort of an integration or change the Ballerina source files for some other reason, he could engage with the project after the setup phase and do the required modifications before the distribution is built.
All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:
Join our mailing list and correspond with the developers directly.
Developer List: [email protected] | Subscribe | Mail Archive
User List: [email protected] | Subscribe | Mail Archive
We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Micro Gateway through the public API Manager Microgateway Git Repo.