Page History
...
You can use this pattern when you are working with a low throughput.
...
Pattern
...
1 - High Availability
Multi-node deployment with API Manager (WSO2 OB APIM, WSO2 OB KM and WSO2 Open Banking Business Intelligence ) and Key Manager (WSO2 OB BIIAM) servers.
...
Pattern
...
2
Multi-Single node deployment with API Manager (WSO2 OB APIM), Key Manager (WSO2 OB IAM), and WSO2 OB KMOpen Banking Business Intelligence (WSO2 OB BI) servers.
...
Pattern
...
2 - High Availability
Multi-node deployment with API Manager (WSO2 OB APIM), Key Manager (WSO2 OB KM and IAM), and WSO2 Open Banking Business Intelligence (WSO2 OB BI) servers.
...
Pattern
...
3
Multi-node deployment with separate Gateways, API Manager (WSO2 OB APIM), Key Manager (WSO2 OB KM IAM), and WSO2 Open Banking Business Intelligence (WSO2 OB BI) servers.
| Tip | ||
|---|---|---|
| ||
To set up and configure a HA deployment of WSO2 Open Banking API Manager, see the following topics: . |
Open ports
| Product | Port | Usage |
|---|---|---|
WSO2 Open Banking API Manager | 9763 | HTTP servlet port |
| 9443 | HTTPS servlet port | |
| 8280,8243 | NIO/PT transport ports |
Scaling the Gateway
Scaling For deployments like Pattern 3 , the Gateway requires considering can be scaled based on the load that the Gateways will handle. We We recommend that a load test be carried out on the Gateways in the environment. For more information on what factors affect the load, and how the numbers have to be derived in order to scale, see the article on Capacity Planning. Make sure to check the backends as well for the expected load.
Overview
Content Tools
Activity