ABSTRACT
Perhaps you are a technology-savvy financial analyst, have just finished taking Essbase training, and are now facing building your first real Essbase application. You know how to build all the major components that make up an Essbase application, but how do you translate what your division controller is asking for into an actual Essbase design? How do you know you are headed in the right direction? Or perhaps you have one or two Essbase systems under your belt, but the experience of building them was not as straightforward as you thought it would be when you started, or the performance of the systems was disappointing when they were finished. Or perhaps you are an information technology (IT) professional who has worked with Essbase applications in your organization for some time, managing, administering, and maintaining them successfully, but now you are being asked to develop a new application based on relational databases that you know well. Where do you start? Will you be able to distinguish a good Essbase design from a bad one?
