com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links' is unknown.

Working with Databases

Owned by Former user (Deleted)
Last updated: Oct 30, 2016
1 min read

The default databases that WSO2 products uses to store registry, user manager and product-specific data are the H2 databases in <PRODUCT_Home>/repository/database as follows:

  • WSO2CARBON_DB.h2.db: used to store registry and user manager data

  • WSO2AM_DB.h2.db:: used to store product specific data 

These embedded H2 databases are suitable for development, testing, and some production environments. For most production environments, however, we recommend you to use an industry-standard RDBMS such as Oracle, PostgreSQL, MySQL, MS SQL, etc.

You can find several subfolders inside the <PRODUCT_HOME>/dbscripts folder. These contain several .sql files which are used to create the tables required by specific features. The scripts found in the apimgt folder are related to the Product API Store feature. The scripts found in the bps folder are related to the Business Processes and Human Tasks related to the Work List functionality. The scripts found in the service-provider folder are related to the Identity Provider feature and the scripts found in the identity folder are related to the other identity functionalities such as OAuth, SCIM, OpenID and STS.

You can use the scripts provided with WSO2 products to install and configure several other types of relational databases, including MySQL, IBM DB2, Oracle, and more. 

The following sections describe the tables used in Governance Registry and explain how to change the default databases:

com.atlassian.confluence.content.render.xhtml.migration.exceptions.UnknownMacroMigrationException: The macro 'next_previous_links2' is unknown.