Policy and Application Stores

In addition to the identity store, AM allows you to configure data stores for different types of data.

Depending on the characteristics of the different data types, it can be beneficial to store them separately from other data types, for example to allow specific tuning of the indexes in the directory server.

AM supports configuration of data stores for the following data types:

  • UMA data.

    Provides storage for UMA-related data, such as resources, labels, and pending requests.

  • Core Token Service (CTS) data.

    Provides highly available storage for sessions and tokens used by AM.

  • Policy data.

    Provides storage for policy-related data, such as policies, policy sets, and resource types.

    Warning

    If you change the policy data store, any existing policy sets and resource types will no longer be available to the realm where you made the change. Either recreate these items manually, or use Amster to export them from the old data store, then import them back after changing to the new data store.

  • Application data.

    Provides storage for application-related data, such as web and Java agent configuration, federation entities and configuration, and OAuth 2.0 clients definitions.

Tasks to Configure Policy and/or Application Stores
TaskResources

Prepare the Store(s)

You must install new DS servers for the store(s). Moreover, if you are configuring an AM instance that already has policy or application data on its configuration store, you may want to migrate that data to the new store(s).

"Preparing Policy and Application Stores"

Configure the Store(s)

Configure the newly-installed store(s) so that AM can use them.

"Setting Up Policy and Application Stores."

Read a different version of :