This chapter covers the following topics:
This document explains what you need to do to install Oracle Rapid Planning.
Make sure that you have the latest version of this document before proceeding.
Minimum Client Hardware Requirements:
1 GB of memory
1.5 GHz (or higher) processor
Minimum Browser Requirements:
Microsoft Internet Explorer versions 7.x or 8.x. Microsoft Internet Explorer version 9 is supported only with ADF 11gR1 Patch Set 5 (PS5), which is required for Rapid Planning 12.1.3.9 and 12.2.2 and later. Microsoft Internet Explorer version 10 is not supported.
Mozilla Firefox version 3.0 or later.
You do not need to install client software.
The following list is the technology stack on which Oracle Rapid Planning receives rigorous testing. Other variations are possible.
Java: JDK 1.6 update 11 or later. JDK 1.7 is supported only with ADF 11gR1 Patch Set 5 (PS5), which is required for Rapid Planning 12.1.3.9 and 12.2.2.
ADF Libraries (Oracle Fusion MiddleWare 11g) and WebLogic application server requirements by Rapid Planning release:
Release 12.1.3.4 to 12.1.3.8, Release 12.2, and Release 12.2.1 requires - ADF 11gR1 Patch Set 3 (11.1.1.4.0) used with WebLogic Server 10.3.4
Release 12.1.3.9 and Release 12.2.2 or later - ADF 11gR1 Patch Set 5 (11.1.1.6.0) used with WebLogic Server 10.3.6
For customers upgrading to 12.2.2 or 12.2.3:
Install or upgrade to WebLogic 11gR1 (10.3.6) and Oracle ADF to Patch Set 5 (11.1.1.6.0) for Rapid Planning User Interface (UI) and Engine domains before you upgrade Oracle Rapid Planning.
Database Server: Oracle Database Server 11g
Oracle Value Chain Planning Suite: The entire Oracle VCP suite, which includes Rapid Planning, must be on the same release (12.2).
Oracle E-Business Suite: Release 12.1.3 or later.
Oracle JD Edwards: Release 9.1 (requires Oracle Value Chain Planning to Oracle JD Edwards Process Integration Pack). Rapid Planning 12.2 or later is only supported under Oracle JD Edwards 9.1.
Oracle Rapid Planning has an administrator application that allows you to perform the following:
Monitor loaded plans.
Close plans.
Start and stop Managed Servers.
Close plans before stopping or restarting the Managed Servers associated with those plans.
For solution architecture, the most important consideration is the size of the implementation:
Small: 0 - 5 concurrent users and with a relatively low volume of data
Medium: 5 - 20 concurrent users
Large: 20 or more concurrent users across multiple time zones, with complex data structures, and with a relatively high volume of data
See also Hardware Requirements for the Servers.
Another consideration is the number of simulation plans that you want to run concurrently. Since each simulation plan needs a Managed Server, you need to provide a suitable number of Managed Servers to meet your processing needs.
Multi-Tier Architecture
An Oracle Rapid Planning implementation consists of the following architectural tiers:
E-Business Suite tier with concurrent manager
Oracle WebLogic domain and the Oracle WebLogic Server for the Oracle Rapid Planning User Interface
Oracle WebLogic domain and the Oracle WebLogic Server for the Oracle Rapid Planning Administrator Utility
Oracle WebLogic domain for the Engine and a suitable number of Managed Servers for the Engine
Common file system or network storage device between the e-Business Suite tier and the Engine Managed Servers
This section provides sample hardware requirements for the servers used in an Oracle Rapid Planning installation, as well as for the Analytical Engine.
These are basic guidelines. See Oracle Rapid Planning Implementation and User's Guide, Implementation: Sizing Template. Contact your account representative or Oracle Support Services for help to more precisely configure and tune your memory.
Oracle Rapid Planning runs on 64-bit platforms using 64-bit version of the Java virtual machine (JVM) and the -d64 flag.
The term Managed Server represents a single plan loaded in memory.
Based on the number of plans that you run concurrently, create multiple managed servers in the WebLogic engine domain. You need one managed server to run or load a single plan. Multiple users can concurrently view each plan. To find the memory you need for the
Engine domain: Multiply the memory to run or load a single plan by the number of managed servers you have. Monitor the memory as your data volumes grow.
UI domain: Start with 4 GB and add 1 GB for each user.
Small Implementation:
Engine domain: 10 Managed Servers configured with memory of 500 - 750 MB each
User interface: 2 - 3 GB for its server
Free hard disk space: Minimum 10 GB plus a variable component of 1 GB for each active plan
Medium Implementation:
Engine domain: 20 Managed Servers configured with memory of 1 - 1.5 GB each
User interface: 4 - 6 GB for its server
Free hard disk space: Minimum 10 GB plus a variable component of 2 - 3 GB for each active plan
Large Implementation:
Engine domain: 20 Managed Servers configured with memory of 2 GB or higher each
User interface: 6+ GB for its server
Free hard disk space: Minimum 10 GB, plus a variable component of 2 - 3 GB for each active plan
Multi-Tier Solution:
In a multi-tier solution, the servers and the Analytical Engine may be on different machines.
Size of the supply chain: Supply chain size is determined by the number of organizations, items, resources, demands, supplies, bill of material components, and routings.
Number of simulation plans that you plan to run concurrently: Each simulation plan will use up a Managed Server, and the requirement for the Managed Server depends on the size of the supply chain.
Number of concurrent users: Impacts the user interface memory requirements.
Binary Disk File Space
You need to plan for additional disk space to store the binary files. Estimate the binary file size per plan as 30% to 40% of the plan size. Each run of plan creates a set of binary files and each subsequent simulation run creates a new set of binary files. Plan for this disk space based on the total number of plans and the number of simulations you expect to run against these plans. Purge the binary files periodically to release the disk space.
Horizontal Scaling
If your WebLogic server has an upper limit on memory and all the managed servers need more memory than that limit, use horizontal scaling. It configures managed servers to span machines.
Install the WebLogic Server on all machines and bring the node manager utility up and running on all hosts.
Create a managed server on one machine (primary host) and other managed servers on other machines (secondary hosts).
With the node manager utility, you can perform these tasks on all managed servers:
Start and stop them.
Monitor their health check information and automatically kill them is their health state is failed.
Automatically restart those that have health state failed or that shut down, for example, because of a system crash or reboot.
To be able to run more concurrent plans:
Add managed servers to machines
Associate them to the Rapid Planning domain
Your planners can run, load, and launch plans without knowledge of the machine and managed server configuration.
The WebLogic server documentation is on http://www.oracle.com/technetwork/middleware/weblogic/documentation/index.html.
Database Server
Use the same sizing that you need for your other Oracle Value Chain Planning products.
Application Server
The table below shows the Application Server requirements.
| Entity | Windows Stacks | UNIX Stack |
|---|---|---|
| Processor | 8 core 1.6 GHz processor Higher for increased performance |
8 core 1.6 GHz processor Higher for increased performance |
| Memory (depends on number of concurrent users) | See the hardware requirements for small, medium, and large implementations. | See the hardware requirements for small, medium, and large implementations. |
| Disk | See the hardware requirements for small, medium, and large implementations. | See the hardware requirements for small, medium, and large implementations. |
For a web-based solution, the wide-area network requirements vary by implementation.
In general, place these components on a high-speed LAN 1 or 10 Gigabits per second:
E-Business Suite tier
User Interface Server
Database Server
Engine Managed Servers