Obiee Scenarios 362s36
This document was ed by and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this report form. Report l4457
Overview 6h3y3j
& View Obiee Scenarios as PDF for free.
More details h6z72
- Words: 3,357
- Pages: 11
Hi, Can we two facts? I ave one fact and four dimensions ed, and i want to get a column of another fact into the first fact. If i directly drag the column of another fact into the first fact which is in BMM layer, in my report the second fact’s column is not showig any result. If i second fact with the first fact, then it is giving the values in report. Could u pls clarify my doubt… # 24 July 2010 at 5:00 PM
JAY said: Can u please explain the difference between Physical and Complex ? # 29 July 2010 at 4:07 PM
Rohit (author) said: Yes, Sure JAY!!! The Difference between Physical and complex s is that the Physical s are the s which are placed on the Primary and Foreign Keys between the 2 tables. The physical s are mostly used in Physical Layer. The OBIEE server creates its Physical query based on these s which further hits the Database and fetches the data. Whereas, Complex s are mostly used on the BMM layer and these are not created on PK & FK. The OBIEE server creates a logical requests based on these s. Kindly let me know in case of any further concerns or queries…. # 30 July 2010 at 3:29 AM
Sudhakar said: Hi, Suppose, we implemented complex s in physical layer and the the Analytics server issues query against the underlying database. By seeing the query, how to identify whether the is complex or not? # 14 August 2010 at 2:20 PM
Libral said: Hi Rohit, I am confused about complex and unable to understand in which situation it should be used. My understanding is as follows,
1. you can either have foreign key or complex . 2. in the physical layer, most of the time you use foreign key , the only exception is when you have non-equi condition (for eg between…). Can you please explain the Complex in detail. # 29 October 2010 at 2:56 AM
Rohit (author) said: Hi, When we run a report, the BI Server generates 2 queries: 1) Logical 2) Physical Now, the BI Server takes complex s into consideration while generating the logical query and furthur the Physical query out of the logical query. Generally, we make use of Complex s in the BMM layer. In BMM, Complex s are always applied between the tables folders and not the logical table sources, hence, it facilitates the extendibility for future uses. We can add many LTS to the table folder without changing the s in BMM. The compplex s doesnt apply on any specific columns in BMM and the server takes the reference from the Physical layer and establish the s between them. We can also make use of the Complex s in the Physical Layer in case of the non equal conditions eg: When we on some non key columns and use non equality conditions. Kindly let me know what else do u want to know about the complex s or if you have any confusion. # 31 October 2010 at 1:24 AM
Libral said: Rohit, Thank you so much, I have understood the concept to a certain extentd but can you explain it with one example (for example foreign key is straight forward, you define it and when select column from table having parent child relationship then it be applied, BUT HOW a complex is defined and WHAT EFFECT it has on the physical query that is generated by BI server is not clear).
OBIEE - How to define one different database credential for each (the shared logon) ? About
For system architecture reasons, you may want to have one database credential by . Example :
When one schema (of one ) is the logical entity of one company, you may decide to have the same table in two different schema but with the data for only one company
Articles Related
OBIEE - Connection Pool
OBIEE 10G/11G - Query Cache of BI Server
OBIEE - Security
How to do To achieve it, you have to unmark the check box “Shared Logon” of the connection pool property in the physical layer. You can remark that the and box become gray. Now, the Obiee s don't share no the same credential and you have to define for each Obiee , one credential (one name, one ). To define the new credentials :
open the Oracle BI istration tool
open the security manager (Manage> Security)
click on the map
double click on a
define in the tab logon the credential for your database
The importance of disabling the cache If the don't share the same data, you have to disable the query cache by setting NO on theENABLE parameter in the cache section of the file nqsconfig If you don't disable the query cache, Obiee will perform an hit cache and retrieve the data from its cache as you can see in the log :
Insight of OBIEE Architecture 21 MAY 2010 27,906 VIEWS 10 COMMENTS (16 votes, average: 4.63 out of 5)
Table of contents for Architecture
1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, I am sorry that I engrossed myself in posting some complex stuff and left the Basics in between, so, here I am again with the Basics of OBIEE. In our previous posts we have covered Data Modelling, Basics, Connection Pool, s etc. So, lets start to build more on that and lets go through the Architecture of OBIEE. The below diagram shows the basic architecture of OBIEE and its components:
Now, first of all lets understand the flow in which a request flows from Client to Data Source. If a client runs a report, the request first goes to the Presentation Server and then it gets routed to the BI Server and then it gets further routed to the underlying Database or the data source. Client -> Presentation Server -> BI Server -> Data source Now, the request is routed back through the similar route to the client. Which means, the data is fetched from the Data source and it gets routed to Presentation server through BI server and then to the client. Client <- Presentation Server <- BI Server <- Data Source The above flows provide a very basic idea of how the data is fetched and showed in a report in OBIEE. Now, lets understand it more properly by dividing the above diag. into segments and then : 1) Client and Interface 2) Presentation Server & Presentation Catalog 3) BI Server & Tool 4) Datasource Client & Interface: This level has the UI of OBIEE which is accessible to the clients and s. The OBIEE UI has several components like OBIEE Answers, Interactive Dashboards etc.
Oracle BI Answers is a powerful, ad hoc query and analysis tool that works against a logical view of information from multiple data sources in a pure Web environment.
Oracle BI Interactive Dashboards are interactive Web pages that display personalized, role-based information to guide s to precise and effective decisions.
BI Delivers is an alerting engine which gives s flexibility to schedule their reports and get them delivered to their handheld devices or interactive dashboards or any other delivery profile and helps in making quick business decisions.
In simpler we can say that, this is a web application which is accessible to the s for preparing their reports/dashboards and do Ad-Hoc reporting to cater the business needs.
We will continue with the other segments in the posts. Till that time if you have any questions or comments they are most welcome. Keep posting…
Insight of OBIEE Architecture-II 22 MAY 2010 17,811 VIEWS 4 COMMENTS (3 votes, average: 5.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, In the previous post we were studying the architecture of OBIEE, so, lets continue with it. We have divided OBIEE Architecture in 4 segments to better understand it. 1) Client and Interface 2) Presentation Server & Presentation Catalog 3) BI Server & Tool 4) Datasource We have covered the first segment in the previous post. So, lets understand the second segment.
Presentation Server & Presentation Catalog: The BI Presentation server is basically a web server on which the OBIEE web application runs. It processes the client requests and routes it to the BI Server and vice versa. It can be deployed on any of the following IIS or Oc4j. It makes use of the Presentation catalog which contains the aspects of the application.
The Presentation catalog stores the application dashboards, reports, folders and filters. It also contains information regarding the permissions of dashboards & reports created by s. It is created when the Presentation server starts and can be istered using the tool called Catalog Manager. In other words we can say that the Presentation server and the Presentation Catalog are together responsible for providing the clients with a web server on which the web application runs and also isters the look and feel of the Interface. This post covers basics of the Presentation server & catalog. We will be covering the BI server in the post. Till that time stay tuned and keep posting… Previous in series Next in series
Insight of OBIEE Architecture-III 18 AUGUST 2010 13,244 VIEWS 11 COMMENTS (1 votes, average: 5.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, Sorry to keep you waiting for the next post, but here it comes. Previously, in the second segment we have discussed the Presentation Server and the Presentation catalog. So, lets continue with the third segment where we will see what is the role of the BI Server in the OBIEE Architecture.
BI SERVER AND TOOL BI Server is a highly scalable query and analysis server. It is the heart of the entire architecture. It efficiently integrates data from multiple relational, unstructured, OLAP application sources, both Oracle and non-Oracle. It interacts with the Presentation server over T/IP and takes the reporting request from the presentation server. Then the BI server processes the request and form logical and physical queries(in case of database as data source) and this physical query is sent to the underlying data source from which the data is processed. The BI Server interacts with the underlying database using ODBC. Hence, the entire processing of request is done by the BI server. In the above paragraph I have mentioned that the BI server creates a logical and physical query. But how will the BI server generate this query?? How will the BI Server know what all s need to be used?? I guess all these questions must be coming to your mind. So, lets understand the underlying process..
The BI server makes use of the BI Repository for converting the request into logical and physical queries. The BI Repository is the metadata using which the server gets the information of the s and the filters to be used in the query. It is the backbone of the architecture. Now, this is the place where all the modelling is done and the role of OBIEE developers come into picture
.
The BI Repository is created using the istration Tool. The repository contains three layers: Physical, BMM and Presentation Layer.
Physical Layer: Contains the tables imported from the underlying DB with appropriate s between them. BMM Layer: This is the Business Model layer and hence all the Business logics are implemented on this layer eg: Calculation of %age Sales, Revenue etc. Presentation Layer: As the names specifies this layer is used for Presentation of required tables and columns to the s. The columns pulled in this layer are directly visible to the s. Where BI Server and Tool come in picture??? Now, when the s to the BI Answers i.e the interface, they see all the columns that are pulled on the Presentation Layer in the Repository. They choose the desired columns from there and click results button to view the report. After that the request is sent to the BI Server through the Presentation server, the BI server makes use of the BI Repository to formulate a query out of the requested report based on the s and tables specified in the repository. This query is sent to the underlying DB and hence results are fetched.
Insight of OBIEE Architecture-IV 20 NOVEMBER 2010 10,232 VIEWS 7 COMMENTS
(4 votes, average: 4.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hey Friends, We have been discussing the OBIEE Architecture and we have covered 3 segments. So, here I am with the 4th segment DataSources. This is a rather simple one as we all know till now that OBIEE is a reporting tool and works on data from underlying Databases, so here DataSources are the underlying Databases with which the OBIEE server interacts. OBIEE is a very smart tool and it has got the capability of reporting on multiple Databases and also multiple types of Databases like XML, Oracle, SQL Server etc.
Now, in the previous posts you have seen what is an OBIEE Repository and what is the Physical Layer and what are connection pools. I am reminding you of these things because our current segment is based on this and we will see how. Now, when we design the OBIEE Metadata or repository for reporting, we import the tables on which we need to perform reporting into the physical layer from the respective DBs. And then we apply appropriate s between the tables and furthur pull them to BMM and then to Presentation Layer for reporting. The question that comes out here is “How does the BI Server interacts with the underlying DBs for showing the reports???” The answer to this question lies in the Connection Pools. If we open the Connection Pool we can see that we need to select the Call Interface, give the name of the DSN, give a name and . These things help up to connect to the Database. Call Interface – There is a drop down from where we can select the appropriate Call Interface. Some examples are ODBC, OCI etc. Both ODBC and OCI can be used for Oracle. The main difference between using them is, In ODBC we need to create a DSN in the system where the server is installed but OCI is a native DSN and we can use it directly without creating the DSN in the system. DSN- This is the name of the DSN which OBIEE uses to connect to the underlying DB. name- The with which OBIEE connects the DB. Generally the used for reporting should only have the read priviledges on the DB. - of the with which OBIEE connects to the DB. Now, when a runs the report in Answers the OBIEE server accesses the DB using the connection pool with the specified Call Interface and name and returns the data. The next question is “How does the BI server takes care of a report formed using columns and tables from multiple DBs???” As I have told you earlier also that BI server is very intellegent and is built in such a way that it can process request formed form multiple DBs. When the generates a report involving multiple DBs, the request navigates to the Navigator section in the BI Server which checks the underlying DBs with which OBIEE needs to interact to. Then the BI server generates separate queries for the DBs and fire them on the respective DBs. Then it fetches the data from the underlying DBs and combines the result set in its own memory and displays the result in the report. With this post we have covered the 4 segments of the OBIEE Architecture. I hope this will help you alot in understanding the BI Architecture and also in understanding the OBIEE behaviour. In the posts I will also try to go into the details and throw some more light on the BI Server components.
vertical tabs/pages in obiee dashboards
hello world............. Intermittently I stumble across requests seeking a workaround to display tabs unconventionally i.e. vertically. Work around on how to display tabs across rows is purely simple manual effort (I don't think there exists more than 15 tabs, which is acceptable). Infra, the steps on how to accomplish this:
1. After creating dashboard pages, access the speed menu and "View Source"...locate the table with id="TabsTable", which consists of all dashboard pages & is unique within a dashboard. 2. In above table tag add style attribute, i.e. style="position: absolute; top: 90px; left: 0px;". In here the table is removed from normal workflow by specifying absoulte position. Customize other options. 3. TabsTable consists of only a single row, which must be changed to accomodate all the tabs. Just add multiple row tags leaving all td tags as is. In the sample script below assume there exists two pages: 1-My Page, & 2-Page Under Construction... as highlighted in blue & My Page is active tab. [table cellspacing="0px" cellpadding="0px" border="0" style="position: absolute; top: 90px; left: 0px;" id="TabsTable"] [tbody] [tr] [td class="TabHiCell"][a class="TabHiFontLink" href="javascript:void(null)" id="HighTab" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=My\x2520Page')" title=""][span class="TabHiFont"]My Page[/span][/a][/td][/tr] [tr] [td class="TabDimCell"][a class="TabDimFont" href="javascript:void(null)" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=Page\x2520Under\x2520Construction...')" title=""]Page Under Construction...[/a][/td][/tr] [/tbody] [/table] 4. From the script, id="HighTab" can be removed, which does not have any side effects. Also note the classes of the two defined tabs. It is sufficice to just saw.dll?Dashboard&PortalPath=xxxx&Page=yyyy as an argument to DashboardChangePage shown in the above script. I did leave as is to
illustrate the example. 5. Place the above script in a text object on My Page. Place the text object at last. 6. Now, before placing the same script on Page Under Construction... toggle all the classes & add span tag to the innerHTML text of the anchor tag. As this tab is being activated currently, the previous tab looses focus. Changes are highlighted in black i.e. [table cellspacing="0px" cellpadding="0px" border="0" style="position: absolute; top: 90px; left: 0px;" id="TabsTable"] [tbody] [tr] [td class="TabDimCell"][a class="TabDimFont" href="javascript:void(null)" id="HighTab" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=My\x2520Page')" title=""]My Page[/a][/td][/tr] [tr] [td class="TabHiCell"][a class="TabHiFontLink" href="javascript:void(null)" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=Page\x2520Under\x2520Construction...')" title=""][span class="TabHiFont"]Page Under Construction...[/span][/a][/td][/tr] [/tbody] [/table] 7. The final step involves hiding the already existing horizontal tabs....you do this simply by adding additional dashboard text object. Make sure you add this dashboard text object ABOVE the text object containing above scripts. [script type="text/javascript"]
document.getElementById('TabsTable').style.display="none"; [/script]
8. Thus, all the tabs are displayed vertically. Make sure you align your dashboard objects with respect to the vertically displayed tabs. If not aligned properly, content overlaps. 9. A sample screen shot of the dashboard pages are shown on the right. Note: Tabs can be formatted in anyway as per the requirement. -nag
Editing All choices in Dashboard prompts of OBIEE Step1: Create a prompt under the Sql results use the following SQL SELECT CASE WHEN 1=0 THEN Products.UPC ELSE 'All Items' END FROM Paint UNION ALL SELECT Products.UPC FROM Paint
a) Why we are using CASE WHEN 1=0 whether that condition is always false.Because the BI Server will refer to a table to fire query.If you doesn't give then it will give an error like State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 42021] The query does not reference any tables. (HY000) SQL Issued: SELECT 'All Items' FROM Paint UNION ALL SELECT Products.UPC FROM Paint
Step2:In the report you will get No results where UPC is equal to All Items
JAY said: Can u please explain the difference between Physical and Complex ? # 29 July 2010 at 4:07 PM
Rohit (author) said: Yes, Sure JAY!!! The Difference between Physical and complex s is that the Physical s are the s which are placed on the Primary and Foreign Keys between the 2 tables. The physical s are mostly used in Physical Layer. The OBIEE server creates its Physical query based on these s which further hits the Database and fetches the data. Whereas, Complex s are mostly used on the BMM layer and these are not created on PK & FK. The OBIEE server creates a logical requests based on these s. Kindly let me know in case of any further concerns or queries…. # 30 July 2010 at 3:29 AM
Sudhakar said: Hi, Suppose, we implemented complex s in physical layer and the the Analytics server issues query against the underlying database. By seeing the query, how to identify whether the is complex or not? # 14 August 2010 at 2:20 PM
Libral said: Hi Rohit, I am confused about complex and unable to understand in which situation it should be used. My understanding is as follows,
1. you can either have foreign key or complex . 2. in the physical layer, most of the time you use foreign key , the only exception is when you have non-equi condition (for eg between…). Can you please explain the Complex in detail. # 29 October 2010 at 2:56 AM
Rohit (author) said: Hi, When we run a report, the BI Server generates 2 queries: 1) Logical 2) Physical Now, the BI Server takes complex s into consideration while generating the logical query and furthur the Physical query out of the logical query. Generally, we make use of Complex s in the BMM layer. In BMM, Complex s are always applied between the tables folders and not the logical table sources, hence, it facilitates the extendibility for future uses. We can add many LTS to the table folder without changing the s in BMM. The compplex s doesnt apply on any specific columns in BMM and the server takes the reference from the Physical layer and establish the s between them. We can also make use of the Complex s in the Physical Layer in case of the non equal conditions eg: When we on some non key columns and use non equality conditions. Kindly let me know what else do u want to know about the complex s or if you have any confusion. # 31 October 2010 at 1:24 AM
Libral said: Rohit, Thank you so much, I have understood the concept to a certain extentd but can you explain it with one example (for example foreign key is straight forward, you define it and when select column from table having parent child relationship then it be applied, BUT HOW a complex is defined and WHAT EFFECT it has on the physical query that is generated by BI server is not clear).
OBIEE - How to define one different database credential for each (the shared logon) ? About
For system architecture reasons, you may want to have one database credential by . Example :
When one schema (of one ) is the logical entity of one company, you may decide to have the same table in two different schema but with the data for only one company
Articles Related
OBIEE - Connection Pool
OBIEE 10G/11G - Query Cache of BI Server
OBIEE - Security
How to do To achieve it, you have to unmark the check box “Shared Logon” of the connection pool property in the physical layer. You can remark that the and box become gray. Now, the Obiee s don't share no the same credential and you have to define for each Obiee , one credential (one name, one ). To define the new credentials :
open the Oracle BI istration tool
open the security manager (Manage> Security)
click on the map
double click on a
define in the tab logon the credential for your database
The importance of disabling the cache If the don't share the same data, you have to disable the query cache by setting NO on theENABLE parameter in the cache section of the file nqsconfig If you don't disable the query cache, Obiee will perform an hit cache and retrieve the data from its cache as you can see in the log :
Insight of OBIEE Architecture 21 MAY 2010 27,906 VIEWS 10 COMMENTS (16 votes, average: 4.63 out of 5)
Table of contents for Architecture
1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, I am sorry that I engrossed myself in posting some complex stuff and left the Basics in between, so, here I am again with the Basics of OBIEE. In our previous posts we have covered Data Modelling, Basics, Connection Pool, s etc. So, lets start to build more on that and lets go through the Architecture of OBIEE. The below diagram shows the basic architecture of OBIEE and its components:
Now, first of all lets understand the flow in which a request flows from Client to Data Source. If a client runs a report, the request first goes to the Presentation Server and then it gets routed to the BI Server and then it gets further routed to the underlying Database or the data source. Client -> Presentation Server -> BI Server -> Data source Now, the request is routed back through the similar route to the client. Which means, the data is fetched from the Data source and it gets routed to Presentation server through BI server and then to the client. Client <- Presentation Server <- BI Server <- Data Source The above flows provide a very basic idea of how the data is fetched and showed in a report in OBIEE. Now, lets understand it more properly by dividing the above diag. into segments and then : 1) Client and Interface 2) Presentation Server & Presentation Catalog 3) BI Server & Tool 4) Datasource Client & Interface: This level has the UI of OBIEE which is accessible to the clients and s. The OBIEE UI has several components like OBIEE Answers, Interactive Dashboards etc.
Oracle BI Answers is a powerful, ad hoc query and analysis tool that works against a logical view of information from multiple data sources in a pure Web environment.
Oracle BI Interactive Dashboards are interactive Web pages that display personalized, role-based information to guide s to precise and effective decisions.
BI Delivers is an alerting engine which gives s flexibility to schedule their reports and get them delivered to their handheld devices or interactive dashboards or any other delivery profile and helps in making quick business decisions.
In simpler we can say that, this is a web application which is accessible to the s for preparing their reports/dashboards and do Ad-Hoc reporting to cater the business needs.
We will continue with the other segments in the posts. Till that time if you have any questions or comments they are most welcome. Keep posting…
Insight of OBIEE Architecture-II 22 MAY 2010 17,811 VIEWS 4 COMMENTS (3 votes, average: 5.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, In the previous post we were studying the architecture of OBIEE, so, lets continue with it. We have divided OBIEE Architecture in 4 segments to better understand it. 1) Client and Interface 2) Presentation Server & Presentation Catalog 3) BI Server & Tool 4) Datasource We have covered the first segment in the previous post. So, lets understand the second segment.
Presentation Server & Presentation Catalog: The BI Presentation server is basically a web server on which the OBIEE web application runs. It processes the client requests and routes it to the BI Server and vice versa. It can be deployed on any of the following IIS or Oc4j. It makes use of the Presentation catalog which contains the aspects of the application.
The Presentation catalog stores the application dashboards, reports, folders and filters. It also contains information regarding the permissions of dashboards & reports created by s. It is created when the Presentation server starts and can be istered using the tool called Catalog Manager. In other words we can say that the Presentation server and the Presentation Catalog are together responsible for providing the clients with a web server on which the web application runs and also isters the look and feel of the Interface. This post covers basics of the Presentation server & catalog. We will be covering the BI server in the post. Till that time stay tuned and keep posting… Previous in series Next in series
Insight of OBIEE Architecture-III 18 AUGUST 2010 13,244 VIEWS 11 COMMENTS (1 votes, average: 5.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hi Frens, Sorry to keep you waiting for the next post, but here it comes. Previously, in the second segment we have discussed the Presentation Server and the Presentation catalog. So, lets continue with the third segment where we will see what is the role of the BI Server in the OBIEE Architecture.
BI SERVER AND TOOL BI Server is a highly scalable query and analysis server. It is the heart of the entire architecture. It efficiently integrates data from multiple relational, unstructured, OLAP application sources, both Oracle and non-Oracle. It interacts with the Presentation server over T/IP and takes the reporting request from the presentation server. Then the BI server processes the request and form logical and physical queries(in case of database as data source) and this physical query is sent to the underlying data source from which the data is processed. The BI Server interacts with the underlying database using ODBC. Hence, the entire processing of request is done by the BI server. In the above paragraph I have mentioned that the BI server creates a logical and physical query. But how will the BI server generate this query?? How will the BI Server know what all s need to be used?? I guess all these questions must be coming to your mind. So, lets understand the underlying process..
The BI server makes use of the BI Repository for converting the request into logical and physical queries. The BI Repository is the metadata using which the server gets the information of the s and the filters to be used in the query. It is the backbone of the architecture. Now, this is the place where all the modelling is done and the role of OBIEE developers come into picture
.
The BI Repository is created using the istration Tool. The repository contains three layers: Physical, BMM and Presentation Layer.
Physical Layer: Contains the tables imported from the underlying DB with appropriate s between them. BMM Layer: This is the Business Model layer and hence all the Business logics are implemented on this layer eg: Calculation of %age Sales, Revenue etc. Presentation Layer: As the names specifies this layer is used for Presentation of required tables and columns to the s. The columns pulled in this layer are directly visible to the s. Where BI Server and Tool come in picture??? Now, when the s to the BI Answers i.e the interface, they see all the columns that are pulled on the Presentation Layer in the Repository. They choose the desired columns from there and click results button to view the report. After that the request is sent to the BI Server through the Presentation server, the BI server makes use of the BI Repository to formulate a query out of the requested report based on the s and tables specified in the repository. This query is sent to the underlying DB and hence results are fetched.
Insight of OBIEE Architecture-IV 20 NOVEMBER 2010 10,232 VIEWS 7 COMMENTS
(4 votes, average: 4.00 out of 5)
Table of contents for Architecture 1.
Insight of OBIEE Architecture
2.
Insight of OBIEE Architecture-II
3.
Insight of OBIEE Architecture-III
4.
Insight of OBIEE Architecture-IV
Hey Friends, We have been discussing the OBIEE Architecture and we have covered 3 segments. So, here I am with the 4th segment DataSources. This is a rather simple one as we all know till now that OBIEE is a reporting tool and works on data from underlying Databases, so here DataSources are the underlying Databases with which the OBIEE server interacts. OBIEE is a very smart tool and it has got the capability of reporting on multiple Databases and also multiple types of Databases like XML, Oracle, SQL Server etc.
Now, in the previous posts you have seen what is an OBIEE Repository and what is the Physical Layer and what are connection pools. I am reminding you of these things because our current segment is based on this and we will see how. Now, when we design the OBIEE Metadata or repository for reporting, we import the tables on which we need to perform reporting into the physical layer from the respective DBs. And then we apply appropriate s between the tables and furthur pull them to BMM and then to Presentation Layer for reporting. The question that comes out here is “How does the BI Server interacts with the underlying DBs for showing the reports???” The answer to this question lies in the Connection Pools. If we open the Connection Pool we can see that we need to select the Call Interface, give the name of the DSN, give a name and . These things help up to connect to the Database. Call Interface – There is a drop down from where we can select the appropriate Call Interface. Some examples are ODBC, OCI etc. Both ODBC and OCI can be used for Oracle. The main difference between using them is, In ODBC we need to create a DSN in the system where the server is installed but OCI is a native DSN and we can use it directly without creating the DSN in the system. DSN- This is the name of the DSN which OBIEE uses to connect to the underlying DB. name- The with which OBIEE connects the DB. Generally the used for reporting should only have the read priviledges on the DB. - of the with which OBIEE connects to the DB. Now, when a runs the report in Answers the OBIEE server accesses the DB using the connection pool with the specified Call Interface and name and returns the data. The next question is “How does the BI server takes care of a report formed using columns and tables from multiple DBs???” As I have told you earlier also that BI server is very intellegent and is built in such a way that it can process request formed form multiple DBs. When the generates a report involving multiple DBs, the request navigates to the Navigator section in the BI Server which checks the underlying DBs with which OBIEE needs to interact to. Then the BI server generates separate queries for the DBs and fire them on the respective DBs. Then it fetches the data from the underlying DBs and combines the result set in its own memory and displays the result in the report. With this post we have covered the 4 segments of the OBIEE Architecture. I hope this will help you alot in understanding the BI Architecture and also in understanding the OBIEE behaviour. In the posts I will also try to go into the details and throw some more light on the BI Server components.
vertical tabs/pages in obiee dashboards
hello world............. Intermittently I stumble across requests seeking a workaround to display tabs unconventionally i.e. vertically. Work around on how to display tabs across rows is purely simple manual effort (I don't think there exists more than 15 tabs, which is acceptable). Infra, the steps on how to accomplish this:
1. After creating dashboard pages, access the speed menu and "View Source"...locate the table with id="TabsTable", which consists of all dashboard pages & is unique within a dashboard. 2. In above table tag add style attribute, i.e. style="position: absolute; top: 90px; left: 0px;". In here the table is removed from normal workflow by specifying absoulte position. Customize other options. 3. TabsTable consists of only a single row, which must be changed to accomodate all the tabs. Just add multiple row tags leaving all td tags as is. In the sample script below assume there exists two pages: 1-My Page, & 2-Page Under Construction... as highlighted in blue & My Page is active tab. [table cellspacing="0px" cellpadding="0px" border="0" style="position: absolute; top: 90px; left: 0px;" id="TabsTable"] [tbody] [tr] [td class="TabHiCell"][a class="TabHiFontLink" href="javascript:void(null)" id="HighTab" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=My\x2520Page')" title=""][span class="TabHiFont"]My Page[/span][/a][/td][/tr] [tr] [td class="TabDimCell"][a class="TabDimFont" href="javascript:void(null)" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=Page\x2520Under\x2520Construction...')" title=""]Page Under Construction...[/a][/td][/tr] [/tbody] [/table] 4. From the script, id="HighTab" can be removed, which does not have any side effects. Also note the classes of the two defined tabs. It is sufficice to just saw.dll?Dashboard&PortalPath=xxxx&Page=yyyy as an argument to DashboardChangePage shown in the above script. I did leave as is to
illustrate the example. 5. Place the above script in a text object on My Page. Place the text object at last. 6. Now, before placing the same script on Page Under Construction... toggle all the classes & add span tag to the innerHTML text of the anchor tag. As this tab is being activated currently, the previous tab looses focus. Changes are highlighted in black i.e. [table cellspacing="0px" cellpadding="0px" border="0" style="position: absolute; top: 90px; left: 0px;" id="TabsTable"] [tbody] [tr] [td class="TabDimCell"][a class="TabDimFont" href="javascript:void(null)" id="HighTab" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=My\x2520Page')" title=""]My Page[/a][/td][/tr] [tr] [td class="TabHiCell"][a class="TabHiFontLink" href="javascript:void(null)" target="_self" onclick="return DashboardChangePage('saw.dll?Dashboard&_scid=e55KyvQkYnQ&PortalPath=/s/xxxxxx/ _portal&Page=Page\x2520Under\x2520Construction...')" title=""][span class="TabHiFont"]Page Under Construction...[/span][/a][/td][/tr] [/tbody] [/table] 7. The final step involves hiding the already existing horizontal tabs....you do this simply by adding additional dashboard text object. Make sure you add this dashboard text object ABOVE the text object containing above scripts. [script type="text/javascript"]
document.getElementById('TabsTable').style.display="none"; [/script]
8. Thus, all the tabs are displayed vertically. Make sure you align your dashboard objects with respect to the vertically displayed tabs. If not aligned properly, content overlaps. 9. A sample screen shot of the dashboard pages are shown on the right. Note: Tabs can be formatted in anyway as per the requirement. -nag
Editing All choices in Dashboard prompts of OBIEE Step1: Create a prompt under the Sql results use the following SQL SELECT CASE WHEN 1=0 THEN Products.UPC ELSE 'All Items' END FROM Paint UNION ALL SELECT Products.UPC FROM Paint
a) Why we are using CASE WHEN 1=0 whether that condition is always false.Because the BI Server will refer to a table to fire query.If you doesn't give then it will give an error like State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 42021] The query does not reference any tables. (HY000) SQL Issued: SELECT 'All Items' FROM Paint UNION ALL SELECT Products.UPC FROM Paint
Step2:In the report you will get No results where UPC is equal to All Items
Related Documents 543cg
Obiee Scenarios 362s36
October 2019 63
Sd Scenarios 6v3p4n
August 2020 0
Obiee Introduction 2p1c1a
July 2022 0
Obiee Functions 6qj4m
December 2019 42
Obiee 12c z23x
December 2019 47