Having just spent some time on a prjoect with Christian Berg and Venkat, and seeing some of the presentations at the BI Forum, I have come up with my all time top 10 of 'Don't do this without an Adult Supervisor'
1. Implement Essbase in OBIEE
2. Use xml editors to create reports
3. Have your repository created by UDML from a dynamic source
4. BPEL (Leave that to Tony H)
5. Use custom Javascript to manipulate the dashboards
6. Implement WebSSO
7. Use LDAP Groups
8. Use Dynamic Go URLs (Particularly when you have finished the development of the RPD)
9. Integrate multiple stars and Multiple dimensional attributes in a single Subject Area
10. Integrate BI Publisher
Relatively easy compared to the above is:
Settings up delivers, installing BI Apps in a Unix environment, creating multiple instances on a Linux blade, Briefing books, Configuring the DAC, customising BI Apps
But do your homework before going on the client site
Do you have any?
Subscribe to:
Post Comments (Atom)
6 comments:
a.) Shouldn't you be posting somewhere else?
b.) 5 an 8 are definitely ugly :-P
Modeling 3NF structurs in OBIEE should also be avoided by newbies.
Cheers,
Stijn
Integrate OBIEE with workspace.
Try Single Sign on for workspace.
Having just tried to model a 3NF structure from Ebiz suite (and given up) I'd like to understand what is possible here. My basic understanding is that a table has to be either a dimension or fact, and OBIEE makes this distinction based on the relation direction (1 end is the dimension, many end is the fact). So what do you do when you have what I call a circular relationship with 3 tables:
Table 1:Table 2 1:M
Table 2:Table 3 1:M
Table 3:Table 1 1:M
If anyone has some time I'd like to send you the actual ERD for your views, let me know
Having just tried to model a 3NF structure from Ebiz suite (and given up) I'd like to understand what is possible here. My basic understanding is that a table has to be either a dimension or fact, and OBIEE makes this distinction based on the relation direction (1 end is the dimension, many end is the fact). So what do you do when you have what I call a circular relationship with 3 tables:
Table 1:Table 2 1:M
Table 2:Table 3 1:M
Table 3:Table 1 1:M
If anyone has some time I'd like to send you the actual ERD for your views, let me know
Circular Join can be avoided my using Aliases. In the above example , create an alias for Table1 and then you can model without a CJ
Post a Comment