Pricing Design Center Pre-Upgrade Tasks

6 Pricing Design Center Pre-Upgrade Tasks

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

Topics in this document:

Preinstallation Tasks for the PDC Software Upgrade

Preinstallation Tasks for the PDC Software Upgrade

For information about the supported upgrade paths for PDC, see "Supported PDC Upgrades" in BRM Compatibility Matrix.

To upgrade PDC, do the following:

Shut down the current PDC instance. See "Shutting Down the Current Instance".
Make a complete offline backup of your existing PDC installation. See "Backing Up the Current Installation".
Install the compatible version of BRM on the machine on which BRM is installed.
- See "BRM Suite Compatibility" in BRM Compatibility Matrix for more information about compatible versions.
- See BRM Installation Guide for information about installing BRM.
Install the recommended version of JRE/JDK on the machine on which PDC is installed. See "Installing JRE/JDK".
Upgrade the PDC database.

If you have created a separate database for migration and transformation, upgrade the migration cross-reference database and the transformation cross-reference database. For instructions to upgrade the database, see the Oracle Database upgrade documentation.
Configure SSL for the PDC database to ensure secure communications between the PDC application and the database. See "Configuring SSL for the PDC Database".
If you have installed PDC and BRM Integration Pack on different machines, copy the client-side KeyStore (client.jks) file that you generated to the machine on which BRM Integration Pack is installed.
Undeploy the existing PDC installation deployed on the WebLogic Server domain. For instructions, see the discussion about undeploying applications in the Oracle WebLogic Server Administration Console Help.
Install the recommended version of WebLogic Server (on the machine on which PDC is installed). See "Downloading and Installing Oracle WebLogic Server".
Copy updated WebLogic library JARs to the appropriate location. See "Copying Library JARs for PDC Upgrades".
For secured communication, use an SSL-enabled data source in Oracle WebLogic Server. See "Configuring WebLogic Server to use SSL-Enabled Data Source".
Update the JDBC LLR Table Name. See "Updating JDBC LLR Table Name".
Set the JAVA_HOME environment variable. See "Setting the JAVA_HOME Environment Variable".
Enable JRE permissions. See "Enabling JRE Permissions".
Upgrade Oracle Application Development Runtime (on the machine on which PDC 11.x is installed) to the recommended version. See "Installing Oracle Application Development Runtime".
Enable the SSL port for the WebLogic Server domain in which the existing PDC 11.x is deployed, if it is not enabled during the WebLogic Server domain creation. See "Enabling the SSL Port for the WebLogic Server Domain".
Configure the minimum SSL protocol version that is enabled for SSL connection, if it is not configured during the WebLogic Server domain creation. See "Configuring the SSL Protocol Version".

Shutting Down the Current Instance

To shut down the current PDC instance:

Ensure that no users are logged in.

Users include customers, client applications, customer service representatives (CSRs), and so on.
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 upgrade, back up your existing installation.

Before installing PDC, 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 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.

Installing JRE/JDK

Install the recommended version of JRE/JDK on the machine on which you want to deploy PDC. See "PDC Software Compatibility" in BRM Compatibility Matrix for the recommended version of JRE/JDK.

To verify the JRE/JDK version:

Go to the command prompt on the machine on which you want to deploy PDC.
Enter the following command:
```
java -version
```
The Java version is displayed. For example:
```
java version "1.8.0_221"
```
If the version displayed does not start with 1.8.0_, JRE/JDK 1.8 is not installed.

For information about installing JRE/JDK, see the Oracle Java documentation.

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.

Downloading and Installing Oracle WebLogic Server

WebLogic Server is a component of the Oracle Fusion Middleware media pack. For the compatible version of WebLogic Server, see "PDC Software Compatibility" in BRM Compatibility Matrix.

For information on installing Oracle WebLogic Server and the patches (if any), see the Oracle WebLogic Server documentation on the Oracle Help Center:

http://docs.oracle.com

Copying Library JARs for PDC Upgrades

If you are upgrading from a previous PDC release, do the following:

Apply patch p26626168_122140_Generic.zip on top of your WebLogic Server 12.2.1.4 installation.
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.
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.
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:

Set the prerequisite library location to the PDC_Oracle_home/apps/lib directory.

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

Updating JDBC LLR Table Name

If 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:

Log in to WebLogic Server Administration Console.
In the Domain Structure section, expand Environment and select Servers.

The Summary of Servers page appears.
Select the server for which you want to change the LLR table name.
Click the Configuration tab.
Click the General subtab.
Click Advanced to show the advanced configuration options.
Set JDBC LLR Table Name to a different name.
Click Save.

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

Setting the JAVA_HOME Environment Variable

Set the JAVA_HOME environment variable to the recommended version of JRE/JDK before running any PDC processes.

Set the JAVA_HOME environment variable on the machine on which you want to deploy PDC. For example, in C-shell:

Open the .cshrc file in a text editor.
Add or modify the following entries:
```
setenv JAVA_HOME jre/jdk_path
```
where jre/jdk_path is the absolute path to the directory in which JRE/JDK is installed.

For example:
```
setenv JAVA_HOME /pinhome/jre/1.8.0_144
```
Save and close the file.
Update the environment by running the following command:
```
source .cshrc
```

Verify the Java version by running the following command:

$JAVA_HOME/bin/java -version

The Java version is displayed. For example:

java version "1.8.0_144"Java(TM) SE Runtime Environment (build 1.8.0_144-b07)Java HotSpot(TM) 64-Bit Server VM (build 20.60-b01, mixed mode)

To set the JAVA_HOME environment variable for the WebLogic Server domain:

Go to the Middleware_home/user_projects/domains/bin directory, where Middleware_home is the directory in which the Oracle Middleware components are installed.
Open the setDomain.sh file in a text editor.
Add or modify the following entries before the EXTRA_JAVA_PROPERTIES entry:
```
JAVA_HOME="${JAVA_HOME}"
export JAVA_HOME
```
Save and close the file.

Enabling JRE Permissions

To enable JRE permissions:

Go to the jre/jdk_path/lib/security directory.
Open the java.policy file in a text editor.

Add the following entries to the file:

grant {// JMX Java Management eXtensionspermission javax.management.MBeanTrustPermission "register";};

Save and close the file.

Installing Oracle Application Development Runtime

Oracle Application Development Runtime must be installed on the machine on which you will install PDC. For more information on the compatible version, see "PDC Software Compatibility" in BRM Compatibility Matrix.

Download Oracle Application Development Runtime from the following page:

https://www.oracle.com/tools/downloads/application-development-framework-downloads.html

For information on installing Oracle Application Development Runtime, see Oracle Fusion Middleware Installation Guide for the appropriate version.

Note:

The Oracle Fusion Middleware Application Developer Installer installs Oracle Application Development Runtime and Oracle Enterprise Manager.

Enabling the SSL Port for the WebLogic Server Domain

Before installing PDC the new version of PDC, enable the SSL port for the WebLogic Server domain in which you deployed PDC, if it is not enabled during the WebLogic Server domain creation. You must enable the SSL port even if you are not configuring SSL for the WebLogic Server domain.

To enable the SSL port for the WebLogic Server domain:

Start the WebLogic Server domain.
Log in to WebLogic Server Administration Console.
In the Environment tree, click Servers.

The Summary of Servers pane appears.
Select the server in which you want to deploy PDC.
Click the Configuration tab.
Click the General subtab.
Select the SSL Listen Port Enabled check box.
In the SSL Listen Port field, enter a free port number.
Click Save.
Log out of WebLogic Server Administration Console.
Restart the WebLogic Server domain.

See the discussion about enabling the SSL port in the Oracle WebLogic Server Administration Console Help for more information.

Configuring the SSL Protocol Version

In a production environment, Oracle recommends the TLSv1 protocol for sending and receiving messages in an SSL connection.

Note:

You need to set the same protocol version for managed servers and the administration server. Ensure that all the managed servers are down when making changes to the administration server for setting up the protocol. Oracle recommends to set the properties in the administration server and then the managed server.

To set the minimum protocol version to TLS version 1.2, specify the following as a command-line option in the WebLogic Server startup parameters:

-Dweblogic.security.SSL.minimumProtocolVersion=TLSv1.2

Note:

When you set a minimum protocol version, the TLS protocol that is enabled depend on the protocols that are configured in the SSL implementation.

See the discussion about specifying the version of the SSL protocol in the Oracle WebLogic Server documentation for more information. More information is also available in the following support article: "WebLogic 12.2.1.x Versions That Support TLS 1.3"