This documentation is for WSO2 Enterprise Store version 1.0.0. View documentation for the latest release.

Unknown macro: {next_previous_link3}
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Current »

WSO2 products provide scripts for installing and configuring several types of relational databases, including MySQL, IBM DB2, Oracle, and more. Each of these databases supports stored procedures, which allow business logic to be embedded inside the database as an API, providing a powerful mechanism to interact with a relational database. Because these procedures are stored in a precompiled format within the database itself, execution speed is very fast. Client programs can be restricted to accessing a database via stored procedures only, thereby enforcing fine-grained security, preservation of data integrity, and improved productivity.

The default database of user manager is the H2 database that comes with WSO2 products. You can configure it to point to databases by other vendors such as IBM DB2, Oracle, MySQL using the scripts provided by WSO2 for installing and configuring relational databases. The scripts in <PRODUCT_HOME>/dbscript/ folder are available in all WSO2 products. They store data related to WSO2 Carbon, on top of which all WSO2 products are built. 

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

All common Carbon based databases are supported by any of the listed DBs. However, the JAGH2 database in WSO2 ES is only supported by the H2 and MySQL. While, the SOCIAL_CACHE database is supported by H2.

 

  • No labels