Technology

How OBIEE Works

How OBIEE WorksIntroduction

OBIEE is a vast and an exceptionally convoluted item suite – Oracle had composed around 2800 pages to document all the functions of OBIEE; in this article, it is impossible to enlist all of them although will try to cover some elements that will let you know that how OBIEE works.

How specially appointed inquiry devices function

How about we begin with an extremely straightforward case. From your gathering of social database tables, put away in, say, an Oracle database, you select a subset that is important to a specific gathering of business clients. How about we assume you select the “Clients”, “Items”, and “Deals” tables:

To keep things basic how about we assume that every table just contains the accompanying rather a unassuming number of sections:

Presently your engineers could consolidate these tables to make a solitary denormalized perspective of the whole arrangement of tables, forgetting those sections that are not of intrigue, and giving those segments that are incorporated business-accommodating presentation false names:

SELECT c.customer_name “Client Name”, p.product_name “Item Name”, s.sales_quantity “Deals Quantity”, s.sales_value “Deals Value” FROM clients c, items p, deals s WHERE c.customer_id = s.customer_id Also, p.product_id = s.product_id Arrange by 1, 2;

Rearranged OBIEE Architecture

In the event that we diminish the design of OBIEE to its minimum necessities, we can state it comprises of a “client confronting” part – the “BI Presentation Services” – and an “information source confronting” segment – the “BI Server”:

The BI Presentation Services get the choice of presentation things made by a business client, develop an exceptionally straightforward SQL inquiry, and advances it to the BI Server. On account of our case, the log record records the SQL sent to the BI Server as Disentangled Query dispatched by BI Presentation Services. All these concepts are very well articulated in Mindmajix OBIEE training.

How OBIEE Works

The Business User Perspective

Presently, we should take a gander at our basic inquiry from the business client point of view. The part of the BI Presentation Services that is utilized to figure questions (in OBIEE talk they are called “demands” – it makes OBIEE sound more up market, and subsequently justify an improved permit charge) is called “BI Answers”. In the event that a business client had quite recently made a “demand” comparing to the above question then his web program would show the accompanying screen:

In the left-hand sheet you can see the four presentation things that we’ve made accessible for our client to choose from: “Client Name”, “Item Name”, “Add up to Sales Quantity”, and “Aggregate Sales Value”. Each has been sorted out inside a suitable envelope, and these thus have been assigned to a “Branch of knowledge” called “OBIEE Introduction”. While this level of association is unmistakably pointless for this situation of this straightforward case, you can see that it would demonstrate extremely helpful were there many things from which a client could pick.

In the right-hand sheet, you can see the two presentation things that the client has chosen by tapping on them in the left-hand sheet: “Client Name” and “Aggregate Sales Value”. Presently to run the inquiry – sorry “demand” – all the client needs to do is to tap on the “Show Results” catch. At that point, after a brief, or not all that brief, rest – amid which the client is presented with a time ticking at a maddeningly quick pace – the after effects of the “demand” are shown:

The Developer Perspective

Presently, obviously, some designer will need to make the ace inquiry that furnishes business clients with their disentangled perspective of business information. In OBIEE what might as well be called ace inquiries are held in an information store called a “vault”, and they are made and kept up utilizing a product item called the “BI Administration Tool”. On account of our case, the show inside the Administration Tool resembles this:

Presently you can see that the left-hand “Presentation” layer is indistinguishable to the sheet that the client found in BI Answers. So the left-hand sheet speaks to the yield, the view that the BI Server presents to the BI Presentation Services.

You can likewise observe that the right-hand sheet, the “Physical” layer, is practically indistinguishable to the table portrayals we saw before in SQL*Plus (the “Association Pool” component advises the BI Server how to explore the system to the database or record framework that contains the information being referred to). In this chart, every one of the tables dwells in a solitary database, yet in a more unpredictable circumstance, different databases may be included with a solitary “heterogeneous” or “combined” question crossing dissimilar information sources. So the right-hand sheet is the view that the BI Server sees when it watches out over the system to the sources from which it draws its information.