All WSO2 products are shipped with embedded H2 databases for storing data. These default databases are located in the
<PRODUCT_HOME>/repository/database directory of the product pack.
Explained below are the default databases that you will find in the
- Carbon database:
WSO2CARBON_DB.h2.dbis the main Carbon database in a WSO2 product. This stores registry and user management data by default. In addition, if the product uses features of WSO2 Identity Server or WSO2 Enterprise Store (ES), data which are specific to those will by default reside in the embedded Carbon database. However, for production environments, we recommend you to use separate RDBMS databases to store identity-related and storage-related data.
- Product-specific databases: In addition to the main Carbon database, your product may have other databases for storing product specific data.
Changing the default databases
The embedded H2 databases shipped with your product are suitable for development, testing, and some production environments. For most production environments, we recommend you to use an industry-standard RDBMS such as Oracle, PostgreSQL, MySQL, MS SQL, etc. Further, if you have features of WSO2 Identity Server or WSO2 Enterprise Store (ES) in your product, it is recommended to use separate RDBMSs for each, i.e., identity-related and storage-related data.
WSO2 products are shipped with scripts for creating the required tables in the Carbon database as well as other required databases. The scripts for creating tables for user management and registry data are stored in the
<PRODUCT_HOME>/dbscripts folder. If product-specific databases are required, and if features of WSO2 Identity Server or WSO2 Enterprise Store (ES) are used in the product, there will be subfolders in the
<PRODUCT_HOME>/dbscripts directory with separate scripts.
To change the default database settings according to the above recommendation, you simply have to set up new physical databases, point the product server to the new databases by updating the relevant configuration files in the product, and create the required tables using the scripts provided in the product pack. See the following sections for instructions: