Configuring the External Resources Data Store

Oracle Waveset's external resource data store is a single data store that holds information about external resources and assignments to external resources. This data store can be a database or a directory.

• If the external resource data store is a database, that data store is managed by the ScriptedJdbcResourceAdapter.

• If the external resource data store is a directory, that data store is managed the LDAPResourceAdapter.

You must have the External Resource Administrator capability to configure the external resource data store.

The external resource data store allows you to store data in whatever attribute values you want and you can store those values in one or more tables.

For example, if you are using a MySQL database, Oracle Waveset stores external resource information in the following tables:

• The extres.accounts table contains accountIDs and resourceIDs. Because external resource data store is a single data store, Oracle Waveset provides a unique ID key, <accountId>@<resourceId>, that uniquely identifies an account by its resourceID.

• The extres.attributes table contains a collection of name/value pair attributes. You define these attributes in the schema mapping when creating an external resource.

Sample scripts used to create the database tables are co-packaged with Oracle Waveset in the following location:

wshome/sample/ScriptedJdbc/External

Oracle Waveset supports multiple database types, and provides sample scripts for each type. You can modify these scripts as needed for your specific environment.

The external resource data store also supports LDAP using the LDAPResourceAdapter, which enables you to store data in existing or custom classes. A sample LDIF script is also co-packaged with Oracle Waveset in the following location:

wshome/sample/other/externalResourcePerson.ldif

You can modify this script as part of configuring an external resources directory data store.