IBM InfoSphere Discovery Sample Projects - Internode

2y ago
18 Views
2 Downloads
1.76 MB
64 Pages
Last View : 1d ago
Last Download : 6m ago
Upload by : Aiyana Dorn
Transcription

IBM InfoSphere DiscoveryVersion 4 Release 5.1Sample Projects SC23-9880-04

IBM InfoSphere DiscoveryVersion 4 Release 5.1Sample Projects SC23-9880-04

Copyright IBM Corporation 2006, 2011.US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.

ContentsChapter 1. Installing IBM InfoSphereDiscovery . . . . . . . . . . . . . . 1Prerequisites . . . . . . . . . . . . .Supported Data and Database . . . . . . .Automatic Database Configuration . . . . .Using IBM InfoSphere Discovery with a DifferentDB2 Database . . . . . . . . . . . .Installing Discovery with IBM DB2 Express EditionUninstalling Discovery . . . . . . . . . . 1. 1. 1. 2. 2. 3Chapter 2. Introduction todemonstrations about IBM InfoSphereDiscovery . . . . . . . . . . . . . . 5Demonstration Project: Overlaps and the UnifiedSchema Builder . . . . . . . . . . . .Start Discovery Studio and create a project . .Create and populate the data sets . . . . .Import tables from the JDBC connection into thedata set . . . . . . . . . . . . . .Create the Region data set . . . . . . .Create the CRM data set . . . . . . . .Run and review column analysis . . . . .Identifying critical elements . . . . . . .Discover and review PF Keys . . . . . .Discover and review data objects . . . . .Overlaps . . . . . . . . . . . . .Creating a unified customer model . . . . Copyright IBM Corp. 2006, 2011. 5. 6. 9.111416162021242629Unified column analysis . . . . . . . . .Perform match and merge analysis . . . . .Create a report to include in your developmentspecifications . . . . . . . . . . . . .Demonstration Project: Archiving tables by definingbusiness objects . . . . . . . . . . . . .Start InfoSphere Discovery . . . . . . . .Create the project and the data sets . . . . .Import CIS tables . . . . . . . . . . .Defining option sets for your analysis . . . .Analyzing and reviewing discoveredrelationships . . . . . . . . . . . . .Adjusting the data object . . . . . . . . .Export artifacts . . . . . . . . . . . .3030323334343536394042Contacting IBM . . . . . . . . . . . 43Product accessibility. . . . . . . . 45Accessing product documentation. . . 47Links to non-IBM Web sites. . . . . . 49Notices and trademarks . . . . . . . 51Index . . . . . . . . . . . . . . . 55iii

ivIBM InfoSphere Discovery Sample Projects

Chapter 1. Installing IBM InfoSphere DiscoveryDiscovery consists of three components: Discovery Server, Discovery EngineService, and Discovery Studio.When you choose to install IBM DB2 Express Edition during installation, allthree Discovery components must be installed on a single host.The Discovery installer installs IBM DB2 Express Edition and all database tablesnecessary to run the demo project, along with a completed version of the projectthat you can use for reference. If you do not install IBM DB2 Express Edition, thedemo project will not be installed and you cannot use this IBM InfoSphereDiscovery Sample Projects guide or run the demo project.PrerequisitesTo run the demo project, you can either install IBM DB2 9.7 Express Edition alongwith Discovery or you can use the existing installation of IBM DB2 9.7 ExpressEdition on Windows platform.Prerequisites are described in the IBM InfoSphere Discovery Installation Guide.Supported Data and DatabaseThe tutorials and demos used here are pre-configured for IBM DB2 9.7 onWindows. The bundled demo project uses DB2 source, a DB2 repository and DB2staging databases.The IBM InfoSphere Discovery Installation Guide lists the operating systemrequirements, supported databases, and supported ODBC or JDBC drivers or yourproduction environment.Automatic Database ConfigurationYou have the option of installing IBM DB2 Express Edition along with Discovery. Ifyou do, the Discovery installer automatically preconfigures IBM DB2 ExpressEdition and IBM InfoSphere Discovery for the demo projects by performing thefollowing actions:v creating the data sources and loading the tables into the databasev creating the required users and JDBC connectionsv creating a default staging data source in Discovery Studiov importing a completed version of one project into Discovery StudioThe Discovery installer catalogs the system JDBC data sources with the samenames as the databases.Note: IBM DB2 Express Edition cannot be installed on a host that already has anyexisting DB2 version installed (including other versions of DB2 clients or servers). Copyright IBM Corp. 2006, 20111

To install the bundled IBM DB2 Express Edition version and the pre-configureddemo project along with Discovery, make sure any previous DB2 packages arecompletely uninstalled from the host.Using IBM InfoSphere Discovery with a Different DB2DatabaseYou may use a different DB2 database with IBM InfoSphere Discovery, but theinstaller will not automatically preconfigure it or Discovery Studio.Installing Discovery with IBM DB2 Express EditionAbout this taskThe following instructions are for installing IBM InfoSphere Discovery with IBMDB2 Express Edition.Note: If IBM InfoSphere Discovery cannot be installed using these steps, install theproduct using the instructions in the IBM InfoSphere Discovery Installation Guide.Procedure1. Make sure the host meets the hardware and software prerequisites.2. Close all applications and windows on the machine.3. In a file explorer window, open the installation disk /CD directory, thendouble-click the file install.exe.The installation package starts extracting, which can take up to one minute.When it is finished, the installer's Introduction screen appears.4. Click Next to start the installation.5. Accept the license agreement and click Next.6. On the remaining screens, click Next to accept the default options.7. If any of the following situations occurs during installation, take action asnoted below.v If an error message states that IBM DB2 Express Edition cannot be installed,you have the following options:– Quit installation and completely uninstall any existing DB2 product fromthe machine (including deleting the DB2 directory), then start Discoveryinstallation again.– Uncheck the IBM DB2 Express Edition option in the installer, thencontinue installation. IBM DB2 Express Edition will not be installed andyou will not be able to use this IBM InfoSphere Discovery Sample Projectsguide or run the demo project.v If the Discovery Server Port screen states that some or all of the required portsare unavailable, change the ports as prompted. Contact your systemadministrator if needed.v If a security notice about blocking Java 2 Platform Standard Edition Binaryappears, click Unblock to allow Windows to access Java.v If the installer asks to install Microsoft Visual J# 2.0 Redistributable Package,click Next to accept the installation.v If an error message states that the installer did not successfully preconfigureIBM DB2 Express Edition or Discovery Studio, you will not be able to usethis IBM InfoSphere Discovery Sample Projects guide or run the demo project.8. In the Discovery Server Host screen, enter the following value:2IBM InfoSphere Discovery Sample Projects

v Discovery Server Hostname: localhost9. When the Start Both Services screen appears, click Next and then Done to closethe Discovery installer.ResultsIBM InfoSphere Discovery and IBM DB2 Express Edition are now installed. Theappropriate ODBC connections, users, and databases are created, the demo tablesare loaded, and you are ready to start Discovery Studio.Uninstalling DiscoveryAbout this taskThe uninstaller automatically uninstalls Discovery Server, Discovery EngineService, and Discovery Studio.To uninstall IBM InfoSphere Discovery:Procedure1. Stop Discovery Studio, Discovery Server, and Discovery Engine Service. Makesure no Discovery Studio tasks are queued or running.2. From the Start menu, select Programs IBM InfoSphere Discovery UninstallIBM InfoSphere Discovery.3. Accept the default, Full, by clicking Next.4. The uninstaller stops the selected components, if they are running, anduninstalls them from the machine.5. If any components or files could not be uninstalled, a message appears. In mostcases these are logs, configuration files, or user-created files. These files do notcontain any project data and can be deleted.ResultsIBM InfoSphere Discovery is now uninstalled.Chapter 1. Installing IBM InfoSphere Discovery3

4IBM InfoSphere Discovery Sample Projects

Chapter 2. Introduction to demonstrations about IBMInfoSphere DiscoveryBy using InfoSphere Discovery, you can find and manipulate relationships. Thesedemonstrations display some of the basic principles of Discovery.These instructions assume the following things:v You installed IBM DB2 Express Edition with IBM InfoSphere Discoveryv IBM DB2 Express Edition and InfoSphere Discovery Studio are successfullypreconfigured with the following objects:– The necessary data sources are created.– The tables are loaded in IBM DB2 Express Edition.– The required users and JDBC connections are created.– A default staging server is created in IBM InfoSphere Discovery Studio.As part of this preconfiguration, four completed demonstration projects areimported into Discovery Studio. You can review the completed projects before yourun these learning modules, and use them for reference as you work.Important: If you did not install IBM DB2 Express Edition, your demonstrationprojects will not be automatically configured. See the IBM InfoSphere Discovery UserGuide for instructions on creating projects and executing tasks.Learning objectivesThe objective of the demonstrations is to help you understand how to useInfoSphere Discovery to analyze data. Specifically you will be able to do thefollowing:v Create a project.v Create and populate data sets.v Run and review column analysis.v Discover and review primary and foreign keys.v Discover and review data objects.v Discover and review overlaps and unified schemas.Time requiredEach demonstration should take approximately 60 minutes to finish. If you exploreother concepts related to the demonstrations, it could take longer to complete.Demonstration Project: Overlaps and the Unified Schema BuilderConsolidating data from multiple systems can be difficult. IBM InfoSphereDiscovery enables a 4-step methodology for prototyping the artifacts for the finalsolutionThe four steps are:1. Inventory the data landscape2. Model the target Copyright IBM Corp. 2006, 20115

3. Map to and analyze the target4. Perform match and merge analysis.The Discover Data Consolidation sample project contains three data sets alreadydefined and configured for you:v CRMv Regionv CommunityEach of the data sets appears as a tab in the Data Sets view. You can view theconnection information for any of the data sets by using the following procedure:1. Click on a data set tab.2. Right-click on the data set in Database Connections & Tables.3. Select Edit the selected connection.You can also view the data content by clicking the Column Analysis tab.Learning objectivesAfter completing the lessons in this module you will be able to consolidate datafrom multiple source systems.This module should take approximately 60 minutes to complete.Start Discovery Studio and create a projectYou can create your own project to start learning to consolidate data from multiplesystems.All work in IBM InfoSphere Discovery is done in projects. Begin the lesson byopening Discovery Studio and then creating a project.1. From the Windows Start menu, select Programs IBM InfoSphere Discovery Discovery Studio. Discovery Studio opens and automatically connects tothe Discovery Server. The sample projects that were loaded during installation,Discover Data Consolidation, Discover PFKey DataObject, andDiscover Sensitive Critical Data, appear in the project list of the Source DataDiscovery tab. There is also a sample project in the Transformation Discoverytab called Discover Transformation.6IBM InfoSphere Discovery Sample Projects

To hide the Error List and Output pane, click the button in the upper rightcorner of the pane.2. In the Source Data Discovery tab, click New Project. You can create as manyprojects as necessary, but only one project can be open at a time.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery7

3. In the Name field, type the name of the project. In this example, type Training- Overlaps and Unified Schema Builder.4. Clear the Use Password checkbox, or you can enter the password to protectyour project from unauthorized access. Use the default settings for the otherfields.5. Click OK.The project Training - Overlaps and Unified Schema Builder is now created. Discoveryautomatically opens the next tab, Data Sets. You can click the Home tab to see theTraining - Overlaps and Unified Schema Builder project in the Source Data Discoveryproject list.8IBM InfoSphere Discovery Sample Projects

Create and populate the data setsThe new project requires three data sets. Create and name the data sets, specify aJDBC connection for each one, and import tables into each one.1. In the Data Sets tab, click Rename. In the dialog box type Community and clickOK.2. Click the Click here to add a new connection link.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery9

3. In the Create Connection window, complete the following fields using thevalues shown:v Connection Name: Community Sourcev Database Server Name: localhostv Database Name: ISD SRCv User Name: ISD MDMv Password: ISD user110IBM InfoSphere Discovery Sample Projects

4. In the Create Connection window, click Test Connection to verify theconnection parameters.5. Click OK to save the connection. The Community Source connection is addedto the Import Objects list under the Database Connections & Tables section.You have created a new data set and specified JDBC connection information forthat data set.Import tables from the JDBC connection into the data setAfter creating the data set, you need to add tables to begin working with the data.1. In the Import Objects list of the Data Sets tab, right-click the JDBC connection,Community Source, that you created in the previous lesson. Select ImportTables/File Formats from the drop-down menu.2. In the Import Table Wizard, click Search Tables.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery11

3. In the Table Name field, type COMMUNITY to search for tables that have namesthat begin with that string.4. Click Next.5. The result of the search found three tables beginning with the stringCOMMUNITY . Click Select All and then click Finish to select all three tables toimport.12IBM InfoSphere Discovery Sample Projects

The tables are imported into the Community data set. The physical tables arelisted in the Database Connections & Tables list and are appended with PT. Onelogical table is created for each physical table, and is listed in Logical Tables.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery13

Create the Region data setYou can now create the second data set that is needed for this demonstration andimport tables into it. You follow the same steps that you did for the Communitydata set.1. Right-click on the Community tab and select Add Data Set. A second, blankdata set is added to the project.14IBM InfoSphere Discovery Sample Projects

2. Rename the second data set by clicking Rename and changing the name toRegion.3. Click the Click here to add a new connection link.4. In the Create Connection window, complete the connection information byusing the following values:v Connection Name: Region Sourcev Database Server Name: localhost (same as previous connection)v Database Name: ISD SRC (same as previous connection)v User Name: ISD MDM (same as previous connection)v Password: ISD user1 (same as previous connection)5. Click OK.6. In the Import Objects list of the Data Sets tab, right-click the JDBC connection,Region Source that you just created. Select Import Tables/File Formats fromthe drop-down menu.7. In the Import Table Wizard, click Search Tables.8. In the Table Name field, type Region to search for tables that have namesthat begin with that string.9. Click Next.10. The result of the search found three tables beginning with the string Region .Click Select All and then click Finish to select all three tables to import. Theseare the tables to import:v ISD MDM.REGION ACCT NAMESv ISD MDM.REGION ADDR TYPEChapter 2. Introduction to demonstrations about IBM InfoSphere Discovery15

v ISD MDM.REGION BRCHThe tables are imported into the Region data set. The physical tables are listed inthe Database Connections & Tables list and are appended with PT. One logicaltable is created for each physical table, and is listed in Logical Tables.Create the CRM data setCreate the third of the three data sets and populate the data set. You follow thesame steps that you did for the Region and Community data sets.1. Right-click the Region tab and select Add Data Set. A third blank data set isadded to the project.2. Rename the third data set by clicking Rename and changing the name to CRM.3. Click the Click here to add a new connection link.4. In the Create Connection window, complete the connection information byusing the following values:v Connection Name: CRM Sourcev Database Server Name: localhost (same as previous connection)v Database Name: ISD SRC (same as previous connection)v User Name: ISD MDM (same as previous connection)5.6.7.8.9.v Password: ISD user1 (same as previous connection)In the Import Objects list of the Data Sets tab, right-click the JDBC connection,CRM Source, that you just created. Select Import Tables/File Formats from thedrop-down menu.In the Import Table Wizard, click Search Tables.In the Table Name field, type CRM to search for tables that have names thatbegin with that string.Click Next.The result of the search found three tables beginning with the string CRM . ClickSelect All Finish to select all three tables to import. These are the tables toimport:v ISD MDM.CRM ACCT TYPEv ISD MDM.CRM ADDRESS TYPEv ISD MDM.CRM BRCH 1AThe tables are imported into the CRM data set. The physical tables are listed in theDatabase Connections & Tables list and are appended with PT. One logical tableis created for each physical table, and is listed in Logical Tables.Run and review column analysisColumn analysis is performed individually on each table within each data set.The Column Analysis tab displays information about all columns in the data sets,such as the following information:v Metadatav Data types from physical or logical tables (Native Type)v Data types used in the staging databasev Formats for textual data discovered as number (NUMBERSTRING) or date-timedata (DATETIMESTRING)v Statistics gathered during the profiling step16IBM InfoSphere Discovery Sample Projects

If necessary, you can manually change a data type of a column and some othermetadata. You can use data preview to verify the actual data.Tip: Always re-run Discovery, including Column Analysis, after importing tablesor text files, changing a primary sample set, reloading or reimporting tables, orperforming any other action that affects the contents of a table, file, or data set.1. In the Data Sets tab, click Run Next Steps.2. In the Processing Options window, click Run to accept the defaults and queuethe Column Analysis task for processing on the tables in the project.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery17

As soon as you queue the task, the Column Analysis tab appears. Importedmetadata and other information available without discovery is displayed.While the task is queued or running, the project is locked. You can click onother tabs but you cannot make any changes that affect the project, such asadding data sets or tables, while a project is locked. Notice in the followingColumn Analysis figure that Discovery can include textual data types (the SSNcolumn is a NumberString).18IBM InfoSphere Discovery Sample Projects

3. When processing is complete, review the results in the Column Analysis tab.Review the tables in the data sets by clicking on each data set tab to display itstables in the Tables list, and then clicking each table to display the columninformation in the center grid.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery19

To display the actual data in a selected table, click Preview Data. You can sort,filter, and export the data from the preview.4. Verify that all of the metadata is correct. Imported or discovered metadata isshown in the first nine columns of the center grid in the Metadata category.The Data Type, Length, Precision, Scale, and Formats fields are editable, ifnecessary. If you change any of those values, click Re-Run Step to re-runColumn Analysis.5. Review the discovered statistics in the remaining columns of the center grid.Scroll to the right if necessary to view all columns in the center grid. If thesestatistics are not correct, these values can help you identify which columns ortables might be related. Statistics cannot be manually changed.For example, Cardinality and Selectivity are used together to identify howunique the values are in a column. Click Value Frequencies in the menu barfor a list of each value in the column and how often it appears.Min and Max display the actual smallest and largest values in the column.Mode is the most common value in the column.You have done a very basic column analysis to get an understanding of the data inthese sample data sets.Identifying critical elementsIn most projects you understand at least one data source more than others. For thepurposes of this lesson, assume that you know the CRM data more than the othersources.20IBM InfoSphere Discovery Sample Projects

You know the CRM source, so you first need to mark up the known critical dataelements (CDE).1. Click the Column Analysis tab.2. Select the CRM data set.3. Select the table CRM BRCH 1A.4. Select the following boxes in the CDE column:v FIRST NAMEv LAST NAMEvvvvTAX IDADDRESS LINE 1CITYSTATEThis process identifies these particular columns with specific attributes that youwant to include in your new target schema.5. Click Run Next Steps to process these attributes.You can go into the other data sets to mark any data elements that you recognizeas critical to retain in the consolidated project. You can also use the ValueFrequencies, Pattern Frequencies, or Length Frequencies views to examine the datacontent of a column that you think might be critical. These CDEs help you focuson the relationships in later discovery steps.Discover and review PF KeysPF Key discovery is performed across all columns within each data set.PF Keys are primary-foreign key pairs. InfoSphere Discovery discovers columnmatches, which are relationships between the data in two or more columns indifferent tables in the same data set. Based on the statistics and additionalcalculations not shown, Discovery promotes certain column matches to the statusof PF Keys. The PF Key with the best statistics for each column pair is selected asthe primary PF Key for that column pair.1. In the Column Analysis tab, click Run Next Steps.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery21

2. In the Processing Options window, ensure that the slider is next to PF Keys.Click Run to run PF Key discovery. Processing will take a minute or two tocomplete.3. When processing is complete, review the discovered primary-foreign keys byclicking on each data set tab.The Connected Tables and Unconnected Tables in each data set are listed onthe left of the screen and are also shown graphically in the center pane. Expandthe list and each table in the list to view its PF Keys and column matches.Scroll the display until the PF Keys and column matches of interest are visiblein the center pane, dragging tables (boxes) and relationships (lines) to rearrangethem as necessary.The Display Mode allows you to filter the center panel to show only columnmatches, only PF Keys, or only the selected item. Zoom is also useful.22IBM InfoSphere Discovery Sample Projects

4. Review the statistics for each PF Key by clicking on its connection in theConnected Tables list or on the connecting line in the center pane. The SQL forthe selected PF Key and its discovered statistics are displayed in the grid belowthe center pane.You now know something about the primary and foreign key relationships andhave a better understanding of the data.The statistics for each relationship are based on the join expression, shown in theForeign Keys tab. There might be several join expressions discovered for eachrelationship, each with different statistics.v Row Hit Rate (RHR) is the total number of table rows that satisfy the PF Keyexpression.v Value Hit Rate (VHR) is the number of unique values that satisfy the PF Keyexpression.v Cardinality is the number of unique value combinations involved in the PF Keyexpression.v Selectivity is the Cardinality divided by the total number of rows.A strong PF Key relationship has a high RHR, high VHR on the primary andforeign side, and a high Selectivity on the primary side.In some cases, especially when the statistics for all discovered relationships aresimilar, you might need to investigate further to determine which relationships areChapter 2. Introduction to demonstrations about IBM InfoSphere Discovery23

valid and which join expression is the best. The Show Hits, Show Misses, orShow Duplicates drop-down button allows you to preview the actual data in thetables.Discover and review data objectsData object discovery is performed across all tables within each data set.A data object is a logical cluster of all tables in a data set that have one or morecolumns that contain data that is related to the same business entity. Data objectsare not maps, but instead represent an object view of related tables. By groupingtables in this way, InfoSphere Discovery can narrow the focus of the analysis toonly the tables that are known to be related.Each table in the data set is represented in at least one data object, and a dataobject can contain as many tables as necessary. If more than one PF Key was foundbetween a pair of tables, Discovery creates one data object for the tables based onthe primary PF Key. A data object with only one table means that no other tablesin the data set contain data that is related to that table.Tip: A table that is not related to any others within its own data set may still berelated to a table in another data set. Discovery across data sets is performed in theTarget Matches step, which is not included in these lessons.For example, assume a data set contains three tables. In the PF Keys step,Discovery found several primary-foreign keys between two of the tables andselected one PF Key as primary. In the Data Objects step, Discovery creates twodata objects: one for the two tables related by the primary PF Key, and one for theunrelated third table.1. In the PF Keys tab, click Run Next Steps .24IBM InfoSphere Discovery Sample Projects

2. In the Processing Options dialog, click Run to execute Data Object processing.3. When processing is complete, verify that the data objects are sensible andaccurate, as measured by the statistics and your knowledge of the data.The data objects discovered within each data set are shown in the Data Objectslist on the left of the screen. Expand each data object in the list to display thetables in it. When you click on a data object or one of its tables, the data objectis displayed in the center pane.Scroll the center pane display, if necessary, to see all of the tables andrelationships within a data object, dragging tables (boxes) and relationships(lines) to rearrange them as necessary.Click on a connecting line in the diagram to display statistics about the PF Keyrelationships between the two tables.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery25

You have reviewed the PF Key relationships in the data objects and are satisfiedwith the validity of the relationships.OverlapsThe main task in the Overlaps tab is to review the discovered overlaps. Thisincludes viewing the column data to verify that the overlaps are useful and valid,deleting incorrect overlaps, and adding overlaps that you know exist but were notdiscovered. Accurate results provide a clear picture of overlapping data in yourdata sources.1. In the Data Objects tab, click Run Next Steps.26IBM InfoSphere Discovery Sample Projects

2. In the Processing Options window, click Run.3. When processing is complete, review the overlaps. Results are providedseparately for each data set, but are combined into Data Set Summary andData Set Overlaps pages.The graphic on the top-level Data Set Summary page provides a visualsummary of the overlap statistics. Each group of columns corresponds to a rowin the grid above the graphic.Chapter 2. Introduction to demonstrations about IBM InfoSphere Discovery27

4. Review the results by clicking on the statistics to drill down into the data. TheData Set Summary pages and Data Set Overlaps pages each have three levels:Data Set Summary, Table Summary, and Column Summary.When you examine the CRM data set, you can see that 22 out of the 33columns overlap with columns from other data sets. These overlaps canprovide important insight into the relationships between the CRM data set andother data sets.a. Click on the 22 in the table. You see a list of all CRM columns that overlapin data value (exact values) with some columns in Region and Community.The instances where you see zeroes, which indicates low overlap, meansthat the two sets of data do not have much in common.b. Examine the overlap on a critical data element such as LAST NAME, whichis an important natural key. A high degree of overlap on LAST NAME is agood indicator of overlapping customers. In this case, out of 77 last namesin CR

The following instructions are for installing IBM InfoSphere Discovery with IBM DB2 Express Edition. Note: If IBM InfoSphere Discovery cannot be installed using these steps, install the product using the instructions in the IBM InfoSphere Discovery Installation Guide. Procedure 1. Make sure the host meets the hardware and software prerequisites. 2.

Related Documents:

InfoSphere DataStage—Processes changes delivered from InfoSphere CDC that can be used by InfoSphere DataStage jobs. 4. Related information: Supported sources and targets 5-----IBM InfoSphere Change Data Capture, Version 10.2 About InfoSphere CDC and InfoSphere CDC Management Console

creating any warranties or representations from ibm (or its suppliers or licensors), or altering the terms and conditions of any agreement or license governing the use of ibm products and/or software. IBM, the IBM logo, ibm.com, InfoSphere, IBM InfoSphere Information Server, IBM InfoSphere

sample project described in IBM InfoSphere Discovery Sample Projects guide. Discovery Server is automatically configured to use these repository and staging data source databases. You can create and connect to different repository and staging data sources at any time using the instructions in the IBM InfoSphere Discovery User Guide.

IBM & non-IBM InfoSphere MDM DB2 & non-IBM Cognos & SPSS Unica ECM Data Growth Management InfoSphere Optim Rules / BPM iLog & Lombardi Data Warehouse InfoSphere Warehouse IBM Big Data Solutions Client and Partner Solutions Big Data Enterprise Engines Big Data Accelerators Text Image/Vi

IBM InfoSphere Change Data Capture (InfoSphere CDC) is a replication solution that captures database changes as they happen and delivers them to target databases, message queues, or an ETL solution such as InfoSphere DataStage based on table mappings configured in the InfoSphere CDC Management Console GUI application.

quality (InfoSphere Information Server, InfoSphere Data Replication, InfoSphere Federation Server), master data management (InfoSphere MDM), data life-cycle management (I nfoSphere Optim), and data security and privacy (I nfoSphere Guardium and InfoSphere Optim). Please see page 21 for an overview of the

Exploring Data Insights with IBM InfoSphere Master Data Management and IBM Watson Explorer 4 InfoSphere Master Data Management provides a trusted view of an entity, such as person, product, or location. The two products are connected through the InfoSphere MDM connector, as shown in Figure 3.

ANSI A300 (Part 1)-2001 Pruning Glossary of Terms . I. Executive Summary Trees within Macon State College grounds were inventoried to assist in managing tree health and safety. 500 trees or tree groupings were identified of 40 different species. Trees inventoried were 6 inches at DBH or greater. The attributes that were collected include tree Latitude and Longitude, and a visual assessment of .