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. Run the following command, which upgrades the PDC database schema:

   SQL> @PricingDesignCenter.sql  

4. Exit SQL*Plus.

Perform this task if you are upgrading from PDC 11.x to PDC 12.0 Patch Set 1 or later.

If you are using ECE for usage charging, ensure that you migrate the existing offer profile data from BRM into PDC and use only PDC for configuring policy specifications.

To migrate offer profiles from BRM into PDC:

1. If you are upgrading to PDC 12.0 Patch Set 1 or later, do the following:

   1. Replace @PDC_SCHEMA_USER_NAME@ with the PDC schema user name in the PDC_home/PDC/sqlscripts/policyspecification/DatabaseLinkPrivilege.jdbc file.

   2. Run the following command as a SYS user:

      SQL> connect sysUser@databaseName
      Enter password: password
      
      SQL> DatabaseLinkPrivilege.jdbc

2. Open the PDC_home/PDC/sqlscripts/policyspecification/PolicySpecificationDataUpgrade.sql file in a text editor.

3. Specify the following parameters:

   CREATE DATABASE LINK brmpdclink
   CONNECT TO brm_dbhost_username
   IDENTIFIED BY brm_dbhost_password
   USING '(DESCRIPTION =
           (ADDRESS = (PROTOCOL = TCP)(HOST = brm_schema_hostname)(PORT = brm_schema_port_number)))
           (CONNECT_DATA =
                   (SID = brm_schema_sid)
           )
   )';

   where:

   • brm_dbhost_username is the BRM database user name.

   • brm_dbhost_password is the BRM database user password.

   • brm_schema_hostname is the BRM schema host name.

   • brm_schema_port_number is the port number assigned to the BRM schema.

   • brm_schema_sid is the SID of the BRM schema.

4. Save and close the file.

5. Ensure that the BRM and PDC databases are running.

6. Connect to the PDC 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.

7. Migrate offer profiles into PDC by running the following command:

   SQL> @PolicySpecificationDataUpgrade.sql

   The offer profiles are migrated from BRM into PDC in the PDC format as policy specifications and policy labels.

8. Type exit to exit SQL*Plus.

9. Restart WebLogic Server.

10. Export the policy specifications and policy labels to XML files by running the following command:

    ImportExportPricing -export FileNamePrefix -config POLICY_SPECIFICATION
    ImportExportPricing -export FileNamePrefix -config POLICY_LABEL

    where FileNamePrefix is the prefix to append to the beginning of the generated XML file name.

    The policy specifications and policy labels are exported to the respective XML files.

11. Verify the migrated data in the XML files and make any necessary changes if required.

12. If you make any changes in the XML files, import the policy specifications and policy labels into the PDC database by running the following command:

    ImportExportPricing -import -config POLICY_LABEL filename
    ImportExportPricing -import -config POLICY_SPECIFICATION filename

    where filename is the name of the XML file.

    The policy specifications and policy labels are imported into the PDC database.

13. Publish the required pricing and setup components to ECE by running the following command:

    ImportExportPricing -publish POLICY_SPECIFICATION -target ece
    ImportExportPricing -publish CHARGE_OFFERING -target ece
    ImportExportPricing -publish ALTERATION_OFFERING -target ece

    The policy specifications, charge offers, and discount offers are published to ECE.

    Note:

    During PDC installation, the create database link privilege is granted to the PDC schema user. After migrating offer profiles from BRM into PDC, you can revoke the create database link privilege from the PDC schema user by running the following command as the SYS user:

    sqlplus sysUser@databaseName
    Enter password: password
    
    SQL> revoke create database link from pdc_schema_hostname;

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.

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

1. Log in to WebLogic Server Administration Console.

2. In the Domain Structure panel, click Services and Datasources.

   The available data sources are displayed.

3. Select the following data sources for which you want to enable SSL:

   • PricingDB

   • JobDispatcherDS

   • JobDispatcherPersistentDS

4. In the Configuration tab, select Connection Pool.

5. Modify the connection URL:

   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.

6. Add the following properties:

   javax.net.ssl.trustStore = path to client wallet

   javax.net.ssl.trustStoreType = wallet type

   where:

   • path to client wallet is the location of the client wallet that is used to connect to the database.

   • wallet type is 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.

7. If wallet type is PKCS12, add the following property:

   javax.net.ssl.trustStorePassword = wallet password

8. Restart the WebLogic Server domain.

9. Log in to the PDC application.

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

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.

Update the JAVA_HOME path to the latest recommended Java Development Kit (JDK) version for the following PDC and BRM Integration Pack utility files:

• PDC_home/apps/bin/setEnv.sh

• BRM_Integration_Pack_home/apps/bin/startRRETransformer

• BRM_Integration_Pack_home/apps/bin/startBRETransformer

• BRM_Integration_Pack_home/apps/bin/startSyncPDC

• BRM_Integration_Pack_home/apps/bin/MigrateBRMPricing

See "Additional PDC Software Requirements" in BRM Compatibility Matrix for the recommended JDK version for each release.

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.

When you run SyncPDC after upgrading to Patch Set 6 or later, changes are made to add tax code handling in PDC. See "Tax Codes Are Now Created in PDC" in Patch Set Release Notes for more information.