TIBCO?? Cloud MDM - TIBCO Product Documentation€¦ · TIBCO® Cloud MDM is a cloud service to...

Two-Second Adv

TIBCO® Cloud MDM

Provisioning and Configuration Guide

Software Release 2.0.0February 2016

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 THE LICENSE FILE) 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, are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation 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 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 © 1999-2016 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

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

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

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiTIBCO Cloud MDM Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiOther TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Access TIBCO Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

The TIBCO Cloud MDM Console Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

The TIBCO Cloud MDM Console Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Chapter 2 Working with TIBCO Cloud MDM Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

Creating an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Password Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

De-Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Chapter 3 Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Configurator GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Accessing Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Cluster and Configuration Outlines. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Using Configuration Outline Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Other Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Adding New Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Searching Configuration Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Working with Hot Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Applicability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Properties that Require Reinitialization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

TIBCO Cloud MDM Provisioning and Configuration Guide

iv | Contents

Properties that are Auto Refreshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Invoking Hot Deployment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Controlling Major Flags through Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Timing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Chapter 4 Working with Data Model Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Data Model Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Importing the Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Prerequisite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Modifying the Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Downloading Data Model from Salesforce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61


| v

Preface

TIBCO® Cloud MDM is a cloud service to manage master data of your organization by providing a framework for governance, rules, and processes.

The TIBCO Cloud MDM Console is used to create, monitor, and control all the environments or instances available as part of a subscription.

Topics

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

• Related Documentation, page vii

• Typographical Conventions, page ix

• Connecting with TIBCO Resources, page xi


vi | Changes from the Previous Release of This Guide

Changes from the Previous Release of This Guide

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

Password Management

TIBCO MDM Cloud is enhanced to support the authentication implementation. The new password management supports the password strength, password expiration, and audit trail. For more information, refer to Password Management on page 14.


Preface | vii

Related Documentation

This section lists documentation resources you may find useful.

TIBCO Cloud MDM DocumentationThe following documents form the TIBCO Cloud MDM documentation set:

• TIBCO Cloud MDM Provisioning and Configuration Guide: Read this manual to learn the TIBCO Cloud MDM Console features. This manual guides you to use the console and its functionality as well as all the screens.

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

• TIBCO MDM Release Notes: Read the release notes for a list of new and changed features. This document also contains lists of known and closed issues for this release.

• TIBCO MDM User’s Guide: Read this manual to learn the TIBCO MDM features. This manuals guides you to use the product. It describes the functionality as well as all the screens.

• TIBCO MDM System Administration: Read this manual to learn the features relevant to the system administrator.

• TIBCO MDM Customization: Read this manual to understand how the application can be customized to your enterprise needs.

• TIBCO MDM Workflow Reference: Read this manual as a reference for the automation of business processes.

— JAVA API Reference: This Help includes a list of workflows that are used in TIBCO MDM.

• TIBCO MDM Web Services: Read this manual as a reference for using web services.

• TIBCO MDM Studio Installation Guide: Read this manual for instructions on installation of TIBCO MDM Studio.

• TIBCO MDM Studio Process Designer User’s Guide: Read this guide as a reference for designing workflows using the TIBCO MDM Process Designer graphical user interface.


viii | Related Documentation

• TIBCO MDM Studio Process Designer Tutorial: Read this guide to learn how to design the workflows using the TIBCO MDM Process Designer graphical user interface.

• TIBCO MDM Studio Repository Designer User’s Guide: Read this guide as a reference for designing repositories using the TIBCO MDM Repository Designer graphical user interface.

• TIBCO MDM Studio Repository Designer Tutorial: Read this guide to learn how to design repositories using the TIBCO MDM Repository Designer graphical user interface.

• TIBCO MDM Studio Rulebase Designer User’s Guide: Read this guide to learn how to design rulebases using the TIBCO MDM Rulebase Designer graphical user interface.

• TIBCO MDM Studio Rulebase Designer Tutorial: Read this guide to learn how to design rulebases using the TIBCO MDM Rulebase Designer graphical user interface.

• TIBCO Enterprise Message Service™: This software helps the application to send and receive messages using the Java Message Service (JMS) protocol. It also integrates with TIBCO Rendezvous and TIBCO SmartSockets™ messaging products.

• TIBCO BusinessWorks™: This is a scalable, extensible, and easy-to-use integration platform that helps you to develop and test integration projects. It includes a graphical user interface (GUI) for defining business processes and an engine that executes the process.

• TIBCO BusinessConnect™: This software helps your company to send and receive XML or non-XML business documents over the Internet. Based on a mutually agreed process flow and common document format, you and your trading partners can conduct secure and verifiable business transactions online.


Preface | ix

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

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 MDM System Administration.

• 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

Key combinations

Key names 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.


x | Typographical Conventions

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


Preface | xi

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 DocumentationDocumentation for this and other TIBCO products is available on the TIBCO Documentation site:

https://docs.tibco.com

Documentation on the TIBCO Documentation site is updated more frequently than any documentation that might be included with the product. To ensure that you are accessing the latest available help topics, please visit us at https://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.tibco.com/services/support

https://support.tibco.com

http://www.tibcommunity.com



xii | Connecting with TIBCO Resources


| 1

Chapter 1 Introduction

This chapter is an overview of the TIBCO Cloud MDM Console application.This chapter also describes the interface of the application.

Topics

• The TIBCO Cloud MDM Console Overview, page 2

• The TIBCO Cloud MDM Console Interface, page 3


2 | Chapter 1 Introduction

The TIBCO Cloud MDM Console Overview

TIBCO Cloud MDM is a cloud service for Master Data Management (MDM). TIBCO Cloud MDM is available through TIBCO Marketplace at http://marketplace.cloud.tibco.com. To use TIBCO Cloud MDM, you require a current subscription. The various subscription types are described at TIBCO Marketplace.

TIBCO Cloud MDM Console is used to create, monitor, and control all the environments or instances available as part of a subscription. The TIBCO Cloud MDM Console uses the credentials from TIBCO Marketplace for authentication. A current subscription to TIBCO Cloud MDM is required to access the TIBCO Cloud MDM Console.


http://marketplace.cloud.tibco.com

The TIBCO Cloud MDM Console Interface | 3

The TIBCO Cloud MDM Console Interface

When you log in for the first time, the TIBCO Cloud MDM Console displays the Help, Visit Silver Marketplace, and Sign Out menu on the upper right corner. In addition, TIBCO Cloud MDM Console displays the link for creating a new instance. For more information on TIBCO Cloud MDM Console Interface, refer to, Dashboard, on page 11.

Figure 1 TIBCO Cloud MDM Console Interface

• To view TIBCO Cloud MDM documentation, click Help; you are then directed to http://docs.tibco.com/products/tibco-cloud-mdm.

• On expiry of current subscription, you cannot login to TIBCO MDM and TIBCO MDM Configurator. However, you can login to TIBCO Cloud MDM Console. Renew your subscription at TIBCO Marketplace. Click Visit Silver Marketplace to renew your subscription. You are then directed to http://marketplace.cloud.tibco.com.

• To log out of TIBCO Cloud MDM Console, click Sign Out.


http://marketplace.cloud.tibco.com

https://docs.tibco.com/products/tibco-cloud-mdm

4 | Chapter 1 Introduction


| 5

Chapter 2 Working with TIBCO Cloud MDM Console

This chapter introduces you to working with TIBCO Cloud MDM Console and describes how to create instances, provision, and de-provision them.

Topics

• Creating an Instance, page 6

• Dashboard, page 11

• Password Management, page 14

• De-Provisioning, page 16


6 | Chapter 2 Working with TIBCO Cloud MDM Console

Creating an Instance

The TIBCO Cloud MDM Console provides a wizard to provision a TIBCO MDM instance. After you log into TIBCO Marketplace and select TIBCO Cloud MDM, click Launch. The MDM Console wizard is displayed.

Based on your subscription type and the licenses associated with the subscription type, you can create one or more instances. On consuming all the licenses available for a particular subscription, the Create New Instance button on TIBCO Cloud MDM Console is disabled.

To create an instance, do the following:

1. Click the Create New Instance link.

Figure 2 Create new Instance page

2. The New Environment Wizard: Step 1 of 3 is displayed. Your access to the MDM Console depends on your subscription type.

Figure 3 Create New Environment Step 1


Creating an Instance | 7

3. Select the Medium instance type and click Next.


4. In the What do you want to call this environment? field, specify the relevant environment name. In case of multiple instances provide unique environment name.

5. Select the data model based on which you want to create the TIBCO MDM instance. The available options are:

— Insurance- Select Insurance if you want to create a insurance TIBCO MDM instance based on the Insurance model template.

— None - Select None if you want to create your own data model. To create your own data model, you must download the TIBCO MDM Studio designer and create the data model. The TIBCO MDM Studio download link is available on the Dashboard. For more information on TIBCO MDM Studio, see the TIBCO MDM Studio documentation on http://docs.tibco.com.

— Party- Select Party if you want to create a customer TIBCO MDM instance based on the Party model template.

6. Click the Details link corresponding to the party data model to know more details about the data model. A PDF file with the data model details is displayed.

7. Click the Next button. The step three of the new environment wizard is displayed.


http://docs.tibco.com



Table 2 New Instance Parameters

Field Descriptions

Enter company name: Specify the company name in this field. The company name is the MDM Enterprise name. The company names can be same for multiple instance. However, the environment name must be unique.

Password for Super User: Specify the super user’s password in this field. Use this password to login to the configurator.

Note: The password must be according to the new password policy.

Confirm Password for Super User:

Specify the super user’s password again to confirm.

User name for MDM Admin: Specify the MDM admin user name in this field.

Password for MDM Admin: Specify the MDM admin password as per the new password management rule in this field.

Confirm Password for MDM Admin:

Specify the MDM admin password again to confirm.


Creating an Instance | 9

8. Click Launch. The provisioning progress bar is displayed.

Figure 6 Provisioning the Environment

9. The provisioning complete screen is displayed.

Figure 7 Provisioning Complete

10. Click Proceed to MDM Console. The MDM Console dashboard is displayed.

Email Id for MDM Admin Specify the email ID for the Instance ID. On clicking Message to Admin on the MDM Console, email is sent to the admin using this email ID.

Table 2 New Instance Parameters

Field Descriptions



Figure 8 MDM Console Dashboard with New Instance


Dashboard | 11

Dashboard

The TIBCO Cloud MDM Console dashboard provides support in keeping track of all the instances available to a user. The TIBCO Cloud MDM Console displays the instances and all the components running on the instances.

• The two components of the TIBCO Cloud MDM Console are the following:

— MDM Application

— MDM Configurator

Figure 9 MDM Console Dashboard

• The MDM component displays the URL of the MDM application. You can login to the MDM application using the MDM Enterprise name, Super User or Admin username, and Password provided during provisioning. For more information on TIBCO MDM documentation, refer to http://docs.tibco.com.

• The MDM Configurator displays the URL of the MDM configurator. You can click the URL and login using the default login credentials. For more information on Configurator refer to, Chapter 3 on page 19.




• To search for a particular instance when you have many instances running, type the instance name in the search field, and click Search.

• To sort the instance, specify the following options:

— All Instance - You can sort by specifying all the instances.

— Date Created - You can sort based on the creation date of the instances.

— A-Z - You can sort based on the ascending order of the instances.

• To create new instance, click Create New Instance.

• To download TIBCO MDM Studio, click Download MDM Studio.

• To view TIBCO Cloud MDM documentation, click Help; you are directed to http://docs.tibco.com.

• To convey a message to the MDM administrator, click Message to Admin. A text box is displayed. Enter the message in the text box and click Send.

• To de-provision the instance, click Terminate. The Terminate Instance wizard is displayed. For more information on de-provisioning refer to, De-Provisioning, on page 16.

• You can reset the MDM superuser password from the TIBCO MDM Console, to reset the password click .

• The confirmation screen with the email id to which the reset password link is sent is displayed.

Figure 10 Password Reset with Email ID

• Click Continue. The confirmation message is displayed.



Dashboard | 13

Figure 11 Password Reset with email sent message

• Click Close. An email with the link to reset the password is sent to the email id, click the link provided in the email. The TIBCO MDM Reset Password page is displayed.

Figure 12 TIBCO MDM Reset Password screen

• Enter the new super user password in the appropriate fields and click Reset.



Password Management

The Cloud MDM is enhanced to support authentication implementation. In today’s world the danger of exposing vital company data to the world is significant, the factor determining the data exposure is due to users choosing weak passwords. To add to that the administrator of the application do not have control on such weak password management.

The enhancement is introduced to provide an internet acceptable authentication solution, which can support authentication policies, is self-serviceable, auditable and secure.

The authentication implementation supports the following requirements:

Password Strength

The password strength values are not visible to the end user. However, on request, the cloud operations team can configure it for the end user. The passwords specified is subject to the rules as follows:

• Password Length

• Password Character Classes

• Password Repeated Characters

Based on the rules, validation are invoked while creating a user, modifying a user, changing the password from the UI or webservices. The validations are as follows:

— Password is case sensitive.

— Must be at least eight characters long.

— Must be no more than 30 characters long.

— Must include at least one letter.

— Must include at least one number.

— Must have at least one symbol (non letter or number) character.

— Must not repeat any character sequentially more than four times.

— Must have at least one lowercase letter.

— Must have at least one uppercase letter.

— Must not include a common word or commonly used sequence of characters."


Dashboard | 15

Password Expiration

The administrator can define the password expiration time for each user. The password expiration period is specified in seconds. The default value is 15552000 seconds which is equal to 6 months. The password expiration value is configured using the com.tibco.mdm.authentication.cloud.password.expiration property in configvalues.xml. By default, password expiration is enabled.

User Audit Trail

The events related to the authentication and user management are stored in the log file authentication.log under MQ_LOG directory. The log message format is as follows:

timestamp className eventType resultCode message

For example, [2015-08-31 08:11:48,031] "Login request" 403 "Cannot authenticate credentials with user name 'p', domain 'MartQuestNet'."



De-Provisioning

If your TIBCO Marketplace subscription expires, the TIBCO Cloud MDM Console does not de-provision your instance. However, you can manually de-provision the instance.

1. To de-provision the instance, click Terminate.

Figure 13 MDM Console with Terminate

2. The Terminating Instance wizard is displayed.


De-Provisioning | 17

Figure 14 Terminating Instance

3. Click Next to terminate the instance. Step one of the de-provisioning wizard is displayed with a backup option for handling data.

Figure 15 De-provisioning Step 1

4. Select the Send the data to me through email option. The operations team contacts you with your data backup. If you select Don’t keep data, then the backup is not saved.



Figure 16 De-provisioning step 2 with success

5. Click Proceed to MDM Console. The MDM Dashboard is displayed.

Figure 17 MDM Console main screen


| 19

Chapter 3 Configurator

This chapter explains how to configure TIBCO MDM using Configurator, a web-based configuration utility.

Topics

• Overview, page 20

• Getting Started, page 22

• Adding New Property, page 29

• Searching Configuration Values, page 30

• Working with Hot Deployment, page 31

• Controlling Major Flags through Configurator, page 35


20 | Chapter 3 Configurator

Overview

Configurator is a web-based configuration tool that configures TIBCO MDM. Previously, configuring TIBCO MDM involved command-line access and the use of a text editor. Configurator provides a centralized way to configure and validate TIBCO MDM. In addition, it is easy to use, with an intuitive user interface.

The configuration is divided into various categories, such as Database, Email, and so on. The configuration has metadata that is used to display and describe the values, allowing for validation of the values before they are saved.

Configurator GUI

Configurator provides a user interface to centralize the configuration information stored previously in the following configuration files on each member of the cluster: bus.prop, queue.prop, MqLog.cnf, and MqProperties.confg.

The properties set using Configurator are stored in $MQ_HOME/config/ConfigValues.xml. This XML file contains descriptions of all important configuration values and classifies them into appropriate logical groups.

To convert existing properties defined in the MqProperties.confg, MqLog.cnf, queue.prop, and bus.prop files to the new XML format, use the xmlPropMergeUtil utility or Installer. For more information on using this utility, refer to TIBCO MDM Installation and Configuration Guide.

Configurator is supported on the following versions of these browsers:

• Internet Explorer 9 and 10

• Google Chrome 33

• Mozilla FireFox 24

Accessing Configurator

To access Configurator, click the configurator URL into your browser. For example,

http://mdm-staging.cloud.tibco.com/johntibco.com/mdm-70/manage/config/index.html#/login

The configurator URL is displayed after the provisioning in the MDM Console.


Overview | 21

Logging in to Configurator

After the browser connects, the following default User Login screen is displayed:

1. Enter the login credentials in the User Name and Password fields. The default user name is "tadmin" and password is the password provided in provisioning wizard details.

2. Click Login. The Configurator main screen is displayed.

Logging out of Configurator

Before logging out, save the configurations that you have already updated.

1. Hover the mouse over the Hi,username link in the upper right part of the Configurator page.

2. Click the Logout option. A message is displayed to confirm whether you want to log out from Configurator.

3. Click Logout if you want to log out of the application.

When you are successfully logged out, the main User Login window is displayed.



Getting Started

After successful login, the Configurator with the basic database configuration is displayed. The initial database configuration is the minimal configuration required to set up and start TIBCO MDM with defaults.

After you log in to Configurator, the following screen is displayed:

On the left, the Cluster Outline and Configuration Outline panels are displayed. When you click an option listed in these panels, corresponding properties, values, and descriptions are displayed on the right side.

Property

The Configuration property name is displayed in this column.

Value

Values corresponding to various properties are displayed in this column. You can modify the values by clicking a specific value.

Description

Description of the each property is displayed in this column. You can point to a description to view the complete details.

The subsequent sections describe these panels.


Getting Started | 23

Cluster and Configuration Outlines

Properties that are at the cluster level are applicable to all the members in the cluster. For example, Database, Email, Software Edition, and so on. Instance-level properties are applicable to a specific node or member. For example, JNDI properties for an Application server.

Cluster Outline

Cluster management is built into the user interface. You can view the configuration for a whole cluster or a cluster member. In the Cluster Outline section, the name of the Cluster is displayed, and cluster members are displayed after it.

Modifying the Cluster

A cluster view facilitates navigation between instances (nodes) and cluster-wide configuration. You can change the cluster configuration.

Consider the scenario, where you have an application called Item Master - Production, and you need two cluster members under it, for example, host01 and host02.

1. Select the Cluster. A square icon is displayed next to it.

2. Click the icon and then click Edit to edit the cluster details. The Edit Cluster details window is displayed.

When an TIBCO MDM instance is started, the NODE_ID environment variable must be defined, and should be the name of the members defined in the Cluster Outline section.



3. In the Name field, type the new configuration name, that is, Item Master - Production. By default, the InitialConfig configuration name is displayed.

4. In the Description field, type the description.

5. Click Save. The modified cluster name is displayed.

Using Cluster Members Options

Similar to the cluster, after you select the Cluster member, a square icon is displayed next to each cluster member. Click the icon to edit, clone, or delete the cluster members.

Modifying Cluster Member

1. Select the cluster member that you want to modify.

2. Click the square icon next to the selected cluster member.

3. Click the Edit option. The Edit Cluster details window is displayed.

4. In the Name field, type the new name of the cluster.

5. In the Description field, type the description for the new cluster name.

6. Click Save. The successful modification message is displayed and the updated cluster member is displayed.

Cloning Cluster Member

1. Select the cluster member that you want to clone.


3. Click the Clone option. The Clone window is displayed.

4. In the Name field, enter the clone name of the cluster.

5. Click Save. The successful clone creation message is displayed and the specified clone name is displayed after the previously selected cluster member.



Deleting Cluster Member

1. Select the cluster member that you want to delete.


3. Click the Delete option. The Confirm Delete window is displayed.

4. Click Delete to delete the selected cluster member. The successfully cluster member deletion message is displayed.

Configuration Outline

In this section, you can view Basic and Advanced configurations by selecting the appropriate option.

• Basic: represents the configuration data which is minimally needed to get a TIBCO MDM server is running.

• Advanced: includes all configuration that can be changed by a TIBCO MDM system administrator.

Basic Configuration Outline

If you select Basic, the following categories are displayed:

• Email: you can define Email related settings, such as whether email is enabled, the email server username, password, the error email receiver, the error email sender, the Inbox URL, the SMTP Host, the standard email recipient, the standard email server, and the work item email sender.

• Software Edition: After you expand the Software Edition option, the default MDM software edition is displayed. The Basic view displays the Application Usage Profile property, and the Advanced view displays the Common Menus Configuration property.

If the Display Hidden Configurations check box is selected in settings, the Advanced configuration includes all hidden categories. If it is not selected, only the Basic and Advanced configurations are displayed.



Advanced Configuration Outline

If you select Advanced, the following categories are displayed:

• Bus Setup

• Internal

• Logging

• Messaging Settings

• Miscellaneous

• Optimization

• Repository

• System Debugging

• Timing Log

• UI Settings

• UI Customization

• Workflow Settings

Using Configuration Outline Options

A square icon is displayed next to each configuration outline. Click the icon to edit, clone, or delete the configuration outline.

Modifying Configuration Outline Category

1. Select the configuration category that you want to modify.

2. Click the square icon next to the selected configuration category.



3. Click the Edit option. The Edit Configurations details window is displayed.

Modifying the Name of a configuration outline category is not possible.

4. In the Description field, type the description for the selected configuration category.

5. Click the Basic or Advanced visibility option.

6. Select Set as Hidden Configuration check box if you want hide the configuration.

7. Click Save. The successful modification message is displayed and the updated configuration is displayed.

The Cloning and deleting steps are similar to the Cluster member options.

• For cloning the configuration outline, refer to Cloning Cluster Member on page 24.

• For deleting the configuration outline, refer to Deleting Cluster Member on page 25.

Other Menu Options

Load Defaults

On clicking Load Defaults, the default values are loaded for the currently selected category.

The Delete option is not available for the categories that are already in use. For example, Database, Queue categories.



Save & Redeploy

Clicking this option saves the configuration and hot deploys the values to the TIBCO MDM server if it is currently running. For more details on Hot Configuration, refer Working with Hot Deployment, page 31.

Save

Clicking this option saves the configuration.


Adding New Property | 29

Adding New Property

You can add a new property at the Cluster and Server levels. The Add New Property option is available in the Configuration and setup for Cluster Name - Basic or Advanced option name or Configuration and setup for Server Name - Basic or Advanced option name.

1. Click Add New Property. The Add New Property window is displayed. Type details for the new property in the following fields:

2. Click Finish. The newly added configuration value is internally added to the ConfigValues.xml file under one of the cluster-level or server-level categories.

Table 3 Add New Property Fields

Field Name Description

Configuration Value Name Specify the name of a configuration property. For example, Timing Log File Name.

Internal Name Specify the name of a configuration property. For example, log4j.appender.timinglogdefault.File.

Version Select the version number.

Visibility Select the Configuration Outline option. The options are Basic or Advanced.

Read only Select the check box for the read-only property.

Description Specify the description of the property.

Value Type Select the value type. The valid values are String, Numeric, Boolean, Enumeration, Password, and List. For more information on the value types, refer to TIBCO MDM User’s Guide.

Current Value Specify the current value.

Default Value Specify the default value. You can set the default value to the current value.



Searching Configuration Values

Using the search facility, you can quickly locate the configuration values by name. The Search Property field is located in the upper-right corner of the window. You can type the search term in the field and press Enter. The search term may be the property name, propname, value, or description.

Search results are returned in a separate window where the Property, Location, and Value columns are displayed for the specified property.

Click any link to reach the value and the appropriate category.


Working with Hot Deployment | 31

Working with Hot Deployment

Prior to TIBCO MDM 7.1, all configuration properties were defined in the ConfigValues.xml file, segregated based on various categories, and marked within appropriate tags <ConfigValue>. Changes to the properties were updated through MqRevivify (invoking PropManager.refresh()). This approach enabled a reread of all properties from the ConfigValues.xml file.

However, reinitialization of already configured objects did not happen, such as init classes (where sequences may have been changed or new classes may have been added), JMS sender and receiver managers involved in integration with TIBCO MDM, Email, FTP, LDAP server configurations, and so on.

You can reinitialize various configured objects at run time without requiring a server restart. In other words, as soon as values are changed, the Administrator can issue a request to reconfigure the application.

Applicability

Hot deployment is applicable to the following configurations:

• Initialization

• Logging

• Authentication

• ThreadLogger

• Network

• LDAP

• Email

• Comm (internal) and Standard (external) Integration Messaging

These map to the following configurations:

— Introduction of new queues/topics.

— Native cache configuration.

— Authentication handlers.

— Log management properties.

— Servers used for Email, FTP, LDAP, and EMS.

— Several other categories which get refreshed without explicit code changes.



The following properties or configurations are not hot deployable (Messaging Properties, Database, Application Server, Security provider, and Internal categories):

— Choice of Database and Application server

— JMS Messaging properties and EMS server configuration

— Database space management parameters

— Pipeline changes configured in Queue and Bus properties

— Ports for JNDI registry

— Changes in sender/receiver manager configurations and pipelines

Properties that Require Reinitialization

The following property categories require reinitialization:

• Network

• Authentication

• Optimization (MqCacheManager)

Properties that are Auto Refreshed

The following properties do not require reinitialization and are refreshed (when redeployment is triggered):

• Rule base

• Configuration file

• Email

• Miscellaneous

• System Debugging

• Repository

• UI Settings

• Security Provider

• Software Edition Type

• Optimization

• Network

• Logging

• Workflow settings


Working with Hot Deployment | 33

• Rule Engine setup

• Timing Log

• Internal

• UI Customization

Invoking Hot Deployment

You can invoke the hot deployment using the UI by clicking Save and Redeploy in Configurator.

Using Configurator UI

Using the Save And Redeploy option in Configurator, you can hot deploy the configuration property.

After modifying the configuration property, perform the following steps:

1. Select the NodeID.

2. Click Save & Redeploy. The Save And Redeploy window is displayed.

3. Type the host name, port number, and description of the TIBCO MDM server on which the configuration or property changes should be deployed.

If you do not specify a port number, the default application server specific port is considered. For example, for the JBoss Application Server, the default port is 9999.

4. Click Save. The property is deployed on the selected TIBCO MDM server. It then initiates a runtime refresh as well as re-initialization of the configuration within



TIBCO MDM. Certain properties that can be autorefreshed and some still require a server restart for reinitialization.

In case of clustered environment, a message is displayed to deploy the configuration property on a different port. Select the another NodeID and enter its host name and port number. After completing the hot deployment on all NodeIDs, the Save And Redeploy option is disabled.


Controlling Major Flags through Configurator | 35

Controlling Major Flags through Configurator

This section describes the new major flags you can control through Configurator in this release.

Timing Log

Timing log information is consolidated into a single timing.log file.

The timing log properties are hot deployable.

To upload timing data for analysis, refer to the timinglogLoad.bat sample database table script located at $MQ_HOME/Bin (Windows only). The Timing Log File Name Default property in Configurator (Configuration Outline > Logging > Default Timing Log) provides the timing.log file location.

Cluster Specific Timing Log

In the prior release, the timing log properties were divided into various categories, such as Rulebase Timing Log, UI Servlet Timing Log, Workflow Activity Timing Log, SQL Timing Log, Timer Timing Log, and Service Timing Log. This categorization was cluttering in Configurator. To avoid clutter, all existing timing log configurations are removed and a set of the default timing log properties is introduced in the 8.3.2 release.



The following table describes the default timing log property set, which is applicable for the entire cluster. To view these properties in Configurator, Navigate to Cluster Outline > Initial Config > Timing Log.


Controlling Major Flags through Configurator | 37

Enabling the Timing Log

To enable the timing log, the following properties should be set to true from the Configurator, All Configuration Outline, Timing Log:

— Timing Log Services Switch(enables the timing log for webservices)

— Timing Log Servlet Switch(enables timing log for UI servlets)

— Timing Log SQL Switch(enables timing log for SQL)

— Timing Log Timer Switch(enables timing log for the timer)

— Timing Log Workflow Activity Switch

Table 4 Cluster Specific Timing Log Properties

Property Name Propname Description

Timing Log Default Category

com.tibco.cim.timinglog.default.categoryName

Specifies the value to configure the category of the timing log. This must be defined in the logging configuration. The default value is timinglogdefault.

Timing Log Default Class

com.tibco.cim.timinglog.default.class

This timing log Java class receives the submitted form and processes it. It writes the timing information to a file.

Timing Log Default Threshold

com.tibco.cim.timinglog.default.threshold

Controls whether or not any time statistics to be generated. Set the threshold in milliseconds. If you set it to 0, all timings are tracked.

Timing Log Default Switch

com.tibco.cim.timinglog.default.enabled

Indicates the timing log for a certain category. The timing logs are generated only when the value is set to true.

Valid values are True or False. The default value is False.



(enables timing log for workflow activities and generates time statistics for workflows)


| 39

Chapter 4 Working with Data Model Template

This chapter introduces you to the data model template and describes how to modify it.

Topics

• Data Model Template, page 40

• Importing the Data Model, page 41

• Modifying the Data Model, page 43

• Downloading Data Model from Salesforce, page 56


40 | Chapter 4 Working with Data Model Template

Data Model Template

The data model template is a sample set of metadata used to quick start the TIBCO MDM project. For example, the Party model is the commonly used data model for customer details. Depending on the requirements of your company, you can modify the model and deploy it.

You can download the Data model template from https://tibbr.tibcommunity.com/tibbr/web/messages/62658

In addition to the data model template, you can also modify a template as a starting point or create your own data model.

To modify the data model, use the following two ways:

• Download the data model template from tibbr, and then import the data model to TIBCO MDM Studio.

• Download your company specific data model available in Salesforce.


https://tibbr.tibcommunity.com/tibbr/web/messages/62658

http://tap.tibco.com/storefront/index.ep

https://tibbr.tibcommunity.com/tibbr/web/messages/62658

Importing the Data Model | 41

Importing the Data Model

Prerequisite

After downloading the data model from tibbr, copy the zip file to your local drive. Using TIBCO MDM Studio, import the zip file to your workspace.

To Import the data model into your workspace, follow these steps:

1. From the File menu, select Import. The import wizard is displayed.

2. Expand the General folder and select Existing Studio Projects into Workspace.

3. Click the Select the archive file.

4. Click Browse to navigate to the folder where you have saved the data model zip file.

5. Select the zip file and click Open.

6. Select the check box corresponding to the project and click Finish.

7. The data model is displayed in the Project Explorer.

Ensure that you have installed TIBCO MDM Studio.



Figure 18 Data Model in MDM Studio


Modifying the Data Model | 43

Modifying the Data Model

Depending on the requirements of your company, you can modify the data model. You can modify the data model by adding a new repository, a new relationship, adding or removing attributes from a repository, and so on.

For example, consider the scenario where you want to modify the Party model template. Perform the following steps:

• Add a new attribute in the Address repository - Street4

• Add a new datasource attribute - Email.ds

• Add a new input map in the Email repository - Email_InputMap

• Add a new Synchronization format - EmailSyncFormat

• Add a new output map in the Email repository - Email_OutputMap



To modify the Party model:

1. Open the sample Party model project in TIBCO MDM Studio. The Project Explorer with sample Party model is displayed.

Figure 19 Repository Models



2. Select the Address repository and define a new attribute Street4. For more information on defining attributes, refer to TIBCO MDM Studio Repository Designer User’s Guide.

Figure 20 Add New Attribute



3. Create a new datasource, such as Email.ds. For more information on creating a datasource, refer to TIBCO MDM Studio Repository Designer User’s Guide.

Figure 21 New Datasource - Email.ds



4. Create a new inputmap, such as Email_InputMap. For more information on creating input maps, refer to TIBCO MDM Studio Repository Designer User’s Guide.

Figure 22 New Input Map - Email_InputMap



5. Create a synchronization format, such as EmailSynchFormat. For more information on creating synchronization format, refer to TIBCO MDM Studio Repository Designer User’s Guide.

Figure 23 New Synchronization Format - EmailSynchFormat



6. Create a new output map, such as Email_OutputMap. For more information on creating output maps, refer to TIBCO MDM Studio Repository Designer User’s Guide.

Figure 24 New Output Map - Email_OutputMap



7. After you modify the data model, it must be deployed on the TIBCO MDM server. Create a new deployment server.

Figure 25 Deployment Server Parameters

8. Enter the following parameters:

— Base URL - For example, https://mdm.cloud.tibco.com/user1tibco.com/Env_1.

— Enterprise- For example, Company1

— User Name- For example, admin

— Password- For example, admin

9. Click Test Connection to test whether the newly created server connection is established.

10. Deploy the modified data model in the TIBCO MDM server.



11. From the TIBOC Cloud MDM Console, click the TIBOC MDM Server URL. The TIBCO MDM server page is displayed.

Figure 26 MDM Login Page



The following sections display the screens before and after the data model was modified:

Figure 27 The Datasource Screen Before Modifying the Party Model

Figure 28 The Datasource Screen After Modifying the Party Model



Figure 29 The Input Map Screen Before Modifying the Party Model

Figure 30 The Input Map Screen After Modifying the Party Model



Figure 31 The Output Map Screen Before Modifying the Party Model

Figure 32 The Output Map Screen After Modifying the Party Model



Figure 33 The Synchronization Format Screen Before Modifying the Party Model

Figure 34 The Synchronization Format Screen After Modifying the Party Model



Downloading Data Model from Salesforce

In a company, you may have your own data model for your business needs. Many companies use Salesforce for managing customer data, and need to extend the TIBCO MDM service to include additional salesforce metadata. You can download you own data models from Salesforce. These data models can then be mapped to the sample data model template or you can create custom model for your TIBCO MDM service.

To download the data model from Salesforce, follow these steps:

1. Login to http://login.salesforce.com using your login credentials.The salesforce screen is displayed.

2. Click Setup. The Administer page is displayed.

3. Click .The Data Management options are displayed.

4. Select Data Export.


http://tap.tibco.com/storefront/index.ep

http://login.salesforce.com

Downloading Data Model from Salesforce | 57

5. The Weekly Export Service page is displayed.

6. Click Export Now to download the data or click Schedule Export to schedule a data download.



7. On clicking Export Now, the Weekly Export Service page with the download parameter is displayed.

— Select Unicode (UTF-8) from the Export file Encoding drop-down.

— Select the Include images, documents, and attachments check box.

— Select the Include Chatter files and Salesforce CRM Content document versions check box.

— Select the Replace carriage returns with spaces check box.

— Select the Include all data check box from the Exported Data section.

— Click Start Export. The export is initiated with the message Your export has been queued. You will receive an email notification when it is completed.


Downloading Data Model from Salesforce | 59

8. On clicking Schedule Export, the Weekly Export Service page with the schedule data export parameter is displayed.

— Select Unicode (UTF-8) from the Export file Encoding drop-down.

— Select the Include images, documents, and attachments check box.

— Select the Include Chatter files and Salesforce CRM Content document versions check box.

— Select the Replace carriage returns with spaces check box.

— Select the frequency from the Schedule Data Export section.

— Select the Include all data check box from the Exported Data section.

— Click Save.

— Click Schedule Export. The export is initiated with the message Your export has been queued. You will receive an email notification when it is completed.




| 61

Index

A

All Instance 12A-Z 12

C

changes from the previous release vicompany name 8component 11components 11, 11Configurator

Cluster Outline 23Configuration

Advanced 26Basic 25

Configuration Outline 25Configuration Values

Search 30Deploying 20Hot Deployment 31

Invoking 33Through UI 33

Logging into 21Overview 20

Creating Instance 6customer support xi

D

Dashboard 7dashboard 11data backup 17data model 7Date Created 12

de-provision 12De-Provisioning 16Details 7

E

email 17environment 6

L

Large 6Launch 9

M

MDM Admin 8MDM Application 11MDM Configurator 11MDM Studio designer 7Medium 6Message to Admin 12

N

None 7


62 | Index

P

Password 8Proceed to MDM Console 9

R

reset 12reset password 12

S

Small 6subscription types 6Super User 8support, contacting xi

T

technical support xiTerminate 12, 16track 11

W

wizard 6


Date post:	24-May-2018
Category:	Documents
Upload:	lyminh
View:	225 times
Download:	3 times

TIBCO?? Cloud MDM - TIBCO Product Documentation€¦ · TIBCO® Cloud MDM is a cloud service to...

Documents