InfoSphere Metadata Asset Manager tutorial

Transcription

1 IBM InfoSphere Information Server InfoSphere Metadata Asset Manager tutorial Version 9 Release 1

2

3 IBM InfoSphere Information Server InfoSphere Metadata Asset Manager tutorial Version 9 Release 1

4 ii IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

5 Contents Tutorial: Importing and managing common metadata assets Setting up the tutorial environment Copying the installed tutorial files Module 1: Importing common metadata assets... 3 Lesson 1: Running express imports of logical and physical data models Lesson 2: Running a managed import of a logical data model Lesson 3: Importing database schemas into the metadata repository Module summary Module 2: Managing assets on the Repository Management tab Lesson 1: Setting implementation relationships. 20 Lesson 2: Deleting the duplicates Module summary Contacting IBM Accessing and providing feedback on the product documentation Product accessibility Notices and trademarks Index Copyright IBM Corp., 2012 iii

6 iv IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

7 Tutorial: Importing and managing common metadata assets In this module you learn to use IBM InfoSphere Metadata Asset Manager to import a logical data model, a related physical data model, and a related database schema into the metadata repository. After the data is imported, you learn to browse for the assets in the repository, set implementation relationships, and delete duplicate assets. This tutorial teaches you the process of importing, analyzing, previewing, and sharing metadata from InfoSphere Data Architect and from a database. You learn how to reimport the source metadata if it fails analysis or if the source has been updated. The module demonstrates managed imports and the automated express imports. After you import the metadata, you learn how to browse for it on the Repository Management tab, to delete any duplicate assets that are imported, and to set implementation relationships that help you trace the lineage of the metadata. The tasks in this model are typical import and metadata-management tasks that users would undertake before they use the database metadata in jobs, analyze columns, or study data lineage. Learning objectives After you complete the exercises, you will know how to: v Import logical data models, physical data models, and database schemas v Run express imports v Run managed imports, including analyzing and previewing the import source and sharing the import to the metadata repository v Run reimports v Set implementation relationships v Delete duplicate assets Time required 60 minutes Setting up the tutorial environment You must prepare your system to run the tutorial. You access InfoSphere Metadata Asset Manager by using your web browser. Before you begin You must know the user name and password of an account in InfoSphere Metadata Asset Manager with the following roles: v Common Metadata Importer v Common Metadata Administrator Copyright IBM Corp.,

8 About this task The following software must be installed: v InfoSphere Metadata Asset Manager Version 9.1 v Metadata interchange agent and bridges v ODBC connector v Any supported version of the Microsoft Windows operating system v One of the following databases: IBM DB2 Enterprise Server Edition Versions 9.7 or 10.1 Microsoft SQL Server Enterprise Edition 2005 or 2008 Oracle Database 10g Enterprise Edition Release 2 Oracle Database 11g Enterprise Edition Release 2 v Microsoft Internet Explorer Versions 8 or 9, or Mozilla Firefox ESR 10 You must know the web address of InfoSphere Metadata Asset Manager. The default web address is loginform.jsp You must use the default import settings which are set on the Administration tab. For additional information about import settings, see the topic Import settings for InfoSphere Metadata Asset Manager. For additional information about preparing to use InfoSphere Metadata Asset Manager and for information about specifying metadata interchange servers, see the topic Preparing to use InfoSphere Metadata Asset Manager. For additional information about assigning specific user roles, see the topic Assigning users to a project and assigning roles. For additional information about how to install InfoSphere Information Server, see the topic Installing IBM InfoSphere Information Server software. Copying the installed tutorial files You must copy the installed tutorial files to a temporary directory on your computer. When InfoSphere Metadata Asset Manager is installed on the services tier of InfoSphere Information Server, the tutorial files are also installed. The tutorial files are in a compressed format. To copy the tutorial files to your computer: 1. Go to the directory \IS_Installer\is-suite\TutorialData\IMAM on the installation media. 2. Copy the file Tutorial_files.zip to a directory on your computer, such as C:\. 3. Extract all files in Tutorial_files.zip to the temporary directory. Note: When you extract the files, keep the default file structure intact. 2 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

9 Module 1: Importing common metadata assets In this module, you use InfoSphere Metadata Asset Manager to import logical and physical data models and a database schema into the metadata repository. You run express imports and a managed import. Express import The source metadata is imported to the staging area, where it is analyzed and previewed automatically. Your administrator s settings for this tutorial determine that the import is then shared automatically to the metadata repository. Managed import The source metadata is imported to the staging area, where you manually analyze the import contents and preview the result of sharing it to the metadata repository. When you are satisfied with the contents of the import, you share the import assets to the metadata repository. 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 staging area. You can preview the effects that the import might have on the repository. You can take time out to fix problems in the source metadata, or reimport with other parameters. An express import saves time when you have high confidence in the contents of your import source. Learning objectives After completing the lessons in this module, you will understand the concepts and know how to do the following tasks: v Create an import area v v Run an express import of a logical data model, a physical data model, and a database schema Run a managed import of a logical data model Time required This module takes approximately 45 minutes. Lesson 1: Running express imports of logical and physical data models In this lesson you run separate express imports of a logical data model and a physical data model that were created in InfoSphere Data Architect for the Sample Financial Company (SFCO). The logical data model is in the file SFCO.ldm. The physical data model is in the file SFCO.dbm. Tasks in this lesson 1. Running an express import of a physical data model 2. Running an express import of a logical data model Tutorial: Importing and managing common metadata assets 3

10 Running an express import of a physical data model Because the physical data model was created in InfoSphere Data Architect, you use the IBM InfoSphere Data Architect MetaBroker to import the.dbm file that contains the model. Procedure 1. Open InfoSphere Metadata Asset Manager. Log in with the user name and password of an account with the Common Metadata Importer role or the Common Metadata Administrator role. 2. Click the Import tab, and then click New Import Area. 3. Specify the details for the import area in the Create New Import Area window and then click Next. a. In the Import area name field, type SFCO PDM. IntheImport area description field, type SFCO physical data model. An import area with the specified name and description is created when you run the import. b. In the Metadata interchange server list, select the server that you want to use to run the import. c. In the Select a Bridge or Connector list, expand the IBM folder. Select IBM InfoSphere Data Architect MetaBroker, and click Next. 4 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

11 Figure 1. Parameters for the Create New Import Area screen 4. In the File location field, select Metadata interchange server. 5. In the DBM or LDM file field, browse to the following directory: C:\Tutorial_files\IDA\Physical. Select the file SFCO.dbm and click OK. Note: The file path to the tutorials might be different if you did not extract the file Tutorial_files.zip directly to your C drive. 6. Select 7.5 in the IDA version field and select Import LDM assets with DBM. Click Next. 7. In the Identity Parameters section, specify SFCO_physical_data_model in the Model namespace field, and then click Next. 8. In the Import Description field, type Initial import of sample financial company (SFCO) physical model and select Express Import. The import description helps you differentiate between multiple reimports in the same import area. Tutorial: Importing and managing common metadata assets 5

12 9. Click Import. The express import analyzes file contents, previews the results of importing the assets into the metadata repository, and then imports the assets directly into the repository. After the import completes, a message shows that 115 assets are created and zero are merged or deleted. Figure 2. Import results for the import area SFCO PDM 10. Click OK. The import results are displayed in the Shared Imports tab. Figure 3. Detailed view of the import results for the SFCO PDM import area In the Statistics field, notice that one physical data model was created. In the Resulting Assets section, you can expand the Physical model folder and see the SF_BANK2 physical data model that you imported. 11. Click Close under Import Areas in the top left of the screen. 12. Display the imported assets in the Repository Management tab in the top Navigation menu. 6 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

13 a. Click the Repository Management tab, and select Browse Assets > Physical Data Models > SF_BANK2. b. Expand the SF_BANK2 physical data model, and see that it contains six design tables. Figure 4. Repository Management view of the SF_BANK2 physical data model Running an express import of a logical data model Because the logical data model was created in InfoSphere Data Architect, you use the IBM InfoSphere Data Architect MetaBroker to import the.ldm file that contains the model. Procedure 1. Click the Import tab, and then click New Import Area. 2. Specify the details for the import area in the Create New Import Area window. a. In the Import area name field, type SFCO LDM. IntheImport area description field, type SFCO logical data model. An import area with the specified name and description is created when you run the import. b. In the Metadata interchange server list, select the server that you want to use to run the import. c. In the Select a Bridge or Connector list, select IBM InfoSphere Data Architect MetaBroker. d. Click Next. 3. In the File location field, select Metadata interchange server. 4. In the Select a File field, browse to the following directory: C:\Tutorial_files\IDA\Logical. Select the file SFCO.ldm and OK. Note: The file path to the tutorials might be different if you did not extract the file Tutorial_files.zip directly to your C drive. 5. Select 7.5 in the IDA version field and select Import LDM assets with DBM. Click Next. Tutorial: Importing and managing common metadata assets 7

14 6. In the Identity Parameters section, specify SFCO_logical_data_model in the Model namespace field, and then click Next. 7. In the Import Description field, type Initial import of sample financial company (SFCO) logical model and select Express Import. 8. Click Import. After the import completes, a message shows that 89 assets are created, zero are merged, and zero are deleted. Figure 5. Import results for the SFCO LDM Import Area 9. Click OK to view the assets in the Shared Imports tab. 10. Click Close under Import Areas in the top left of the screen. 11. Display the imported assets in the Repository Management tab in the top Navigation menu. a. Click the Repository Management tab, and select Browse Assets > Logical Data Models > Sample Financial Company logical model. b. Expand the Sample Financial Company logical model, and verify that the logical data model assets are there. Notice that the Implemented by field displays no implemented by relationships for the Sample Financial Company logical data model. 8 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

15 Figure 6. Sample Financial Company logical model and its contained assets and properties displayed in Repository Management tab Lesson 2: Running a managed import of a logical data model In this lesson, you create an import area to do a managed import of the logical data model SFCO.ldm. This model has been updated in InfoSphere Data Architect with new information since you originally imported it. Prerequisites In this lesson, you will import the logical data model SFCO.ldm, which contains the new logical entity BANK_DEMOGRAPHICS. The BANK_DEMOGRAPHICS asset is added in InfoSphere Data Architect for the purpose of this tutorial. Because the updated logical model has an additional object in it, you want to make sure that there are no problems with the import contents, and issues with merging the assets in the updated model with the assets from the earlier version that you imported into the repository in Lesson 1. When you run a managed import you can inspect the metadata closely in the staging area before you share it to the metadata repository. The managed import reveals duplicate assets and invalid identities among the imported assets. These errors prevent you from sharing the import to the metadata repository. In the second section of this lesson you reimport the file after the errors are fixed in the source tool, InfoSphere Data Architect. You can then share the import to the metadata repository. Tasks in this lesson 1. Running a managed import of a logical data model 2. Reimporting a logical data model Running a managed import of a logical data model You run a managed import by using the IBM InfoSphere Data Architect MetaBroker. You specify connection information and information about the source metadata, and choose to run a managed import. Tutorial: Importing and managing common metadata assets 9

16 Procedure 1. Open InfoSphere Metadata Asset Manager. Log in with the user name and password of an account with the Common Metadata Importer role or the Common Metadata Administrator role. 2. Click the Import tab, and then click New Import Area. 3. Specify the details for the import area in the Create New Import Area window and then click Next. a. In the Import area name field, type SFCO logical data model-updated to indicate that you are creating a new import area with a new version of the logical data model file. In the Import area description field, type SFCO logical data model. b. In the Metadata interchange server list, select the server that you want to use to run the import. c. In the Select a Bridge or Connector list, expand the IBM folder. Select IBM InfoSphere Data Architect MetaBroker, and click Next. 4. In the File location field select Metadata interchange server. 5. In the DBM or LDM file field, browse to the following directory: C:\Tutorial_files\IDA\ManagedError. Select the file SFCO.ldm, click OK. 6. Select 7.5 in the IDA version field and select Import LDM assets with DBM. Click Next. 7. In the Identity Parameters section, specify SFCO_logical_data_model in the Model namespace field, and then click Next. 8. Enter Added BANK_DEMOGRAPHICS in the Import Description field. 9. Select Managed Import. 10. Click Import. 11. Click OK after the import completes. The Staged Imports tab shows that 105 assets are imported. 12. Analyze the import: a. Click Analyze in the Staged Imports tab of the import. You analyze imports to see if there are duplicates assets or assets with invalid identities. b. Review the analysis results in the Statistics section. Notice there is one set of duplicate assets and one invalid identity. c. Click the link in the Duplicate Sets column. 10 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

17 Figure 7. The analysis results show that there is one duplicate set of logical entities Notice that the duplicate logical entity is the asset BANK DEMOGRAPHICS. d. Click the link in the Invalid Identities column. Notice that the entity attribute Invalid Identity 01 contains the invalid identity Delete Me. e. Click Close. Due to the errors, you cannot preview or share the file before the invalid identity and duplicate asset are fixed. You must delete the duplicate asset and update the invalid identity in InfoSphere Data Architect before you can preview or share. In the next task you will reimport a version of the file in which the errors are fixed. Reimporting a logical data model When analysis errors prevent preview and sharing, you can reimport the metadata after fixing it the source tool. In this section of the lesson, you reimport a version of the logical data model SFCO.ldm in which the duplicate assets have been removed and the invalid identities have been fixed in InfoSphere Data Architect. In the fixed version of the file, the objects with invalid identities are corrected and one of the duplicate assets was deleted. You reimport it in the same import area that the file with errors was imported into. Procedure 1. On the Import tab, select the import area SFCO logical data model-updated and click Open. 2. Click the Staged Imports tab. 3. Click Reimport. Note: The import settings from the last import are saved, so you can accept the defaults as you go through the following sub-steps. 4. Specify parameter values for the reimport. Where values from the previous import have been saved, accept the default values. a. In the File location field select Metadata interchange server. b. In the DBM or LDM file field, browse to the following directory: C:\Tutorial_files\IDA\ManagedFixed. Select the file SFCO.ldm and click OK. Tutorial: Importing and managing common metadata assets 11

18 c. Select 7.5 in the IDA version field and select Import LDM assets with DBM. Click Next. d. In the Identity Parameters section, click Next. e. Enter Fixed duplicates and invalid identities in the Import Description field and select Managed Import. f. Click Reimport. After the import completes successfully, click OK. The Staged Imports tab shows that 103 assets are imported. 5. Click Analyze. Notice that the invalid identities and the duplicate sets no longer exist. Figure 8. The results of reimporting the updated SFCO logical data model 6. Click Preview. Notice that 14 assets are created, 89 are merged, and 0 assets are deleted. Figure 9. A preview of the assets that will be imported into the metadata repository 7. Click Share to Repository. Click Yes when the Alert message appears. 8. Click Close to close the import area. 9. Display the imported assets in the Repository Management tab in the top Navigation menu. 12 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

19 a. Click the Repository Management tab, and then select Browse Assets > Logical Data Models. b. Expand the Sample Financial Company logical model and notice that the BANK DEMOGRAPHICS entity was added. Figure 10. The Sample Financial Company logical data model and its contained assets on the Repository Management tab Lesson 3: Importing database schemas into the metadata repository In this lesson, you import a database schema that is based on the physical data model that you imported in Lesson 1. Prerequisites You must have access to an existing database or create a new database before you begin this lesson. You will create a database schema in the database. 1. Create the database schema. Tutorial: Importing and managing common metadata assets 13

20 Option To create a DB2 database schema: To create a non-db2 database schema: Description 1. Open a DB2 Command Line Processor window and issue the following command: connect to <name_of_database>. For example, connect to xmeta. Note: Your installation of InfoSphere Metadata Asset Manager might already use a DB2 database as the metadata repository (xmeta). To create the database schema in the metadata repository database, specify the name of the database in the connect to <name_of_database> command. If you want to use a database other than the existing metadata repository database, or if you created a new database, then specify the name of the new database in the command above. 2. Issue the following command to create the database schema needed for this tutorial: DB2 -tvf C:\tutorial_files\ DB2\SFCO_DB_create.sql. Open the file SFCO_DB_create.sql file and issue the SQL statements contained in the file in your database software program. 2. Verify that the database that you created has an OBDC system DSN that points to the database and test the connection. If the database does not have an OBDC system DSN that points to the database, then you must register the system DSN. You can register the system DSN by going to your control panel, clicking Administrative Tools > Data Sources, and specifying the connection information. Running an express import of the database schema SF_BANK2 You run an express import by using the ODBC Connector. You create a data connection, specify information about the source metadata, and choose to run an express import. Procedure 1. Open InfoSphere Metadata Asset Manager and log in with the user name and password of an account with the Common Metadata Importer role or the Common Metadata Administrator role. 2. Click the Import tab, and then click New Import Area. 3. Specify the details for the import area in the Create New Import Area window and then click Next. a. In the Import area name field, type SFCO_DB. b. In the Import area description field, type SFCO_DB. c. In the Metadata interchange server list, select the server that you want to use to run the import. d. In the Select a Bridge or Connector list, expand the IBM folder. e. Select ODBC Connector, and click Next. 14 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

21 Figure 11. Parameters for the new import area 4. In the Data connection field, select the browse icon and then select New Data Connection... a. Enter SFCO_DB connection in the Name field. b. Enter Data connection to the database that contains the SF_BANK2 database schema in the Description field. c. In the Data source field, select the database that you created the database schema in earlier in this module. Enter the user name and password for the database. d. Click Test Connection to verify that you can connect to the database and then click OK. Tutorial: Importing and managing common metadata assets 15

22 Figure 12. New data connection that connects to the database that contains the SF_BANK2 database schema 5. In the Assets to import field, browse to the database that contains the SF_BANK2 database schema and expand the browse tree. 6. Select SF_BANK2 <DataSchema>, and then click OK. Click Next. 16 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

23 Figure 13. Selecting the SF_BANK2 database schema to import into the metadata repository 7. In the Host system name field, type SFCO_HOST, and then click Next. 8. Enter SF_BANK2 in the Import Description field and select Express Import. 9. Click Import. After the import completes successfully, click OK. Inthe Resulting Assets section, verify that the SFCO_DB connection was created and that the SF_BANK2 database schema was imported. Tutorial: Importing and managing common metadata assets 17

24 Figure 14. Resulting assets for the import area SFCO_DB 10. Click the Repository Management tab in the top Navigation menu to display the imported assets. a. Select Browse Assets > Implemented Data Resources > SFCO_HOST > SFCO_DB. b. Expand the SFCO_DB asset and verify that the database schema SF_BANK2 appears. Notice that the tables contained by the SF_BANK2 database schema are similar to the design tables contained by the physical data model SF_BANK2. 18 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

25 Figure 15. View of the SF_BANK2 database that you imported on the Repository Management tab Module summary In this module, you ran express imports, a managed import, and a reimport of assets into the metadata repository. You imported the following assets: v Logical data model from a file v Physical data model from a file v Database schema from a database In the next module you set implementation relationships between the imported assets and manage duplicate assets. You use the Repository Management tab to perform these tasks. Module 2: Managing assets on the Repository Management tab In this module, you set implementation relationships between the physical data model and the database schema that you imported in Module 1. You also use the Repository Management tab to delete duplicate assets. Learning objectives After completing the lessons in this module, you will understand the following concepts and know how to do the following tasks: v v v v Set an implementation relationship between a physical data model and a database schema. Modify the InfoSphere Metadata Asset Manager administrative settings to allow the import of duplicates. Use the Manage Duplicates workspace on the Repository Management tab to find duplicate assets. Delete duplicate assets. Tutorial: Importing and managing common metadata assets 19

26 Time required This module takes approximately 45 minutes to complete. Lesson 1: Setting implementation relationships The logical data model that you imported in Lesson 2 of Module 1 is implemented by the physical data model that was also imported in Lesson 1. The physical data model SFCO_DB.dbm that you imported in Lesson 1 of Module 1 is implemented by the database schema SFCO_DB that you imported in Lesson 3 of Module 1. In this lesson, you set an implementation relationship between the logical data model assets and the physical data model assets. You also set an implementation relationships between the physical data model assets and the database schema and its contained assets. Learn more about implementation relationships: When you design and implement a database, it is valuable to track the relationships between the design objects and the implemented database. When, for example, the definition of a database column changes over time, you can make corresponding changes in the related design column from the physical data model and in the entity attribute in the logical data model. You can use InfoSphere Metadata Asset Manager to set the implementation relationships. Then you can track the relationships on the Repository Management tab of InfoSphere Metadata Asset Manager and in InfoSphere Metadata Workbench. For example, a designer might want to change an entity attribute in a logical data model that is implemented by a physical data model and by a real-world database schema. To understand the impact of the change, you can inspect the implementation relationships on the Repository Management tab. You can view how the logical data model implements the physical data model, and then view how the physical data model implements the database schema. You can then use InfoSphere Metadata Workbench to see which InfoSphere DataStage and QualityStage jobs use the database column. Tasks in this lesson 1. Setting an implementation relationship between a logical data model and physical data model 2. Setting an implementation relationship between a physical data model and database schema Setting an implementation relationship between a logical data model and physical data model Procedure 1. Open InfoSphere Metadata Asset Manager. Log in with the user name and password of an account with the Common Metadata Administrator role. 2. Click the Repository Management tab, and then select Browse Assets > Logical Data Models > Sample Financial Company logical model. 3. Expand the Properties section on the right side of the screen, expand the Implemented by section on the right side of the screen, and then click New Implementation Relationship. 20 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

27 Figure 16. Setting an implementation relationship between the logical data model Sample Financial Company logical model and the physical data model SF_Bank2 4. Click the Search for Asset tab, select Physical data model in the Asset Type field, and click Search. Figure 17. Searching for a physical data model while setting an implementation relationship 5. Select the physical data model SF_BANK2, and click OK. This is the physical data model that you imported in Lesson 1 of Module 1. Relationships are set between the logical data model and the physical data model, and between their corresponding contained assets that have the same name. 6. In the New Implementation Relationship Created window, select View contained relationships and click OK. Tutorial: Importing and managing common metadata assets 21

28 Figure 18. The details of the implementation relationship between the logical data model and the physical data model 7. Optional: If there are any matched assets in the Implementation Relationships section, click Remove next to each relationship and then click Save. 8. Select source assets in the column on the left side of the screen. Drag them to the target assets in the column on the right side of the screen. a. Drag BANK SAVINGS to BANK_SAVINGS. b. Drag BANK BRANCH to BANK_BRANCH. c. Drag BANK INVESTMENTS to BANK_INVESTMENTS. d. Drag BANK DEMOGRAPHICS to BANK_DEMOGRAPHICS. e. Drag BANK CHECKING to BANK_CHECKING. f. Drag BANK ACCOUNTS to BANK_ACCOUNTS. 22 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

29 Figure 19. Drag the source assets to the target assets 9. Click Save. Figure 20. The implementation relationships between the contained assets of the logical data model Sample Financial Company logical model and the physical data model SF_BANK2 and the database schema SF_BANK2 10. In the Set Unset Response window, click OK. 11. Display the implementation relationships in the Repository Management tab in the top Navigation menu. a. Click the Repository Management tab, and then select Browse Assets > Logical Data Model > Sample Financial Company logical model and expand the Implemented by section. b. Select SF_BANK2 and click View Contained Relationships. Tutorial: Importing and managing common metadata assets 23

30 Figure 21. Viewing the implementation relationships between the contained assets of the logical data model Sample Financial Company logical model and the physical data model SF_BANK2 Setting an implementation relationship between a physical data model and database schema Procedure 1. Click the Repository Management tab, and then select Browse Assets > Physical Data Models > SF_BANK2. 2. Expand the Properties section on the right side of the screen. In the Namespace field, verify that the file name contains SFCO_physical_data_model. 3. Expand the Implemented by section on the right side of the screen and click New Implementation Relationship. 4. Click the Search for Asset tab, select Database schema in the Asset Type field, and click Search. Figure 22. Searching for a database schema while setting an implementation relationship 5. Select the database schema SF_BANK2, and click OK. This is the database schema that you imported in Lesson 3 of Module 1. Relationships are set between the physical data model and the database schema, and between their corresponding contained assets that have the same name. 6. In the New Implementation Relationship Created window, select View contained relationships and click OK. 24 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

31 Figure 23. The details of the implementation relationship between the physical data model and the database schema 7. Select source assets in the column on the left side of the screen. Drag them to the target assets in the column on the right side of the screen. a. Drag BANK_DEMOGRAPHICS to BANK_DEMOGRAPHICS_01. b. Drag BANK_SAVINGS to BANK_SAVINGS_01. c. Drag BANK_BRANCH to BANK_BRANCH_01. d. Drag BANK_CHECKING to BANK_CHECKING_01. e. Drag BANK_INVESTMENTS to BANK_INVESTMENTS_01. f. Drag BANK_ACCOUNTS to BANK_ACCOUNTS_01. Tutorial: Importing and managing common metadata assets 25

32 Figure 24. Drag the source assets to the target assets 8. Click Save. Figure 25. The implementation relationships between the contained assets of the physical data model SF_BANK2 and the database schema SF_BANK2 9. In the Set Unset Response window, click OK. 10. Display the implementation relationships in the Repository Management tab in the top Navigation menu. a. Click the Repository Management tab, and then select Browse Assets > Physical Data Model > SF_BANK2 and expand the Implemented by section. b. Select SF_BANK2 and click View Contained Relationships. 26 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

33 Figure 26. Viewing the implementation relationships between the contained assets of the physical data model SF_BANK2 and the database schema SF_BANK2 Lesson 2: Deleting the duplicates This lesson shows you how to find duplicate assets in the metadata repository and delete them in the Repository Management tab. As prerequisites you must modify the administrative settings to allow duplicates to be imported, and then import a logical model that contains duplicates. Prerequisites You must modify InfoSphere Metadata Asset Manager administrative settings to allow duplicates into the metadata repository and import the logical data model SFCO_duplicates.ldm before starting this lesson. 1. Modifying administrative settings 2. Running an express import of a logical data model Modifying administrative settings You must modify InfoSphere Metadata Asset Manager administrative settings to allow duplicates into the metadata repository for the purpose of this lesson. 1. Open InfoSphere Metadata Asset Manager. Log in with the user name and password of an account with the Common Metadata Administrator role. 2. Click the Administration tab. 3. Click Import Settings in the Navigation menu on the left side of the screen. 4. Select Allow imports that contain duplicate assets to be shared to the repository. 5. Click Save. Running an express import of a logical data model Import the logical data model that contains duplicate assets. To run an express import of a logical data model: 1. Click the Import tab and then click New Import Area. 2. In the Import area name field, type SFCO LDM Duplicates. IntheImport area description field, type SFCO LDM with duplicates allowed. Tutorial: Importing and managing common metadata assets 27

34 3. In the Metadata interchange server list, select the server that you want to use to run the import. 4. In the Select a Bridge or Connector list, expand the IBM folder. Select IBM InfoSphere Data Architect MetaBroker, and click Next. 5. In the File location field select Local. IntheDBM or LDM file field, browse to the SFCO_duplicates.ldm file in the following directory: C:\tutorial_files\IDA\ManageDuplicates. Click OK. 6. Select 7.5 in the IDA version field and select Import LDM assets with DBM. Click Next. 7. In the Identity Parameters section, specify SFCO_logical_data_model_dups in the Model namespace field, and then click Next. 8. In the Import Description field, enter SFCO logical data model with duplicates allowed, and select Express Import. 9. Click Import. Click OK when the import completes. Figure 27. The import results for the import area SFCO LDM Duplicates 10. Click Share to Repository in the top left of the screen. Click Yes in the alert window. 28 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

35 Figure 28. Sharing the imported assets to the metadata repository 11. Click Close under Import Areas in the top left of the screen. You have imported duplicates. You can see the duplicate BANK DEMOGRAPHICS logical entity assets in the Resulting Assets section on the right side of the screen. Figure 29. Duplicate BANK DEMOGRAPHICS logical entity assets Deleting duplicate assets You compare two duplicate assets that are contained in the logical data model SFCO_duplicates.ldm and delete one of the duplicates. Procedure 1. Click the Repository Management tab, and then select Manage Duplicates > Logical Data Models Tutorial: Importing and managing common metadata assets 29

36 2. Click View Duplicates next to the Logical entity icon. Figure 30. Viewing duplicate logical entity assets on the Repository Management tab 3. Expand the BANK DEMOGRAPHICS section, select the two BANK DEMOGRAPHICS assets that have the model namespace SFCO_logical_data_model_dups, and click Compare. Figure 31. Select the two assets with the name BANK DEMOGRAPHICS and then click Compare 4. Review and compare the properties and relationships of both assets in the Compare Logical Entities workspace to verify that the assets are true duplicates. 5. Delete one of the duplicate assets. a. Select one of the BANK DEMOGRAPHICS assets and click Delete. 30 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

37 Figure 32. Delete one of the BANK DEMOGRAPHICS logical entities b. Click Yes in the Delete Confirmation window. c. Click OK when the Alert window appears. 6. In the Navigation menu on the left side of the screen, select Browse Assets > Logical Data Models. 7. Expand both Sample Financial Company logical model files and look for the logical data model that has the namespace SFCO_logical_data_model_dups in the Properties section. Expand this logical data model. 8. Observe that one BANK DEMOGRAPHICS logical entity exists. The duplicate asset has been deleted. Figure 33. The duplicate BANK DEMOGRAPHICS logical entity is deleted Tutorial: Importing and managing common metadata assets 31

38 Module summary In this module, you performed repository management tasks on the assets that you imported into the metadata repository. Lessons learned In this module, you learned how to do the following tasks: v Set an implementation relationship between a physical data model and a database schema. v Modify the InfoSphere Metadata Asset Manager administrative settings to allow the import of duplicates. v Use the Manage Duplicates workspace on the Repository Management tab to find duplicate assets. v Delete assets duplicate assets. 32 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

39 Contacting IBM You can contact IBM for customer support, software services, product information, and general information. You also can provide feedback to IBM about products and documentation. The following table lists resources for customer support, software services, training, and product and solutions information. Table 1. IBM resources Resource IBM Support Portal Software services My IBM Training and certification IBM representatives Description and location You can customize support information by choosing the products and the topics that interest you at entry/portal/software/ Information_Management/ InfoSphere_Information_Server You can find information about software, IT, and business consulting services, on the solutions site at businesssolutions/ You can manage links to IBM Web sites and information that meet your specific technical support needs by creating an account on the My IBM site at You can learn about technical training and education services designed for individuals, companies, and public organizations to acquire, maintain, and optimize their IT skills at You can contact an IBM representative to learn about solutions at Copyright IBM Corp.,

40 34 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

41 Accessing and providing feedback on the product documentation Documentation is provided in a variety of locations and formats, including in help that is opened directly from the product client interfaces, in a suite-wide information center, and in PDF file books. The information center is installed as a common service with IBM InfoSphere Information Server. The information center contains help for most of the product interfaces, as well as complete documentation for all the product modules in the suite. You can open the information center from the installed product or from a Web browser. Accessing the information center You can use the following methods to open the installed information center. v Click the Help link in the upper right of the client interface. v v Note: From IBM InfoSphere FastTrack and IBM InfoSphere Information Server Manager, the main Help item opens a local help system. Choose Help > Open Info Center to open the full suite information center. Press the F1 key. The F1 key typically opens the topic that describes the current context of the client interface. Note: The F1 key does not work in Web clients. Use a Web browser to access the installed information center even when you are not logged in to the product. Enter the following address in a Web browser: com.ibm.swg.im.iis.productization.iisinfsv.home.doc/ic-homepage.html. The host_name is the name of the services tier computer where the information center is installed, and port_number is the port number for InfoSphere Information Server. The default port number is For example, on a Microsoft Windows Server computer named iisdocs2, the Web address is in the following format: com.ibm.swg.im.iis.productization.iisinfsv.nav.doc/dochome/ iisinfsrv_home.html. A subset of the information center is also available on the IBM Web site and periodically refreshed at index.jsp. Obtaining PDF and hardcopy documentation v A subset of the PDF file books are available through the InfoSphere Information Server software installer and the distribution media. The other PDF file books are available online and can be accessed from this support document: v You can also order IBM publications in hardcopy format online or through your local IBM representative. To order publications online, go to the IBM Publications Center at servlet/pbi.wss. Copyright IBM Corp.,

42 Providing comments on the documentation Your feedback helps IBM to provide quality information. You can use any of the following methods to provide comments: v v v v To comment on the information center, click the Feedback link on the top right side of any topic in the information center. Send your comments by using the online readers' comment form at Send your comments by to comments@us.ibm.com. Include the name of the product, the version number of the product, and the name and part number of the information (if applicable). If you are commenting on specific text, include the location of the text (for example, a title, a table number, or a page number). You can provide general product feedback through the Consumability Survey at 36 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

43 Product accessibility You can get information about the accessibility status of IBM products. The IBM InfoSphere Information Server product modules and user interfaces are not fully accessible. The installation program installs the following product modules and components: v IBM InfoSphere Business Glossary v IBM InfoSphere Business Glossary Anywhere v IBM InfoSphere DataStage v IBM InfoSphere FastTrack v IBM InfoSphere Information Analyzer v IBM InfoSphere Information Services Director v IBM InfoSphere Metadata Workbench v IBM InfoSphere QualityStage For information about the accessibility status of IBM products, see the IBM product accessibility information at index.html. Accessible documentation Accessible documentation for InfoSphere Information Server products is provided in an information center. The information center presents the documentation in XHTML 1.0 format, which is viewable in most Web browsers. XHTML allows you to set display preferences in your browser. It also allows you to use screen readers and other assistive technologies to access the documentation. The documentation that is in the information center is also provided in PDF files, which are not fully accessible. IBM and accessibility See the IBM Human Ability and Accessibility Center for more information about the commitment that IBM has to accessibility. Copyright IBM Corp.,

44 38 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial

45 Notices and trademarks This information was developed for products and services offered in the U.S.A. Notices IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Shimotsuruma, Yamato-shi Kanagawa Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web Copyright IBM Corp.,

46 sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation J46A/G4 555 Bailey Avenue San Jose, CA U.S.A. Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to 40 IBM InfoSphere Information Server: InfoSphere Metadata Asset Manager tutorial