1. PDC Installation Guide
  2. Pricing Design Center Patch Set Installation
  3. Pricing Design Center Patch Set Pre-Installation Tasks

9 Pricing Design Center Patch Set Pre-Installation Tasks

Learn about prerequisite tasks, such as backing up your current installation, before upgrading to the latest Oracle Communications Pricing Design Center (PDC) patch set.

Topics in this document:

Pre-Installation Tasks for the PDC Patch Set Installation

Before upgrading PDC 12.0 or a PDC 12.0 patch set to a later patch set release, perform the following tasks:

  1. Shut down the current PDC instance. See "Shutting Down the Current Instance".

  2. Make a complete offline backup of your existing PDC installation. See "Backing Up the Current Installation".

  3. Install the compatible version of BRM on the machine on which BRM is installed. See "Installing BRM 12.0 Patch Sets" in BRM 12.0 Patch Set Installation Guide.

    See "BRM Suite Compatibility" in BRM Compatibility Matrix for more information about compatible versions.

  4. If you are upgrading to PDC 12.0 Patch Set 4 or later, copy the updated WebLogic library JARs to the appropriate location. See "(Patch Set 4 or later) Copying Library JARs for PDC Upgrades".

  5. Configure SSL for the PDC database to ensure secure communications between the PDC application and the database. See "Configuring SSL for the PDC Database".

  6. For secured communication, use a SSL-enabled data source in Oracle WebLogic Server. See "Configuring WebLogic Server to use SSL-Enabled Data Source".

  7. If you are upgrading to PDC 12.0 Patch Set 2 or later, update the JDBC LLR table name. See "(Patch Set 2 or later) Updating JDBC LLR Table Name".

  8. If you installed PDC on a different machine from BRM Integration Pack, copy the client-side KeyStore file (client.jks) that you generated for PDC to the machine on which BRM Integration Pack is installed.

Shutting Down the Current Instance

To shut down the current PDC instance:

  1. Ensure that no users are logged in.

    Users include customers, client applications, customer service representatives (CSRs), and so on.

  2. Stop all PDC processes.

    Only the PDC database instance should be running during the PDC installation or upgrade.

Backing Up the Current Installation

To prevent any data loss and minimize the impact of software or hardware failure during the patch installation, back up your existing installation.

Before installing a PDC 12.0 patch set, make a complete offline backup of the following:

  • The WebLogic server domains directory; by default, Middleware_home/user_projects/domains.

  • The PDC installation directory and its content: PDC_home.

  • The Oracle Inventory (oraInventory) directory. Open the /etc/oraInst.loc (Linux) file or the /var/opt/oracle/OraInst.loc (Solaris) file to find the default location of the oraInventory directory.

  • The PDC database schema. See your database documentation for more information on performing full database backups.

  • The transformation cross-reference database schema. See your database documentation for more information on performing full database backups.

    Note:

    Store this backup in a safe location. The data in these files will become necessary if you encounter any issues in the installation process.

  • The migration cross-reference database schema if installed. See your database documentation for more information on performing full database backups.

(Patch Set 4 or later) Copying Library JARs for PDC Upgrades

If you are upgrading from a previous PDC release, such PDC 11.x or PDC 12.0, to PDC 12.0 Patch Set 4 or later, do the following:

  1. Apply patch p26626168_122140_Generic.zip on top of your WebLogic Server 12.2.1.4 installation.

  2. If you will be upgrading the PDC software, copy the ojdbc8.jar file from your Oracle database installation to the PDC_Oracle_home/apps/lib directory, where PDC_Oracle_home is the ORACLE_HOME directory for your PDC installation.

  3. If you will be upgrading the BRM Integration Pack, copy the following files to the PDC_BRM_Oracle_home/apps/lib directory, where PDC_BRM_Oracle_home is the ORACLE_HOME directory for your PDC and BRM Integration Pack installation.

    • The ojdbc8.jar file from your Oracle database installation

    • Middleware_home/oracle_common/modules/oracle.xdk/xmlparserv2.jar

    • Middleware_home/oracle_common/modules/com.sun.xml.bind.jaxb-impl.jar

    • Middleware_home/oracle_common/modules/com.sun.xml.bind.jaxb-core.jar

    where Middleware_home is the ORACLE_HOME directory of your WebLogic Server installation.

  4. During the PDC and BRM Integration Pack installation process, the installer will prompt you for the directory in which your prerequisite libraries are located. You will need to enter the path where you copied the JAR files.

    Note:

    If you are upgrading from 11.x to the full version of 12.0 Patch Set 4 or later, set the prerequisite library location to the PDC_Oracle_home/apps/lib directory.

Configuring SSL for the PDC Database

You can configure secure sockets layer (SSL) for the Oracle database by creating wallets for storing certificates and then modifying the following configuration files:

  • sqlnet.ora

  • tnsnames.ora

  • listener.ora

You can use the Orapki utility to create the wallets.

For information about configuring SSL for the Oracle database, see the Oracle Database documentation.

Configuring WebLogic Server to use SSL-Enabled Data Source

You can use the Secure Sockets Layer (SSL)-enabled data source in Oracle WebLogic Server for secured communications.

You must configure WebLogic Server before configuring the data sources. For more information on configuring WebLogic Server, see the discussion about using SSL with data sources and Oracle drivers in the Oracle WebLogic Server documentation and in the following page:

https://www.oracle.com/middleware/technologies/weblogic/configure-use-jdbcdriverssl.html

(Patch Set 2 or later) Updating JDBC LLR Table Name

If you are upgrading or installing the PDC 12.0 Patch Set 2 or a later patch set, and you are using an existing database schema during installation, the Logging Last Resource (LLR) table name must be changed to avoid errors.

To change the LLR table name:

  1. Log in to WebLogic Server Administration Console.

  2. In the Domain Structure section, expand Environment and select Servers.

    The Summary of Servers page appears.

  3. Select the server for which you want to change the LLR table name.

  4. Click the Configuration tab.

  5. Click the General subtab.

  6. Click Advanced to show the advanced configuration options.

  7. Set JDBC LLR Table Name to a different name.

  8. Click Save.

For more information on LLR, see the discussion about administrative considerations and limitations for LLR data sources in the WebLogic Server documentation.