PDP Requirements

Requirements and Recommendations

To run PDP, the following products must be installed:

Product Description
Oracle Advanced Planning Command Center Version 12.1.3.9 or higher.
Oracle Business Intelligence Enterprise Edition Version 11.1.1.6.5
Oracle Exadata (all X3 series) Hardware and Software Oracle Exadata must run Oracle Database 11g R2 or higher.
WebLogic Version 11gR1 patch set 5

If you are running Oracle Rapid Planning or Oracle Demantra products, or if you are working with large volumes of data, it is recommended that you also run Oracle Exalogic Hardware and Software.

Oracle Exadata Database Machine

Oracle Exadata Database Machine is the preferred platform to use with VCP products because of its performance and advanced connection capabilities to Oracle Exalogic and Oracle Exalytics. Due to extensive tuning, the hardware(Oracle Exadata Database Machine) and the software (VCP) are engineered to work together.

Oracle Exalytics In-Memory Machine

It is recommended that you use PDP in conjunction with the Oracle Exalytics In-Memory This hardware consists of a single server that is optimally configured for in-memory analytics for business intelligence workloads and includes powerful compute capacity, abundant memory, and fast networking options.

For more information, see the Oracle Exalytics Installation and Administration Guide.

Oracle Exalogic Elastic Cloud

The Oracle Exalogic Elastic Cloud (EEC) is an Oracle Engineered System, consisting of software, firmware and hardware. Oracle business applications, Oracle Fusion Middleware or third-party software products can be deployed on EEC. Oracle Exalogic is designed to eliminate a single-point-of-failure through hardware redundancy and automated failover for every major component including power, I/O and cooling.

For more information, see the Oracle Exalogic Elastic Cloud Installation and Configuration Guide.

Configuration Requirements

Configuring JDBC Data Sources

When configuring PDP with Rapid Planning for Exadata, the Java Database Connection (JDBC) data source needs to be updated. Delete the old data source and create a new one for Exadata. The host name or URL should include the TNS entry for database RAC instead of single node.

Example of a TNS string:

(DESCRIPTION=(ADDRESS_LIST=(LOAD_BALANCE=YES)(FAILOVER=YES) (ADDRESS=(PROTOCOL=tcp)(HOST=DB_NODE_A_URL)(PORT=1234)) (ADDRESS=(PROTOCOL=tcp)(HOST=DB_NODE_B_URL)(PORT=1234))) (CONNECT_DATA= (SERVICE_NAME=VIS)))

Replace DB_NODE_A_URL and DB_NODE_B_URL with the URLs for the database nodes. This needs to be done for the RP Engine and the UI domain.

For more information, refer to the Oracle Rapid Planning Installation Guide.

Profile Options

MSC: Enable In-Memory Performance Driven Planning

Use this profile option to control whether the inter process communication will use Advanced Queues or DBMS_PIPES. This impacts the following:

When the profile option MSC: Enable In-Memory Performance Driven Planning is set to Yes, the inter-process communication uses Advanced Queues.