Try Local Setup

This document provides you with instructions on how to configure and try out WSO2 Open Banking in your local environment.

The scripts for the below local setup in the Quick Start Guide are configured for a Linux and MySQL/MSSQL environment. Notice that WSO2 Open Banking solution is applicable to Windows/Linux and MySQL/MSSQL and Oracle environments.

Prerequisites

Download OpenJDK 8 in all the nodes of the setup.
- In the environment variables, update the JAVA_HOME and PATH variables. For instance, you can do this on a Mac/Linux server by adding the following to the ~/.bashrc file:
```
export JAVA_HOME="<JDK_LOCATION>"

export PATH=$PATH:$JAVA_HOME/bin
```
Download and unzip the following files:
- wso2-obam-1.5.0.zip (WSO2 Open Banking API Manager)
- wso2-obkm-1.5.0.zip (WSO2 Open Banking Key Manager)
  Click here to see how to download the packs from WUM
  Loading
  WSO2 Updates Manager (WUM) is deprecated and will be unavailable from July 2021 onwards. WSO2 Updates is the new tool to include the solution and security improvements that are released by WSO2 Open Banking, on top of a released version. For more information, see WSO2 Updates.
  Click here to see how to update the solution via WSO2 Update tool...
  The WSO2 Update tool delivers hotfixes and updates seamlessly on top of products as WSO2 Updates. They include improvements that are released by WSO2. You need to update all the products using the relevant script.
  Go to <PRODUCT_HOME>/bin and run the WSO2 Update tool:
  
  Repeat this step for both the wso2-obkm-1.5.0 and wso2-obam-1.5.0 products.
Setup a database server using MySQL 5.7, Microsoft SQL Server 2016 or, Oracle 12c.

Setting up the databases and starting the servers

Loading

If you're setting up Open Banking for AU:

Configuring consumer authentication

By default, WSO2 Open Banking comes with basic authentication configured. For CX guideline aligned experience, you can configure Identifier-first authentication paired with a secondary identity provider. In the section above, we configured SMS OTP as the secondary identity provider.

Click here to see how it is done

Loading

Restart the Key Manager and API Manager servers after the configuration changes.

You have started the servers. Next, configure users, roles, and APIs.

Configuring users and roles

Configuring APIs

You can configure APIs through the API Publisher by signing in as a user whose role includes Internal/publisher. Follow the steps given below:Loading

Configuring a consent management application

A consent management application is configured in order to manage consents granted to an application.Loading

Try out the Customer Care Portal at https://localhost:9446/ccportal.Sign in to the Customer Care Portal with the credentials for ann@gold.com Internal/CustomerCareOfficer.

Try out the consent revocation apps in WSO2 Open Banking.

What's Next

Now that you have created the APIs that allow you to initiate payments and access account information, let's try out the flows in WSO2 Open Banking: