2 Configuring Subscriber Data Storage

This chapter describes how to set up data storage for Oracle Communications Service Broker applications.

About Subscriber Data Persistence

The Subscriber Store can use one of the following types of persistence mechanisms:

• Oracle Berkeley DB

• Oracle Database 11g

The persistence mechanism that the Subscriber Store uses depends on which persistence package is installed in the Service Broker domain. By default, the Berkeley DB persistence package is installed. Therefore, to complete the Subscriber Store persistence implementation with Berkeley DB, you only need to configure the file storage locations and settings for the managed servers in your deployment.

Alternatively, to switch to Oracle Database storage, you must install the package and then set up the database connections for each managed server.

The following steps provide an overview of how to configure persistence for the Service Broker Subscriber Store. See configuring data storage information in Oracle Communications Service Broker Installation Guide for more details.

Configuring Oracle Berkeley DB Persistence

Oracle Berkeley DB is a file-based persistence mechanism that stores data in the local file system.

To configure Oracle Berkeley DB file-based persistence for the Subscriber Store:

1. Verify that the Berkeley DB package is installed in the domain as follows:

   1. In the Administration Console, expand the Domain Management node.

   2. Click the Packages node.

   3. Verify that the package list includes the following package:

      oracle.ocsb.app.rcc.service.subscriber_store.providers.store.config_bdb

2. If the managed servers in the domain are not already configured to use Berkeley DB persistence, configure the settings for the domain. For more information on configuring Berkeley DB settings for managed servers, see Oracle Communications Service Broker Installation Guide.

Configuring Oracle Database 11g Persistence

To configure the Subscriber Store to use Oracle Database 11g for data persistence:

1. Remove the existing Subscriber Store persistence package from the domain. By default, it is:

   oracle.ocsb.app.rcc.service.subscriber_store.providers.store.config_bdb

2. Install the Oracle Database persistence package:

   oracle.ocsb.app.rcc.service.subscriber_store.providers.store.config_db

3. Make sure the run level for the package matches that of the following package:

   oracle.ocsb.app.rcc.service.subscriber_store.core

4. Configure the database schema for the Subscriber Store using the following SQL script:

   Oracle_home/ocsb/admin_console/scripts/database/subscriber_store.sql

   To use the script to configure your database schema, run the script using the SQL client tool or interface provided by your database management system.

5. If the managed servers in the domain are not already configured to connect to the database, configure the connections in the Data Store node under Domain Management.

   For the Subscriber Store database, the connection pool name value in the JDBC configuration should be oracle_driver.

   See Oracle Communications Service Broker Installation Guide for more information about configuring data storage.