Database Reference
In-Depth Information
•  operating system installation
•  hardware installation
•  Essbase clustering
1.1.3 What Will Be Covered
•  Skills
•  hardware/software tips and tricks
•  Essbase architecture and sizing
•  System maintenance
•  troubleshooting
•  Deployment considerations
1.2 inFrastruCture skill sets
When thinking about an oracle EPm (Enterprise Performance management) imple-
mentation, I break skill sets up into two major areas:
1. Functional
2. Infrastructure
A functional person handles everything from collection of requirements to writing
calculations. Every other chapter in this topic deals with a functional developer's
interaction with Essbase.
This chapter is different, just like infrastructure resources (we are somewhat different”
but nice, honest). An infrastructure resource handles everything from racking a server
through installing the base software. The skill sets are different enough that it is rare to
find an individual who excels at both. Figure 1.1 is an overview of the different areas an
infrastructure person must cover.
1.2.1 Typical Infrastructure Organization
A good oracle EPm infrastructure person must be able to navigate the maze of corpo-
rate information technology (It). These organizations run the gamut from a single It
person at a $25 million company to a $50 billion company having an It organization
containing thousands of people.
typical departments within a very large organization are broken out into major
categories including:
•  Windows ®
•  unix™
•  middleware/Web
•  Storage
•  Database
•  network/Firewall/Load Balancing
The hyperion infrastructure role may be a separate role or bundled into one of the
above areas (usually not Storage or network). There are formal processes to engage
the proper resources from each team as well as formal change processes to approve
the work to be performed. understanding both the processes and delivery timelines for
Search WWH ::




Custom Search