Replicating Data Between PDC Systems

37 Replicating Data Between PDC Systems

Learn how to replicate Pricing Design Center (PDC) data from one Oracle Communications Billing and Revenue Management (BRM) system to another, such as from a development system to a test system.

Topics in this document:

About Replicating Data

You replicate PDC data by extracting data from a source PDC database and then loading the data into a destination PDC database by using the ImportExportPricing utility. See "Importing and Exporting Pricing and Setup Components" for more information.

The target system must include both the BRM server components and a PDC database. If you create a new BRM installation, do not load the sample files in the PDC_home/apps/samples/examples directory after installing PDC, where PDC_home is the directory in which the PDC software is installed.

Replicating PDC data between two BRM systems involves the following tasks:

Replicating Setup Components Managed in BRM

Some setup components are managed in BRM and are then synchronized with PDC.

To ensure that all the setup components managed in the source BRM system are synchronized with the destination BRM and PDC systems, extract the setup components from the source BRM database and load them into the destination BRM database by using the BRM load utilities. When you replicate the PDC data, these components will be synchronized with the destination PDC system.

Table 37-1 lists the type of setup components that are managed in BRM and their corresponding load utilities.

Table 37-1 Setup Components Managed in BRM and Their Corresponding Load Utilities in BRM

Setup Component Type	BRM Load Utility
Service	pin_deploy
Account	pin_deploy
Event	pin_deploy
G/L ID	load_pin_glid
Tax Supplier	load_tax_supplier
Provisioning Tag	load_config_provisioning_tags

Replicating Data Between PDC Databases

To replicate data:

Extract the service, account, event, and profile attribute specifications from the source PDC database and load them into the destination PDC database by doing the following:
1. Export the service, account, event, and profile (if applicable) attribute specifications from the source PDC database by running the following command:
```
ImportExportPricing -export -metadata
```
  The service, account, event, and profile (if applicable) attribute specifications are exported to the export_meta_config.xml file.
  
  Note:
  
  Do not change the internal IDs of the exported attribute specifications.
2. Ensure that the transformation engines are running. See the discussion about starting the transformation engines in PDC Installation Guide for more information.
3. Import the exported attribute specifications from the export_meta_config.xml file into the destination PDC database by running the following command:
```
ImportExportPricing -import -metadata export_meta_config.xml
```
Run the SyncPDC utility by doing the following:
1. Go to the BRM_Integration_Pack_Home/apps/syncpdc directory.
2. Enter the following command:
```
startSyncPDC
```
  The Enter Key Password prompt appears.
3. Enter the password PDC uses for accessing the PDC alias key in the keystore (BRM_Integration_Pack_Home/apps/conf/pdc.jks).
Extract all the setup components that are defined in PDC from the source PDC database and load them into the destination PDC database by doing the following:
1. Export all the setup components from the source PDC database by running the following command:
```
ImportExportPricing -export -config
```
  The setup components are exported to the export_config.xml file.
2. Import the exported setup components from the export_config.xml file into the destination PDC database by running the following command:
```
ImportExportPricing -import -config export_config.xml
```
Extract all the pricing components from the source PDC database and load them into the destination PDC database by doing the following:
1. Export all the pricing components from the source PDC database by running the following command:
```
ImportExportPricing -export -pricing
```
  The pricing components are exported to the export_pricing.xml file.
2. Import all the pricing components from the export_pricing.xml file into the destination PDC database by running the following command:
```
ImportExportPricing -import -pricing export_pricing.xml
```