Getting Started with Oracle Enterprise Metadata Management (OEMM)

[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:

• Download the OEMM software from one of two locations
• Install the Windows client software
• Start the Windows Tomcat (Java) services
• Start the browser to view either Metadata Manager and/or Metadata Explorer
• Create the DB schema on an Oracle database needed for the OEMM repository
• Test the connections to the repository.

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.

[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:

• Create and examine models for Oracle Database schemas, both ones you create and pre-existing sample ones
• Create and examine models for Oracle Data Integrator projects. If you have a live ODI system, you can harvest actual models.
• Examine existing models for OBIEE reports. OBIEE is not used in this tutorial, but its metadata is.
• Examine other possible sources of metadata such as Big Data or Microsoft Excel using import bridges

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.

[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.

In this tutorial, you will learn to:

• Run a performance test script to validate that the environment is sufficiently robust
• Backup and restore the whole repository (with instructions on how to do just a piece of the repository)
• Configure the source and destinations in such a way as to stitch the objects together in the proper order. This set of sources and destinations is saved as a "configuration."
• Validate the configuration and examine the error messages

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.

[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.

In this tutorial, you will learn to:

• View a source report such as BI Reports (these reports already exist in the sample repository)
• Generate data lineage in static and comma-separated formats (suitable for exporting)
• Explore interactive lineage graphs
• Drill down to various levels exploring the details available for each kind of object and link

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.

[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.

In this tutorial, you will learn to:

• View graphical data impact analysis
• Expand and collapse pieces of the graph to focus on areas of interest

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.

[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).

In this tutorial, you will learn to:

• Create a new glossary by importing models
• Explore the new and existing glossaries
• Update some of the metadata within a glossary
• Create generalization categories (similar to wiki tags)
• Do (limited) semantic analysis for a field in both a textual and graphical format

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.

[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.

In this tutorial, you will learn to:

• Create users (including casual users, power users, and administrators)
• Create roles (permissions and privileges)
• Assign users to roles
• Assign security to folders
• Schedule scripts
• Document and measure performance of the environment
• Display and download logs (info, warnings, errors)

For the full list of OEMM OBEs see the Oracle Enterprise Metadata Management (OEMM) Getting Started series.