Versions Compared

Old Version 23

changes.mady.by.user Former user

Saved on

compared with

New Version 24

changes.mady.by.user Former user

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Remove

...

  1. Install JDK 1.8 or later in all nodes used for the setup.

  2. In the environment variables, update the JAVA_HOME and PATH variables. For instance, you can do this by adding the following to the ~/.bashrc file in Linux or Mac:

    Code Block
    languagebash
    export JAVA_HOME="<JDK_LOCATION>"

export PATH=$PATH:$JAVA_HOME/bin
  3. Multiexcerpt
    MultiExcerptNameWUM_Instructions

    WUM_UpdatesSet up the WSO2 Update Manager (WUM). 

    • WUM is a simple command-line tool that connects to the WSO2 update service, determines which updates are new and relevant, and downloads them. You can get the latest version of the WSO2 Open Banking product packs through WUM.

      You need a WSO2 subscription to start using the WSO2 Update Manager.

    • Follow the guidelines provided in the Download WUM page to download, and install WUM in your environment. For more information on how to use WUM, see the .

        1. Add the necessary product packs using the commands given below:

        2. Update the product packs using the commands given below:

        3. Additionally, download and update the other instances of WSO2 Open Banking product.

    • The product packs reside in the <WUM_HOME>/products/<Product_Name>/<version>/full directory as <Product_name-<version>+<timestamp>.full.zip. Copy the product packs to a preferred location in each node, and extract them.

      This document refers to the file paths of the product packs for the Key Manager, API Manager, API Manager Analytics, and Enterprise Integrator as <wso2-obkm>, <wso2-obam>, <wso2am-analytics, and <wso2ei> respectively.

  4. Open the ports, as described below.
    WSO2 Open Banking consists of six instances that run in different machines/servers. It is mandatory to open the ports of each server to allow a successful data flow. The six instances mentioned below specify the ports that need to be opened.

    Instance/ProductPortUsage
    WSO2_OBAM

    		9443

    HTTPS servlet transport

    (The default URL of the management console is https://localhost:9443/carbon)

    8243

    NIO/PT transport HTTPS port.

    WSO2_OBKM9446

    HTTPS servlet transport

    (The default URL of the management console is https://localhost:9443/carbon)

    WSO2_AM_Analytics

    		9444HTTPS servlet transport
    7612Thrift TCP port to receive events from clients
    7712Thrift SSL port for secure transport where the client is authenticated
    WSO2_EI_Integrator9447HTTPS servlet transport
    8247NIO/PT transport HTTPS port.
    WSO2_EI_BPS9445

    HTTPS servlet transport

    (The default URL of the management console is https://localhost:9443/carbon)

    WSO2_OBBI_Worker9448HTTPS netty transport
    7616

    Thrift TCP port to receive events from clients

    7716Thrift SSL port for secure transport where the client is authenticated
    WSO2_OBBI_Dashboard9449HTTPS netty transport

...

Note
titleUpdating keystore:

If you are using the default keystores available in the solution, update them by removing any unnecessary or expired Root CA Certificates.

  • The keystores are available in <WSO2_OB_KM_HOME>/repository/resources/security/wso2carbon.jks and <WSO2_OB_APIM_HOME>/repository/resources/security/wso2carbon.jks.

  • List and identify problematic certificates:

    Code Block
    keytool -list -v -keystore wso2carbon.jks

  • Remove the expired certificates using the alias: 

    Code Block
    keytool -delete -alias <alias_to_remove> -keystore wso2carbon.jks
  • For Open Banking UK and Open Banking Berlin:
    • For the eIDAS regulation, remove all the existing Root CA Certificates as you only need the qualified certificates from the eIDAS Qualified Trusted Service Providers (QTSPs). See eIDAS Implementation for PSD2 Compliance, for more information.

...