Database Reference
In-Depth Information
MS Oce using
Smart View
Oracle HTTP
Server
19000
IIS + ASP.NET
80/443
RA Framework
Web aka
Workspace
45000
Provider
Services Web
13080
Web Analysis
Web
1600
Financial
Reporting Web
8200
Essbase Excel
Addin
ESSVR
32768+
RA Framework
Services aka
Core Services
6800-6805, 6860
ESSBASE
1423
OPMN
6711,6712
Relational DB
Figure 1.3
Essbase architecture: Logical view.
An environment with plenty of hardware resources does not guarantee excellent per-
formance. yes, hardware is the foundation and the main component, but there is also a
very important factor and that is application design.
Developers should not underestimate the importance of a good application design.
A poorly designed application along with poorly designed calculations can cause a bot-
tleneck in the application. When this situation arises, you may hear comments from
your It resources like: “Server utilization is less than 30%,” “I don't know, everything
looks good from my end,” etc. This is something that is out of the hands of an infrastruc-
ture resource that tends to have little knowledge of how Essbase works. Spending a good
amount of time in design sessions will help avoid situations like this. Providing your
development team with access to the nonproduction Essbase server also will help them
tune the system properly. Engage performance testing and infrastructure resources in
tuning activities to ensure the hardware is fully utilized. In regard to oracle's assump-
tions on their sizing, these evolve over time. For instance, the Web server requirements
have grown steadily over time. A recently released standard deployment guide simplifies
sizing and recommends four physical cores on every machine, 32 gb on the Foundation
Server and 16 gb on all other servers. While this is an approach that works, it is a one
size fits all approach.
you will find more specialized sizing guidelines placed at the end of this section.
I suggest you continue reading this section to understand the drivers of load and what
rationale went into the sizing guidelines.
Essbase is memory, CPu (central processing unit), and Input/output (I/o) intensive—
all these needs grow to some extent as you add concurrent users and more applications.
