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 that are used in WSO2 Open Banking Key Manager (WSO2_OB_KM) and WSO2 Open Banking API ManagerĀ (WSO2_OB_APIM):

      1. openbank_am_configdbĀ  Ā 
      2. openbank_apimgt_statsdb

      3. openbank_apimgtdb

      4. openbank_openbankingdb

      5. openbank_govdb

      6. openbank_iskm_configdb Ā Ā Ā Ā Ā Ā 

      7. openbank_mbstoredb

      8. openbank_userdb

  2. Update the data type of the INPUTS field in AM_APPLICATION_REGISTRATION table in the sql file according to your database. The sql scripts are available in the <WSO2_OB_KM_HOME>/dbscripts/apimgt directory. (mysql5.7.sql, mssql.sql, oracle.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:

For more information on configuring databases, seeĀ Working with Databases.