Managing the Configuration and Metadata Stitching with OEMM

1. On the top-right corner, navigate to Tools > Administration.

   

2. On the System tab, click Scripts > Test performance.

   

3. The script that is about to run is displayed for your information.

   

   Click Run Script.

4. There is an intentional 30 second pause built-in. Note the Total run time.

   

   When the performance test is finished, click Close. Close the Administration tab.

You have successfully run the performance testing script.

1. If the total time is less than one minute, you are all set to proceed with backups and restores. Skip to Topic 2.
2. If the total time is greater than two minutes, try increasing the RAM size of the VM, or closing other apps on the host of the VM.
3. If you suspect network latencies, if possible, locate both the VM and the Windows host on the same subnet.
4. See if only one of the tasks is taking the bulk of the time. Try to determine why.

After these corrective steps, rerun the performance test and see if it is acceptable now.

1. On the main navigation panel, right-click Repository and select More > Backup.

   

2. Browse or type an existing directory destination for the backup files. It must be a drive writeable from the OEMM (Windows) PC.

   

   It is a good practice to put the date in the folder name. Click Backup.

3. The log messages show the progress of the backup. This can take a while.

   

   When the backup is finished, click Close.

4. Examine the files that are created as part of the backup.

   

   The backup is composed of lots of little files. That is why you want to put this in its own directory.

5. For your information, you can also back up subsets of the repository, such as individual folders.

   

   Do not bother to actually do this, this is just to show you that you could.

You have successfully backed up the repository.

1. To simulate a catastrophe, right-click My Demo and select Delete.

   

2. It does warn you, but only once!

   

   Click Yes to continue.

Unfortunately, deleting is very easy! Fortunately, so is restoration.

1. To recover from our simulated catastrophe, right-click Repository, and select More > Restore.

   

2. Browse to where you stored the backup, and then click Restore.

   

   You cannot restore pieces of the backup, it is all or nothing. It is smart enough to not duplicate what is already there, but to overlay/replace it.

3. Examine the Log Messages to see that it completed successfully.

   

   Click Close to continue.

4. Verify that the My Demo folder has been restored successfully.

   

You have successfully restored a folder to the repository.

1. Create a new configuration by right-clicking on Repository > My Demo and selecting New > Configuration.

   

2. Give the configuration the name: Sales Reporting Application.

   

   Click Create to continue.

An empty configuration exists. It needs to be populated.

1. Select four Oracle Tutorial models from the Repository:

   • DB - Dimensional DW
   • DB - OLTP Source
   • Load to Dimensional DW
   • BI Reports

   

   Use the [Ctrl] key to select multiple objects.

2. Drag and drop into the configuration Model Manager.

   

   Note the Warning icons () indicating that you are not done yet.

While the four objects are in the configuration, the flow (source and destination) still needs to be specified.

The objects need to be linked together in a specific order for metadata stitching. The ultimate goal is the following logical order:

1. DB - OLTP Source
2. Load to Dimensional DW
3. DB - Dimensional DW
4. BI Reports

1. Select Load to Dimensional DW. (You know this needs further configuration because of the icon.)

   

   Click Edit Connection.

2. Select SRC_ODIDEMO.OLTP_SRC as the Source, and under Store, select DB - OLTP Source.

   

   Stay on this panel, do not click OK yet.

3. Select OBIEE DW.SAMPLE as the Destination, and under Store, select Dimensional DW.

   

   Stay on this panel, do not click OK yet.

4. Select FILE_GENERIC.E, and under Store, select [Ignore].

   

   Now click OK. (The icon should be cleared now.)

5. Select BI Reports as well. You know this needs further configuration because of the icon. Click Edit Connection. Only 01 - Sample App Data (ORCL) needs to be mapped to DB - Dimensional DW, and the others will be ignored.

   

   Click OK.

The source and destination have been identified, the non-source/destinations are ignored.

1. On the Sales Reporting > Model Manager tab, click Validate.

   

2. Nothing to do here, just look.

   

   The alert icon is next to BI Reports, so that is where you need to look next.

3. Click Architecture Diagram tab. (This requires Adobe Flash Player.)

   

   Nothing to do here, just look.

The configuration messages have been examined.

1. To see why you are getting validation warnings, open the Connection Editor for BI Reports.

   

   Click Open Connections.

2. You can see the attributes match between database BISAMPLE and the attributes in the connection Sample App Data (ORCL) of BI Reports model. Notice that some attributes have not matched. This is why there was a warning. If attributes do not match, the metadata analysis for those attributes cannot be done. It also will cause errors in deployed applications. Some reports in BI Report will not find the table/columns in the BISAMPLE database and fail.

   

   The two highlighted lines, ODM_LTV_BIN_RULES are examples of matching lines (with the blue chain link icon). The lines above them (for example, DM$PZODM_LTV_BIN and MEMBERSHIP_TRANSLATIONS) are examples of non-matching lines (no chain shown). For our purposes, these non-matching stitching errors can be ignored.

The errors have been acknowledged, but not corrected. We can live with that.