1 of 1 people found this helpful
hi Petar Shumov ,
Are you looking to
1. replace OBIEE completely with Tableau?
2. Complement OBIEE with Tableau?
For #1, an ideal approach is to implement a data virtualization layer that provides RPD like functionality. An alternative approach is to directly connect to the DW from Tableau and create data sources. However, the challenge with this approach is the proliferation of data sources and it could quickly get out of hand. Migrating from OBIEE to Tableau is a long process, typically several months or year(s).
For #2, you can directly connect from Tableau to OBIEE Subject Area & Reports and publish as a data source. We developed BI Connector to simplify the Tableau-OBIEE integration. It is also used as a transition tool to go from OBIEE into Tableau.
If you are interested in chatting further about #1 or #2, drop me an email at firstname.lastname@example.org. Happy to connect.
2 of 2 people found this helpful
I'm not that familiar with OBIEE (beyond knowing what it is and the basics of what it does), but in general you would have a setup that goes from your student information system to the data warehouse to the reporting tool. So, from this standpoint you could build reports in Tableau directly from the data warehouse. In this setup, I would recommend creating some standard views in the warehouse that could then be used as data sources for Tableau reports. Creating your own published data sources on Tableau Server in addition to the views would be a benefit long term since it adds an additional layer at which data governance can be applied and can allow end users access to the data without needing to know about the underlying structure of the data warehouse. This would also mean that different levels of access could be granted to the data sources in Tableau versus the data warehouse itself.
In our current setup we are connecting directly to Banner (actually a "real-time backup") and building reports from there. In other words, we don't have a data warehouse which means we spend a lot of time writing SQL in order to pull the necessary data from Banner for each report. Ideally we hope to move to a combination of standard database views and published Tableau data sources to eventually serve as our data warehouse. (The lack of a data warehouse is a long story for another time, but there are ways of working around things without it.)
Another thing to consider is that Tableau is not necessarily the right tool for everything. For example, we often get requests for lists of students (names, addresses, demographics, etc) who meet certain criteria since these "reports" were available in a prior system. Although these long, tabular lists can be built in Tableau, it really isn't he most efficient solution. Again, there are ways of doing it, it just isn't what Tableau was really designed to do.