This site contains the documentation that is relevant to older WSO2 product versions and offerings.
For the latest WSO2 documentation, visit https://wso2.com/documentation/.

Configuring Databases for Berlin

Once you have successfully prepared the environment for the deployment, you can configure the databases.

  1. Create the following databases:

      1. openbank_am_configdb   
      2. openbank_apimgt_statsdb

      3. openbank_apimgtdb

      4. openbank_openbankingdb

      5. openbank_govdb

      6. openbank_iskm_configdb       

      7. openbank_userdb

     If you are setting up the WSO2 Open Banking Business Intelligence server...

    The WSO2 Open Banking Business Intelligence is an OSGi-based product. Therefore, when you integrate third-party products such as Oracle, MS SQL or PostgreSQL with the Business Intelligence server, you need to check whether the libraries you need to add are OSGi based. If they are not, you need to convert them to OSGi bundles before adding them to the  <WSO2_OB_BI_HOME>/lib  directory.

    To convert the jar files to OSGi bundles, follow the steps below.

    1. Download the non-OSGi jar for the required third party product, and save it in a preferred directory in your machine.

    2. Go to the <WSO2_OB_BI_HOME>/bin directory. Run the command given below to generate the converted file in the<WSO2_OB_BI_HOME>/lib directory. 

    ./jartobundle.sh <PATH_TO_NON-OSGi_JAR> ../lib
  2. Update data type of the INPUTS field in AM_APPLICATION_REGISTRATION table using the SQL file according to your database. The SQL scripts are available in the <WSO2_OB_IAM_HOME>/dbscripts/apimgt directory. (mysql.sql, mssql.sql, oracle.sql, postgresql.sql)

    If you are using Microsoft SQL, do the following changes, in addition to the step above.

    Update the IDN_OIDC_REQ_OBJECT_REFERENCE table in <WSO2_OBKM_HOME>/dbscripts/apimgt/mssql.sql file, by replacing the following lines:

    1. Replace FOREIGN KEY (CONSUMER_KEY_ID) REFERENCES IDN_OAUTH_CONSUMER_APPS(ID) ON DELETE CASCADE with

      FOREIGN KEY (CONSUMER_KEY_ID) REFERENCES IDN_OAUTH_CONSUMER_APPS(ID)
    2. Replace FOREIGN KEY (TOKEN_ID) REFERENCES IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) with

      FOREIGN KEY (TOKEN_ID) REFERENCES IDN_OAUTH2_ACCESS_TOKEN(TOKEN_ID) ON DELETE CASCADE
  3. To create the database schema, execute the following scripts against the given database: