Database access

The application stores data about content and users in its database. It can also be configured to use another data source, such as an LDAP database, to authenticate user accounts when people log in.

Application database

The application database is designed to store content data (such as content, properties for widgets, and application settings) as well as user data (including the contents of user profiles). The application can optionally use its own database to store credentials for authenticating users.

Analytics database

Using analytics (an optional add-on), community managers can capture and analyze data about their community's use. This database is modeled as a star schema of the sort used by other applications that support data warehousing.

User data

When installing Jive, you can specify that it should use an external data store for getting the list of users and groups who will be using the application. The application can use this data store to authenticate people when they log in. By default, LDAP and Active Directory are supported.

Note: Even if the application is using an external data store for authentication, information about users (profile information and permissions, for example) is kept in the application database.

Customizing

Developers can add tables to the application database and access them from within plugin code.