Metadata Creation In OBIEE

OBIEE A Webinar Metadata Creation In OBIEE

Agenda Introduction to OBIEE Metadata Use of Administration Tool Concepts of Physical Layer Concepts of Business Model and Mapping Layer Concepts of Presentation Layer Building of these 3 layers

Introduction to Oracle BI EE Repository Stores Meta Data used by Oracle Server Is accessed and configured using the Oracle BI Administration Tool, Oracle BI Repository models the data using the metadata from heterogeneous data sources into objects called Layers. Physical Layer Business Model And Mapping Layer Presentation Layer.

Introduction to Oracle BI EE Repository Physical layer to get the metadata directly from the database Business model and mapping layer is where you can apply your business logic according to business requirement. Presentation layer is used for providing the customized view to the users hiding all the business logic.

Oracle Administration Tool The Administration Tool is used to build a repository. It provides a graphical representation of the three layers. Also it helps you to build, manage and administer Oracle BI Repositories.

Physical Layer This is the First Layer in the repository Contains Information about the physical sources to which the Oracle BI server submits queries. Can connect to multiple Data Sources e.g. DB2, SQL, Flat Files, Excel files, MS Access, Sybase, Oracle etc.

Physical Layer Objects Database object Connection Pool Schema Folder Physical Table Physical Column Key Column Database object Physical table Physical column Key column Schema older Connection Pool

Physical Layer Objects cont… Database Object: Database Object highest level object. Defines the data source to which the BI server submits the queries. Database object Name Type

Physical Layer Objects cont… Database Features Tab: Is used to view and set the SQL features that is used with Oracle Data Source. Enable or Disable Feature Default SQL Features for this data source

Physical Layer Objects cont… Connection Pool: Contains information about the connection between Oracle BI Server and the Data Sources. Allows multiple users to share a pool of data source. Maximum number of connections Connection pool name Data source name Shared logon user name & password Connection pooling enabled

Physical Layer Objects Cont…. Schema Folder: Contains the Tables and columns when it is imported from the Database. Physical Table: Typically imported from the database or other Data Sources Provides the necessary metadata to the OBI server to access the tables with SQL requests. Schema folder Physical table

Physical Table Properties Name Table type Physical Table Stored Procedure Select Cacheable Foreign Key Table type Use tabs to create, view, or modify other properties. Name Cacheable

Physical Table :Alias Table Type Name Source Table Name Source Table

Physical Layer Objects Cont…. Physical column: Corresponds to the column in the Physical Layer. Key Column: Relationship between tables Primary Key: Uniquely identifies single row of data and is identified by the key column. Foreign Key: Refers to the Primary key columns in the other table. Composed of a column or a set of column.

Joins Represents the Primary Key- Foreign Key relationships between the tables in the Physical layer.

Business Model and Mapping Layer

Business Model and Mapping Layer A Second Layer in the repository. In this layer the physical schemas are simplified and restructured. Can contain one or more Business model objects. Mappings among tables in the BMM layer can be done in a consolidated way as to suit our business requirement.

Business Model Mappings Business Model and Mapping layer objects map to source data objects in the physical layer. Mappings may not really be one to one.

Business Model and Mapping Layer Objects Business Model. Logical Tables. Logical Table Sources. Logical Primary Keys. Logical Joins. Logical Complex Joins. Measures. Business model Logical Dimension Table Logical Table source Logical key Logical Column Logical fact Table Measures

Business Model And Mapping Layer Objects Business Model: Highest level Object in the BMM layer. Contains Business Model Definitions. Simplifies the physical schema. Logical Table: Represents Fact and Data. Can be created Implicitly or Explicitly. Can be modified with out affecting the physical layer. Logical Table Source: Defines logical table to physical table mapping. Logical tables may have multiple logical sources One logical table source may map to many physical sources .

Business Model And Mapping Layer Objects cont.. Logical Table Source : Column Mapping The Column Mapping Tab in the logical Table Source dialog box can be used to view, modify ,build logical to physical Mappings. Logical Columns: Represents the business view of data. May map to many columns in the physical layer. May be defined by other logical columns. Can be created Implicitly. Explicitly.

Business Model And Mapping Layer Objects cont... Logical Primary Keys: Defines unique identifiers for the logical tables. Defines the lowest level detail. A prerequisite for each logical dimension table. Logical Joins Expresses the cardinality relationship. Helps the BI server to understand relationships between various objects of the business model. Helps the BI server to understand how to construct physical queries.

Business Model And Mapping Layer Objects cont… Logical Complex Join: Define join relationship in the BMM layer. Help the BI server to take the best decision about what physical SQL should be generated based on the logical request. Measures: Are facts about the business. Calculations that define measurable quantities. A aggregate rule is defined (e.g. Sum, Avg).

Presentation Layer This layer provides the customized view of business model to users. Exposes meaningful Data to the End Users. Organizes data the way users analyze it. Renames data as per the user or the business requirements.

Presentation Catalog. Allows to show different views of business model to different users. Single catalog must be populated with single business model. Multiple catalogs can reference same business model. Catalogs can be created Explicitly (right click) or Implicitly (drag and drop which is preferred). Can be modified on the way you want to present data to users.

Presentation Tables Organizes presentation columns as per the user requirement. May contain columns from one or more logical tables. Modification can be done independently without affecting the logical tables. Can be created Implicitly. Explicitly.

Presentation Columns Defines the columns used to build queries. Maps to logical columns in the BMM layer. Can be created Explicitly. Implicitly . Can be modified as per the user specifications.

Presentation Layer Mappings Presentation layer object maps to objects in the BMM layer. Presentation table do not necessarily need to have one-to-one mapping to a logical table. Name and object properties of the presentation table are independent of the logical table properties. Presentation objects do not necessarily need to mirror logical objects.

Nested Presentation Tables Can be used to give the appearance of nested folders. Only one level of nesting is possible.

Aliases Keep a track of any changes to Presentation layer objects. Maintains compatibility with previously written queries. The Alias tab can be used to specify or delete a alias.

Repository Directory Repository files reside in ….\OracleBI\server\Repository directory where the oracle BI software is installed.

Repository Modes The Repository can be opened in two modes: Offline Oracle BI server is not started Repository is not loaded in to Oracle BI server memory. Used for development. Online Oracle BI server is started Repository is loaded into the memory Users can submit query requests.

Adding entry into the NQS Config file NQS Config file is a configuration file read by the Oracle BI Server to decide which repository to load into the memory.

Direct Database Requests Feature of the Database properties. Once checked, allows everyone to edit physical queries directly in the database from Presentation Layer. The cache is not hit when this checkbox is selected.

Column Level Security OBIEE offers Column Level security also. We can restrict users or a group from accessing a particular column.

Limiting Queries According to the time periods According to maximum runtime. By setting up filters. According to number of rows received by a user or group.

iWare Logic's Oracle BIEE Services iWare Logic an Oracle Gold Partner, focuses on Oracle Enterprise Applications and Technologies including Oracle BI. Areas of expertise within iWare Logic Services includes: Oracle Data Warehouse Implementation using Oracle Warehouse Builder (OWB) Heterogeneous Data Integration using Oracle Data Integrator (ODI) Oracle Business Intelligence Enterprise Edition (OBIEE) Implementations Design and build of the Analytics repository (RPD) Design and build of reports and dashboards Pixel-perfect production reporting using Oracle BI Publisher (BIP) Migrations from Oracle Discoverer (OBISE) to Oracle BI Suite Enterprise Edition (OBIEE) Oracle Essbase Oracle BI QA and Dedicated test center Oracle BI End-user and developer Training and Education services

Thank You iWare Logic Technologies Pvt. Ltd. Aditi Samruddhi, Baner, Pune, India - 411045 Email: [email_address] Website: www.iwarelogic.com

Metadata Creation In OBIEE

More Related Content

Viewers also liked (15)

Similar to Metadata Creation In OBIEE (20)

More from iWare Logic Technologies Pvt. Ltd. (20)

Recently uploaded (20)

Metadata Creation In OBIEE

Editor's Notes