WSO2 API Manager Microgateway Toolkit 2.5.0-UPDATE1 Released!

v2.5.0-update1

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

WSO2 API Manager Microgateway Toolkit 2.5.0 Released!

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.

Bug Fixes And Improvements in 2.5.0

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Manager Microgateway Toolkit 2.5.0-RC2 Released!

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

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-RC2

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Manager Microgateway Toolkit 2.5.0-RC1 Released!

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

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-RC1

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Micro Gateway 2.5.0-Beta2 Released!!!

The WSO2 API Manager team is pleased to announce the release of API Manager Micro Gateway 2.5.0-Beta2. It's now available to download.

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-Beta2

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Micro Gateway 2.5.0-Beta Released!!!

The WSO2 API Manager team is pleased to announce the release of API Manager Micro Gateway 2.5.0-Beta. It's now available to download.

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-Beta

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Micro Gateway 2.5.0-Alpha Released!!!

The WSO2 API Manager team is pleased to announce the release of API Manager Micro Gateway 2.5.0-Alpha. It's now available to download.

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-Alpha

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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

WSO2 API Micro Gateway 2.5.0-M1 Released!!!

The WSO2 API Manager team is pleased to announce the release of API Manager Micro Gateway 2.5.0-M1. It's now available to download.

Documentation

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

Introduction

The Microgateway is a specialized form of the WSO2 API Gateway. Its main characteristics are

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

Design Goals

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.

Architecture

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

Setting up 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.

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

Bug Fixes And Improvements in 2.5.0-M1

• 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: [email protected] | Subscribe | Mail Archive

• User List: [email protected] | Subscribe | Mail Archive

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