A series of OBEs to help you get started with Oracle Enterprise Metadata Management (OEMM) version 12.1.3.
Duration: 140 minutes
This content is intended for the following job role(s): Data Modeler, Data Warehouse Administrator
Release Date: 04-MAY-2015
[1 of 7] Installing Oracle Enterprise Metadata Management (OEMM) on a Windows PC. This assumes another host with an Oracle Database, ODI, and possibly other tools such as BI already exists. (This may be supplied by a VM.) In this tutorial, you will learn to:
Installing OEMM is a prerequisite to the later OBEs.
For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.
Duration: 15 minutes
[2 of 7] Harvesting Metadata from Various Sources using Oracle Enterprise Metadata Management (OEMM). Sources include Oracle Database (DB), Oracle Data Integrator (ODI), Oracle Business Intelligence Enterprise Edition (OBIEE), and others.
In this tutorial, you will learn to:
Duration: 20 minutes
[3 of 7] Managing the Configuration and Metadata Stitching with Oracle Enterprise Metadata Management (OEMM), including backup and restore.
You will be using the models (from Oracle Database, ODI and OBIEE) already existing in the VM repository because these are part of a functioning application. This means the objects inside the model will match correctly with their ounterpart in another model. For example, tables defined in the physical layer of the OBIEE model are named exactly same as in Data Warehouse model in the database. This will allow us to "stitch" the models together.
[4 of 7] Configuring Data Lineage Analysis with Oracle Enterprise Metadata Management (OEMM), graphically and exporting to a format compatible with Microsoft Excel.
Imagine that you have a report that was generated using OBIEE, and you want to see where all the data came from (its lineage). You want to see this information graphically as well as to export it to a Microsoft Excel (spreadsheet) format.
[5 of 7] Using Impact Analysis with Oracle Enterprise Metadata Management (OEMM)
You could think of it as the "opposite" of data lineage analysis (covered in the preceding OBE, 4 of 7). While data lineage shows you all fields that led up to a given report, impact analysis shows you all reports that are based on a given field.
[6 of 7] Creating a Business Glossary in Oracle Enterprise Metadata Management (OEMM), using the enterprise edition.
Critical to the development and management of complete data architecture is a Business Glossary. OEMM provides an ISO 11179 based Business Glossary to capture, define, maintain and implement an enterprise Business Glossary of terminology, data definitions, code sets, domains, validation rules, and so on. In addition, semantic mappings describe how elements in a source Model (more conceptual like the Business Glossary) define elements in a destination Model (closer to an implementation or representation).
[7 of 7] Administering Oracle Enterprise Metadata Management (OEMM), creating users, roles, and scripts.
While the default behavior of OEMM will run in a proof-of-concept or development environment, a production environment usually requires additional administration and configuration to enforce best practices for security.