2 Setting Up the Subscriber Store

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

About Subscriber Data Persistence

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

• Oracle Berkeley DB (BDB)

• Oracle Enterprise Database 11g

The persistence mechanism that the local Subscriber Store uses depends on which persistence package is installed in the Service Broker domain. The interactive domain creation wizard prompts you to specify whether to use the BDB or Oracle Database persistence mechanism. Likewise, the chosen persistence mechanism can be specified for silent domain creation.

The domain creation process will install and activate the package used by the chosen persistence mechanism. The Subscriber Store supports only one type of persistence. If you choose to change or want to validate your persistence mechanism, use the instructions included in "Configuring Oracle Berkeley DB Persistence" or "Configuring Oracle Database 11g Persistence".

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. See configuring data storage information in Oracle Communications Service Broker Installation Guide for more details.

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

Configuration Overview

The general steps for setting up the Subscriber Store are:

1. Configure Subscriber Store operating settings.

2. Configure the persistence mechanism for the Subscriber Store. The Subscriber Store supports persistence in either an Oracle Berkeley or Oracle Enterprise 11g database.

3. Populate and maintain the Subscriber Store with user information.

The Subscriber Store settings consist primarily of access settings for the Subscriber Provisioning API. The API provides operations for reading, adding and managing subscriber information in the store. As a SOAP-based API, the Subscriber Provisioning API allows the Subscriber Store to be integrated with existing subscriber repositories and management applications.

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 Domain Management.

   2. Click Packages.

   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. Open the Administration Console.

2. Expand Domain Management.

3. Click Packages.

4. Remove the existing Subscriber Store persistence package from the domain by selecting this package and clicking Uninstall:

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

5. Install the Oracle Database persistence package by selecting this package and clicking Install:

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

6. Make sure the run level for the package matches that of this package:

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

7. Configure the database schema for the Subscriber Store using this 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.

8. 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.

Local Subscriber Store Configuration Workflow

To configure the local Subscriber Store:

1. Set up the Subscriber Store and enable the Subscriber Provisioning API. See "Enabling Subscriber Provisioning Service Connectivity", for more information.

2. Populate the Subscriber Store with subscriber profiles. See "Using the Subscriber Provisioning API", for more information.

3. Configure the OE to use the Subscriber Store as a source of subscriber profiles.

   Configure the OE as described in "Configuring the Orchestration Engine" in Oracle Communications Service Broker Modules Configuration Guide. Use the following configuration data, specifically:

   1. In the General tab, in the Subscriber Profile Receiver list, select OlpCustomInfoReceiver.

   2. In the Custom OLP tab, in the Custom OPR Name field, enter UP OPR.