Studio database requirements

Studio requires a relational database to store configuration and state, including component configuration, user permissions, and system settings. If you install with multiple Studio instances, all of them must be connected to the same database.

Studio supports the following database types:

Oracle 11g
Oracle 12c 12.1.0.1.0+
MySQL 5.5.3+

If you're installing BDD in a production environment, you must create the following:

A database of one of the types listed above.
A database username and password.
An empty schema. The name of this is arbitrary.

Note that BDD doesn't currently support database migration. If you decide to switch to a different type of database later on, you must reinstall BDD with a new database instance. If you're installing BDD in a non-production environment with the QuickStart option, you must use a MySQL database named studio. For more information, see QuickStart Installation.

You can optionally use a clustered database configuration. For clustering, Oracle 11g uses RAC and MySQL has MySQL Cluster. Refer to the documentation for your database system for details on setting up a clustered configuration.

Additionally:

You must install the database client on the install machine. For MySQL, this should be MySQL client. For Oracle databases, this should be Oracle Database Client, installed with a type of Administrator. Note that the Instant Client is not supported.
If you have a MySQL database, you must set UTF-8 as the default character set.
If you have an Oracle database, you must set the ORACLE_HOME environment variable to the directory one level above the /bin directory that the sqlplus executable is located in. For example, if the sqlplus executable is located in /u01/app/oracle/product/11/2/0/dbhome/bin, you should set ORACLE_HOME to /u01/app/oracle/product/11/2/0/dbhome. Note that this is different from the ORACLE_HOME property in BDD's configuration file.

Sample commands for creating Oracle and MySQL database users and schemas are available in Sample commands for production databases.

Studio database requirements in demo environments

In demo environments, Studio supports Hypersonic (HSQL) databases in addition to the types listed above. Hypersonic is an embedded database that runs inside the JVM. It is useful for getting Studio up and running quickly, but can't be used in a production environment due to performance issues and its inability to support multiple Studio nodes.

Note: The Connector Service and the Component Registry don't support Hypersonic databases, even in demo environments.

If you want to use a Hypersonic database, the installer will create it for you. You can enable this in BDD's configuration file.

Important: If you install in a demo environment with a Hypersonic database and later decide to scale up to a production environment, you must reinstall BDD with one of the supported MySQL or Oracle databases listed above.