1. Tell me about your self?
Ans: Your profile and project details. and also explain about your worked domains.
2. Explain OBIEE 11g Architecture?
Ans:OBIEE 11g Architecture
Domains in OBIEE
7. What is the purpose of Alias Tables?
An Alias table is a physical table with the type of Alias. It is a reference to a physical table, and inherits all its column definitions and some properties from the physical table. A logical table source shows how the logical objects are mapped to the physical layer and can be mapped to physical tables, stored procedures and select statements. An alias table can be a reference to any of these logical table source types.
Alias Tables can be an important part of designing a physical layer. The following is a list of the main reasons to create an alias table:
1. To reuse an existing table more than once in your physical layer (without having to import it several times)
2. To set up multiple alias tables, each with different keys, names, or joins
3. To help you design sophisticated star or snowflake structures in the business model layer. Alias tables are critical in the process of converting ER Schemas to Dimensional Schemas.
13. What are different types of variables? Explain each.
There are two classes of variables:
1. Repository variables
2. Session variables
Repository variables-
A repository variable persists from the time the repository is started.
Static: This value does not change until a Siebel Analytics Server administrator decides to change it.
Dynamic: The values of these variables change with the values returned by queries. These variables are linked to an initialization block. An initialization block contains a SQL query. When the repository is started the value returned by the query in the initialization block will be assigned to the dynamic variable.
Session Variables-
Session variables are created and assigned a value when each user logs on(when a new session is started). There are two types of session variables:
1. System: System variables have reserved names, which cannot be used for other kinds of variables (such as static or dynamic repository variables, or for non-system session variables).
Ex: To filter a column on the value of the variable LOGLEVEL set the filter to the Variable NQ_SESSION.LOGLEVEL.
2. Non-system: A common use of non-system variables is for setting user filters. Ex: you could define a non-system variable called ‘SalesRegion’ that would be initialized to the name of the user’s sales region. You could then set a security filter for all members of a group that would allow them to see only data pertinent to their region. For example, to filter a column on the value of the variable ‘SalesRegion’ set the filter to the Variable NQ_SESSION.SalesRegion.
14.What is Authentication? How many types of authentication do we have in OBIEE?
Authentication is the process by which a system verifies a user with the help of a user ID and password. It checks if user has the necessary permissions and authorizations to log in and access data. There are 4 main types of Authentication in OBIEE:
Operating system authentication
External table authentication
Database authentication
LDAP authentication
Ans: Your profile and project details. and also explain about your worked domains.
2. Explain OBIEE 11g Architecture?
Ans:OBIEE 11g Architecture
Web Logic Server Domain
• WLS Admin Console
• Admin GUI for WLS,Security and J2EE Components
• Fusion Middleware-EM Control (FMW EM)
• Admin GUI to Manage the BI Domain
• JMX Beans
• Java components that provide programmatic access for managing a BI domain.
Managed Server Components
• BI Plugin : Sends web http requests to BI Presentation Services
• BI Security :Integrates BI Server and FMW sec platform(using webservice calls)
• BI Action Services: Dedicated web services for Action framework
• BI Web Service SOA: Provides Web services for objects in the BIEE Presentation Catalog, to invoke analysis, agents, and conditions.
• BI Office: Provides the integration between Oracle Business Intelligence and Microsoft Office products
BIEE Domain System Components
• BI Server
– Provides capabilities to query and access data as well as services for accessing and managing the RPD file (BIEE Metadata).
• BI Presentation Services
– Provides the framework and interface for the presentation of business intelligence data to Web clients. It maintains an Oracle BI Presentation Catalog service on the file system for the customization of this presentation framework.
• BI Scheduler
– Provides framework for scheduling and delivering reports to users (used by delivers)
• BI Javahost
– Enables BI Presentation Services to support various components: Java tasks for BI Scheduler, BI Publisher, and Graph generation.
• BI Cluster Controller
– Used for distributing requests to BI server and ensure load balancing
• Files
– Repository file (e.g. SampleSales.rpd)
– Config Files (nQconfig.ini,instanceconfig.xml,)
– Log Files (nqserver.log,nqquery.log, nqscheduler.log, sawlog0.log etc)
– Presentation catalog(<MW_HOME>\OracleBIPresentationServicesComponent\coreapplication_obips1\ca
• J2EE App Server used across the board for all 11g BI applications
• Contains :
– Managed Server : Set of J2EE Applications used for “functioning” the BIEE system
– Admin Server : Set of J2EE Applications used for “administering” of BI EE system
· Oracle Process Manager and Notification Server (OPMN) domain
• Used to start/Stop system components (BI Svr, BI Pres Svr, BI Schdlr, BI ClustrCntrl)
• Can be accessed from CMD or from EM page(GUI)
Admin Server Components• WLS Admin Console
• Admin GUI for WLS,Security and J2EE Components
• Fusion Middleware-EM Control (FMW EM)
• Admin GUI to Manage the BI Domain
• JMX Beans
• Java components that provide programmatic access for managing a BI domain.
Managed Server Components
• BI Plugin : Sends web http requests to BI Presentation Services
• BI Security :Integrates BI Server and FMW sec platform(using webservice calls)
• BI Action Services: Dedicated web services for Action framework
• BI Web Service SOA: Provides Web services for objects in the BIEE Presentation Catalog, to invoke analysis, agents, and conditions.
• BI Office: Provides the integration between Oracle Business Intelligence and Microsoft Office products
BIEE Domain System Components
• BI Server
– Provides capabilities to query and access data as well as services for accessing and managing the RPD file (BIEE Metadata).
• BI Presentation Services
– Provides the framework and interface for the presentation of business intelligence data to Web clients. It maintains an Oracle BI Presentation Catalog service on the file system for the customization of this presentation framework.
• BI Scheduler
– Provides framework for scheduling and delivering reports to users (used by delivers)
• BI Javahost
– Enables BI Presentation Services to support various components: Java tasks for BI Scheduler, BI Publisher, and Graph generation.
• BI Cluster Controller
– Used for distributing requests to BI server and ensure load balancing
• Files
– Repository file (e.g. SampleSales.rpd)
– Config Files (nQconfig.ini,instanceconfig.xml,)
– Log Files (nqserver.log,nqquery.log, nqscheduler.log, sawlog0.log etc)
– Presentation catalog(<MW_HOME>\OracleBIPresentationServicesComponent\coreapplication_obips1\ca
3.What is end to end life cycle of OBIEE?
Ans: -> Gather Business Requirements.
-> Identify source system.
-> Design ETL to load to a DW if source data doe's not Exist.
-> Build the repository
-> Build the dash boards and reports
-> Define securty
-> the peformance and use the agregations/cache mechanism if it is requre.
-> Testing and QA.
4. Difference of OBIEE 10g and 11g
Ans:
a. In 10g OC4J (Oracle container for java) . In 11g its Weblogic server
b. Security is managed by RPD in 10 g. In 11g the security is managed by the welogic server.
c. In 10g we had Foreign key join (physical layer) & complex key join (BMM). We only have a New Key Join in case of 11g , which is used at both the BMM & Physical layer.
d. 11g supports cross join hierarchies example we can move from customer dimension to product dimension during drilling down. Supports ragged hierarchies etc.
e. 11g also has column hierarchies available in the presentation services, which are created simply by dragging the dimension hierarchies from the BMM layer to the presentation layer in RPD.
when column hierarchies are used to build an analyses the default view is Pivot table.
f. The time series functions Ago & ToDate which where only available in the RPD with 10g are now also available in the presentation services along with a new function RollingPeriod.
g. The analyses can now by reconstructed at run time, that means we can move column attribute from the x-axis to the y-axis and reverse as well.
h.KPI’s are available in the 11g along with KPI Watchlist on which they are deployed to be viewed by the end user. Key Performance indicators (metrics very essential for the business)
i. Concept of scorecards is available in 11g, which can measure the goal/mission by using KPI’s as the building blocks for the same
j. concept of Seletions is now available in the presentation services in 11g.
k. There is a single portal for the bi publisher/bi intelligence. The reports that are built in the BI Publisher are stored in the same catalog, as the analyses created using the bi intelligence.
l. 11g has Action Framework which can by used to invoke, existing analyses, html, java procedures
5 – What kind of sources can be
connected to OBIee ?
Ans:
OBIee can be plugged on
Relational Databases, Cubes or Flat files, with the following constraints :
- The sources must be modeled as star schemas or snowflakes schemas in order to have an efficient and safe behavior.
- In case of multiple sources directly in OBIee used together, be aware that OBIee will conduct the needed joins itself, and OBIee is not a database.
Theoretically, yes. In
practice, the two subject area must come from the same business model in the
repository.. Then, we can consider the two following
alternatives :
- Create an analysis with “combine request”: one subrequest by subject area. Note that it’s tricky to implement for standard users.
7. What is the purpose of Alias Tables?
An Alias table is a physical table with the type of Alias. It is a reference to a physical table, and inherits all its column definitions and some properties from the physical table. A logical table source shows how the logical objects are mapped to the physical layer and can be mapped to physical tables, stored procedures and select statements. An alias table can be a reference to any of these logical table source types.
Alias Tables can be an important part of designing a physical layer. The following is a list of the main reasons to create an alias table:
1. To reuse an existing table more than once in your physical layer (without having to import it several times)
2. To set up multiple alias tables, each with different keys, names, or joins
3. To help you design sophisticated star or snowflake structures in the business model layer. Alias tables are critical in the process of converting ER Schemas to Dimensional Schemas.
8.Can you use
physical join in BMM layer?
Yes we can use physical join in BMM layer.
9.What is level based metrics?
Level based metrics means, having a measure pinned at a certain level of the dimension.
A LBM is a metric that is defined for a specific level or intersection of levels.
Monthly Total Sales or Quarterly Sales are the examples.
Ex: if you have a measure called “Dollars”, you can create a “Level Based Measure” called “Yearly Dollars” which is Dollars for a Year. This measure will always return the value for the year even if you drill down to a lower level like quarter, month, etc. To create a level based measure, create a new logical column based on the original measure (like Dollars in the example above). Drag and drop the new logical column to the appropriate level in the Dimension hierarchy in the above example you will drag and drop it to Year in Time Dim.
9.What is level based metrics?
Level based metrics means, having a measure pinned at a certain level of the dimension.
A LBM is a metric that is defined for a specific level or intersection of levels.
Monthly Total Sales or Quarterly Sales are the examples.
Ex: if you have a measure called “Dollars”, you can create a “Level Based Measure” called “Yearly Dollars” which is Dollars for a Year. This measure will always return the value for the year even if you drill down to a lower level like quarter, month, etc. To create a level based measure, create a new logical column based on the original measure (like Dollars in the example above). Drag and drop the new logical column to the appropriate level in the Dimension hierarchy in the above example you will drag and drop it to Year in Time Dim.
10. What is object level security?
There are two types of object level security: Repository level and Web level
Repository level: In presentation layer we can set Repository level security by giving permission or deny permission to users/groups to see particular table or column.
Web level: this provides security for objects stored in the OBIEE web catalog, such as dashboards, dashboards pages, folder, and reports you can only view the objects for which you are authorized. For example, a mid-level manager may not be granted access to a dashboard containing summary information for an entire department.
11. What is data level security?
This controls the type or amount of data that you can see in a report. When multiple users run the same report the results that are returned to each depend on their access rights and roles in the organization. For example a sales vice president sees results for all regions, while a sales representative for a particular region sees data for that region.
12. What is the difference between Data Level Security and Object Level Security?
Data level security controls the type and amount of data that you can see in a report. Object level security provides security for objects stored in the OBIEE web catalog like dashboards, dashboards pages, folder and reports.
There are two types of object level security: Repository level and Web level
Repository level: In presentation layer we can set Repository level security by giving permission or deny permission to users/groups to see particular table or column.
Web level: this provides security for objects stored in the OBIEE web catalog, such as dashboards, dashboards pages, folder, and reports you can only view the objects for which you are authorized. For example, a mid-level manager may not be granted access to a dashboard containing summary information for an entire department.
11. What is data level security?
This controls the type or amount of data that you can see in a report. When multiple users run the same report the results that are returned to each depend on their access rights and roles in the organization. For example a sales vice president sees results for all regions, while a sales representative for a particular region sees data for that region.
12. What is the difference between Data Level Security and Object Level Security?
Data level security controls the type and amount of data that you can see in a report. Object level security provides security for objects stored in the OBIEE web catalog like dashboards, dashboards pages, folder and reports.
13. What are different types of variables? Explain each.
There are two classes of variables:
1. Repository variables
2. Session variables
Repository variables-
A repository variable persists from the time the repository is started.
Static: This value does not change until a Siebel Analytics Server administrator decides to change it.
Dynamic: The values of these variables change with the values returned by queries. These variables are linked to an initialization block. An initialization block contains a SQL query. When the repository is started the value returned by the query in the initialization block will be assigned to the dynamic variable.
Session Variables-
Session variables are created and assigned a value when each user logs on(when a new session is started). There are two types of session variables:
1. System: System variables have reserved names, which cannot be used for other kinds of variables (such as static or dynamic repository variables, or for non-system session variables).
Ex: To filter a column on the value of the variable LOGLEVEL set the filter to the Variable NQ_SESSION.LOGLEVEL.
2. Non-system: A common use of non-system variables is for setting user filters. Ex: you could define a non-system variable called ‘SalesRegion’ that would be initialized to the name of the user’s sales region. You could then set a security filter for all members of a group that would allow them to see only data pertinent to their region. For example, to filter a column on the value of the variable ‘SalesRegion’ set the filter to the Variable NQ_SESSION.SalesRegion.
14.What is Authentication? How many types of authentication do we have in OBIEE?
Authentication is the process by which a system verifies a user with the help of a user ID and password. It checks if user has the necessary permissions and authorizations to log in and access data. There are 4 main types of Authentication in OBIEE:
Operating system authentication
External table authentication
Database authentication
LDAP authentication
No comments:
Post a Comment