Understanding the Database Tier

Waveset stores all of its provisioning and state information in the Waveset repository. The repository is comprised of tables that store all the configuration data about Waveset. It is a single point for Waveset to look up data and lock objects. The repository also contains an audit log, which is a history of actions taken in Waveset. Waveset data is stored as XML. The repository can reside in local files or a relational database, although in production, a relational database is required.

See Repository Database Servers in Oracle Waveset 8.1.1 Release Notes for a list of supported database servers.

Note that, beyond a minimal amount of identity information about individual users, user data is not kept in Waveset. Instead, only those attributes that are needed to identify and differentiate users within Waveset (for example, name and email address) are saved in the repository.

Waveset can connect to the repository over a direct JDBC connection, or it can use data source functionality made available by your application server.

The Waveset Service Provider feature requires an additional LDAP repository for storing user information. See Understanding Waveset Service Provider System Architecture for details.