Take the following information into consideration when sizing your infrastructure:
User counts are approximations. Concurrent usage could be much higher or much lower based on the hardware recommended in the following sections depending on concurrent user actions, number of concurrent user per application, and number of applications.
Number and size of servers per application could vary depending on designated use cases. More or less hardware might need to be dedicated to certain application functions depending on the scenario and concurrent usage.
Use case scenarios, times between queries, volume of report generation, size of reports, and views being used could adversely affect these general guidelines.
Adequate load and performance testing should be integrated into the testing phase of your implementation to validate your production environment hardware sizing and to assess the overall technical readiness prior to going live.
The RDBMS server does not have to be dedicated and can reside on an existing server. Requirements for the RDBMS vary greatly. For example, in a Planning implementation it would vary greatly depending on use of Planning Line Item detail and the setup of data staging tables for use with the Planning application.
All recommendations are based on application best practices. Requirements might vary if any or all applications are not built within best practice guidelines.
Server CPU is a physical processor. Multi-core technology is supported and a dual core is counted as 2 CPUs but only with the understanding that performance is based on the manufacturer's claim and not by any testing done by Oracle.
The deployment diagrams are samples for a production environment, and do not include development, quality assurance, or test environment recommendations.
Guidelines do not include external overhead such as network latency, firewalls, or SSL incorporation.
Additional considerations:
The Administration Services server size can vary greatly depending on the use of Oracle Hyperion Business Rules.
Increased disk space for the database repository is required under certain circumstances. Some of the reasons may be:
You are using Financial Management. Since all Financial Management application data is stored in database tables, more disk space is needed for storage of Financial Management applications.
The database and Essbase are on the same server or share disk space.
You are using Financial Reporting or Interactive Reporting against the relational database.