Restricting access to the Studio and Provisioning Service databases

The Studio database stores the Studio data sources, applications, and configuration. The Provisioning Service also has an associated database. Access to these databases should be restricted to prevent corruption of the data.

By default:

Studio uses a Hypersonic database. For a production environment, you must change to either an Oracle or a MySQL database.
The Provisioning Service uses a Derby database. For a production environment, you must change to an Oracle database. You should then also disable the Derby database in WebLogic Server.

For both Studio and the Provisioning Service, only the account used to communicate with the respective databases should have write access.

The only exception to this is when you create a new database schema in order to change to a different database. Once the database is up and running, the write access should be removed.

See the Studio Installation Guide for information on configuring permissions before and after changing the Studio database.

For details on securing an Oracle database, see the Oracle Database Security Guide.

For details on securing a MySQL database, see the MySQL Security Guide.