@Rajith90 Rajith90 released this Oct 19, 2018 · 16 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 3.0.0-M2. It is now available to download.

Introduction

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)

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

Architecture

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 3.0.0-m2

GitHub (Product-Microgateway)

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

GitHub (Product-Microgateway)

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Developer List: dev@wso2.org | Subscribe | Mail Archive

User List: user@wso2.org | Subscribe | Mail Archive

Reporting Issues

We encourage you to report issues, documentation faults, and feature requests regarding WSO2 API Manager Microgateway through the public (API Manager Microgateway Git Repo).

@Rajith90 Rajith90 released this Oct 12, 2018 · 22 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 3.0.0-M1.

Introduction

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:

  • 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.

Documentation

https://docs.wso2.com/display/AM300/Working+with+the+API+Microgateway

Design Goals

Following are some of the main expectations of Microgateway

  • Ability to host just one or a selected set (subset) of APIs only.
  • Easy integration with CI/CD processes.
  • Seamless integration with deployment automation tools and techniques.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 3.0.0-m1

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

Oct 12, 2018
v2.6.0 release

@chamilaadhi chamilaadhi released this Sep 15, 2018 · 42 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC3.

Introduction

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:

  • 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 2.6.0-RC3

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

@chamilaadhi chamilaadhi released this Sep 14, 2018 · 46 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC2.

Introduction

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:

  • 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 2.6.0-RC2

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

@tharikaGitHub tharikaGitHub released this Sep 8, 2018 · 57 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-RC1.

Introduction

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:

  • 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 2.6.0-RC1

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

@tharikaGitHub tharikaGitHub released this Sep 3, 2018 · 71 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-Beta.

Introduction

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:

  • 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 2.6.0-Beta

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

@tharikaGitHub tharikaGitHub released this Sep 14, 2018 · 107 commits to master since this release

Assets 3

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway 2.6.0-Alpha.

Introduction

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:

  • 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 (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM2xx/Working+with+the+API+Microgateway

Design Goals

Following are some of the 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.

Architecture

The following diagram illustrates an overview of how API Manager Microgateway works.

microgateway-with-api-manager

Setting up Microgateway

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.

  • Setting up a Microgateway project.
  • Running the Microgateway project.

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.

Bug Fixes And Improvements in 2.6.0-Alpha

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --

Assets 3
v2.5.0-update1

[maven-release-plugin] copy for tag v2.5.0-update1
Assets 7

The WSO2 API Manager team is pleased to announce the release of API Manager Microgateway Toolkit 2.5.0.

Introduction

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:

  • Its ability to execute in isolation without mandatory connections to other components (Key Manager, Traffic Manager, Analytics).
  • Ability to host a subset of APIs of choice (defined on the API Publisher) instead of all.
  • Immutability - The gateway runtime is immutable. If APIs or Policies change after the Microgateway has been built, a rebuild process is required to capture the changes.
  • Seamless integration with deployment automation tools and techniques.
  • Easy integration with CI/CD processes.

Microgateway offers you a proxy that is capable of performing security validations (Signed JWT, OAuth), in-memory (local) rate limiting and Analytics.

Documentation

https://docs.wso2.com/display/AM250/Configuring+the+API+Microgateway

Architecture

The following diagram illustrates the process of getting an API (or a selected set of APIs) to be hosted on a Microgateway.

Architecture

Bug Fixes And Improvements in 2.5.0

Known Issues

All the open issues pertaining to WSO2 API Manager Microgateway are reported at the following location:

How You Can Contribute

Mailing Lists

Join our mailing list and correspond with the developers directly.

Reporting Issues

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.

-- The WSO2 API Manager Team --