Importing metadata by using InfoSphere Metadata Asset Manager
You can import by using a bridge or connector that is on any computer that is designated as a metadata interchange server. You specify connection information and information about the source metadata, and choose to run either an express import or a managed import.
Before you begin
You must have the role of Common Metadata Importer or Common Metadata Administrator.
- Installing InfoSphere Metadata Asset Manager and bridges The bridges must be installed on the same computer where the SAP BusinessObjects client and SAP BusinessObjects Reporter are installed.
- Preparing to use InfoSphere Metadata Asset ManagerPreparing to use InfoSphere Metadata Asset Manager (http://www.ibm.com/support/knowledgecenter/SSZJPZ_11.3.0/com.ibm.swg.im.iis.mmi.doc/topics/t_first_steps.html)
- Prerequisites for using the SAP BusinessObjects Repository bridge
- Prerequisites for using the Cognos BI Reporting - Content Manager bridge
- Prerequisites for using the MicroStrategy bridge
- Prerequisites for using the Oracle Business Intelligence (OBI) Enterprise Edition bridge
About this task
You create an import area by running an import. The import area is created whether you run an express import or a managed import.
When you run a managed import, you can closely study the metadata assets in the import. You can preview the effects that the import might have on the repository. You can take time to fix problems in the source metadata, or reimport with other parameters.
When you first import into an import area and share the import to the metadata repository, the metadata is reconciled with existing metadata in the repository. If an imported asset has the same identity as another asset that already exists in the metadata repository, the two assets are merged. Merge rules are used to determine the specific behavior, depending on the object type. When you reimport into the same import area, the reimport logic assumes that you are importing the same basic source metadata. Any assets that were imported in the previous import but are not present in the reimport are assumed to have been deleted in the source. The missing assets are deleted from the metadata repository when the reimport is shared.
Procedure
Results
When the import completes, if you ran a managed import, analyze the imported assets in the Staged Imports tab of the import area.
In this case | Take this action |
---|---|
If the analysis shows problems that you must fix | The Staged Imports tab is displayed. Review the analysis results. If necessary, reimport the staged event. |
If your administration settings require a preview | The View Share Preview screen is displayed. Preview the result of sharing the import. |
If your administration settings do not require a preview | Preview will be skipped. The assets are shared to the metadata repository. The Shared Imports tab is displayed. You can browse the assets on the Repository Management tab and work with them in other suite tools. |
An import log is written to the metadata repository. For troubleshooting purposes, you can download a copy of the log from the Summary section of the Staged Imports tab.