2 Setting Up the Subscriber Store

This chapter describes how to set up the Oracle Communications Service Broker Subscriber Store.

About the Subscriber Store

The Online Mediation Controller provides a way to deliver online charging and related services to subscribers. It integrates with an OCS for online charging services and includes built-in applications that extend the OCS functionality. For example, the Balance Manager application enables subscribers to check the balance of and add value to their accounts.

To deliver subscriber-specific services, Service Broker maintains its own profile of subscribers. Subscriber profile contains subscriber-specific information required by the Service Broker's built-in applications. For example, the Balance Manager applications requires subscriber language to know in which language to compose SMS messages that it sends to the subscriber. The subscriber profile is supplemental to the subscriber data maintained the OCS.

The subscriber profile also includes an orchestration logic defining how to route subscriber sessions through applications. Orchestration logic in the subscriber profile is stored in an iFC format. Oracle recommends that you use the Service Broker Orchestration Studio to graphically create orchestration logic, and use the iFC formatted source of the orchestration logic to provision a subscriber profile in the Subscriber Store.

While conditions in the orchestration logic are mostly based on session information, they can also depend on the following subscriber data available in the Subscriber Store:

• Degraded Mode state. See "Using Degraded Mode".

• Lifecycle state. See "Using Subscriber Lifecycles" in Oracle Communications Service Broker Subscriber Store Users's Guide.

For example, you can configure the orchestration logic to route a session to the OCS only if the subscriber state is Active.

In the Online Mediation Controller you must configure the OE to use the Subscriber store as the source for subscriber profiles.

WARNING:

In the Online Mediation Controller, you can only use the Subscriber Store as the source for subscriber profiles. You cannot use the Local Subscriber Server (LSS) to store orchestration profiles.

The persistent mechanism for Subscriber Store can be a database or a file-based storage. The data store is set up by default, as part of the Service Broker post installation step. See "Configuring Data Storage" in the chapter "Post Installation Tasks" in Oracle Communications Service Broker Installation Guide.

You populate the Subscriber store using the Subscriber Provisioning Web Services API.

The Service Broker Subscriber Store is described in Oracle Communications Service Broker Subscriber Store User's Guide.

Configuration Workflow

To configure the Subscriber Store:

1. Set up the Subscriber Store and enable the Subscriber Provisioning API. See "Configuring the Subscriber Provisioning Services" in Oracle Communications Service Broker Subscriber Store User's Guide.

2. Populate the Subscriber Store with subscriber profiles. See "Using the Subscriber Provisioning API" and "Subscriber Provisioning API Reference" in Oracle Communications Service Broker Subscriber Store User's Guide.

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