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

3 Pricing Design Center Pre-Installation Tasks

Learn about prerequisite tasks, such as installing and configuring the database, before installing Oracle Communications Pricing Design Center (PDC).

Topics in this document:

Pre-Installation Tasks for Installing the PDC Software for the First Time

Note:

PDC 12.0 patch sets are cumulative. The latest PDC 12.0 patch set includes all of the changes introduced since 12.0. You can install PDC 12.0 or directly install the PDC 12.0 patch sets.

Before installing the complete PDC 12.0 or 12.0 patch set software, do the following:

  1. Install and configure Oracle Database. See "Installing and Configuring Oracle Database".

  2. Install Java Runtime Environment (JRE)/Java Development Kit (JDK). See "Installing JRE/JDK".

  3. Install and configure Oracle WebLogic Server. See "Installing and Configuring Oracle WebLogic Server".

  4. Set the JAVA_HOME environment variable. See "Setting the JAVA_HOME Environment Variable".

  5. Enable JRE permissions. See "Enabling JRE Permissions".

  6. Enable compatibility view for PDC in Internet Explorer 11. See "Enabling Compatibility View in Internet Explorer 11".

  7. Install the compatible version of BRM on the machine on which you will install PDC BRM Integration Pack. See "Installing BRM" in BRM Installation Guide.

    See "BRM Suite Compatibility" in BRM Compatibility Matrix for the compatible version of BRM.

  8. Enable integration between BRM and PDC. See "Enabling BRM-PDC Integration".

Installing and Configuring Oracle Database

Oracle recommends that the installation and configuration of Oracle Database be performed by an experienced database administrator. To install and configure Oracle Database, see the Oracle Database installation documentation.

When you install the software, do the following:

  • Install Oracle Database Enterprise Edition.

  • Create the PDC database.

  • Create a database to store the transformation cross-reference tables, or use the PDC database to store the transformation cross-reference tables.

  • Create a database to store the migration cross-reference tables, or use the PDC database or the transformation cross-reference database to store the migration cross-reference tables.

  • (Optional) Create PDC tablespaces and temporary tablespaces for the following:

    • The PDC schema, to store the pricing and setup components.

    • The transformation cross-reference schema, to store tables that map pricing and setup components in PDC to the corresponding component in a target rating engine.

    • The migration cross-reference schema, to store tables that map the pricing and setup components that are migrated from the BRM database to the corresponding component in a target rating engine.

    Oracle recommends that you create separate PDC tablespaces and temporary tablespaces for each schema. However, you can use a single PDC tablespace and temporary tablespace to create all the schemas.

Setting the Database Time Zone

The PDC database must have the appropriate local time zone setting.

For more information on setting the time zone, see the Oracle Database Globalization Support Guide.

Note:

Ensure that the BRM database and the PDC database are in the same time zone.

After PDC has been installed, the database time zone cannot be changed. Ensure the time zone is correctly set before installing PDC.

Tuning the Database

Table 3-1 and Table 3-2 provide recommended database parameters for tuning your database for the PDC installation. These are the minimum requirements for PDC.

Table 3-1 Database Creation Parameters

Parameter Recommended Value

SGA+PGA

At least 4 GB in total.

Oracle recommends that you use as much memory as you have available in the machine, and also use Automatic Memory Management.

Processes

2000

Connection mode

Dedicated server

Redo log file size

1024 MB minimum

Table 3-2 Database Initialization Parameters

Parameter Recommended Value

db_file_multiblock_read_count

16

distributed_lock_timeout

7200

dml_locks

9700

job_queue_processes

10

log_buffer

31457280

open_cursors

5000

parallel_max_servers

640

plsql_code_type

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

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:

  1. Go to the command prompt on the machine on which you want to deploy PDC.

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

Installing and Configuring Oracle WebLogic Server

This section describes procedures relating to installing Oracle WebLogic Server and configuring the WebLogic Server domain in which you will deploy PDC.

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

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

If you are installing 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 installing the PDC software, copy the following files to a directory on your PDC machine:

    • The ojdbc8.jar file from your Oracle database installation

    • Middleware_home/oracle_common/modules/oracle.pki/oraclepki.jar

    • Middleware_home/oracle_common/modules/oracle.osdt/osdt_cert.jar

    • Middleware_home/oracle_common/modules/oracle.osdt/osdt_core.jar

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

  3. If you will be installing the BRM Integration Pack, copy the following files to a directory on your PDC machine:

    • The ojdbc8.jar file from your Oracle database installation

    • Middleware_home/oracle_common/modules/oracle.idm/identitystore.jar

    • Middleware_home/oracle_common/modules/oracle.jps/jps-api.jar

    • Middleware_home/oracle_common/modules/oracle.nlsrtl/orai18n.jar

    • Middleware_home/oracle_common/modules/oracle.nlsrtl/orai18n-collation.jar

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

    • Middleware_home/oracle_common/modules/oracle.xdk/xml.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

    • Middleware_home/oracle_common/modules/oracle.pki/oraclepki.jar

    • Middleware_home/oracle_common/modules/oracle.osdt/osdt_cert.jar

    • Middleware_home/oracle_common/modules/oracle.osdt/osdt_core.jar

    • Middleware_home/oracle_common/modules/javax.jms.javax.jms-api.jar

    • Middleware_home/wlserver/modules/javax.transaction.javax.transaction-api.jar

    • Middleware_home/wlserver/server/lib/wlthint3client.jar

    • Middleware_home/wlserver/server/lib/wlclient.jar

    • Middleware_home/wlserver/server/lib/wljmsclient.jar

    • Middleware_home/wlserver/server/lib/wljmxclient.jar

    • Middleware_home/wlserver/server/lib/wlnmclient.jar

    • Middleware_home/wlserver/server/lib/wlsafclient.jar

  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 installing the full version of 12.0 Patch Set 4 or later, set the prerequisite library location to the PDC_Oracle_home/apps/lib directory.

(Patch Set 7 or later) Applying WebLogic Server Patch

If you are installing PDC 12.0 Patch Set 7 or later, install Patch 33903365 on top of your WebLogic Server installation.

To apply the WebLogic Server patch:

  1. Apply patch p33903365_122140_Generic.zip on top of your WebLogic Server 12.2.1.4.0 installation.

  2. Restart WebLogic Server.

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.

Creating the Oracle WebLogic Server Domain

Before creating a WebLogic Server domain, use the Oracle Fusion Middleware Repository Creation Utility (RCU) to create the required Oracle Identity and Access Management (IAM) database schema. See Fusion Middleware Repository Creation Utility User's Guide for more information on RCU.

To create a WebLogic Server domain in which to deploy PDC, see the description of using the Configuration Wizard in the Oracle WebLogic Server documentation. You can use the Configuration Wizard in graphical mode or console mode.

Note:

If you are migrating the PDC pricing data from a source PDC system to a target PDC system that supports ECE, ensure that you create the WebLogic Server domain for the target PDC system on the same machine on which the WebLogic Server domain for the source PDC system exists.

Table 3-3 shows the values to choose when creating the WebLogic Server domain for PDC.

Create the WebLogic Server domain with at least one managed server configured along with the administration server because Oracle recommends that you deploy PDC on a managed server in the production environment.

Table 3-3 Oracle WebLogic Server Domain Configuration Values

Configuration Value Description

Domain source

Select Generate a domain configured automatically to support the following products.

From the list, select Oracle JRF - 12.2.1.2.0 [oracle_common].

Domain Mode Configuration

Select Production Mode.

JDK Selection

From the Available JDKs list, select the JDK version required for installing PDC. For more information, see BRM Compatibility Matrix.

Optional Configuration

Select the following:

  • Administration Server. Select this option to configure the Oracle WebLogic Server domain administration server.

  • (Optional) Managed Servers, Clusters and Machines. Select this option if you want to configure only WebLogic Server domain managed servers or machines that host WebLogic servers.

    Note: PDC does not support WebLogic cluster deployment.

  • (Optional) Deployments and Services. Select this option if you want to target your deployments to servers.

Administration Server Listen Address

Use a listen address that is equal to a resolvable DNS host or IP address.

Administration Server Listen Port

Enter a free port number.

Managed Server Listen Address

(Optional) Enter a listen address that is equal to a resolvable DNS host or IP address.

Managed Server Listen Port

(Optional) Enter a free port number.

Target Deployments to Clusters or Servers

(Optional) Add all libraries to the managed server target and to the administration server.

Target Services to Clusters or Servers

(Optional) Add all services to the managed server target.

SSL Listen Port Enabled

Select the SSL Listen Port Enabled check box.

SSL Listen Port

Enter a free port number.

See Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite for the appropriate version to see more information on WebLogic Server domains.

You can now start the administration server manually and log in to WebLogic Administration Console.

Configuring SSL for the WebLogic Server Domain

If you want to enable secure communication for PDC, you must configure SSL for the WebLogic Server domain in which you deploy PDC.

To configure SSL for the WebLogic Server domain:

  1. Generate the server-side KeyStore file by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

  2. Export the public certificate from the server-side KeyStore file by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

  3. Generate the client-side KeyStore file from the exported public certificate by using the recommended version of the JRE/JDK keytool utility. See Key and Certificate Management Tool for more information.

    Note:

    Note the path of the client-side KeyStore file. You need to provide this path during the PDC installation if you choose to use SSL.

    If you are installing PDC and BRM Integration Pack on different machines, copy the client-side KeyStore file to the machine on which you want to install BRM Integration Pack.

  4. Configure SSL for the server on which you want to deploy PDC in WebLogic Server Administration Console. See the Oracle WebLogic Administration Console Help for more information.

  5. Enable Java Secure Socket Extension-based SSL for the server on which you want to deploy PDC in WebLogic Server Administration Console. See 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 V1, specify the following as a command-line option in the WebLogic Server startup parameters: 

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

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.

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:

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

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

  3. Restore the PDC database schema.

  4. Restore the transformation cross-reference database schema.

  5. Restore the migration cross-reference database schema.

Setting the JDBC Path for the WebLogic Server Domain

You must obtain the ojdbc8.jar file and set the path to this file for the WebLogic Server domain.

To set the JDBC path for the WebLogic Server domain:

  1. Download the ojdbc8.jar file and copy it to the Domain_home/lib directory, where Domain_home is the directory in which the WebLogic Server domain is created.

    You can download this file from the following page:

    https://www.oracle.com/database/technologies/jdbc-ucp-122-downloads.html

  2. Go to the Middleware_home/user_projects/domains/bin directory, where Middleware_home is the directory in which the Oracle Middleware components are installed.

  3. Open the setDomainEnv.sh file in a text editor.

  4. Add or modify the following entry to point to ojdbc8.jar: 

    setDomainEnv.sh CLASSPATH=${Domain_home}/lib/ ojdbc8.jar:${CLASSPATH}
export CLASSPATH

  5. Save and close the file.

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.

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:

  1. Open the .cshrc file in a text editor.

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

  3. Save and close the file.

  4. Update the environment by running the following command:

    source .cshrc

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

  1. Go to the Middleware_home/user_projects/domains/bin directory, where Middleware_home is the directory in which the Oracle Middleware components are installed.

  2. Open the setDomain.sh file in a text editor.

  3. Add or modify the following entries before the EXTRA_JAVA_PROPERTIES entry: 

    JAVA_HOME="${JAVA_HOME}"
export JAVA_HOME

  4. Save and close the file.

Enabling JRE Permissions

To enable JRE permissions:

  1. Go to the jre/jdk_path/lib/security directory.

  2. Open the java.policy file in a text editor.

  3. Add the following entries to the file:

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

  4. Save and close the file.

Enabling Compatibility View in Internet Explorer 11

To enable compatibility view in Internet Explorer 11:

  1. On Windows 10, open Internet Explorer 11.

  2. Press ALT or F10.

  3. From the Tools menu, select Compatibility View settings.

    The Compatibility View Settings dialog box appears.

  4. In the Add this website field, enter oracle.com.

  5. Click Add.

  6. Click Close.

Enabling BRM-PDC Integration

After installing BRM, enable the BRM-PDC integration in BRM. This enables PDC to transform and transfer pricing components configured in PDC to BRM.

To enable the BRM-PDC integration:

  1. Go to BRM_home/sys/data/config and run the following command, which creates an editable XML file from the pricing instance of the /config/business_params object, where BRM_home is the directory in which BRM is installed. 

    BRM_home/bin/pin_bus_params -r BusParamsPricing bus_params_pricing.xml

    This directory includes the support files used by the pin_bus_params utility. To run it from a different directory, see the discussion about the pin_bus_params utility in the BRM documentation.

    This command creates the XML file named bus_params_pricing.xml.out in your working directory. If you do not want this file in your working directory, specify the path as part of the file name.

  2. Search the bus_params_pricing.xml.out file for the following line: 

    <PriceDesignCenterInst>disabled</PriceDesignCenterInst>

  3. Change disabled to enabled.

  4. Save the file as bus_params_pricing.xml.

  5. Run the following command, which loads the updated file into the /config/business_params object: 

    BRM_home/bin/pin_bus_params bus_params_pricing.xml

  6. Read the object with the testnap utility or Object Browser to verify that all fields are correct. See "Reading Objects" in BRM Developer's Guide.

  7. Stop and restart the Connection Manager (CM).

    For more information, see "Starting and Stopping the BRM System" in BRM System Administrator's Guide.