Bot releases are hidden (Show)
Published by fazlan-nazeem about 6 years ago
Published by malinthaprasan over 6 years ago
The Microgateway Toolkit 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.
https://docs.wso2.com/display/AM250/Configuring+the+API+Microgateway
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
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 Micro Gateway Git Repo.
Published by ruks over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.
Published by malinthaprasan over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.
Published by ruks over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.
Published by malinthaprasan over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.
Published by harsha89 over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.
Published by harsha89 over 6 years ago
https://docs.wso2.com/display/AM2xx/Configuring+the+API+Microgateway
The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are
Following are some of its main expectations of Microgateway
Ability to host just one or a selected set (subset) of APIs only.
Ability to execute in complete isolation once setup, without having the need to contact the Management or Security components.
Easy integration with CI/CD processes.
Seamless integration with deployment automation tools and techniques.
The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.
This product will include a CLI, the B7a platform distribution and a few B7a extensions (Endpoints and Filters). The CLI 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 Run 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 runtime is deployed.
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 Micro Gateway Git Repo.