TIBCO MDM Studio Repository Designer Tutorial - TIBCO Product

Two-Second Adv

TIBCO® MDM Studio

Repository Designer TutorialSoftware Release 3.3September 2013

antage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN TIBCO COLLABORATIVE INFORMATION MANAGER PROCESS DESIGNER USER’S GUIDE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.TIBCO, Two-Second Advantage, TIB, TIBCO Adapter, Predictive Business, Information Bus, TIBCO BusinessConnect, TIBCO ActiveMatrix BusinessWorks, TIBCO Enterprise Message Service, TIBCO Collaborative Information Manager, TIBCO Collaborative Information Manager Studio, TIBCO Collaborative Information Manager Process Designer, TIBCO Collaborative Information Manager Rulebase Designer, TIBCO Collaborative Information Manager Repository Designer are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.EJB, Java EE, J2EE, and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README.TXT FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.Copyright © 2007-2013 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

Contents | iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

Changes from the Previous Release of this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiTIBCO MDM Studio Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Chapter 1 Repository Designer Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Tutorial Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Task A - Create a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Task B - Create Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Task C - Create Attribute Groups and Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Customer Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Account Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Address Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Task D - Create Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Task E - Define Relationship attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Task F - Create a Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Task G - Validate the Repository Model. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Task H - Export the Repository Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Task I - Import the Repository Model into MDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Task J - Generate WSDL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

TIBCO MDM Studio Repository Designer Tutorial

iv | Contents


| v

Preface

The TIBCO MDM Studio provides a graphical interface for designing MDM artifacts and processes. It is based on TIBCO Business Studio and acts as an 'add on' component to Business Studio.

TIBCO MDM Studio comprises three components: the Process Designer, the Repository Designer, and the Rulebase Designer.

The TIBCO MDM Repository Designer provides a graphical user interface for designing repositories. The Repository Designer can be used to define repositories from scratch or to edit existing MDM repositories. The Repository Designer is based on TIBCO Business Studio and acts as an 'add on' component to Business Studio.

Topics

• Changes from the Previous Release of this Guide, page vi

• Related Documentation, page viii

• Typographical Conventions, page x

• Connecting with TIBCO Resources, page xii


vi |

Changes from the Previous Release of this Guide

This section itemizes the major changes from the previous release of this guide.

• Perspective Editor - Using the Perspective wizard of TIBCO MDM Studio, you can define a subset of the model during the design time. In addition, you can also deploy the perspectives in TIBCO MDM. For information on Perspective Editor, refer to Perspective Editor in TIBCO MDM Studio Repository Designer User's Guide. For information on querying records based on Perspective, refer to Record Services in TIBCO MDM WebServices Guide.

• Category Specific Attributes - Support for Classification Schemes is added in TIBCO MDM Studio. You can now create, modify, and delete a Classification Scheme. The Classification Code Editor allows you to define a hierarchical classification tree and map an attribute to the Classification Codes defined in the repository. For information on Category Specific Attribute, refer to Working with Classification Scheme Editor in TIBCO MDM Studio Repository Designer User's Guide.

• Input Map Editor - The Input Map now provides flexibility of mapping repositories with multiple attributes. You can also select the Classification Scheme and link the Classification Code with Category Specific Attributes in the input map editor. For information on Input Map Editor, refer to Input Map Editor in TIBCO MDM Studio Repository Designer User's Guide.

• Synchronization Format - TIBCO MDM Studio provides support for defining Synchronization formats. An editor allows you to define the attributes and other properties of a synchronization format. For information on Synchronization Formats, refer to Synchronization Format Editor in TIBCO MDM Studio Repository Designer User's Guide.

• Output Map Editor - Defining of output maps between attributes in the repository and the various outbound synchronization formats is now supported in TIBCO MDM Studio. For information on Output Maps, refer to Output Map Editor in TIBCO MDM Studio Repository Designer User's Guide.

• Data Source Upload - The Data Source Editor allows the upload of data files into the project and deployment of files to the MDM Server. This upload is not supported for SQL based data sources. For information on Data Source Upload, refer to Data Source Editor in TIBCO MDM Studio Repository Designer User's Guide.

• Incremental Deployment - Repositories, Relationships, and Input Maps can now be deployed as a single unit and do not require full model deployment. This includes renaming of repositories and relationships. For more


| vii

information on Data Source Upload, refer to Deployment in TIBCO MDM Studio Repository Designer User's Guide.

• Command Line Interface - The command line interfaces are provided to automate the export and deployment of the model. For information on Command Line Interface, refer to Command Line Interface in TIBCO MDM Studio Repository Designer User's Guide..


viii |

Related Documentation

This section lists useful documentation resources.

TIBCO MDM Studio DocumentationThe documentation road map shows the relationships between the books and online references in this product’s documentation set.

The following documents form the TIBCO MDM Studio documentation set:

• TIBCO MDM Studio Rulebase Designer User’s Guide

• TIBCO MDM Studio Rulebase Designer Tutorial.

• TIBCO MDM Studio Repository Designer User’s Guide.

• TIBCO MDM Studio Repository Designer Tutorial.

• TIBCO MDM Studio Process Designer User’s Guide.

• TIBCO MDM Studio Process Designer Tutorial.

• TIBCO MDM Studio Release Notes.

Legend Eclipse Help

Process Designer User’s Guide

Repository Designer Tutorial

Process Designer Tutorial

Repository User’s Guide

Flow for MDM Studio Users

Flow for MDM Studio Tutorial

users

Rulebase Designer Tutorial

Rulebase Designer User’s Guide

TIBCO MDM Studio documentation set also contains an installation guide, release notes, and a readme file. The products mentioned in road map are available after you install the product.


| ix

Other TIBCO Product DocumentationYou may find it useful to read the documentation for the following TIBCO products:

• TIBCO MDM User’s Guide: This manual explains features and benefits of TIBCO MDM from the business user’s viewpoint.


x |

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME

ENV_HOME

Many TIBCO products must be installed within the same home directory. This directory is referenced in documentation as TIBCO_HOME. The value of TIBCO_HOME depends on the operating system. For example, on Windows systems, the default value is C:\tibco.

Other TIBCO products are installed into an installation environment. Incompatible products and multiple instances of the same product are installed into different installation environments. The directory into which such products are installed is referenced in documentation as ENV_HOME. The value of ENV_HOME depends on the operating system. For example, on Windows systems the default value is C:\tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code

font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO BusinessWorks Concepts.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand pathname


| xi

Key combinations

Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


xii |

Connecting with TIBCO Resources

How to Join TIBCOmmunityTIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers forums, blogs, and access to a variety of resources. To register, go to http://www.tibcommunity.com.

How to Access TIBCO DocumentationYou can access TIBCO documentation here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows:

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibcommunity.com

http://docs.tibco.com

http://www.tibco.com/services/support

https://support.tibco.com

| 1

Chapter 1 Repository Designer Tutorial

This chapter contains a tutorial that walks you through creating a repository model, adding attributes, relationships, relationship attributes, validating your model, exporting it, and importing it into MDM.

Topics

• Tutorial Overview, page 2

• Task A - Create a Project, page 3

• Task B - Create Repositories, page 8

• Task C - Create Attribute Groups and Attributes, page 9

• Task D - Create Relationships, page 12

• Task E - Define Relationship attributes, page 14

• Task F - Create a Perspective, page 15

• Task G - Validate the Repository Model, page 17

• Task H - Export the Repository Model, page 18

• Task I - Import the Repository Model into MDM, page 20

• Task J - Generate WSDL, page 22


2 | Chapter 1 Repository Designer Tutorial

Tutorial Overview

This tutorial walks you through the process of:

1. Creating a repository model that contains the following:

— Three Repositories: Customer, Account, and Address.

— A CustomerDetails Attribute Group within the Customer Repository containing FirstName, LastName, DateOfBirth, SSN, and EmailAddress as attributes.

— An AddressDetails Attribute Group within the Address Repository containing Street, City, Country, as attributes.

— An AccountDetails Attribute Group within the Account Repository containing AccountNumber, AccountHolderPhoto, AccountOpenDate, and CurrentBalance as attributes.

— A Relationship between Customer and Address with HomeAddress (Boolean), AddressSince(Date), and NoOfPersons(Integer) as Relationship Attributes.

— A Relationship between Customer and Account with AccountType (String), MinimumBalance (Amount), NoOfAccounts (Integer), and NewCustomer (Boolean) as Relationship Attributes.

2. Validating your repository model.

3. Exporting your respository model.

4. Importing the repository model into MDM.


Task A - Create a Project | 3

Task A - Create a Project

First, create a new Project to hold the Repository Model.

1. Go to File->New-> Project.The Create New MDM Developer Project wizard is displayed.

2. Select MDM Developer Project and click Next.

3. Provide a name for the Project: RepositoryTutorial. Clear the Use default location checkbox if you want to provide a different location for the project



(by default, the current workspace). Select Destination Environment as MDM. Click Next.

4. The Asset Type Selection dialog is displayed - select Repository Models and click Next.



5. The folder for the Repository Model is displayed. Click Finish.

This creates a new special folder Repository Models. Expand the project in the Project Explorer to see it.

Next, create a new Repository Model in the Repository Models folder.



1. Right click the Repository Models folder in the Project Explorer and select New - > Repository Model.

2. Accept the name and location for the repository model (.rep extension) and click Finish.



In the Project Explorer, double click RepositoryModel.rep (under the newly created Repository Tutorial project) to open up the drawing pane in the Process Editor.



Task B - Create Repositories

First, create 3 repositories.

1. Click the icon in the Palette and then click in the main drawing pane to insert the Repository. Call the Repository Customer.

2. Create a second repository Account and place it to the right of the Customer Repository.

3. Create a third repository Address and place it the below the Customer and Account Repositories.


Task C - Create Attribute Groups and Attributes | 9

Task C - Create Attribute Groups and Attributes

Next, create attribute groups for each repository and add some attributes.

Customer Repository1. Select the icon from the Palette and click in the Customer

repository (either at the top or bottom of the Repository) to add an Attribute Group. Call the group CustomerDetails.

2. Select the icon in the Palette and click within the newly created CustomerDetails attribute group. Call the attribute FirstName and keep the default string attribute type.

3. Similarly, create the following additional attributes within the CustomerDetails attribute group:

— FirstName, type String

— LastName, type String

— DateofBirth, type Date

— SSN, type String

— EmailAddress, type String

Your Customer repository should look as follows:



Setting EmailAddress as Multivalue attribute

Click the EmailAddress attribute in the repository. In the Properties window, set Multi Value to true. This indicates that this attribute can hold more than one value.

Account Repository1. Select the icon from the Palette and click in the Account

repository to add an attribute group called AccountDetails.

2. Select the icon in the Palette and click within the newly created AccountDetails attribute group. Call the attribute AccountNumber and keep the default string attribute type.

3. Create a second attribute AccountHolderPhoto.Change the attribute type to image by selecting the attribute in the drawing pane, and changing the Type to File in the Properties window, General tab.

4. Create a third attribute AccountOpenDate and change Type to Date.

5. Create a fourth attribute CurrentBalance and change Type to Decimal.


Task C - Create Attribute Groups and Attributes | 11

Your Account repository should looks as follows:

Address Repository1. Select the icon from the Palette and click in the Address

repository to add an attribute group called AddressDetails.

2. Select the icon in the Palette and click within the newly created AddressDetails attribute group. Call the attribute Street and keep the default String attribute type.

3. Similarly, create the following additional attributes within the AddressDetails attribute group:

Your Address repository should look as follows:

Attribute Name Type

City String (default)

Country String (default)



Task D - Create Relationships

Next, create relationships between the Customer and Account repositories and the Customer and Address repositories.

Relationship between Customer and Account

1. Select the icon from the Palette; click on the outer edge of the Customer repository and drag to the outer end of the Account repository to define a relationship.

2. Provide a forward and reverse relationship name. By default, the focus is on the forward relationship (indicated by a forward arrow icon).

a. Enter CustomerToAccount as forward relationship name.

b. Click on the reverse arrow icon and provide AccountToCustomer as the reverse relationship name.

Relationship between Customer and Address

1. Select the icon from the Palette; click on the outer edge of the Customer repository and drag to the outer end of the Address repository to define a relationship.

When attempting to draw a relationship from a source repository, ensure that you see an arrow as indicated below.

Once you correctly touch the edge of a repository, you will see the arrow icon. When dragging to define the relationship, the cursor changes to a hand icon; release the cursor only when you touch the outer edge of the target repository and once you see the cursor change to an arrow again.

The multiplicity icons on the relationships (*) do not influence the model since MDM does not support it, they are simply indicative of multiplicity on the main model diagram.


Task D - Create Relationships | 13

2. Provide CustomerToAddress as forward relationship name and AddressToCustomer as reverse relationship name.



Task E - Define Relationship attributes

Next, define some relationship attributes for the defined relationships. You first need to create Relationship Attribute Groups to hold the attributes and then add the actual attributes.

Relationship attributes for CustomerToAccount

1. Select the icon from the Palette and click in the canvas above or close to the CustomerToAccount relationship to place the attribute group.

2. Select the icon from the Palette and click in the relationship attribute group.

3. Call the new attribute AccountType and keep the default String type.

4. Create a second relationship attribute MinimumBalance. Double click the attribute and change the Type to Amount in the Properties window.

5. Create a third relationship attribute NoOfAccounts of type Integer.

6. Create a fourth relationship attribute NewCustomer of type Boolean.

Relationship attributes for CustomerToAddress

1. Select the Relationship Attribute Group icon from the Palette and click in the canvas close to the CustomerToAddress Relationship to place the relationship attribute group.

2. Add the following relationship attributes:

— HomeAddress, type Boolean

— AddressSince, type Date

— NoOfPersons, type Integer

Connecting the Relationship attribute groups to the relationships

Click the icon in the Palette. Click the outer border of the Relationship Attribute Group (for the CustomerToAccount relationship) and drag to connect the relationship. This connects the relationship attribute group to the relationship.

Repeat the same process to connect the relationship attribute group created for CustomerToAddress.


Task F - Create a Perspective | 15

Task F - Create a Perspective

Next, create a perspective to define the subset of the relationships of the root repository.

Perspective for subset of relationship

1. Right click on Customer Repository and select New--> Perspective Creation

2. The Perspective Generator Wizard is displayed. Enter the Perspective name in the Name field and enter the descripion in the Description field and click Next.

3. Select the relationships which you want to view in the perspective and click Finish. The Perspective Editor with the newly defined perspective is displayed.



4. You can also view the perspective editor by clicking on the perspective link in the Properties section of the Repository model.


Task G - Validate the Repository Model | 17

Task G - Validate the Repository Model

At this point, if you have followed all the steps in the tutorial so far, there should be no validation errors.

If you omitted to perform any of the steps, it may result in a validation error. For instance, if you create a relationship attribute group but leave it empty (without adding any relationship attributes). Or if you fail to connect a relationship attribute group to a relationship. Or if you forget to provide a reverse relationship name for a relationship.

Check the Problems tab for any errors.



Task H - Export the Repository Model

Next, export your repository model.

The Export Wizard is used to export the graphically designed repository to MDM metadata format (.xml file).

1. Select the RepositoryTutorial Project in the Project Explorer and click File->Export or right click the project and select Export.

2. Select MDM Metadata Format under MDM Repository Designer. Click Next.

3. Select the RepositoryModel.rep file for export by selecting the checkbox. The default location to which the file will get exported is displayed in the


Task H - Export the Repository Model | 19

Destination section under Project (/Exports/MDMExportFolder). You can change the path if required. Click Finish.

In the Project Explorer, you will see a new folder Exports created which contains the XML file generated.



Task I - Import the Repository Model into MDM

You can now import the repository meta data into MDM.

1. Start the MDM application

2. Go to System Operations, Import Meta Data.

3. Browse to select the RepositoryModel.xml file, exported from the Repository Designer.

4. You will see details of the file you selected for upload. You can click the Check Progress link to see the status.

5. You can check the status of the process from the Event Log. If the Event shows as complete without any error, it means the repository model was successfully imported in MDM.

6. Go to the Repositories page to check if your repositories have got added. You should see the Customer, Account, and Address repositories here along with the custom attributes, relationships, and relationship attributes defined in the Repository Designer.

If you have already have repositories with same name, the metadata import will overwrite the existing metadata.


Task I - Import the Repository Model into MDM | 21

You can now continue refining your repository, adding records and attributes, and so on.



Task J - Generate WSDL

You can now Generate WSDL for Person Account.

1. Import repository designer sample into your current workspace. Select Help->Welcome. Click on the samples icon.

2. From Solution Designer->Available sample project, click on Repository Model sample.

3. Follow the wizard to import the Person->Account->Email->Phone->Address repository structure. Switch to workbench.

4. Using the WSDL Generator Wizard, generate wsdl for Person repository. Follow the wizard to complete the webservice project creation.

5. Go to File -> New -> and click Other.


Task J - Generate WSDL | 23

6. Select WSDL Generator from the WSDL Generator tree node and click Next. The New Project screen is displayed

.

7. Enter the appropriate project name in the Project Name field. By default, the project name is <repository name>_webservice.



8. Click Next. The New Project screen is displayed..

9. Select the relationship depth, by default 3 level of relationship is supported.

10. Click Next. The Generation Options screen is displayed..


Task J - Generate WSDL | 25

11. Enter the appropriate package name in Package Name field. By default, a package name is provided. The package name convention is com.tibco.mdm.integration.webservice.<repository

name>_webservice.You can modify the package name.

12. Click Finish. The Person_webservice project is created in MDM Studio.

13. From the project explorer, person_webservice\build\lib folder, copy personservice.aar file to your MQ_HOME\dynsservices\services folder.

14. Using network deployment, deploy the whole repository and relationship structure from the Repository Model Samples project onto your MDM Server.



15. In SOAP UI, create a new project and import < your workspace name>\person_webservice\services\PersonService.wsdl as the initial wsdl.

16. The will see PersonHttpBinding with addPerson, deletePerson, findPerson and updatePerson services along with their sample request skeletons in your project.

17. Change the endpoint URL to point to your MDM Server instance.

18. Change the enterprise credentials inside each request before execution through SOAP UI.

The optional <context> section can be used as follows in case of Record Add request:<ns:Context><ns:Validation>false</ns:Validation><ns:Process>true</ns:Process><ns:SystemAttributeReturn>true</ns:SystemAttributeReturn><!-Optional: The following is used when File type attribute values have to be sent as a part of the request.-><ns:ReturnFileAsAttachment>false</ns:ReturnFileAsAttachment></ns:Context>.

Date post:	18-Feb-2022
Category:	Documents
Upload:	others
View:	3 times
Download:	0 times

TIBCO MDM Studio Repository Designer Tutorial - TIBCO Product

Documents