Migrating from On-Premise BRM to BRM Cloud Native

20 Migrating from On-Premise BRM to BRM Cloud Native

Learn how to migrate from an on-premise release of Oracle Communications Billing and Revenue Management (BRM) 7.5.x or 12.x to a BRM 15.0 cloud native release.

Topics in this document:

Migrating to BRM Cloud Native

To migrate from an on-premises release to BRM cloud native:

Upgrade your BRM and PDC database schemas to release 15.0:
- If you are upgrading from a 12.0 or 12.0 Patch Set 1 database schema, follow the instructions in "Installing BRM 12.0 Patch Sets" in BRM Patch Set Installation Guide.
- If you are upgrading from a 12.0 Patch Set 2 or later database schema, follow the instructions in "Upgrading Your Database Schema".
Note:
- To use an existing BRM database schema with your cloud native deployment, follow the instructions in "Deploying BRM with an Existing Schema".
- To use an existing Business Operations Center database schema, point to your existing Business Operations Center schema in the override-values.yaml file for oc-cn-op-job-helm-chart. See "Adding Business Operations Center Keys for oc-cn-op-job-helm-chart".
If you customized BRM or Billing Care, layer your customizations on top of the images provided with this release before deploying the images. For guidelines about customization, see "Customizing BRM Cloud Native Services".

Migrating from PDC On Premises to PDC Cloud Native

Before migrating your system, perform these steps:

Ensure you have upgraded your PDC on-premises release to version 12.0 Patch Set 3 or later. Follow the instructions in "Upgrading Pricing Design Center Software".
Back up your existing PDC and cross-reference database schemas.
Download and load the PDC 15.0.x cloud native images to the image repository or to the virtual machine (VM) where PDC is deployed.
Download and extract the BRM 15.0.x Helm charts.
Verify that BRM has been upgraded to the same 15.0.x cloud native version as PDC cloud native.

The following are the high-level steps for migrating PDC from an on-premises release to cloud native:

Do the following on your PDC on-premises system:
1. Stop your on-premises PDC domain.
2. (Release 15.0.0 only) Connect to your PDC database schema and rename the following tables:
  - Rename the PDCJD_WLSTORE table to PDCJD_WLSTORE_BACKUP
  - Rename the WL_LLR_ADMINSERVER table to WL_LLR_ADMINSERVER_BACKUP

In your override-values.yaml file for oc-cn-op-job-helm-chart, set the following keys to match the PDC and cross-reference database schema details for your existing on-premises release:

ocpdc:
    configEnv:
        crossRefSchemaPDCTableSpace:
        crossRefSchemaTempTableSpace:
        crossRefSchemaUserName: UserName
        pdcSchemaPDCTableSpace:
        pdcSchemaTempTableSpace:
        pdcSchemaUserName: UserName
    secretValue:
        crossRefSchemaPassword: Password
        pdcSchemaPassword: Password

Set any other mandatory keys in your override-values.yaml file. For more information, refer to "Adding PDC Keys for oc-cn-op-job-helm-chart".
Deploy the PDC 15.0.x domain to your cloud native environment:
```
helm install OpJobReleaseName oc-cn-op-job-helm-chart --namespace BrmNameSpace --values OverrideValuesFile
```
where:
- OpJobReleaseName is the release name for oc-cn-op-job-helm-chart and is used to track this installation instance. It must be different from the one used for the BRM Helm chart.
- BrmNameSpace is the namespace in which to create BRM Kubernetes objects for the BRM and Job Helm charts.
- OverrideValuesFile is the path to a YAML file that overrides the default configurations in the oc-cn-op-job-helm-chart/values.yaml file.
In your override-values.yaml file for oc-cn-helm-chart, set the ocpdc.configEnv.upgrade key to true.
Deploy the PDC 15.0.x cloud native services to your cloud native environment, and ensure that the pdc-domain pod is in completed status:
```
helm install BrmReleaseName oc-cn-helm-chart --namespace BrmNameSpace --values OverrideValuesFile
```
where:
- BrmReleaseName is the release name for oc-cn-helm-chart and is used to track this installation instance. It must be different from the one used for oc-cn-op-job-helm-chart.
- OverrideValuesFile is the path to a YAML file that overrides the default configurations in the oc-cn-helm-chart/values.yaml file.
Ensure all files are upgraded successfully. To do so, check the status of the SQL upgrade log files in pdc-brm-pvc. If there is no failure message, all files upgraded successfully.