Using MDM - Relate 360 to Create Relationship Graph for ... Library/1/0987... · relationships between them. When you create relationships between two or more types of data, the relationships

Using MDM - Relate 360 to Create Relationship

Graph for MDM - Customer 360

© Copyright Informatica LLC 2017. Informatica, the Informatica logo, PowerCenter, and PowerExchange are trademarks or registered trademarks of Informatica LLC in the United States and many jurisdictions throughout the world. A current list of Informatica trademarks is available on the web at https://www.informatica.com/trademarks.html

AbstractIn an organization, you can use multiple applications to store and manage data. The data can be customer data, transaction data, product data, and other types of data. When you use MDM - Customer 360 to create and manage customer data, you can use MDM - Relate 360 to relate the customer data with other types of data and create the relationship graph for the customer data.

This article describes how to use Relate 360 to create the relationship graph for Customer 360.

Supported Versions• MDM - Relate 360 10.0 HotFix 7

• PowerCenter® 10.x

• PowerExchange® for Hadoop 10.x

• MDM - Customer 360 10.2

Table of ContentsOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Relationship Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Creating Relationship Graph in Relate 360. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Migrating Data to HDFS. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Step 1. Import Source Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Step 2. Create the Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Step 3. Create an HDFS Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Step 4. Run the Mappings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Creating the Configuration and Matching Rules Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Run the Extractor Utility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating the Relationship Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creating a Properties File for the Relationship Graph User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Packaging and Deploying the WAR Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Processing Data in Relate 360. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Creating the Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Integrating Customer 360 with Relate 360. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring a Custom View for the Person Business Entity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Configuring an External Link for the Custom View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring a Graph Component for the Person Dashboard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Configuring an External Link for the Graph Component. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Viewing the Relationship Graph. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Relationship Graph User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Filtering the Business Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Aggregating the Business Entities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

2

Setting the Visualization Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Modifying the Graph View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

OverviewIn an organization, you can use multiple applications to store and manage data. The data can be customer data, transaction data, product data, and other types of data. Relate 360 can process different types of data and create relationships between them. When you create relationships between two or more types of data, the relationships result in the relationship graph. When you use Customer 360 to manage the customer data, you can leverage the scalability and capabilities of Relate 360 to create the relationship graph for the customer data.

Relate 360 requires the data to be in HDFS in the fixed-width format. Use a data integration tool to read data from different data sources including the Hub Store of Customer 360 and write the data to HDFS in the fixed-width format. You can consider each type of data as a business entity type. After you create relationships between two or more business entity types, you can integrate Customer 360 with Relate 360 to view the relationship graph in Customer 360.

For more information about Customer 360 and Relate 360, see the Customer 360 and Relate 360 documentation set.

Relationship GraphA relationship graph displays all the related business entities of a business entity and its relationships with the related business entities.

The following image shows a representational relationship graph:

In the representational relationship graph, Customer, Product, Transaction, and Service Request are business entity types, and owns, transaction, and complaint are relationships that connect the business entity types. The representational graph can display all the products a customer owns. The graph can also display the service requests and the transaction details of each product the customer owns.

ScenarioYou work for a large insurance organization that uses Customer 360 to manage customer data and other applications to manage product data and transaction data. You want to use Relate 360 to process each type of data, relate the product and transaction data to the customer data, and create the relationship graph. You want to use the relationship

3

graph to have a 360-degree view of the customers, understand them better, and come up with targeted marketing programs.

Creating Relationship Graph in Relate 360You can use Relate 360 to process different types of data and create relationships between them. You must migrate the required data to HDFS in the fixed-width format for Relate 360 to process. Use PowerCenter with PowerExchange for Hadoop to migrate data from the Hub Store of Customer 360 for customer data and from other data sources for the product and transaction data. You can consider each type of data as a business entity type and its data as business entity. For example, each customer record from Customer 360 is a business entity of type Customer.

1. Migrate the customer, product, and transaction data from their data sources to HDFS in the fixed-width format.

You can use PowerCenter with PowerExchange for Hadoop to migrate data.

2. Create the configuration and matching rules files for each business entity type.

You can use the extractor utility of Relate 360 to generate the configuration file and the matching rules file for the customer data stored in Customer 360.

3. Create the relationship configuration file.

4. Create a properties file for the relationship graph user interface.

5. Package and deploy the WAR files for the RESTful web services and the relationship graph user interface.

6. Process data and load the processed data into the repository.

7. Create relationships between the business entity types.

8. Integrate Customer 360 with Relate 360.

9. View the relationship graph in Customer 360.

Migrating Data to HDFSYou must migrate the customer, product, and transaction data from their data sources to HDFS in the fixed-width format for Relate 360. You can use the PowerCenter Designer and the PowerCenter Workflow Manager to migrate data to HDFS.

Note: Ensure that the transaction data uses the ROWID_OBJECT column to refer to the customer data.

1. Import source definitions for each data source.

2. Create a mapping with one or more source definitions and a target definition for each data source. If you add more than one source definition, add a Joiner transformation to the mapping.

3. Create an HDFS connection.

4. Run the mappings to migrate data to HDFS.

Step 1. Import Source DefinitionsUse the Designer to import source definitions for the data sources. A source definition extracts data from a data source. For Customer 360, import a relational source definition for the base object in the Hub Store. If you want to integrate data from more than one base object, create a relational source definition for each base object. For example, if you have separate base objects for person names and addresses, create two relational source definitions, one for the person names and another for the addresses. You can use a Joiner transformation to integrate the person names and the address details.

The following image shows the source definitions for the person names and addresses base objects:

4

Step 2. Create the MappingsUse the Designer to create a mapping for each data source. A mapping represents the data flow between the source and target instances.

To create a mapping, perform the following tasks:

1. Create a mapping and add the source definitions that you import.

When you add the source definitions to the mapping, the Designer adds a Source Qualifier transformation for each source definition.

2. If you add a single source definition, perform the following tasks:

a. Create and add a target definition from the Source Qualifier transformation.

When you create a target definition from a transformation, the type of target is the same as the source instance by default. You must update the writer type of the target definition to HDFS Flat File Writer in the Workflow Manager.

b. Link the ports between the Source Qualifier transformation and the target definition.

3. If you add more than one source definition, perform the following tasks:

a. Create a Joiner transformation.

A Joiner transformation joins data from two or more source definitions. The Joiner transformation uses a condition that matches one or more pairs of columns between the source definitions.

b. Link the ports between the Source Qualifier transformations and the Joiner transformation.

c. Configure a condition to integrate data from the source definitions.

The following image shows a condition based on which the Joiner transformation integrates data:

5

d. Create and add a target definition from the Joiner transformation.

When you create a target definition from a transformation, the type of target is the same as the source instance by default. You must update the writer type of the target definition to HDFS Flat File Writer in the Workflow Manager.

e. Link the ports between the Joiner transformation and the target definition.

4. Validate the mapping.

The Designer marks a mapping as not valid when it detects errors.

Step 3. Create an HDFS ConnectionUse the Workflow Manager to create an HDFS connection. You can use the HDFS connection to access the Hadoop cluster.

Step 4. Run the MappingsUse the Workflow Manager to run a mapping. You must run all the mappings to migrate data from all the data sources to HDFS.

To run a mapping, perform the following tasks:

1. Create a workflow and configure the PowerCenter Integration Service for the workflow.

2. Create a Session task and select the mapping.

3. Edit the session to update the following properties:

• Writer type of the target definition to HDFS Flat File Writer.

• HDFS connection details for the target definition.

The following image shows the properties of a target definition:

6

4. Start the workflow to integrate the source data and write the integrated data to the flat file in HDFS.

Creating the Configuration and Matching Rules FilesYou must create a configuration file and a matching rules file in the XML format for each business entity type. A configuration file defines parameters related to the Hadoop distribution, repository, SSA-NAME3, input record layout, and metadata. A matching rules file defines indexes, searches, and matching rules for each index.

To create the configuration and matching files, you can customize the following sample configuration and matching rules file based on your requirement:

• /usr/local/mdmbdrm-<Version Number>/sample/MDMBDRMTemplateConfiguration.xml• /usr/local/mdmbdrm-<Version Number>/sample/MDMBDRMMatchRuleTemplate.xmlFor the Customer business entity, you can run the extractor utility of Relate 360 named config-tools.jar to generate the configuration and matching rules files based on the Customer 360 environment.

Run the Extractor UtilityYou can run the extractor utility to generate the configuration and matching rules files for the Customer business entity type. The utility extracts the index, search, and matching rules definition from the Hub Store and adds the definitions to the matching rules file. The utility creates the configuration file to which you must manually add the parameters related to Hadoop distribution, repository, input record layout, and metadata.

On the machine where you install Relate 360, you can find the config-tools.jar utility in the following directory: /usr/local/mdmbdrm-<Version Number>/bin

Use the following command to run the extractor utility:

java -cp <JDBC Driver Name>:<Extractor Utility Name>:. com.informatica.mdmbde.driver.ExtractConfig <Driver Class> <Connection String> <User Name> <Password> <Schema Name> <Rule Set name>

Use the following parameters to run the utility:

7

Extractor Utility Name

Absolute path and file name of the extractor utility, which is /usr/local/mdmbdrm-<Version Number>/bin/config-tools.jar.

JDBC Driver Name

Absolute path and name of the JDBC driver.

Use one of the following values based on the database you use for the Hub Store:

• Oracle. ojdbc6.jar• Microsoft SQL Server. sqljdbc.jar• IBM DB2. db2jcc.jar

Driver Class

Driver class for the JDBC driver.

Use one of the following values based on the database you use for the Hub Store:

• Oracle. oracle.jdbc.driver.OracleDriver• Microsoft SQL Server. com.microsoft.sqlserver.jdbc.SQLServerDriver• IBM DB2. com.ibm.db2.jcc.DB2Driver

Connection String

Connection string to access the metadata in the Hub Store.

Use the following format for the connection string based on the database you use for the Hub Store:

• Oracle. jdbc:informatica:oracle://<Host Name>:<Port>;SID=<Database Name>• Microsoft SQL Server. jdbc:informatica:sqlserver://<Host Name>:<Port>;Databasename=<Database

Name>• IBM DB2. jdbc:informatica:db2://<Host Name>:<Port>;Databasename=<Database Name>

Host Name indicates the name of the server on which you host the database, Port indicates the port through which the database listens, and Database Name indicates the name of the Operational Reference Store (ORS).

User Name

User name to access the ORS.

Password

Password for the user name to access the ORS.

Schema

Name of the ORS.

Rule Set Name

Name of the match rule set. The utility retrieves the match definitions from the rule set and writes the definitions to the matching rules file.

For example, the following command runs the extractor utility in an IBM DB2 environment:

java -cp /root/db2jcc.jar:/usr/local/mdmbdrm-<Version Number>/bin/config-tools.jar:. com.informatica.mdmbde.driver.ExtractConfig com.ibm.db2.jcc.DB2Driver jdbc:db2://mdmauto10:50000/DEVUT DQUSER Password1 DQUSER TP_Match_Rule_Set

8

Creating the Relationship Configuration FileYou must create a relationship configuration file in the XML format to define the business entity types, their potential relationships, and the columns that you want to display in the relationship graph.

You can customize the following sample relationship configuration file based on your requirement: /usr/local/mdmbdrm-<Version Number>/sample/MDMBDRMRelationshipConfigTemplate.xmlFor more information about the relationship configuration file, see the Informatica MDM - Relate 360 Installation and Configuration Guide.

Creating a Properties File for the Relationship Graph User InterfaceYou must create a properties file with parameters related to the relationship graph.

The following sample shows the properties configured for the relationship graph user interface:

serverURL=10.19.20.43:8080/MDMBDRMCustomer360/v4.0/Customer360/defaultPagination=20graph_depth=3graph_maxnode=50

You can configure the following parameters in the properties file:serverURL

URL to access the relationship graph user interface WAR file.

Use the following format for the URL:

<Host IP Address>:<Port>/<WAR File Name>/<Version Number>/<Configuration File Identifier>/

The URL uses the following parameters:

• Host IP Address. IP address of the host machine on which you plan to deploy the relationship graph user interface WAR file.

• Port. Port number on which the host listens.

• WAR File Name. Name of the WAR file that you plan to generate for the RESTful web services.

• Version Number. Version number of the RESTful web services.

• Configuration File Identifier. Unique identifier for the configuration file and the matching rules file that you specify when you package the RESTful web services.

For example, 10.19.20.43:8080/MDMBDRMCustomer360/v4.0/Customer360/

defaultPagination

Optional. Maximum number of search results to return in the user interface when you search for a record. Default is 10.

graph_depth

Optional. Maximum number of child levels to display in the relationship graph. Default is 5.

graph_maxnode

Optional. Maximum number of nodes that you want to display in the relationship graph. Default is 500.

9

Packaging and Deploying the WAR FilesYou must package the RESTful web services and the relationship graph user interface as the WAR files. You must package the RESTful web services for each business entity type. You require only one relationship graph user interface WAR file for your environment.

1. Package the RESTful web services and the relationship graph user interface for the Customer business entity type.

Use the run_deployment.sh script to generate the WAR files. Ensure that you run the script with the --uiconfig and --relationship parameters.

2. Package the RESTful web services for the Product and Transaction business entity types.

Use the run_deployment.sh script to generate the WAR files.

3. Copy the WAR files that contain the RESTful web services and the bdrm-ui.war file that contains the relationship graph user interface to the following directory: $CATALINA_HOME/webapps

4. Export the LD_LIBRARY_PATH environment variable to include the following directory: /usr/local/mdmbdrm-<Version Number>/bin directory.

For example, export LD_LIBRARY_PATH=/usr/local/mdmbdrm-<Version Number>/bin5. Export the JAVA_OPTS environment variable to configure the minimum and maximum heap sizes based on the

amount of available memory.

For example, export JAVA_OPTS="-Xms1536m -Xmx1536m"6. To start the Tomcat server, from the bin directory of the Tomcat installation, run the following command:

./startup.sh

Processing Data in Relate 360After you migrate data to HDFS, process the data in Relate 360. You can link or tokenize the data based on the type of data. For example, you can link the customer data to identify the household members. You do not require to link the product and transaction data, so you can tokenize the product and transaction data.

1. Link the customer data.

Use the initial clustering job to link the input data based on the rules in the matching rules file and the parameters in the configuration file.

2. Load the linked data into the repository.

Use the load clustering job to create the required tables in the repository and load the linked data into the tables.

3. Load the match-pair data into the repository.

Use the load match pairs job to load the match pairs of the customer data into the repository.

4. Tokenize the product and transaction data.

Use the repository tokenization job to tokenize the input data, create required tables in the repository, and load the tokenized data into the tables. You must run the repository tokenization job separately for the product data and for the transaction data.

For more information about the initial clustering, load clustering, load match pairs, and repository tokenization jobs, see the Informatica MDM - Relate 360 User Guide.

10

Creating the RelationshipsAfter you load the processed data into the repository, you can create relationships between the business entity types. Use the create relationship job to create a relationship between two business entity types.

Run the create relationship job and create relationships between the Customer and Product business entity types, the Customer and Transaction business entity types, and the Product and Transaction business entity types. After you create the relationships between the business entity types, the relationships result in a relationship graph.

For more information about the create relationship job, see the Informatica MDM - Relate 360 User Guide.

Integrating Customer 360 with Relate 360You can integrate Customer 360 with the Relate 360 to view the relationship graph in Customer 360. The relationship graph displays all the related business entities of a Person business entity and its relationships with the related business entities.

In Customer 360, you must configure a custom view to display the relationship graph for a Person business entity. You can also configure a graph component to display an aggregate view of the related business entities in the Person dashboard.

To integrate Customer 360 with Relate 360, perform the following tasks in Customer 360:

1. Configure a custom view for the Person business entity type.

2. Configure an external link for the custom view.

3. Configure a graph component for the Person dashboard.

4. Configure an external link for the graph component.

Configuring a Custom View for the Person Business EntityYou must configure a custom view for the relationship graph in the layout configuration file of the C_REPOS_COMPONENT_INSTANCE table. The configuration type for the layout configuration file is ContainerCoView.

1. Use a database tool to open the C_REPOS_COMPONENT_INSTANCE repository database table.

2. Select the BLOB data of the CustomerPerson instance and ContainerCoView column type.

3. Open the BLOB data in the XML format.

4. Add the following XML code format to configure a layout for the custom view: <layout id="<ID>" name="<Name>" title="<Title>" icon="glyphicon glyphicon-dashboard" order="<Order Number>"> <businessEntity entityState="existing" view="CustomerPersonView" /> <capability name="E360View" type="navigable" /> <container containerId="mainAreaContainer1"> <component configuration="<Name>" type="ExternalLink" view="null" /> </container> <template><div class="row"><div class="col-lg-12"><div class="row"><div class="col-lg-12"><div data-container-id="mainAreaContainer1"></div></div></div></div></div></template></layout>

The XML code format uses the following parameters:

11

ID

Unique identifier for the custom layout.

Name

Name for the custom view.

Title

Name that you want to display in the list of views.

Order Number

Sequence number of the title in the list. The view with the lowest value appears at the top of the lists. If you do not specify values for the order attribute, the views appear in the list in the same order that the layouts occur in the configuration file.

The following XML code creates a layout for the custom view named PersonGraphView:

<layout id="1036" name="PersonGraphView" title="Person Graph View" icon="glyphicon glyphicon-dashboard" order="3"> <businessEntity entityState="existing" view="CustomerPersonView" /> <capability name="E360View" type="navigable" /> <container containerId="mainAreaContainer1"> <component configuration="PersonGraphView" type="ExternalLink" view="null" /> </container> <template><div class="row"><div class="col-lg-12"><div class="row"><div class="col-lg-12"><div data-container-id="mainAreaContainer1"></div></div></div></div></div></template></layout>

5. Save the file and upload the XML file to the BLOB data.

Configuring an External Link for the Custom ViewAfter you configure a custom view, you must configure an external link for the custom view.


2. Select the BLOB data of the custom view instance and ExternalLink column type.

For example, if the custom view name is PersonGraphView, then the custom view instance is PersonGraphView.


4. Add the following XML code format to configure an external link for the custom view: <dataViewLayout xmlns="http://www.informatica.com/mdm/ExternalLink"> <widgetContent><![CDATA[<iframe src="http://<Host>:<Port>/<Relationship Graph UI WAR Name>/noshell/graph/<Source>/Customer/{{rowidObject}}/network" width="100%" height="800px"></iframe>]]></widgetContent></dataViewLayout>

The XML code format uses the following parameters:Host

Host name or IP address of the machine on which you deploy the Relate 360 relationship graph user interface WAR file.

Port

Port on which the host listens.

12

Relationship Graph UI WAR Name

Name of the relationship graph user interface WAR file that you deploy on the host.

Source

Source name of the business entities. If you do not have the source name for the business entities, use the source name that you used in Relate 360 to process the customer data.

The following XML code creates a custom view named PersonGraphView:

<dataViewLayout xmlns="http://www.informatica.com/mdm/ExternalLink"> <widgetContent><![CDATA[<iframe src="http://10.12.128.71:8080/bdrm-ui/noshell/graph/MDM/Customer/{{rowidObject}}/network" width="100%" height="800px"></iframe>]]></widgetContent></dataViewLayout>


Configuring a Graph Component for the Person DashboardYou can configure a graph component for the Person dashboard. The graph component displays an aggregated view of the related business entities for a Person business entity.


2. Select the BLOB data of the CustomerPerson instance and ContainerCoView column type.


4. Add the following XML code format to configure a graph component for the Person dashboard: <component configuration="<Name>" type="ExternalLink" view="null"/>

The Name parameter indicates the name of the graph component that you configure.

The following XML code shows the configuration of the Person dashboard that has a graph component named PersonAggregateView:

<layout icon="glyphicon glyphicon-dashboard" id="1005" name="layout2" order="1" title="Person Dashboard"> <businessEntity entityState="existing" view="CustomerPersonView" /> <capability name="E360View" type="navigable" /> <container containerId="mainAreaContainer1"> <component configuration="B2COverview" type="ExternalLink" view="null" /> </container> <container containerId="mainAreaContainer6"> <component configuration="B2CIdentifiers" type="ExternalLink" view="null" /> </container> <container containerId="mainAreaContainer2"> <component configuration="B2CFinancial" type="ExternalLink" view="null" /> </container> <container containerId="mainAreaContainer3" /> <container containerId="mainAreaContainer4" /> <container containerId="mainAreaContainer5" /> <container containerId="mainAreaContainer7"> <component configuration="ProductComponent" type="ProductComponent" view="null" /> <component configuration="PersonAggregateView" type="ExternalLink" view="null" /> </container> <container containerId="mainAreaContainer8"> <component configuration="C360TagsForPerson" type="C360Tags" view="null" /> </container> <container containerId="toolsAreaContainer3"> <component configuration="B2CCustomerSince" type="ExternalLink" view="null" /> </container> <container containerId="toolsAreaContainer2"> <component configuration="B2CIndicators" type="ExternalLink" view="null" /> </container> <container containerId="toolsAreaContainer1">

13

<component configuration="B2CContact" type="ExternalLink" view="null" /> <component configuration="B2CTwitter" type="ExternalLink" view="null" /> </container> <template><div class="row"><div class="col-lg-9"><div class="row"><div class="col-lg-12"><div data-container-id="mainAreaContainer1"></div></div></div><div class="row"><div class="col-lg-8"><div data-container-id="mainAreaContainer6"></div></div><div class="col-lg-4"><div data-container-id="mainAreaContainer2"></div></div></div><div class="row"><div class="col-lg-4"><div data-container-id="mainAreaContainer3"></div></div><div class="col-lg-4"><div data-container-id="mainAreaContainer4"></div></div><div class="col-lg-4"><div data-container-id="mainAreaContainer5"></div></div></div><div class="row"><div class="col-lg-8"><div data-container-id="mainAreaContainer7"></div></div><div class="col-lg-4"><div data-container-id="mainAreaContainer8"></div></div></div></div><div class="col-lg-3"><div class="row"><div class="col-lg-12"><div data-container-id="toolsAreaContainer3"></div><div data-container-id="toolsAreaContainer2"></div><div data-container-id="toolsAreaContainer1"></div></div></div></div></div></template></layout>


Configuring an External Link for the Graph ComponentAfter you configure the graph component, you must configure an external link for the graph component.


2. Select the BLOB data of the graph component instance and ExternalLink column type.

For example, if the graph component name is PersonAggregateView, then the graph component instance is PersonAggregateView.


4. Add the following XML code format to configure an external link for the graph component: <dataViewLayout xmlns="http://www.informatica.com/mdm/ExternalLink"> <widgetContent><![CDATA[<iframe src="http://<Host>:<Port>/<Relationship Graph UI WAR Name>/noshell/graph/<Source>/Customer/{{rowidObject}}/aggregate" width="100%" height="800px"></iframe>]]></widgetContent></dataViewLayout>

The XML code format uses the following parameters:Host

Host name or IP address of the machine on which you deploy the Relate 360 relationship graph user interface WAR file.

Port

Port on which the host listens.

14

Relationship Graph UI WAR Name

Name of the relationship graph user interface WAR file that you deploy on the host.

Source

Source name of the business entities. If you do not have the source name for the business entities, use the source name that you used in Relate 360 to process the customer data.

The following XML code creates a graph component named PersonAggregateView:

<dataViewLayout xmlns="http://www.informatica.com/mdm/ExternalLink"> <widgetContent><![CDATA[<iframe src="http://10.12.128.71:8080/bdrm-ui/noshell/graph/MDM/Customer/{{rowidObject}}/aggregate" width="100%" height="800px"></iframe>]]></widgetContent></dataViewLayout>


Viewing the Relationship GraphYou can access the relationship graph through the custom view that is created for the relationship graph.

1. Open a business entity.

2. Select the custom view that is created for the relationship graph.

The relationship graph appears.

Relationship Graph User InterfaceThe relationship graph displays a graph, filters, and column values for the selected business entity. The graph displays all the related business entities of the selected business entity. You can filter the business entities in the graph based on the filters that are available for the business entity type.

The following image shows a sample relationship graph:

1. Graph panel

2. Fields panel

15

3. Filters panel

4. Visualization Options panel

A relationship graph includes the following panels:Graph panel

Displays how the selected business entity is connected to other business entities. The graph changes based on the filters that you apply.

Fields panel

Displays the columns related to a business entity that you select in the graph. The columns that appear in the Fields panel depend on the parameters that you configure in the relationship configuration file.

Filters panel

Displays the filters that you can use to filter the business entities. You can filter the business entities based on the business entity types and their column values. You can also aggregate the business entities based on the columns of the business entity type.

Visualization Options panel

Allows you to highlight the relationships and business entities. You can also hide or show the labels of the relationships and nodes.

Filtering the Business EntitiesYou can filter the business entities based on their column values. You can also filter all the business entities that are related to a business entity type.

1. Open the relationship graph.

By default, the graph displays the selected business entity and all its related business entities.

2. To remove all the business entities that belong to a business entity type from the graph, under Filter, clear the business entity type.

The graph refreshes and removes all the business entities that belong to the business entity type from the graph.

3. To include all the business entities that belong to a business entity type in the graph, under Filter, select the business entity type.

4. To filter the business entities based on the column values of a business entity type, perform the following tasks:

a. Under Filter, click the filter icon of a business entity type whose columns you want to use to filter the business entities.

A list of columns appear. The columns that are available in the list are based on the parameters that you configure in the relationship configuration file.

b. Select a column.

If you have configured the column as an exact filter, a text box appears. If you have configured the column as an enumeration filter, a list of enumeration values appear.

c. For an exact filter, type the exact column value based on which you want to filter the business entities.

d. For an enumeration filter, select the enumeration value based on which you want to filter the business entities.

16

The following image shows the enumeration values configured for the PaymentMode column:

e. Click OK.

The graph refreshes to reflect the filtered business entities.

Aggregating the Business EntitiesYou can aggregate the business entities based on the selected columns of a business entity type.

1.

Under Filter, click the aggregate icon of a business entity type whose columns you want to use to aggregate the business entities.

17

2. Select the columns based on which you want to aggregate the business entities, and click OK.

The graph refreshes to reflect the aggregated business entities.

The following image shows Gene Jackson's related business entities that are aggregated based on the ProductName column:

Setting the Visualization OptionsYou can select to show or hide the relationship and node labels in the relationship graph. You can also turn the highlight effect on or off for the relationships and nodes.

In the Visualizations Options panel, click the following icons that you can find against each relationship and business entity type:

Icon Description

Turns the highlight effect on or off.

Shows or hides the relationship or business entity labels.

Modifying the Graph ViewYou can zoom in, zoom out, and perform other actions in the graph to modify the view of the graph.

In the Graph panel, click the following icons that you can find in the upper right corner of the panel:

Icon Description

Adjusts the graph to highlight how the selected node is related to the main node.

Aligns the graph to the center of the panel.

18

Icon Description

Zooms in or zooms out the graph so that the entire graph fits the panel.

Resets the graph to its original size.

Zooms out to reduce the size of the nodes.

Zooms in to increase the size of the nodes.

Resets the graph to its default layout.

AuthorBharathan JeyapalLead Technical Writer

19

Documents

Using MDM - Relate 360 to Create Relationship Graph for ... Library/1/0987... · relationships between them. When you create relationships between two or more types of data, the relationships