WSO2 Open Banking 2.0 Adapts a Centralized Configuration Model

If you haven’t heard already, WSO2 Open Banking 2.0 is here!

The solution now supports updated compliance requirements, microservices and enables premium Open Banking capabilities.

The latest version of the WSO2 Open Banking solution is based on WSO2 Identity Server 5.10 and WSO2 API Manager 3.1. Both these base products have adapted a centralized configuration model and as a result of this, the Open Banking solution also switched to an easy-to-configure model. Now, all we have to do is configure 2 files to set up and run the solution.

The Open Banking solution contains two deployment.toml files (one each for Identity Server and API Manager) that contain all configurations in theTOML format.

Advantages of a Centralized Configuration Model

In a decentralized configuration model to configure a single scenario/flow, a user will have to modify several files. This could be a challenge for new users as the folder structure and files are completely new. This could also slow down the process of familiarizing yourself with the configurations in the beginning. But with the new TOML based, centralized model all it takes is to edit a single file to configure all available features. This will also help the users to easily comprehend the folder structure. Additionally, the new naming convention of the properties introduced with the centralized configuration model assist the new users as all the properties/tags are self-explanatory.

Usage of TOML

If you are using XML files for configurations, you will notice how the syntax is verbose and redundant compared to other formats. When comparing TOML with the YAML configurations, I’m sure we all can relate how the strict spacing can cause trouble. Whereas, TOML is designed to be a human-readable file format and easy to digest and edit when compared with XML and YAML. Its simple structure and the new self-explanatory naming convention improve user experience.

How to Adapt the TOML Model (for Existing Users)

This new change will have a minimal effect if you are completely new to the solution, but if you’ve been playing with the previous versions, you might wonder how to map/match all previous XML tags to the new model. Since we’ve refined some property names, there can be problematic. That’s why we came up with this XML to TOML Config mapper.

Want to Know More?

This new model is designed to enhance user experience and to minimize the configuration overhead for users. If you want to learn more about these configurations and the solution, refer to the WSO2 Open Banking documentation at https://docs.wso2.com/display/OB200, where we have explained everything you want to know about the solution. These include several other UI/UX improvements like redesigned WSO2 Open Banking API Publisher Portal, Developer Portal, and support for React JS applications to address all your Open Banking requirements.