TIBCO Configuration Guide · 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

TIBCO® Cloud MDM Provisioning andConfiguration GuideSoftware Release 2.0.1May 2017

Two-Second Advantage®

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCHEMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (ORPROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THEEMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANYOTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS ANDCONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTEDSOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THECLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOADOR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USERLICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THESOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, ANDYOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BEBOUND BY THE SAME.

This document contains confidential information that is subject to U.S. and international copyright lawsand treaties. No part of this document may be reproduced in any form without the writtenauthorization of TIBCO Software Inc.

TIBCO and Two-Second Advantage are either registered trademarks or trademarks of TIBCO SoftwareInc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform EnterpriseEdition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks ofOracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of theirrespective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOTALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASEDAT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWAREVERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSOR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICALERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESECHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCOSOFTWARE 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 ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2017 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

2

TIBCO® Cloud MDM Provisioning and Configuration Guide

Contents

TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

TIBCO Cloud MDM Console Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

TIBCO Cloud MDM Console Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Creating an Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Password Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Password Strength . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Password Expiration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

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

Configurator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Configurator GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Logging in to Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

Logging out of Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuration Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Cluster and Configuration Outlines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Cluster Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20

Modifying the Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Cluster Members Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Modifying Cluster Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Cloning Cluster Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Deleting Cluster Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Configuration Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Basic Configuration Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Advanced Configuration Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Using Configuration Outline Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Modifying Configuration Outline Category . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Other Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Adding New Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25

Searching Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Hot Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Properties that Require Reinitialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

Properties that are Auto Refreshed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Invoking Hot Deployment Using Configurator UI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Control Major Flags through Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

3


Timing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Cluster Specific Timing Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30

Viewing Cluster Specific Timing Log Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Data Model Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Importing the Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Modifying the Data Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34

Downloading Data Model from Salesforce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

4


TIBCO Documentation and Support Services

Documentation for this and other TIBCO products is available on the TIBCO Documentation site. Thissite is updated more frequently than any documentation that might be included with the product. Toensure that you are accessing the latest available help topics, visit:

https://docs.tibco.com

Product-Specific Documentation

The following documents for this product can be found on the TIBCO Documentation site:

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

● TIBCO Cloud MDM Sample Data Models: Read this manual to know the commonly used data models. Usingthese models, you can perform various functions of TIBCO Cloud MDM .

How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, contact TIBCO Support:

● 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 canrequest one.

How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCOmmunity offersforums, blogs, and access to a variety of resources. To register, go to the following web address:

https://www.tibcommunity.com

How to Join TIBCO Community

TIBCO Community is an online destination for TIBCO customers, partners, and resident experts. It is aplace to share and access the collective experience of the TIBCO community. TIBCO Community offersforums, blogs, and access to a variety of resources. To register, go to the following web address:

https://community.tibco.com

5



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

https://support.tibco.com

https://www.tibcommunity.com

https://community.tibco.com

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. Touse TIBCO Cloud MDM, you require a current subscription. The various subscription types aredescribed at TIBCO Marketplace.

Using TIBCO Cloud MDM Console, you can create, monitor, and control all the environments orinstances available as part of a subscription. The TIBCO Cloud MDM Console uses the credentials fromTIBCO Marketplace for authentication. A current subscription to TIBCO Cloud MDM is required toaccess the TIBCO Cloud MDM Console.

6


http://marketplace.cloud.tibco.com

TIBCO Cloud MDM Console Interface

When you log in for the first time, the TIBCO Cloud MDM Console displays the Help, Visit SilverMarketplace, and Sign Out menu on the upper right corner. In addition, TIBCO Cloud MDM Consoledisplays the link for creating a new instance.

For more information on TIBCO Cloud MDM Console Interface, refer to Dashboard.

● 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 MDMConfigurator. However, you can login to TIBCO Cloud MDM Console. Renew your subscription atTIBCO Marketplace. Click Visit Silver Marketplace to renew your subscription. You are thendirected to http://marketplace.cloud.tibco.com.

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

7


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

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

http://marketplace.cloud.tibco.com

Creating an Instance

The TIBCO Cloud MDM Console provides a wizard to provision a TIBCO MDM instance. After you loginto TIBCO Marketplace and select TIBCO Cloud MDM, click Launch. The MDM Console wizard isdisplayed.

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

Procedure

1. Click the Create New Instance link.

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

3. Select the Medium instance type and click Next.

8


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

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

● Insurance- Select Insurance if you want to create a insurance TIBCO MDM instance based onthe Insurance model template.

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

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

6. Click the Details link corresponding to the party data model to know more details about the datamodel. 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.

9



Field Descriptions

Enter company name: Specify the company name in this field. The company name is theMDM Enterprise name. The company names can be same formultiple instance. However, the environment name must beunique.

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

The password must be according to the new password policy.

Confirm Password for SuperUser:

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 policyin this field.

Confirm Password for MDMAdmin:

Specify the MDM admin password again to confirm.

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

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

9. The provisioning complete screen is displayed.

10


10. Click Start MDM. The TIBCO MDM Welcome page is displayed.

Enter the Company Name, User Name, Password and click Login.

11. First time user's are redirected to the Reset Password page.

11


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

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

12


Dashboard

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

● The two components of the TIBCO Cloud MDM Console are:

— MDM Application

— MDM Configurator

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

● The MDM Configurator displays the URL of the MDM configurator. You can click the URL andlogin using the default login credentials. For more information on Configurator refer to, Configurator Overview.

● To search for a particular instance when you have many instances running, type the instance namein 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 https://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.

13




● To de-provision the instance, click Terminate. The Terminate Instance wizard is displayed. For moreinformation on de-provisioning refer to De-Provisioning Instance.

● 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.

● Click Continue. The confirmation message is displayed.

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

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

14


Password PolicyThe Cloud MDM is enhanced to support authentication implementation. In today’s world the danger ofexposing vital company data to the world is significant, the factor determining the data exposure is dueto users choosing weak passwords. To add to that the administrator of the application do not havecontrol on such weak password policy.

The enhancement is introduced to provide an Internet acceptable authentication solution, which cansupport authentication policies, is self-serviceable, audit-able, and secure.

The authentication implementation supports the subsequent requirements.

Password StrengthThe password strength values are not visible to the end user. However, on request, the cloud operationsteam 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 thepassword 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."

Password ExpirationThe administrator can define the password expiration time for each user. The password expirationperiod is specified in days. The default value is 90 days. The password expiration value is configuredusing the com.tibco.mdm.authentication.cloud.password.expiration property in configvalues.xml. Bydefault, password expiration is enabled.

15


De-Provisioning Instance

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.

Procedure

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

2. The Terminating Instance wizard is displayed.

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

16


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

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

17


Configurator Overview

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

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

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

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

To convert existing properties defined in the MqProperties.confg, MqLog.cnf, queue.prop, andbus.prop files to the new XML format, use the xmlPropMergeUtil utility or Installer. For moreinformation 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

Procedure

● Click the Configurator URL into your browser. For example, http://mdm-staging.cloud.tibco.com/johntibco.com/mdm-70/manage/config/index.html#/loginThe Configurator URL is displayed after the provisioning in the MDM Console.

Logging in to ConfiguratorAfter the browser connects, the following default User Login screen is displayed:

18


Procedure

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 ConfiguratorBefore logging out, save the configurations that you have already updated.

Procedure

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 fromConfigurator.

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

Result

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

19


Configuration Setup

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

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 anoption listed in these panels, corresponding properties, values, and descriptions are displayed on theright 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 thevalues by clicking a specific value.

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

The subsequent sections describe these panels.

Cluster and Configuration OutlinesProperties 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 nodeor member. For example, JNDI properties for an Application server.

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

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

20


Modifying the ClusterA cluster view facilitates navigation between instances (nodes) and cluster-wide configuration. You canchange the cluster configuration.

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

Procedure

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 isdisplayed.

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.

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

Modifying Cluster Member

Procedure

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 isdisplayed.

21


Cloning Cluster Member

Procedure

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 isdisplayed after the previously selected cluster member.

Deleting Cluster Member

Procedure

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 deletionmessage 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 isrunning.

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

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

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 serverusername, password, the error email receiver, the error email sender, the Inbox URL, the SMTPHost, 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 editionis displayed. The Basic view displays the Application Usage Profile property, and the Advancedview displays the Common Menus Configuration property.

22


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 OptionsA square icon is displayed next to each configuration outline.

Procedure

1. Click the icon.2. Edit, clone, or delete the configuration outline.

Modifying Configuration Outline Category

Procedure

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.

23


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 isdisplayed.The Cloning and deleting steps are similar to the Cluster member options.

● For cloning the configuration outline, refer to Cloning Cluster Member.

● For deleting the configuration outline, refer to Deleting Cluster Member.

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

Other Menu Options

Menu Name Description

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

Save & Redeploy Clicking this option saves the configuration andhot deploys the values to the TIBCO MDMserver if it is currently running. For more detailson Hot Configuration, refer Hot Deployment.

Save Clicking this option saves the configuration.

24


Adding New Property

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

Procedure

1. Click Add New Property. The Add New Property window is displayed. Type details for the newproperty in the following 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 areBasic 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 moreinformation on the value types, refer to TIBCO MDM User’sGuide.

Current Value Specify the current value.

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

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

25


Searching Configuration Values

Using the search facility, you can quickly locate the configuration values by name. The Search Propertyfield is located in the upper-right corner of the window.

Procedure

1. 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 columnsare displayed for the specified property.

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

26


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>. Changesto the properties were updated through MqRevivify (invoking PropManager.refresh()). This approachenabled a reread of all properties from the ConfigValues.xml file.

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

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

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

27


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 istriggered):

● Rule base● Configuration file● Email● Miscellaneous● System Debugging● Repository● UI Settings● Security Provider● Software Edition Type● Optimization● Network● Logging● Workflow settings● Rule Engine setup● Timing Log● Internal● UI Customization

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

28


After modifying the configuration property, perform the following steps:

Procedure

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 theconfiguration or property changes should be deployed.

If you do not specify a port number, the default application server specific port is considered. Forexample, 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 runtimerefresh as well as re-initialization of the configuration within TIBCO MDM. Certain properties thatcan be autorefreshed and some still require a server restart for reinitialization.

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

29


Control Major Flags through Configurator

You can control some of the new major flags through Configurator.

● Timing Log

● Cluster Specific Timing Log

Timing LogTiming log information is consolidated into a single timing.log file. The timing log properties are hotdeployable.

To upload timing data for analysis, refer to the timinglogLoad.bat sample database table script locatedat $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

The following table describes the default timing log property set, which is applicable for the entirecluster.

Property Name Propname Description

Timing Log DefaultCategory

com.tibco.cim.timinglog.default

.categoryName

Specifies the value to configure thecategory of the timing log. Thismust be defined in the loggingconfiguration. The default value istiminglogdefault.

Timing Log DefaultClass


.class

This timing log Java class receivesthe submitted form and processes it.It writes the timing information to afile.

30


Property Name Propname Description

Timing Log DefaultThreshold


.threshold

Controls whether or not any timestatistics to be generated. Set thethreshold in milliseconds. If youset it to 0, all timings are tracked.

Timing Log DefaultSwitch


.enabled

Indicates the timing log for a certaincategory. The timing logs aregenerated only when the value is setto true.

Valid values are True or False. Thedefault value is False.

Prior to the 8.3.2 release, the timing log properties were divided into various categories, such asRulebase Timing Log, UI Servlet Timing Log, Workflow Activity Timing Log, SQL Timing Log, TimerTiming Log, and Service Timing Log. This categorization was cluttering in Configurator. To avoidclutter, all existing timing log configurations are removed and a set of the default timing log propertiesis introduced in the 8.3.2 release.

Viewing Cluster Specific Timing Log Properties

Procedure

1. Log in to Configurator.

2. Navigate to Cluster Outline.

3. Select Initial Config.

4. Select Timing Log.

31


Data Model Template

The data model template is a sample set of metadata used to quick start the TIBCO MDM project. Forexample, the Party model is the commonly used data model for customer details. Depending on therequirements 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 createyour 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 MDMStudio.

● Download your company specific data model available in Salesforce.

32


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

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

Importing the Data Model

Prerequisites

● Ensure that you have installed TIBCO MDM Studio.

● After downloading the data model from Tibbr, copy the ZIP file to your local drive. Using TIBCOMDM Studio, import the ZIP file to your workspace.

Procedure

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.

33


Modifying the Data Model

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

For example, consider the scenario where you want to modify the Party model template.

Procedure

1. Add a new attribute in the Address repository - Street4

2. Add a new datasource attribute - Email.ds

3. Add a new input map in the Email repository - Email_InputMap

4. Add a new Synchronization format - EmailSyncFormat

5. Add a new output map in the Email repository - Email_OutputMap

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

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

34


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

9. 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.

35


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

36


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

12. After you modify the data model, it must be deployed on the TIBCO MDM server. Create a newdeployment server.

13. 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

37


● Password- For example, admin

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

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

16. From the TIBOC Cloud MDM Console, click the TIBOC MDM Server URL. The TIBCO MDM serverpage is displayed.

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

38


39


40


41


42


Downloading Data Model from Salesforce

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

Procedure

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.

5. The Weekly Export Service page is displayed.

43


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

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 isdisplayed.

● 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.

44


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

8. On clicking Schedule Export, the Weekly Export Service page with the schedule data exportparameter 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.

45


Documents

TIBCO Configuration Guide · 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