Upgrading Pricing Design Center Software

7 Upgrading Pricing Design Center Software

Learn how to upgrade one or more of the following Oracle Communications Pricing Design Center (PDC) components to 12.0 or to a 12.0 patch set: the PDC software or Oracle Communications Billing and Revenue Management (BRM) Integration Pack.

Topics in this document:

About Upgrading PDC

You can upgrade PDC in GUI mode or silent mode. Upgrading PDC in silent mode lets you perform a non-interactive upgrade of PDC. You can use the silent mode to upgrade PDC quickly.

A PDC upgrade must be performed by a user who has permissions to write to the oraInventory directory and the Middleware_home/user_projects/domains directory, where Middleware_home is the directory in which the Oracle Middleware components are installed.

Upgrading PDC in GUI Mode

The steps for upgrading PDC by using the GUI depend on the PDC components you choose to upgrade:

To upgrade both PDC and BRM Integration Pack installed on the same machine, select the Upgrade-Complete installation option. See "Upgrading Both PDC and BRM Integration Pack".
To upgrade only PDC to the 12.0 release, select the Pricing Design Center Upgrade installation option. See "Upgrading Only the PDC Software".
To upgrade only BRM Integration Pack to the 12.0 release, select the BRM Integration Pack Upgrade installation option. See "Upgrading Only BRM Integration Pack".

Upgrading Both PDC and BRM Integration Pack

To upgrade an existing PDC and BRM Integration Pack installation on the same machine:

Obtain the PDC software. See "Downloading the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which the existing PDC installation was deployed, if it is not already started.
Ensure that the PDC database is running.

Note:

Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
Go to the temp_dir directory, and run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar jarfile
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - jarfile is pdcserver-12.0.0.0.0_generic.jar for PDC 12.0 and pdcserver-12.0.0.x.0_generic_full.jar for PDC 12.0 patch sets. For example, pdcserver-12.0.0.1.0_generic_full.jar for PDC 12.0 Patch Set 1 and pdcserver-12.0.0.2.0_generic_full.jar for PDC 12.0 Patch Set 2.
- To start the GUI installer and install PDC using the oraInventory directory in a different location:
```
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar jarfile -record -destinationFile path
```
  where path is the response file location and name.
The Welcome screen appears.
Click Next.

The Installation Location screen appears.
Enter the full path or browse to the directory in which you want to install PDC and BRM Integration Pack for PDC 12.0 or the 12.0 patch set.

Note:

Ensure that you do not enter the path to the same directory in which PDC 11.1 or 11.2 is installed. You can install PDC 12.0 or the 12.0 patch set in a different directory on the same machine.
Click Next.

The Select Installation Type screen appears.
Select Upgrade Complete and click Next.

The PDC WebLogic Server screen appears.
Enter the following details for the WebLogic Server domain in which you want to deploy PDC:
1. In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
3. In the User Name field, enter the WebLogic Server domain administrator user name.
4. In the Password field, enter the WebLogic Server domain administrator user password.
5. In the WebLogic Home field, enter the path to the directory in which the WebLogic Server software is installed. For example, Middleware_home/wlserver.
6. To enable secure communication for PDC, select the Enable SSL? (Recommended) check box, and in the KeyStore Location field, enter the path of the client-side KeyStore file generated from the exported public certificate using the keytool utility.
  
  For more information, see "Configuring SSL for the WebLogic Server Domain".
7. To allow the import and export of large XML files into PDC, select Apply WebLogic tuning parameters. For information about the WebLogic tuning parameters, see the installer Help.
  
  Note:
  
  If you select this check box, you must restart the WebLogic Server domain after PDC installs successfully.
Click Next.

The WebLogic Server screen appears.
Do one of the following:
- If the existing PDC installation is deployed on the WebLogic Server domain administration server, select a WebLogic Server domain administration server from the list.
- If the existing PDC installation is deployed on the WebLogic Server domain managed server, select a WebLogic Server domain managed server from the list.
Enter the following details for the PDC wallet:
1. In the Wallet Location field, enter the path to the directory in which the PDC wallet is located or is to be installed.
2. In the Wallet Password field, enter the PDC wallet password.
3. In the Confirm Wallet Password field, enter the PDC wallet password again.
Click Next.

The Pricing Design Center Schema screen appears.
Enter the following information required to connect to the PDC database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the PDC database schema.
2. In the Port Number field, enter the port number assigned to the PDC database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the PDC database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the PDC database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the PDC database user password.
5. In the Service Name field, enter the name of the PDC database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the PDC database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Pricing Design Center System User screen appears.
Enter the existing PDC user information.
1. In the User Name field, enter the name of the PDC user that you created during the PDC 11.1 or 11.2 installation.
2. In the Password field, enter the password of the PDC user that you created during the PDC 11.1 or 11.2 installation.
Do one of the following:
- If you selected Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) for usage rating during the PDC 11.1 or 11.2 installation, select Elastic Charging Engine.
- If you selected BRM real-time rating and batch rating engines for usage rating during the PDC 11.1 or 11.2 installation, select Realtime Rating and Batch Rating Engines.
Note:

If you are using real-time and batch rating engines for usage rating, and you want to use ECE for usage rating, after the PDC upgrade, install PDC with ECE and then migrate the pricing data from the source PDC database into the target PDC database.

See the discussion about migrating PDC pricing data to PDC with ECE in BRM Upgrade Guide.
Click Next.

The Migration Option screen appears.
Do one of the following:

Note:

Ensure that you select the same option that you selected during the PDC 11.1 or 11.2 installation.
- If you do not want to install the migration utility, select Do not install Migration Utility.
- To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports BRM real-time and batch rating engines, select Migrate RRE and BRE Pricing Data to PDC.
- To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports ECE, select Migrate RRE and BRE Pricing Data to PDC with ECE.
- To migrate the PDC pricing data to a PDC system that supports ECE, select Migrate PDC Pricing Data to PDC with ECE.
Click Next.

The Pricing Design Center WebLogic Server Connection screen appears.
Enter the WebLogic Server domain (the domain on which you deployed the existing PDC installation) information.
1. In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
  
  Note:
  
  If you selected a WebLogic Server domain managed server in step 11, enter the port number to the managed server.
3. In the User Name field, enter the WebLogic Server domain administrator user name.
4. In the Password field, enter the WebLogic Server domain administrator password.
5. In the WebLogic Home field, enter the path to the directory in which the WebLogic Server software is installed.
6. Do one of the following:
  - If you do not want to enable secure communication for PDC, deselect the Use SSL? check box.
  - To enable secure communication for PDC, leave the Use SSL? check box selected, and, in the Keystore Location field, enter the path of the client-side KeyStore file generated from the exported public certificate using the keytool utility.
    
    For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.

The BRM Integration Pack Wallet Location and Password screen appears.
Enter the following details for the BRM Integration Pack wallet:
1. In the Wallet Location field, enter the path to the directory in which the BRM Integration Pack wallet is located or is to be installed.
2. In the Wallet Password field, enter the BRM Integration Pack wallet password.
3. In the Confirm Wallet Password field, enter the BRM Integration Pack wallet password again.
Click Next.

The BRM Server Location screen appears.
Enter the existing BRM batch and real-time rating engine details.
1. In the BRM field, enter the path to the directory in which BRM is installed.
2. In the BRM Pipeline field, enter the path to the directory in which Pipeline Manager is installed.
3. In the Perl Home field, enter the path to the directory in which the Perl libraries are installed.
Click Next.

The BRM Pipeline Database Connection Screen appears.
Enter the following information required to connect to the BRM pipeline database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the BRM pipeline database schema.
2. In the Port Number field, enter the port number assigned to the BRM pipeline database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the BRM pipeline database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the BRM pipeline database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the BRM pipeline database user password.
5. In the Service Name field, enter the name of the BRM pipeline database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the BRM pipeline database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The PDC Cross-Reference Schema screen appears.
Enter the following information required to connect to the PDC cross-reference database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the PDC cross-reference schema.
2. In the Port Number field, enter the port number assigned to the PDC cross-reference database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the PDC cross-reference database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the PDC cross-reference database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the PDC cross-reference database user password.
5. In the Service Name field, enter the name of the PDC cross-reference database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the PDC cross-reference database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Pricing Design Center System User screen appears.
Enter the existing PDC user information.
1. In the User Name field, enter the name of the PDC user that you created during the PDC 11.1 or 11.2 installation.
2. In the Password field, enter the password of the PDC user that you created during the PDC 11.1 or 11.2 installation.
Click Next.

The Migration Cross-Reference Schema screen appears. If you selected Do not install Migration Utility in step 19, proceed to step 36.
Enter the following information required to connect to the migration cross-reference database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the migration cross-reference database schema.
2. In the Port Number field, enter the port number assigned to the migration cross-reference database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the migration cross-reference database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the migration cross-reference database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the migration cross-reference database user password.
5. In the Service Name field, enter the name of the migration cross-reference database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the migration cross-reference database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Migration User screen appears.
Enter the migration user information.
1. In the User Name field, enter the migration user name.
2. In the Password field, enter the migration user password.
Click Next.

The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.

The Installation Progress screen appears.

Note:

After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.
When the installation is done, click Next. The Installation Complete screen appears.

Note down the provided URL, because you will need it to access PDC.
Click Finish to complete and exit.
If you selected Apply WebLogic tuning parameters, you must restart the WebLogic Server domain.

See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC.

See "About Installation Logs" for information on PDC Installer logs.

Upgrading Only the PDC Software

To upgrade an existing PDC 11.x installation to PDC 12.0 or a 12.0 patch set:

Obtain the PDC software. See "Downloading the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which you PDC 11.1 was deployed, if it is not already started.
Ensure that the PDC database is running.

Note:

Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
Go to the temp_dir directory, and run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar jarfile
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - jarfile is pdcserver-12.0.0.0.0_generic.jar for PDC 12.0 and pdcserver-12.0.0.x.0_generic_full.jar for PDC 12.0 patch sets. For example, pdcserver-12.0.0.1.0_generic_full.jar for PDC 12.0 Patch Set 1 and pdcserver-12.0.0.2.0_generic_full.jar for PDC 12.0 Patch Set 2.
- To start the GUI installer and install PDC using the oraInventory directory in a different location:
```
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar jarfile -record -destinationFile path
```
  where path is the response file location and name.
The Welcome screen appears.
Click Next.

The Installation Location screen appears.
Enter the full path or browse to the directory in which you want to install PDC 12.0.

Note:

Ensure that you do not enter the path to the directory in which PDC 11.1 is installed.
Click Next.

The Select Installation Type screen appears.
Select Pricing Design Center Upgrade and click Next.

The PDC WebLogic Server screen appears.
Enter the following details for the WebLogic Server domain in which you want to deploy PDC:
1. In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
3. In the User Name field, enter the WebLogic Server domain administrator user name.
4. In the Password field, enter the WebLogic Server domain administrator user password.
5. In the WebLogic Home field, enter the path to the directory in which the WebLogic Server software is installed. For example, Middleware_home/wlserver.
6. To enable secure communication for PDC, select the Enable SSL? (Recommended) check box, and in the KeyStore Location field, enter the path of the client-side KeyStore file generated from the exported public certificate using the keytool utility.
  
  For more information, see "Configuring SSL for the WebLogic Server Domain".
7. To allow the import and export of large XML files into PDC, select Apply WebLogic tuning parameters. For information about the WebLogic tuning parameters, see the installer Help.
  
  Note:
  
  If you select this check box, you must restart the WebLogic Server domain after PDC installs successfully.
In the PDC Wallet Details screen, enter the following details for the PDC wallet:
1. In the Wallet Location field, enter the path to the directory in which the PDC wallet is located or is to be installed.
2. In the Wallet Password field, enter the PDC wallet password.
3. In the Confirm Wallet Password field, enter the PDC wallet password again.
Click Next.

The WebLogic Server screen appears.
Do one of the following:
- If the existing PDC installation is deployed on the WebLogic Server domain administration server, select a WebLogic Server domain administration server from the list.
- If the existing PDC installation is deployed on the WebLogic Server domain managed server, select a WebLogic Server domain managed server from the list.
Click Next.

The Pricing Design Center Schema screen appears.
Enter the following information required to connect to the PDC database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the PDC database schema.
2. In the Port Number field, enter the port number assigned to the PDC database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the PDC database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the PDC database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the PDC database user password.
5. In the Service Name field, enter the name of the PDC database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the PDC database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Pricing Design Center System User screen appears.
Enter the existing PDC user information.
1. In the User Name field, enter the name of the PDC user that you created during the PDC 11.1 installation.
2. In the Password field, enter the password of the PDC user that you created during the PDC 11.1 installation.
3. In the Confirm Password field, enter the PDC user password again.
Do one of the following:
- If you selected Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE) for usage rating during the PDC 11.1 installation, select Elastic Charging Engine.
- If you selected BRM real-time rating and batch rating engines for usage rating during the PDC 11.1 installation, select Realtime Rating and Batch Rating Engines.
Note:

If you are using real-time and batch rating engines for usage rating, and you want to use ECE for usage rating, after the PDC upgrade, install PDC with ECE and then migrate the pricing data from the source PDC database into the target PDC database.

See the discussion about migrating PDC pricing data to PDC With ECE in BRM Upgrade Guide.
Click Next.

The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.

The Installation Progress screen appears.

Note:

After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.
When the installation is done, click Next. The Installation Complete screen appears.

Note down the provided URL, because you will need it to access PDC.
Click Finish to complete and exit.
If you selected Apply WebLogic tuning parameters, you must restart the WebLogic Server domain.

See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC.

See "About Installation Logs" for information on PDC Installer logs.

Upgrading Only BRM Integration Pack

Note:

The BRM Integration Pack installation must be performed as the UNIX user who installed BRM; for example, pin_user.

To upgrade only BRM Integration Pack:

Obtain the PDC software. See "Downloading the PDC Software".
Start the Oracle WebLogic Server domain administration server or the WebLogic Server domain managed server on which you PDC 11.1 was deployed, if it is not already started.
Verify that you are able to connect to the BRM database.
Go to the temp_dir directory, and run one of the following commands:
- To start the GUI installer:
```
Java_home/bin/java -jar jarfile
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - jarfile is pdcserver-12.0.0.0.0_generic.jar for PDC 12.0 and pdcserver-12.0.0.x.0_generic_full.jar for PDC 12.0 patch sets. For example, pdcserver-12.0.0.1.0_generic_full.jar for PDC 12.0 Patch Set 1 and pdcserver-12.0.0.2.0_generic_full.jar for PDC 12.0 Patch Set 2.
- To start the GUI installer and install PDC using the oraInventory directory in a different location:
```
Java_home/bin/java -jar jarfile -invPtrLoc FilePath/oraInst.loc
```
  where FilePath is the path to the directory in which the oraInst.loc file is located.
- To start the GUI installer and create a silent installer response file during the installation:
```
Java_home/bin/java -jar jarfile -record -destinationFile path
```
  where path is the response file location and name.
The Welcome screen appears.
Click Next.

The Installation Location screen appears.
Enter the full path or browse to the directory in which you want to install BRM Integration Pack for the PDC 12.0 installation.

Note:

Ensure that you do not enter the path to the directory in which BRM Integration Pack for PDC 11.1 is installed.
Click Next.

The Select Installation Type screen appears.
Select BRM Integration Pack Upgrade and click Next.

The Migration Option screen appears.
Do one of the following:

Note:

Ensure that you select the same option that you selected during the PDC 11.1 installation.
- If you do not want to migrate data, select Do not install Migration Utility.
- To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports BRM real-time and batch rating engines, select Migrate RRE and BRE Pricing Data to PDC.
- To migrate the BRM real-time and batch rating engines pricing data to a PDC system that supports ECE, select Migrate RRE and BRE Pricing Data to PDC with ECE.
- To migrate the PDC pricing data to a PDC system that supports ECE, select Migrate PDC Pricing Data to PDC with ECE.
Click Next.

The Pricing Design Center WebLogic Server Connection screen appears.
Enter the WebLogic Server domain (the domain on which you deployed the existing PDC installation) information.
1. In the Host Name field, enter the IP address or the host name of the machine on which the WebLogic Server domain is configured.
2. In the Port Number field, enter the port number assigned to the WebLogic Server domain administration server.
  
  Note:
  
  If you selected a WebLogic Server domain managed server during the PDC installation, enter the port number of the managed server.
3. In the User Name field, enter the WebLogic Server domain administrator user name.
4. In the Password field, enter the WebLogic Server domain administrator password.
5. Do one of the following:
  - If you do not want to enable secure communication for PDC, deselect the Enable SSL? check box.
  - To enable secure communication for PDC, leave the Enable SSL? check box selected, and, in the Keystore Location field, enter the path of the client-side KeyStore file generated from the exported public certificate using the keytool utility.
    
    For more information, see "Configuring SSL for the WebLogic Server Domain".
Click Next.

The BRM Server Location screen appears.
Enter the existing BRM batch and real-time rating engine details.
1. In the BRM field, enter the path to the directory in which BRM is installed.
2. In the BRM Pipeline field, enter the path to the directory in which Pipeline Manager is installed.
3. In the Perl Home field, enter the path to the directory in which the Perl libraries are installed.
Click Next.

The BRM Pipeline Database Connection screen appears.
Enter the following information required to connect to the BRM pipeline database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the BRM pipeline database schema.
2. In the Port Number field, enter the port number assigned to the BRM pipeline database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the BRM pipeline database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the BRM pipeline database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the BRM pipeline database user password.
5. In the Service Name field, enter the name of the BRM pipeline database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the BRM pipeline database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The PDC Cross-Reference Schema screen appears.
Enter the following information required to connect to the PDC cross-reference database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the PDC cross-reference schema.
2. In the Port Number field, enter the port number assigned to the PDC cross-reference database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the PDC cross-reference database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the PDC cross-reference database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the PDC cross-reference database user password.
5. In the Service Name field, enter the name of the PDC cross-reference database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the PDC cross-reference database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Pricing Design Center System User screen appears.
Enter the existing PDC user information.
1. In the User Name field, enter the name of the PDC user that you created during the PDC 11.1 installation.
2. In the Password field, enter the password of the PDC user that you created during the PDC 11.1 installation.
Click Next.

The Migration Cross-Reference Schema screen appears. If you selected Do not install Migration Utility in step 9, proceed to step 24.
Enter the following information required to connect to the migration cross-reference database:
1. In the Host Name field, enter the IP address or the host name of the machine on which to create the migration cross-reference database schema.
2. In the Port Number field, enter the port number assigned to the migration cross-reference database service.
  
  Note:
  
  If you are installing a PDC 12.0 patch set and the database is SSL-enabled, enter the SSL port number in the Port Number field.
3. In the User Name field, enter the migration cross-reference database user name.
  
  This user should be the SYSDBA user or should have the following capabilities on the migration cross-reference database: grant create user, grant any role, grant any privileges, select any table to username, and grant sysdba to username.
4. In the Password field, enter the migration cross-reference database user password.
5. In the Service Name field, enter the name of the migration cross-reference database service.
  
  Note:
  
  Ensure that the Oracle Database server is in Running state. The Installer connects to the Oracle Database server to verify the information you entered is valid.
6. From the SSL list, select the type of SSL connection required for connecting to the migration cross-reference database:
  - No: SSL authentication is not required.
  - Yes-One Way: One-way SSL authentication is required. In this case, the client must authenticate the server's identity.
  - Yes-Two Way: Two-way SSL authentication is required. In this case, both the client and server must authenticate each others identity.
7. If you selected Yes-One Way or Yes-Two Way, do the following:
  - From the Wallet Type list, select the type of wallet to use for secure communication with the database: SSO or PKCS12.
  - In the Truststore Wallet Location field, enter the full path to the directory in which the database wallet is located.
  - In the Truststore Wallet Password field, enter the TrustStore wallet password to be used for secure communication.
  - In the Keytore Wallet Location field, enter the full path or browse to the directory in which the database wallet is located.
  - In the Keystore Wallet Password field, enter the KeyStore wallet password to be used for secure communication.
Click Next.

The Migration User screen appears.
Enter the migration user information.
1. In the User Name field, enter the name of the migration user that you created during the PDC 11.1 installation.
2. In the Password field, enter the password of the migration user that you created during the PDC 11.1 installation.
Click Next.

The Installation Summary screen appears.
Review the selections you have made in the preceding screens, and click Install.

The Installation Progress screen appears.

Note:

After the installation begins, clicking Stop installation stops the installation process, but the files that are already copied are not removed.
When the installation is done, click Next. The Installation Complete screen appears.

Note down the provided URL, because you will need it to access PDC.
Click Finish to complete and exit.

See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of BRM Integration Pack.

See "About Installation Logs" for information on PDC Installer logs.

Upgrading PDC in Silent Mode

Use silent install mode when you are upgrading PDC using the same configuration repeatedly. Silent install mode does not use the GUI and it runs in the background.

In this mode, you use a response file template that contains a predefined set of values to upgrade PDC and BRM Integration Pack. You can generate a response file that contains the parameters and values during the PDC GUI installation.

Creating a Response File

To create a response file:

Create the response file by doing one of the following:
- Create a copy of the response file that was generated during the GUI upgrade. See "Upgrading Both PDC and BRM Integration Pack" for more information.
  
  Note:
  
  The GUI Installer does not store passwords provided during installation in the response file. You must manually add the passwords after creating a copy of the response file.
- Create a response file using the template by running the following command:
```
Java_home/bin/java -jar jarfile -getResponseFileTemplates
```
  where:
  - Java_home is the directory in which you installed the latest supported Java version.
  - jarfile is pdcserver-12.0.0.0.0_generic.jar for PDC 12.0 and pdcserver-12.0.0.x.0_generic_full.jar for PDC 12.0 patch sets. For example, pdcserver-12.0.0.1.0_generic_full.jar for PDC 12.0 Patch Set 1 and pdcserver-12.0.0.2.0_generic_full.jar for PDC 12.0 Patch Set 2.
  A response file named oracle.communications.pdc.PricingDesignCenter.rsp is created with the default values.
You can create as many response files as needed.
Open the file in a text editor.
Modify the response file you copied by specifying the key-value information for the parameters you want in your installation.
Note:
- The response file template contains guidelines and examples on how to enter the values in the parameters.
- The Installer treats incorrect context, format, and type values in a response file as if no value were specified.
Save and close the response file.

Upgrading PDC and BRM Integration Pack in Silent Mode

To upgrade PDC software and BRM Integration Pack in silent mode:

Create the response file. See "Creating a Response File".
Copy the response file you created to the machine on which you run the silent installation.
On the machine on which you run the silent installation, go to the temp_dir directory to which you have downloaded the PDC server software pack, and run the following command:
```
Java_home/bin/java -jar jarfile -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc [parameter=value] -responseFile path -silent
```
where:
- Java_home is the directory in which you installed the latest supported Java version.
- jarfile is pdcserver-12.0.0.0.0_generic.jar for PDC 12.0 and pdcserver-12.0.0.x.0_generic_full.jar for PDC 12.0 patch sets. For example, pdcserver-12.0.0.1.0_generic_full.jar for PDC 12.0 Patch Set 1 and pdcserver-12.0.0.2.0_generic_full.jar for PDC 12.0 Patch Set 2.
- parameter=value is the name-value pair for an installation parameter, such as INSTALL_TYPE=Complete.
- path is the absolute path to the response file.
For example:
```
Java_home/bin/java -jar pdcserver-12.0.0.2.0_generic_full.jar -debug -invPtrLoc Inventory_home/oraInventory/oraInst.loc INSTALL_TYPE=Complete -responseFile /tmp/oracle.communications.pdc.PricingDesignCenter.rsp -silent
```
The upgrade runs silently in the background.

See "Verifying the Pricing Design Center Installation" for information on verifying the successful installation of PDC and BRM Integration Pack.

See "About Installation Logs" for information on the PDC Installer logs.

Restoring the Previous Installation

If your upgrade is not successful, you must restore your system to the previous installation.

To restore the previous PDC 11.1 or 11.2 installation:

Restore the WebLogic server domains directory. Use the domains directory that you backed up before the patch installation to replace the following directory:

Middleware_home/user_projects/domains
Restore the oraInventory directory. Use the oraInventory directory that you backed up before you installed PDC 12.0 or 12.0 Patch Set 1 to restore the oraInventory directory.
Restore the PDC database schema.
Restore the transformation cross-reference database schema.
Restore the migration cross-reference database schema.