Organizations today want to stay informed when it boils down to allowing data access to a third-party solution.

The trial users evaluating BI Connector’s Power BI to OBIEE connector have frequently enquired about the reference architecture to analyze the connectivity between Power BI to OBIEE through BI Connector.

BI Connector team has always been transparent in sharing the reference architecture with the customers and trial users. However, the information was shared only through word of mouth when we had calls or meetings with the customers.

The BI Connector team strongly felt we should publish this reference architecture and make the architecture accessible to the public, instead of just sharing with those who ask for it. And as a result of our transparency to stakeholders, we’re happy to announce that a whitepaper on the topic – Reference Architecture For Visualizing OBIEE/OAC Data From Power BI Using BI Connector is now available.

The whitepaper covers the reference architecture in detail. You’re welcome to share the whitepaper with your IT Architecture, Data Governance and Compliance teams, and clear their doubts and concerns! Here’s the link to the whitepaper for your access anytime.

If you’re looking to know the Reference Architecture at summary level, please read further.

In OBIEE’s view, the connectivity established between Power BI and OBIEE through BI Connector is just like typing the OBIEE secure socket (https) or http url in a web browser and entering the credentials to connect to the subject areas or reports.

The OBIEE credentials are required to be entered during the following events:

1. When a DSN is set up in the ODBC Administrator. The OBIEE credentials must be entered for the Desktop and Server machines separately by connecting through BI Connector Desktop and Server editions respectively.
2. When establishing connectivity with a DSN initially from Power BI Desktop, right after choosing between Direct Query or Import. The credentials need not be entered for subsequent attempts to connect to the same DSN as the credentials will be stored in Power BI, unless the user manually clears the permission for that DSN in the Data Source Settings.
3. When a report is published to a workspace shared with other users, the other users must configure the DSN in their machine in order to access the report. So they’ll have to enter their OBIEE credentials when setting up the DSN in their machines individually.
4. When adding a DSN to the Gateway in Power BI cloud. The users can also schedule the refresh of import queries based on their individual needs.

In all the above events, the connectivity to the BI server is authenticated and authorized in OBIEE Security layer.

Adding to this, the Power BI to OBIEE connector is Power BI certified! This means, the connector passed many tests conducted by the Power BI team, and met the required standards before getting listed in Power BI. Hence, you can add BI Connector to your analytics arsenal without a second thought.

Looking for a hassle-free way to visualize OBIEE Subject Areas and Reports securely in Power BI? Wait no more! Try BI Connector.