PDC REST Services Manager Overview

About PDC REST Services Manager

PDC REST Services Manager integrates an enterprise product catalog, such as Oracle Digital Experience for Communications Launch Experience, with PDC. This enables you to create a variety of product offerings in your enterprise product catalog and then have all the rating and billing performed by PDC and Oracle Communications Billing and Revenue Management (BRM).

You can synchronize the following elements from an enterprise product catalog to PDC:

One-time, recurring, and usage charges, with or without discounts
Charge and discount offers with one-time, recurring, usage, and rollovers charges and discounts (without selectors and product specifications)
Quantity and tier-based pricing and discounting
Quantity ranges (without common properties)
Pricing tags
Effective dates for charges and discounts
Noncurrency balance credits, with or without one-time or recurring fees and overages
Discounts used as counters for noncurrency balance credits to charge overage fees
Validity periods for discounts and noncurrency balance credits
Shared discounts
Charges based on event and service attributes
Generic selectors and charge selectors
Charge selectors with value maps
Packages and bundles containing multiple charge offers and discounts
Subscription terms for packages and bundles
Custom attributes (also called product specification characteristics or product specification attributes)

Note:
To include custom attributes in product offerings synchronized from your enterprise product catalog, you must first create the attributes in a configuration template file and import the file into PDC. See "Configuring Product Specification Attributes for Pricing Components" in PDC Creating Product Offerings.

The enterprise product catalog publishes the product offering objects to registered billing-spoke systems using TMF 620 APIs. PDC REST Services Manager synchronizes this data and transforms it into charge offers, discount offers, bundles, and packages in the PDC-BRM system.

Figure 1-1 shows the PDC REST Services Manager architecture and its integration points with the enterprise product catalog and PDC.

Figure 1-1 PDC REST Services Manager Architecture

Description of "Figure 1-1 PDC REST Services Manager Architecture"

In this figure, PDC REST Services Manager, the enterprise product catalog, and PDC interact as follows:

The enterprise product catalog sends a notification to PDC REST Services Manager about new or updated product offerings. This communication can be encrypted using TLS.
This event notification can optionally include a TMF 620-compliant payload with product and discount definitions, pricing information, and lifecycle status updates. See "Inbound Communications Reference" for information about these events and their payloads.
PDC REST Services Manager uses OAuth 2.0 to authenticate the notification from the enterprise product catalog.
The PDC REST Services Manager event listener sends the authenticated message to the PDC REST Services Manager product offering integration service.
PDC REST Services Manager requests an OAuth token to use with a call to the enterprise product catalog.
PDC REST Services Manager calls the enterprise product catalog TMF 620 API to query for data about the new or updated product offerings.
If the TMF 620 event notification payload already includes the full details, this step is skipped.
PDC REST Services Manager transforms the product offering data and submits it to PDC and BRM. This communication can be encrypted using T3S.
If the TMF 620 event notification payload includes the full details, the flow ends here.
If PDC REST Services Manager queried the product offering data from the enterprise product catalog, the product offering integration service sends a message to the PDC REST Services Manager acknowledgment service.
PDC REST Services Manager requests an OAuth token to use with a call to the enterprise product catalog.
PDC REST Services Manager publishes an acknowledgment notification to the enterprise product catalog.

Throughout all interactions, you can log, trace, and collect metrics for messages passing through the system. You can use this data to troubleshoot errors and monitor the system's overall health. See "Monitoring PDC REST Services Manager".

About Setting Up PDC REST Services Manager

You set up PDC REST Services Manager by performing the following high-level tasks:

Install PDC REST Services Manager. See "Installing Only PDC REST Services Manager" in PDC Installation Guide.
Set up PDC REST Services Manager security. This includes setting up authentication for requests from your enterprise product catalog with OAuth and securing communication between PDC REST Services Manager and other applications with TLS and T3S protocols. See "PDC REST Services Manager Security" in BRM Security Guide.
Create setup components in all applications, then map the product offerings from the TMF 620 API fields in your enterprise product catalog to equivalent fields in PDC and BRM. See "Mapping Product Offerings".

About Monitoring PDC REST Services Manager

You can monitor PDC REST Services Manager to confirm successful integration, track overall system health, and troubleshoot issues.

Monitoring PDC REST Services Manager involves the following tasks:

Monitoring system logs. See "About Logging".
Tracing events with tools like Zipkin. See "About Tracing".
Monitoring metrics with tools like Prometheus. See "About Metrics".
Monitoring system status. See "About Monitoring System Health".