Versions Compared

Old Version 1

changes.mady.by.user Former user

Saved on

compared with

New Version 2

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

WSO2 Open Banking Key Manager clustered deployment takes high availability (HA) into consideration and is recommended for production deployment environments. The following sections provide high level information on the recommended deployment pattern available and point off to instructions on how to set up and configure the deployment. 

...

Tip
titleBefore you begin:

  1. Ensure high availability for the respective RDBMS and Directory Services used for the deployment pattern given below.

  2. In each production deployment, share the runtime deployment artifacts among nodes using a shared file system. In the deployment pattern defined below, this process is referred to as Artifact synchronization.

    The Runtime deployment artifacts are:

    1. Email output event publisher
      /repository/deployment/server/eventpublishers/

    2. Secondary user stores
      /repository/deployment/server/userstores/

    3. Analytics data publishers and event streams
      /repository/deployment/server/eventpublishers/
      /repository/deployment/server/eventstreams/

    4. Workflow engine related artifacts
      /repository/deployment/server/humantasks/
      /repository/deployment/server/bpel/

HA clustered deployment of WSO2 Open Banking Key Manager

This deployment can be scaled from two to N number of nodes based on capacity requirements. 

...

Tip
titleSetting up deployment

To set up and configure a clustered deployment of WSO2 Open Banking Key Manager, see Setting Up Open Banking Key Manager Deployment (200 wip).

Open ports

ProductPortUsage


WSO2 Open Banking

Key Manager

9766HTTP servlet port
9446HTTPS servlet port
4000Ports to be opened with respect to clustering membership scheme used