TIBCO MDM Studio · 2014-11-14 · TIBCO MDM Studio Rulebase Designer Tutorial |3 Preface The TIBCO...

Two-Second Adv

TIBCO® MDM Studio

Rulebase Designer TutorialSoftware Release 4.0July 2014

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-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.TIBCO Software Inc. Confidential Information

| 1

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

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

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5TIBCO MDM Studio Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Other TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9How to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9How to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9How to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Chapter 1 Rulebase Designer Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Tutorial Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Task A - Create a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Task B - Define Repository Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Task C - Create Rulebase Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Task D - Declare Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Task E - Add Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Constraint for Gender Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Constraint to generate Customer ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Constraint for Mandatory Attributes Check. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Constraint to get current User Role . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Constraint to hide MaidenName for male customers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Constraint to generate PreferredName. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Constraint to ensure date of birth is less than current date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Constraints to create a dependent drop-down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Task F - Deploy the Rulebase Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

TIBCO MDM Studio Rulebase Designer Tutorial

2 | Contents


| 3

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 four components: the Process Designer, the Repository Designer, the he Rulebase Designer, and the UI Builder.

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.

The MDM UI Builder is a new tool developed to have a cleaner, simpler, more flexible UI in MDM. MDM UI Builder allows you to quickly, easily, & uniformly develop custom UIs by using simple drag & drop methods.

Topics

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

• Related Documentation, page 5

• Typographical Conventions, page 7

• Connecting with TIBCO Resources, page 9


4 |

Changes from the Previous Release of this Guide

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

Context Variables

The rulebase designer is enhanced to supports three new Context variables CONTEXT_RELATIONSHIP.TYPE, CONTEXT_RELATIONSHIP.REVERSENAME, CONTEXT_RELATIONSHIP.ISFORWARD. For more information, on context variables, refer to TIBCO MDM Studio Rulebase Designer User's Guide.


| 5

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 UI Builder User’s Guide.

UI Builder User’s Guide

UI Builder Tutorial

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.


6 |

• TIBCO MDM Studio UI Builder Tutorial.

• TIBCO MDM Studio Release Notes.

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.


| 7

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


8 |

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


| 9

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

10 |


| 13

Chapter 1 Rulebase Designer Tutorial

This chapter contains a tutorial that walks you through creating a rulebase model, validating your model, and deploying it to MDM.

Topics

• Tutorial Overview, page 14

• Task A - Create a Project, page 15

• Task B - Define Repository Data, page 19

• Task C - Create Rulebase Model, page 20

• Task D - Declare Variables, page 23

• Task E - Add Constraints, page 24

• Task F - Deploy the Rulebase Model, page 34


14 | Chapter 1 Rulebase Designer Tutorial

Tutorial Overview

This tutorial walks you through the process of creating a rulebase model that contains the following:

1. A Repository Model that serves as the base data for the Rulebase. The Repository contains the following:

— A Customer repository that the rulebase will be built on. This Repository contains the following attributes - FirstName, LastName, DateOfBirth, Age, PreferredName, Gender, MaidenName.

— A second repository Address (which contains Address data) which is related to the Customer repository by a CustToAdd relationship and AddressType relationship attribute.

— A third repository Organization (which contains Organization data) which is related to the Customer repository by a CustToOrg relationship and CustomerType and CustomerSince relationship attributes.

2. A Rulebase based on the Customer repository which contains the following:

— Checks if the current user is an Admin User.

— Generates a unique ID for each customer record.

— Performs a mandatory attributes check for FirstName and LastName.

— Hides the MaidenName field if gender is Male.

— Connects the FirstName and LastName fields (minus the MaidenName field) to create PreferredName.


Task A - Create a Project | 15

Task A - Create a Project

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

1. Go to File > New > Project and click Next.The Create New MDM Developer Project wizard is displayed.

2. Select MDM Developer Project and click Next.

3. Provide a name for the Project, for example, RulebaseTutorial. 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.


Task A - Create a Project | 17

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



5. The folder for the Repository Models and Rulebase Models is displayed. Click Finish.


Task B - Define Repository Data | 19

Task B - Define Repository Data

In the Project Explorer, create a new repository model under the Repository Models folder (by right clicking the Repository Models folder, selecting New > Repository Model, and following the wizard). Call the file Tutorial.rep.

Double click the newly created .rep file and create the following repository and relationship structure.

This will form the base data on which a rulebase will be created.



Task C - Create Rulebase Model

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

2. Accept the default name for the rulebase model (default.rul) and location or enter a new location and name. Click Next.


Task C - Create Rulebase Model | 21

3. Select the Rulebase type as Validation. Click Next.

4. Associate repository data with your rulebase.

— Select RepositoryModel as Tutorial.rep

— Select Repository as Customer.

— Select Relationship as None.

5. Click Finish.

6. After creating a new rulebase model, the Editor displays the basic rulebase diagram. The associated repository is displayed at the top (Customer , in this case).



Use the palette to start building the rulebase by declaring variables and adding constraints.


Task D - Declare Variables | 23

Task D - Declare Variables

First, declare a Data-type variable to check for the current user role.

1. In the Palette, click the Data-type icon in the Declare Variables section and then click in the Declare Variables compartment to add the variable.

2. Provide the following details for the variable in the Properties Window:

— Name as IS_ADMIN

— Usage as Local

— Datatype as String



Task E - Add Constraints

In this section, the following constraints are added:

• Constraint for Gender Selection

• Constraint to generate Customer ID

• Constraint for Mandatory Attributes Check

• Constraint to get current User Role

• Constraint to hide MaidenName for male customers

• Constraint to generate PreferredName

• Constraint to ensure date of birth is less than current date

• Constraints to create a dependent drop-down

Constraint for Gender Selection1. In the Palette, click the Constraint icon in the Declare Constraint section and

then click in the Declare Constraints compartment to add the constraint.


Task E - Add Constraints | 25

2. Provide the following details for the constraint in the Properties window:

— Name as SelectGender.

— Description as Select the Gender.

— In the Use for variables section, select the Gender checkbox.

3. Double click the SelectGender constraint to open up the Expression Editor.

4. From the Actions Palette, click the Select Action icon and then click in the Actions compartment to insert it.

5. Provide the following properties:

— Name as ActionName

— No value as Default

— Select Type as Enum

— In the Attributes section, click the Add icon to add two literals: Male and Female.

Constraint to generate Customer ID1. In the Palette, click the Constraint icon in the Declare Constraint section and





— Name as GenerateCustomerID

— Description as Auto generate ID for Customer.

3. Double click the GenerateCustomerID constraint to open up the Expression Editor.

4. From the Actions Palette, click the Assign Action icon and then click in the Actions compartment to insert it.



— Select PRODUCTID from the Assign dropdown.

— In the Expression Editor, enter the following:sequence('CUSTOMERID_SEQUENCE_1')

Constraint for Mandatory Attributes Check1. In the Palette, click the Constraint icon in the Declare Constraint section and





— Name as ReqManadatoryAttributesForCustomer.

— Description as The following attributes are mandatory for a Customer.

3. Double click the ReqManadatoryAttributesForCustomer constraint to open up the Expression Editor.

4. From the Actions Palette, click the Check Action icon and then click in the Actions compartment to insert it.




— Explanation as FirstName and LastName are mandatory fields.

— Expression as defined(useforvars)

Constraint to get current User Role1. In the Palette, click the Constraint icon in the Declare Constraint section and





— Name as GetRoleForUser.

— Description as Gets user role: Admin.

3. Double click the GetRoleForUser constraint to open up the Expression Editor.



— Name as Assign

— Select IS_ADMIN from the Assign dropdown

— Enter the following in the expression editor:in(’Admin’,SESSION.USER_ROLES)

Constraint to hide MaidenName for male customers1. In the Palette, click the Constraint icon in the Declare Constraint section and





— Name as HideMaidenName.

— Description as Hide MaidenName Fields for Male Customers.

3. Double click the HideMaidenName constraint to open up the Expression Editor.

4. From the Condition Expression Palette, click the Expression icon and then click in the Condition compartment to insert it.

5. In the Expression Properties, provide Gender = Male

6. From the Actions Palette, click the Access Action icon and then click in the Actions compartment to insert it.


— Name as Access

— Mode as Hide

— Applies To as Use for Vars



Constraint to generate PreferredName1. In the Palette, click the Constraint icon in the Declare Constraint section and



— Name as AssignPreferredName.

— Description as Build Preferred name if not entered.

3. Double click the AssignPreferredName constraint to open up the Expression Editor.

4. From the Condition Expression Palette, click the Expression icon and then click in the Condition compartment to insert it.

5. In the Expression Properties, provide undefined(PreferredName)




— Select PreferredName from the Assign dropdown.

— In the Expression Editor, enter the following:concat(FirstName, '_', LastName)

Constraint to ensure date of birth is less than current date1. In the Palette, click the Constraint icon in the Declare Constraint section and



— Name as DOBCheck.

— Description as Check for date of birth.

3. Double click the DOBCheck constraint to open up the Expression Editor.

4. From the Actions Palette, click the Assign Action icon and then click in the Actions compartment to insert it. Provide the following properties:


— Select DateofBirth from the Assign dropdown.

— In the Expression Editor, enter the following:SESSION.DATE



5. From the Actions Palette, click the Check Action icon and then click in the Actions compartment to insert it. Provide the following properties:

— Explanation as DateofBirth check (not greater than current date)

— Expressions as DateOfBirth < CurrentDate

Constraints to create a dependent drop-down

Constraint to assign values to Country

1. In the Palette, click the Constraint icon in the Declare Constraint section and then click in the Declare Constraints compartment to add the constraint.

— Name as AssigningValuesToCountry.

— Description as Assigning Values to Country.

2. Double click the AssigningValuesToCountry constraint to open up the Expression Editor.

3. From the Actions Palette, click the Select Action icon and then click in the Actions compartment to insert it. Provide the following properties:

— No value as No.


— Column as 1

— Select the Header checkbox

— In the Attributes section, click the Add icon to add the following attributes: Country Name, US, UK, India.

Constraint to populate US States

1. In the Palette, click the Constraint icon in the Declare Constraint section and then click in the Declare Constraints compartment to add the constraint.

— Name as USStates.

— Description as Dependent dropdown for state if country US.

This is to create a dependent drop-down listing the States depending on the Country. For example, if country is selected as US, the States drop-down is populated with US States.

Three constraints are used to achieve this.



2. Double click the USStates constraint to open up the Expression Editor.

3. From the Actions Palette, click the Select Action icon and then click in the Actions compartment to insert it. Provide the following properties:

— No value as No.


— Column as 1

— Select the Header checkbox

— In the Attributes section, click the Add icon to add the following attributes: State, California, New Jersey, Texas.

Only 3 states are added as an example. The whole list of states can be populated by providing the names as attributes.



Task F - Deploy the Rulebase Model

The created Rulebase model can be directly deployed to MDM. For deployment steps, refer the Deployment chapter in the TIBCO MDM Studio Rulebase Designer User’s Guide.


Date post:	11-Mar-2020
Category:	Documents
Upload:	others
View:	12 times
Download:	0 times

TIBCO MDM Studio · 2014-11-14 · TIBCO MDM Studio Rulebase Designer Tutorial |3 Preface The TIBCO...

Documents