8 Pricing Design Center Post-Upgrade Tasks

Learn how to perform tasks, such as creating users or synchronizing pricing setup components, after upgrading Oracle Communications Pricing Design Center (PDC).

After upgrading your existing PDC installation to PDC 15.1.0 or a later 15.1 release, do the following:

  1. Upgrade your PDC database schema to the new schema. See "Upgrading the PDC Database Schema".

  2. If you are using Oracle Communications Billing and Revenue Management (BRM) Elastic Charging Engine (ECE) for usage rating, upgrade to the compatible version of ECE on the machine on which ECE is installed. See "Installing Elastic Charging Engine" in ECE Installation Guide.

    See BRM Compatibility Matrix for more information about compatible versions.

  3. (Optional) Restrict the tablespace quota for a schema user. The default tablespace quota is unlimited. See "Restricting Tablespace Quota for a Schema User".

  4. Configure Oracle WebLogic Server to use the SSL-enabled data source. See "Configuring WebLogic Server to use SSL-Enabled Data Source".

  5. Configure PDC to use the secure sockets layer (SSL)-enabled data source. See "Configuring PDC to Connect to SSL-Enabled Database".

  6. (Optional) Configure Security Assertion Markup Language (SAML) to enable single sign-on (SSO) for PDC. See "Setting Up Single Sign-On for Pricing Design Center".

  7. Run additional SQL scripts. See "Running the BRM Integration Pack Scripts".

  8. Start the transformation engines. See "Starting the Transformation Engines".

  9. Run the SyncPDC utility. See "Running SyncPDC".

    This synchronizes the setup components defined in other BRM components with PDC.

Upgrading the PDC Database Schema

To upgrade the PDC database schema:

  1. Go to the PDC_home/server/upgrade/schema/pdc directory.

  2. Enter the following command, which opens SQL*Plus:

    sqlplus pdcUser@databaseName
Enter password: password

    where:

    • pdcUser is the PDC database user name.

    • password is the PDC database user password.

    • databaseName is the service name or database alias of the PDC database.

  3. In SQL*Plus, run the following command, which upgrades the PDC database schema:

    @PricingDesignCenter.sql

Restricting Tablespace Quota for a Schema User

PDC grants unlimited tablespace quota to the following schema users:

  • PDC schema

  • Transformation cross-reference schema

  • Migration cross-reference schema

You can restrict the quota limit for a schema user in a tablespace by using SQL*Plus.

To restrict the tablespace quota for a schema user:

  1. Connect to your database using SQL*Plus:

    sqlplus pdcUser@databaseName
Enter password: password

    where:

    • pdcUser is the PDC database user name.

    • password is the PDC database user password.

    • databaseName is the service name or database alias of the PDC database.

  2. At the SQL*Plus prompt, enter the following command:

    SQL> alter user schema_user_name  quota size on tablespace_name;

    where:

    • schema_user_name is the PDC schema user name.

    • size is the tablespace quota size.

    • tablespace_name is the name of the tablespace for the PDC schema user.

    For example:

    SQL> alter user schema_user_name quota 500k on data_ts;

  3. Type exit to exit SQL*Plus.

Configuring WebLogic Server to use SSL-Enabled Data Source

To use the SSL-enabled data source in WebLogic Server:

  1. Log in to WebLogic Remote Console.

  2. Click Edit Tree, then Services, and then Data Sources.

    The available data sources are displayed.

  3. For each of the following data sources, perform the following steps:

    • PricingDB

    • JobDispatcherDS

    • JobDispatcherPersistentDS

    1. Click the data source to update, then click the Connection Pool subtab.

    2. In the General tab, modify the Url field: 

      jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCPS)(HOST = hostname)(PORT = ssl-port))(CONNECT_DATA=(SERVICE_NAME=SID)))

      where:

      • hostname is the name of the machine on which the database is installed.

      • ssl-port is the SSL-enabled port to use for connecting to the database.

      • SID is the unique name of the Oracle database.

    3. Click Save.

    4. Click Properties under the data source you are updating in the tree in the left pane.

    5. Click New.

    6. In the Name field, enter: 
      javax.net.ssl.trustStore

    7. Click Create.

      A window that allows you to add a value to the new property appears.

    8. In the Value field, enter the location of the client wallet that is used to connect to the database.

    9. Click Save.

    10. Click New.

    11. In the Name field, enter: 
      javax.net.ssl.trustStoreType

    12. Click Create.

      A window that allows you to add a value to the new property appears.

    13. In the Value field, enter the type of the client wallet, such as SSO and PKCS12. If the extension of the client wallet is .sso, the wallet type is SSO and if the extension of the client wallet is .p12, the wallet type is PKCS12.

    14. Click Save.

    15. If wallet type is PKCS12, do the following:

      1. In the Name field, enter: 

        javax.net.ssl.trustStorePassword

      2. In the Value field, enter the wallet password.

      3. Click Save.

    16. Click the shopping cart Cart icon at the top right, and then click Commit Changes to commit your changes.

    17. Restart the WebLogic Server domain.

  4. Log in to the PDC application.

    If you cannot log in to the PDC application, verify the WebLogic Server configuration that you have performed.

Configuring PDC to Connect to SSL-Enabled Database

To connect to the SSL-enabled database securely for synchronizing, transforming, and migrating the PDC data, you must specify the SSL port number and the database TrustStore details in the following configuration files:

  • SyncPDCConfiguration.xml

  • TransformationConfiguration.xml

  • MigrationConfiguration.xml

To connect to the SSL-enabled database:

  1. Open the BRM_Integration_Pack_home/apps/configurationfile file.

    where:

    • BRM_Integration_Pack_home is the directory in which BRM Integration Pack is installed.

    • configurationfile is:

      • SyncPDCConfiguration.xml

      • TransformationConfiguration.xml

      • MigrationConfiguration.xml

  2. Uncomment the trustStore and truststoreType section to connect to the database securely: 

    <dbSSLConfiguration>
	     <trustStore>databaseTruststoreLocation</trustStore>
     <trustStoreType>databaseTruststoreType</trustStoreType>
</dbSSLConfiguration>

    where:

    • databaseTruststoreLocation is the path to the client wallet which is used to connect to the database securely.

    • databaseTruststoreType is the type of the trustStore used to connect to the database securely:

      If databaseTruststoreLocation is Wallet_Home/cwallet.sso, the databaseTruststoreType is SSO.

      If databaseTruststoreLocation is Wallet_Home/ewallet.p12 , the databaseTruststoreType is PKCS12.

  3. Specify the SSL port number in the connectionInfo section for all the databases, such as the migration cross-reference database and transformation cross-reference database. For example: 

    <xrefDatabase>
<connectionInfo>
...
<port>SSL_Port</port>
...
</connectionInfo></xrefDatabase>

  4. Save and close the file.

  5. Go to the BRM_Integration_Pack_home/apps/bin directory.

  6. Run the following command, which updates the database TrustStore password in the BRM Integration Pack wallet:

    ./PDCBRMWalletUtil.sh walletlocation walletpassword DB_TRUSTSTORE_PASSWORD password

    where:

    • walletlocation is the location in which the BRM Integration Pack wallet is located.

    • walletpassword is the BRM Integration Pack wallet password.

    • password is the database TrustStore password.

  7. At the command prompt, enter Y.

    The database TrustStore password is added to the BRM Integration Pack wallet.

Running the BRM Integration Pack Scripts

Perform the following steps:

  1. Go to the BRM_Integration_Pack_home/sqlscripts/pdc_brm directory, where BRM_Integration_Pack_home is the directory in which BRM Integration Pack is installed.

  2. Enter the following command, which opens SQL*Plus:

    sqlplus XrefUser@XrefDBName
Enter password: password

    where:

    • XrefUser is the user name for the XREF database schema.

    • XrefDBName is the database alias of the XREF database.

    • password is the password for XrefUser.

  3. Run the following commands:

    @AddProrateCycleXrefRRECharges.sql
@CleanXrefDiscountMaster.sql
@CreateXrefRRETaxCodeTable.sql
@CreateXrefRRETaxExemptionCodeTable.sql
@CreateXrefRRETaxSelectorTable.sql
@CreateXrefRREPriceTagConfigTable.sql
@AddGlidColToXREF_RRE_TAX_CODE.sql

  4. Type exit to exit SQL*Plus.

Starting the Transformation Engines

The transformation engines do not automatically start when you start the PDC server, you must start them manually. See the discussion about starting the transformation engines in BRM System Administrator's Guide for more information.

Running SyncPDC

You must run the SyncPDC utility to synchronize the setup components defined outside of PDC.

See "Synchronizing Pricing Setup Components" in PDC Creating Product Offerings for more information.

If you are upgrading from PDC 12.0 Patch Set 5 or earlier, when you run SyncPDC after upgrading, changes are made to add tax code handling in PDC. See "Tax Codes Are Now Created in PDC" in Patch Set Release Notes for BRM 12.0 for more information.