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) to PDC 15.1.

For information about the supported upgrade paths for PDC, see BRM Compatibility Matrix. Ensure that you are upgrading PDC from a supported patch set.

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 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.
Install the recommended version of WebLogic Server on the machine on which PDC is installed. Perform all of the steps in "Installing and Configuring Oracle WebLogic Server" to install the new version of WebLogic Server.
Set the JAVA_HOME environment variable. See "Setting the JAVA_HOME Environment Variable".
Enable JRE permissions. See "Enabling JRE Permissions".

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 upgrading 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 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.

The version displayed should be the recommended version from the BRM Compatibility Matrix.

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.

Setting the JAVA_HOME Environment Variable

Set the JAVA_HOME environment variable to the recommended version of JRE/JDK before running any PDC processes. See BRM Compatibility Matrix for the recommended version of JRE/JDK.

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.
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.

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 eXtensions
          permission javax.management.MBeanTrustPermission "register";
};

Save and close the file.

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 Remote Console.
Click Edit Tree, then Environment, and then Servers.

The Summary of Servers appears.
Select the server in which you want to deploy PDC.
Click the General subtab.
Turn on SSL Listen Port Enabled.
In the SSL Listen Port field, enter a free port number.
Click Save.
Click the shopping cart at the top right, and then click Commit Changes to commit your changes.
Restart the WebLogic Server domain.

See "Specify Listen Ports" in Oracle WebLogic Remote Console Online Help for more information.

Configuring the SSL Protocol Version

In a production environment, Oracle recommends using the SSL protocol for sending and receiving messages.

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.

When PDC is acting as a server, you can set the minimum protocol version of TLS to be used by specifying the following as a command-line option in the WebLogic Server startup parameters.

You can set the minimum version to TLS 1.2 using this command:

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

You can set the minimum version to TLS 1.3 using this command:

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

Note:

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

WebLogic Server supports both TLS 1.2 and TLS 1.3 by default when PDC is acting as a client, so no configuration is necessary to set that value.

See "Specifying the SSL/TLS Protocol Version" in Administering Security for Oracle WebLogic Server for more information.