1 Reply Latest reply on Jan 7, 2019 1:14 PM by Christian Berg

    Essbase 11g as a data source for OBIEE 12c

    3822941

      Hi Everyone,

       

      We want to use Hyperion Essbase 11.1.2 as a Datasource for OBIEE 12c for creating some analytical reports on data from Essbase.

       

      Please help us with the supporting DOCs ,Best practices followed and Potential integration issues that we may encounter while integrating essbase with OBIEE 12c .

       

      Thanks

      Bhanu

        • 1. Re: Essbase 11g as a data source for OBIEE 12c
          Christian Berg

          Why not start with google and ask more specific questions in here? https://www.google.com/search?q=obiee+essbase+integration

           

          How to Ask Questions in Developer Community Spaces

           

          So, here are some basic rules of how to ask questions:

          1. Search the forum to see if your question has already been asked (and answered). The forums search isn't bad.
          2. Search again using Google. Don't give up after reading the first hit.
          3. Give information about your environment, such as versions of software you use. This is essential, as versions change and other users might run into a similar problem never knowing if the thread they read was about their version.
          4. Give a full, understandable use case of the problem. The process of formulating a good forum question will force you to think more clearly about the question yourself.  Sometimes in the middle of writing the question the answer might come to you because you've restated the problem in terms an outsider can understand.
          5. Tell us what you have already tried to solve the problem. Help the others to get the big picture and show that you haven't just dumped your work on the forum users.
          6. Give information about the technologies you use in your application. For example, if you POI to generate native EXCEL files and this is related to your problem, provide those details. If you use PL/SQL to make changes in the DB, provide that information as well.
          7. Provide code snippets and any other information that might help us to understand the problem and what you've done to try to solve it.
          8. Screenshots help to understand visual problems. It’s hard to describe problems with are only visual like “my fields are not aligned”. Make screenshots and add them to your post.
          9. Provide stacktraces as text if you are asked to provide one. This way we can look at each part.
          10. Format code you provide. This make code readable, regardless if it’s Java, PL/SQL or the source of a .jsff page.

          The list above is not complete,  but it's a starting point. Providing the information described above will help you get an answer to your question.