OEMM: Creating a Business Glossary

1. Expand [+] Repository > My Demo, right-click HR Source model and select Settings.

   

2. Select Import Setup tab and click Test.

   

   If the test is successful, click OK in the Alert pop-up, and then Cancel the Settings for HR Source panel. Skip the next step and proceed to the next topic.

3. If the test is NOT successful, verify the Host, User, and Password as configured in OBE 2: Harvesting Metadata, and re-Test until successful. Once successful, click Save.

   

   The Host address depends on whether the Linux VM database is in the same host with the Windows OEMM. This will determine whether you use localhost or not.

4. Once successful, click Save then Cancel to close the Settings for HR Source panel.

You have verified that you will be able to reach the intended source of the glossary.

1. Right-click My Demo folder and create a New > Glossary.

   

   You can have more than one Glossary in each folder.

2. Name it Tutorial Glossary. A Description is always a good idea.

   

   Click Create.

3. Click No for adding a category. You will populate the Glossary by dragging the HR model into it rather than creating the category and terms manually.

   

   .

You have created a new empty Glossary.

1. Drag the HR Source model into the Glossary Editor to seed the repository.

   

   This will create the terms in the Glossary using the entities/relationships/constraints in the HR Source model based on the HR schema in the orcl instance.

2. Enter Steward to populate default values in the business terms or you can leave it blank and update it later. This value can also be updated after the Glossary population.

   Select the check box to Create a Semantic Mapping. Keep the default name of the semantic mapping. This mapping is similar to data mapping described earlier. The difference is that it is between a semantic model (glossary) and the physical model. This mapping is created automatically which can be updated later.

   

   Click Import.

You have started the import of a model into a Glossary.

1. Depending on the size, this may take a few seconds. Once the import starts, you can close the import window and it will run in the background.

   

   Click Close for the Logs.

2. You can always look at the log any time by right-clicking on the object and selecting View Log.

   

   Click Refresh to check current status. Once it is completed move to the next step.

The database model has been imported into the new Glossary.

1. Refresh the Repository panel to see the new Glossary and the Semantic link.

   Refresh the Glossary Editor to check the newly populated repository.

   

   The automated process has created two categories: Domains and HR.

2. Expand the two categories: Domains and HR.

   

   The Domains category is empty since there was no such thing in the HR Source model.

   The HR category contains all the terms seeded from the model HR Source. All entities and attributes from HR Source are flattened and equivalent terms are created under this category. These are all seeded and can be further updated and maintained in OEMM.

   If there had been constraints in the base model then OEMM would have created a category called Business Rules based on the constraints.

3. Compare and contrast this new Glossary with the existing one named Oracle Tutorial > Sales Glossary. It was created when the environment contained a BI application. Since then, the BI application has been disconnected, but the metadata persists (though obviously in a static state).

   

   Close the Tutorial Glossary tab, you will be using the Sales Glossary from now on.

You have refreshed new and existing Glossaries.

1. Click the down triangle in BISAMPLE model to open the category. You will see flat list of terms. Scroll down to SAMP_REVENUE_F.

   

   Optionally you can Search BISAMPLE and filter for text.

2. Click Edit (pencil) to switch to edit mode. This is a toggle button.

   

   Do not change anything yet, this was just so you could see how for later. The way you can tell which mode you are in is that in Edit mode there are check boxes on the far left, whereas in View mode there are no boxes.

3. Click the right edge of the column header to sort or include/exclude additional columns.

   

   Note that many of the definitions are empty because there were only a very few descriptions in the base model Dimensional DW. A rich base model will result in a richly seeded Glossary.

You have explored some of the fields in the BISAMPLE model in the Sales Glossary.

1. Update the Definition of SAMP_REVENUE_F to Revenue Fact Sample. You can also update the Steward value to any other user in the pick list.

   

   This way you are assigning the terms for further maintenance.

2. Go back to view mode using Edit toggle button.

   

   The way you can tell which mode you are in is that in Edit mode there are check boxes on the far left, whereas in View mode there are no boxes.

3. Double-click SAMP_REVENUE_F to see the detailed properties, documentation, and relationships.

   

   Notice entries in the Relationship section. All the attribute of this fact are mentioned under Contains:. This shows that although all the entities/attributes are flattened in the Glossary, the relationship is maintained for semantic analysis.

4. In Contains:, click COST_FIXED.

   

5. Update the Definition of COST_FIXED (just add anything). Check that its property says SAMP_REVENUE_F in Contained By relationship. Notice that Stewards can add comments to the section Development Logs to keep track of the updates.

   

   Changing the Definition opens a separate dialog box.

6. Click Sales Glossary to go back to the top level of this Glossary.

   

You have updated fields in the Glossary.

The goal is to gather all of the cost terms scattered throughout the glossary into one category.

1. Click (plus sign) to Add a Category.

   

2. Name it Generalizations. In this category, select Add Term to add a generic term.

   

   Click Create.

3. Add a new term called All Costs under the category Generalizations. Deselect Create Another since we are creating only one term.

   

   Click Create.

4. Double click All Costs, then under Relationship, click More Specific.

   

   In the next few steps you are going to add all the terms here that are costs.

5. Search for COST in the Glossary.

   

   Click to start the search.

6. Add all the cost terms by selecting all of them and then clicking Add.

   

   After Add, then click Close.

7. Check that all these terms are added into a generalized term called All Costs.

   

   Leave the tabs open for the next step.

You have added a new category to the Glossary for costs.

Some of the work has already been done for you, specifically the linking of the Glossary and Semantic map to the rest of the model in the Model Manager. Normally you would have to do that step first.

To get semantic analysis for All Costs, perform the following steps:

1. In the Glossary Editor, select Sales Glossary > Generalizations > All Costs, then click Trace Semantic Usage.

   

2. Even though this Glossary and the Semantic map is already in the configuration, you may need to validate it before you can do analysis. If asked for validation, click Yes.

   

   However, validation may not be necessary if there are no other changes. In that case, OEMM will directly take you to the graphical view of the semantic Usage. Jump to "Post Validation" step #5 if no validation needed.

3. Open the configuration Sales Reporting Application to validate the linking of the Sales Glossary and Semantic Mapping from Sales Glossary to BISAMPLE in the Model Manager. The Warnings () tell you the same thing.

   

   Click Validate.

4. It may take up to 10 minutes. If nothing happens after 10 minutes then log out and log back in. Remove first the semantics map Semantic Mapping from Sales Glossary to Dimensional DW and then Sales Glossary from the configuration. After that validate the configuration and drop the semantic link again. It will bring in Sales Glossary in the configuration since it is linked. Validate again.

You have done a simple semantic analysis. There are many more things you can do in this area, but this is the first exposure to OEMM semantic analysis.

1. After it is validated, go to the Architecture Diagram tab. You will see the Sales Glossary linked to Dimension DW via the semantic link.

   

2. Go to the Glossary Editor and search for All Costs term that you had created earlier.

   

   The last entry is the one you want.

3. Open All Costs by double-clicking it. Trace semantic usage for this term.

   

   This time it will work since this glossary is in the configuration.

4. View the same trace graphically. The dotted blue lines depict semantic linkage (compared to solid lines in data flow lineage trace).

   

   You can always zoom in, collapse and expand boxes, and so on to read the tiny text.

5. Click SAMP_OLAP_REVENUE_F_V and expand the Properties panel on the right. Notice that this database view in the model Dimensional DW is also linked to the business term called All Costs on the left.

   

After validation you have confirmed the objects' linkages to views.