This chapter describes the software and hardware requirements for installing Oracle Communications Pricing Design Center (PDC) 11.2.
PDC is an application that is deployed in an Oracle WebLogic Server domain. You must install and connect all required software for optimal performance.
Table 2-1 lists operating systems supported for PDC.
Note:
PDC 11.2 patch set server components do not support any 32-bit server operating systems.Table 2-1 PDC Operating Systems Requirements
Product | Version |
---|---|
Oracle Linux, x86-64 (64bit) Important: To protect from security vulnerabilities, ensure you apply the latest Critical Patch Updates. See PDC is certified on OL 5 and 6 and you should regularly apply the latest patch set for OL 5 and 6 to ensure that your running OL has the latest security fixes. |
6 UL6+ 7 UL2+ |
Red Hat Enterprise Linux, x86-64 (64bit) Important: To protect from security vulnerabilities, ensure you apply the latest Critical Patch Updates. See PDC is certified on RHEL 5 and 6 and you should regularly apply the latest patch set for RHEL 5 and 6 to ensure that your running RHEL has the latest security fixes. |
6 UL6+ 7 UL2+ |
Oracle Solaris for SPARC (64bit) |
10 Update 4+ 11 Update 3+ |
Table 2-2 lists software required for running PDC.
Table 2-2 PDC Software Requirements
Product | Version | Disk Space |
---|---|---|
Oracle WebLogic Server 12c Standard Edition or Enterprise Edition |
12.2.1.3.0 with the following patches:
|
1 GB |
Oracle Fusion Middleware 12c Application Development Framework |
12.2.1.3.0 |
1 GB |
Oracle Database 12c Enterprise Edition |
12c Release 1 (12.1.0.2.0) 12c Release 2 (12.2.0.1.0) |
1.2 GB |
Oracle Communications Billing and Revenue Management (BRM) on Linux x86 or x86-64 or Solaris SPARC (64bit) |
For PDC 11.2:
For PDC 11.2 Patch Set 1:
|
BRM server: 300 MB BRM database: 2 to 5 GB per 10,000 customers per year. This requirement varies greatly with the number of accounts and the amount of activity. |
BRM Elastic Charging Engine (ECE) |
For PDC 11.2:
For PDC 11.2 Patch Set 1:
|
N/A |
Internet Browser |
|
N/A |
Java Important: To protect from security vulnerabilities, ensure that you apply the latest critical patch updates. See "About Critical Patch Updates". PDC is certified on JDK8 and you should regularly apply the latest patch set for JDK8 to ensure that JDK contains the latest security fixes. |
JDK 1.8.0_172 (with heap size of minimum 500 MB) |
N/A |
The PDC Installer checks for all required software and displays errors if it detects any missing or unavailable components.
Note:
For details on how to download a required software component, see the appropriate section of this guide.You should install all Critical Patch Updates as soon as possible. To download Critical Patch Updates, find out about security alerts, and enable email notifications about Critical Patch Updates, see the Security topic on Oracle Help Center:
http://www.oracle.com/technetwork/topics/security/whatsnew/index.html
The number and configuration of the computers that you employ for your PDC installation depend on the scale and the kind of deployment you have planned according to your networks.
Table 2-3 provides the minimal hardware requirement for PDC installed on a single managed server in a WebLogic Server domain.
Table 2-3 PDC Minimum Hardware Requirements
Component | Requirement |
---|---|
Hard disk |
1.5 GB of free disk space Note: A minimum of 1.5 GB should be free in the Oracle WebLogic Server domain home. |
Processor |
Oracle recommends using twin cores, each running at 1.5 GHz CPU. |
Memory |
A minimum of 4 GB physical memory and 4 GB swap. If you plan to have the database installed on the same server as PDC, the minimum memory requirements increase to 6 GB physical memory and 6 GB swap. |
This section describes the information that you will be required to provide during the PDC installation procedure. You define some of these configuration values when you install and configure Oracle Database and WebLogic Server.
Important:
Oracle recommends that you print the tables and record the values for future reference.If you are installing PDC 11.2 on an existing PDC installation, use the values that you provided during the PDC 11.1 installation.
Table 2-4 lists the PDC installation details that are required if you are installing PDC 11.2 on an existing PDC installation.
Table 2-5 lists the details for the WebLogic Server domain (the domain on which you deploy PDC) that are required during the PDC software installation.
Table 2-5 Pricing Design Center WebLogic Server Connection Information
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the WebLogic Server domain is configured. |
- |
Port Number |
The port number assigned to the WebLogic Server domain administration server. |
- |
User Name |
The WebLogic Server domain administrator user name. |
- |
Password |
The WebLogic Server domain administrator user password. |
- |
WebLogic Home |
The path of the directory in which the WebLogic Server software is installed. For example, MW_home/wlserver, where MW_home is the directory in which the Oracle Middleware components are installed. |
- |
KeyStore Location |
(For upgrade only) The path to the client-side keystore file generated from the exported public certificate using the keytool utility. |
- |
Table 2-6 lists PDC database details that are required if you want to create the PDC user during the PDC software installation.
Table 2-6 PDC Database Connection Information
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the PDC database is configured. |
- |
Port Number |
The port number assigned to the PDC database service. |
- |
User Name |
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 privilege, select any table to username, and grant dba to username. |
- |
Password |
The database user password. |
- |
Service Name |
The name of the PDC database service. |
- |
Table 2-7 lists the tablespace details that are required if you want to create the PDC schema user during the PDC software installation.
Table 2-7 PDC Schema Information for New User
Field | Description | Value |
---|---|---|
User Name |
The name of the PDC schema user. |
- |
Password |
The password of the PDC schema user. |
- |
PDC Tablespace |
The name of the tablespace for the PDC schema. This field is case-sensitive. |
- |
Temp Tablespace |
The name of the temporary tablespace for the PDC schema. This field is case-sensitive. |
- |
Table 2-8 lists the tablespace details that are required if you want to use the existing PDC schema user for the PDC software installation.
Table 2-8 PDC Schema Information for Existing User
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the PDC database is configured. |
- |
Port Number |
The port number assigned to the PDC database service. |
- |
Service Name |
The name of the PDC database service. |
- |
User Name |
The name of the PDC schema user. |
- |
Password |
The password of the PDC schema user. |
- |
Table 2-10 lists keystore credentials details that are required if you are installing PDC 11.2 on an existing PDC installation.
Table 2-10 Keystore Credentials Information
Field | Description | Value |
---|---|---|
Key Password |
The password PDC uses for accessing the PDC alias key in the keystores (PDC_home/apps/conf/pdc.jks, where PDC_home is the directory in which PDC is installed, and BRM_Integration_Pack_home/apps/conf/pdc.jks, BRM_Integration_Pack_home is the directory in which BRM Integration Pack is installed). |
- |
Keystore Password |
The password used for accessing the keystore. |
- |
Table 2-11 lists the BRM Integration Pack installation details that are required if you are installing PDC 11.2 on an existing PDC installation.
Table 2-12 lists the BRM server details that are required during the PDC BRM Integration Pack installation.
Table 2-12 BRM Server Information
Field | Description | Value |
---|---|---|
BRM |
The path to the directory in which BRM is installed. The path is defined in the $PIN_HOME environment variable. |
- |
BRM Pipeline |
The path to the directory in which Pipeline Manager is installed. The path is defined in the $IFW_HOME environment variable. |
- |
Perl Home |
The path to the directory in which the Perl libraries for BRM are installed. |
- |
Table 2-13 lists the Pipeline Manager database details that are required during the PDC BRM Integration Pack installation.
Table 2-13 BRM Pipeline Database Information
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the BRM pipeline database is configured. |
- |
Port Number |
The port number assigned to the BRM pipeline database service. |
- |
User Name |
The BRM pipeline database schema user name. |
- |
Password |
The BRM pipeline database schema user password. |
- |
Service Name |
The name of the BRM pipeline database service. |
- |
Table 2-14 lists transformation cross-reference database details that are required if you want to create the transformation cross-reference schema user during the PDC BRM Integration Pack installation.
Table 2-14 Transformation Cross-Reference Database Information
Field | Description | Value |
---|---|---|
Hostname |
The IP address or the host name of the machine on which the transformation cross-reference database is configured. |
- |
Port number |
The port number assigned to the transformation cross-reference database service. |
- |
User name |
The transformation cross-reference 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 privilege, select any table to username, and grant dba to username. |
- |
Password |
The transformation cross-reference database user password. |
- |
Service Name |
The name of the transformation cross-reference database service. |
- |
Table 2-15 lists the tablespace details that are required if you want to create the transformation cross-reference schema user during the PDC BRM Integration Pack installation.
Table 2-15 Transformation Cross-Reference Schema Information for New User
Field | Description | Value |
---|---|---|
User Name |
The name of the transformation cross-reference schema user. |
- |
Password |
The password of the transformation cross-reference schema user. |
- |
PDC Tablespace |
The name of the PDC tablespace for the transformation cross-reference schema. This field is case-sensitive. |
- |
Temp Tablespace |
The name of the temporary tablespace for the transformation cross-reference schema. This field is case-sensitive. |
- |
Table 2-16 lists the tablespace details that are required if you want to use the existing transformation cross-reference schema user during the PDC BRM Integration Pack installation.
Table 2-16 Transformation Cross-Reference Schema Information for Existing User
Field | Description | Value |
---|---|---|
Hostname |
The IP address or the host name of the machine on which the transformation cross-reference database is configured. |
- |
Port number |
The port number assigned to the transformation cross-reference database service. |
- |
Service Name |
The name of the transformation cross-reference database service. |
- |
User Name |
The name of the transformation cross-reference schema user. |
- |
Password |
The password of the transformation cross-reference schema user. |
- |
Table 2-17 lists the migration cross-reference database details that are required if you want to create the migration cross-reference schema user during the PDC BRM Integration Pack installation.
Note:
The migration cross-reference database details are required only if you want to migrate pricing and setup components from the BRM database to the PDC database.Table 2-17 Migration Cross-Reference Database Information
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the migration cross-reference database is configured. |
- |
Port Number |
The port number assigned to the migration cross-reference database service. |
- |
User Name |
The migration cross-reference database user name. |
- |
Password |
The migration cross-reference database user password. |
- |
Service Name |
The name of the migration cross-reference database service. |
- |
Table 2-18 lists the tablespace details that are required if you want to create the migration cross-reference schema user during PDC BRM Integration Pack installation.
Note:
The migration cross-reference schema details are required only if you want to migrate price lists from the BRM database to the PDC database.Table 2-18 Migration Cross-Reference Schema Information for New User
Field | Description | Value |
---|---|---|
User Name |
The name of the migration cross-reference schema user. |
- |
Password |
The password of the migration cross-reference schema user. |
- |
PDC Tablespace |
The name of the PDC tablespace for the migration cross-reference schema. This field is case-sensitive. |
- |
Temp Tablespace |
The name of the temporary tablespace for the migration cross-reference schema. This field is case-sensitive. |
- |
Table 2-19 lists the tablespace details that are required if you want to use the existing migration cross-reference schema user during PDC BRM Integration Pack installation.
Note:
The migration cross-reference schema details are required only if you want to migrate price lists from the BRM database to the PDC database.Table 2-19 Migration Cross-Reference Schema Information for Existing User
Field | Description | Value |
---|---|---|
Host Name |
The IP address or the host name of the machine on which the migration cross-reference database is configured. |
- |
Port Number |
The port number assigned to the migration cross-reference database service. |
- |
Service Name |
The name of the migration cross-reference database service. |
- |
User Name |
The name of the migration cross-reference schema user. |
- |
Password |
The password of the migration cross-reference schema user. |
- |
Table 2-20 lists the migration user details that are required if you are installing PDC 11.2 on an existing PDC installation.