master data manager 3.2.0.1 installation guide

Master Data ManagerInstallation Guide

Release 03.02.00.01B035-9701-072A

July 2012

The product or products described in this book are licensed products of Teradata Corporation or its affiliates.

Teradata, BYNET, DBC/1012, DecisionCast, DecisionFlow, DecisionPoint, Eye logo design, InfoWise, Meta Warehouse, MyCommerce, SeeChain, SeeCommerce, SeeRisk, Teradata Decision Experts, Teradata Source Experts, WebAnalyst, and You’ve Never Seen Your Business Like This Before are trademarks or registered trademarks of Teradata Corporation or its affiliates.Adaptec and SCSISelect are trademarks or registered trademarks of Adaptec, Inc.AMD Opteron and Opteron are trademarks of Advanced Micro Devices, Inc.BakBone and NetVault are trademarks or registered trademarks of BakBone Software, Inc.EMC, PowerPath, SRDF, and Symmetrix are registered trademarks of EMC Corporation.GoldenGate is a trademark of GoldenGate Software, Inc.Hewlett-Packard and HP are registered trademarks of Hewlett-Packard Company.Intel, Pentium, and XEON are registered trademarks of Intel Corporation.IBM, CICS, DB2, MVS, RACF, Tivoli, and VM are registered trademarks of International Business Machines Corporation.Linux is a registered trademark of Linus Torvalds.LSI and Engenio are registered trademarks of LSI Corporation.Microsoft, Active Directory, Windows, Windows NT, and Windows Server are registered trademarks of Microsoft Corporation in the United States and other countries.Novell and SUSE are registered trademarks of Novell, Inc., in the United States and other countries.QLogic and SANbox trademarks or registered trademarks of QLogic Corporation.SAS and SAS/C are trademarks or registered trademarks of SAS Institute Inc.SPARC is a registered trademarks of SPARC International, Inc.Sun Microsystems, Solaris, Sun, and Sun Java are trademarks or registered trademarks of Sun Microsystems, Inc., in the United States and other countries.Symantec, NetBackup, and VERITAS are trademarks or registered trademarks of Symantec Corporation or its affiliates in the United States and other countries.Unicode is a collective membership mark and a service mark of Unicode, Inc.UNIX is a registered trademark of The Open Group in the United States and other countries.Other product and company names mentioned herein may be the trademarks of their respective owners.

THE INFORMATION CONTAINED IN THIS DOCUMENT IS PROVIDED ON AN “AS-IS” BASIS, WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OF IMPLIED WARRANTIES, SO THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. IN NO EVENT WILL TERADATA CORPORATION BE LIABLE FOR ANY INDIRECT, DIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES, INCLUDING LOST PROFITS OR LOST SAVINGS, EVEN IF EXPRESSLY ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

The information contained in this document may contain references or cross-references to features, functions, products, or services that are not announced or available in your country. Such references do not imply that Teradata Corporation intends to announce such features, functions, products, or services in your country. Please consult your local Teradata Corporation representative for those features, functions, products, or services available in your country.Information contained in this document may contain technical inaccuracies or typographical errors. Information may be changed or updated without notice. Teradata Corporation may also make improvements or changes in the products or services described in this information at any time without notice.To maintain the quality of our products and services, we would like your comments on the accuracy, clarity, organization, and value of this document. Please e-mail: [email protected] comments or materials (collectively referred to as “Feedback”) sent to Teradata Corporation will be deemed non-confidential. Teradata Corporation will have no obligation of any kind with respect to Feedback and will be free to use, reproduce, disclose, exhibit, display, transform, create derivative works of, and distribute the Feedback and derivative works thereof without limitation on a royalty-free basis. Further, Teradata Corporation will be free to use any ideas, concepts, know-how, or techniques contained in such Feedback for any purpose whatsoever, including developing, manufacturing, or marketing products or services incorporating Feedback.

mailto:[email protected]

Preface

Purpose

Welcome to Teradata Master Data Manager® (MDM). Master Data Manager provides a way to integrate and consolidate master data without having to replace existing infrastructure investments.

You can stage, consolidate, validate, cleanse, store, augment, cross-reference, and publish data to systems in your IT infrastructure. By ensuring cross-system data consistency, MDM can enable flawless execution of business processes – while leveraging existing IT investments and reducing the total cost of ownership to manage business critical data.

Topics:

• About Teradata Master Data Manager (MDM)• About This Book• Related Documentation• Customer Support• Documentation Feedback

About Teradata Master Data Manager (MDM)

Master Data Manager helps you synchronize key data elements across disparate systems and geographies. Master Data Manager enables you with:

• Data Staging for loading, cleansing, validating, aggregating, and publishing data.• Data Model Maintenance for model extension and model repository.• Master Data LifeCycle Maintenance for data maintenance workflows and versioning,

editing, and archiving data.

MDM simplifies deployment, integration of heterogeneous systems, is easier to manage, provides high quality data, and decouples data from business application software. Consider using Master Data Manager at these levels in your organization:

• Enterprise level• Division level• Process level (for example, Supply Chain, Customer Management)• Sub-Process level (for example, Replenishment, and Master Planning)

Master Data Manager Installation Guide iii

PrefaceAbout This Book

About This Book

This document describes how to install Teradata MDM.

Target Audience

This guide is intended for users who are installing Teradata MDM.

What You Should Know

Some sections of this document assume knowledge of third party software.

Document Structure

This book has the following chapters:

• Chapter 1: “MDM System Requirements.” Describes MDM system requirements and supported platforms.

• Chapter 2: “MDM and CRDM Installation.” Provides a step by step procedure for installing MDM.

• Chapter 3: “MDM Database Preparation.”Describes about database preparation.• Chapter 4: “MDM WebClient Deployment.”Describes about Webclient deployment.• Chapter 5: “Launch MDM Server and Client.”Describes about starting the MDM server

and client.• Chapter 6: “MDM Silent Installation.”Describes MDM uninstallation procedure.• Chapter 7: “MDM Deployment Manager.”Describes MDM Deployment manager.• Chapter 8: “MDM Patch Installation.” Provides a step by step procedure for MDM patch

installation.• Chapter 9: “MDM Upgrade” Describes MDM Upgrade process.• Chapter 10: “MDM Uninstallation” Describes the MDM uninstallation steps.• Appendix A: “Silent Installer Property Files” Provides the silent installer property files.• Appendix B: “MDM Database Sizing Guidelines”Describes MDM database sizing

requirements.

Changes to This Book

The following changes were made to this book in support of the current release. For a complete list of changes to the product, refer MDM Platform Release Definition associated with this release.

iv Master Data Manager Installation Guide


Date and Release Description

March 2009, 02.01.01

“Database User Requirements” section modified.

The section “MDM and the Use of the Teradata Data Dictionary” updated.

Added a note in “Database User Requirements” section specifying that the Installer would stop if no spool space is given to the database user and the workaround for the same is included.

Section “Fallback on MDM Database Tables” added.

In Chapter 3: “MDM Database Preparation”, described more in detail covering the section preparing database for MDM with two possible scenarios and new section “Troubleshooting MDM Database Preparation” added.

Removed all references to Hierarchy Manager war deployment. Removed the section Hierarchy Manager Deployment in WebSphere from Chapter 4: “MDM WebClient Deployment.”

Note: From MDM 2.01.01 onwards, Hierarchy Manager deployment will be part of MDM deployment.

Note included in “WebClient Deployment in BEA WebLogic”to ignore the warning message while using WebLogic 10 for Webclient deployment.

Variable WebLogic_ Server_Name_Boolean_1 removed from Table 12.

August 2009,

2.01.02

Support for BEA WebLogic 10.3 and Java 6 added in section “System Requirements” .

“Override Changes on Base Toolkit (MDM) Tables and Scripts” section added.

Messages changed on the MDM Installer panel for Teradata Jars location and Third Party Location in Chapter 2.

Installer panel updated to include Other Application server deployment in Chapter 2.

Workaround added for Linux support for UTF-8 and UTF-16 in section “Globalization (UTF-8) Setting”

Workaround added for Weblogic 10. Webclient deployment in section“WebClient Deployment in BEA WebLogic”

“WebClient Deployment on Tomcat 6.0” section added.

Installer log file displaying the database Status added in section “Installing MDM”

Added Chapter 9: “MDM Upgrade”

Master Data Manager Installation Guide v


December 2009, 3.00.00

Replaced all the Installer Panels in Chapter 2: “MDM and CRDM Installation” and Chapter 10: “MDM Uninstallation”.

Replaced all the figures as per the Eclipse MDM Studio in Chapter 3: “MDM Database Preparation”.

Included steps for enabling web service in Chapter 2: “MDM and CRDM Installation”.

Updated Chapter 9: “MDM Upgrade”.

June 2010, 3.00.01 Included new Chapter 7: “MDM Deployment Manager”.

Included new Appendix B: “MDM Database Sizing Guidelines”.

Updated web.xml to support Tomcat deployment in Chapter 4: “MDM WebClient Deployment”.

Replaced all the Installer Panels in Chapter 2: “MDM and CRDM Installation” and Chapter 9: “MDM Upgrade”.


September 2010, 3.00.02

Updated Table 5 and Table 6 in Chapter 1: “MDM System Requirements” for Windows 8 and Windows 7 64 bit support.



March 2011, 3.01.00

Included Teradata JDBC 13.10.00.03 version in system requirements.



June 2011, 3.01.00.01


September 2011, 3.01.01



June 2012, 3.02.00 Updated the system requirement tables to include IE 9, Firefox 9, Linux 11 and TD 14 support in Chapter 1: “MDM System Requirements” .

Updated Database requirement for access rights to non MDM and CRDM sandbox in Section : “Database User Requirements” in Chapter 1: “MDM System Requirements”.


Included Section : “Installing CRDM” and Section : “Installing MDM Sample Application”.

Updated Chapter 7: “MDM Deployment Manager” as per 3.2 updates.


vi Master Data Manager Installation Guide


Conventions

Table i lists examples of the typographic conventions used to display different types of information in this document.

Any of the following types of notes may appear in this book:

Note: This kind of note contains information that is useful or interesting but not essential to an understanding of the main text.

Caution: This kind of note contains instructions that are especially important to follow for proper functioning of the product.

Warning: This kind of note contains instructions that must be followed to avoid potential crashes or loss of data.

July 2012, 3.02.00.01

Included workaround for CRDM features to work on TD 13.10 in Chapter 2: “MDM and CRDM Installation”

MDM Upgrade chapter updated.


Table i: Typographic conventions used in this document

Item Example Explanation

Code Call NotifyPending; File names, executable code, commands, and configuration statements are shown in monospaced font.

Class Names Make the Class Configurations pointer in the Module Configuration class a primary key.

Class names appear in bold.

Interface element Click Organization Management in the toolbar.

Button names, field names, window names are shown in a bolded san-serif font.

Pathname C:\Teradata\webdriver

or

/Teradata/webdriver

Windows pathnames are shown in monospaced font, with backslash path separators.

Meta-variable Teradata_Home\webdriver

or

Teradata_Home/webdriver

Portions of code that you replace with specific values are shown in italic monospaced font.

Documentation or book names

Master Data Manager (MDM) - Installation Guide

Document or book names referenced in this book are shown in italics.

Master Data Manager Installation Guide vii

PrefaceRelated Documentation

Related Documentation

For more information on MDM, refer the following documents:

• Master Data Manager Release Definition(MDM Platform 03.02.00 Release Definition.pdf)

• Master Data Manager Developer Guide(MDM Platform 03.02.00 Developer Guide.pdf)

• Master Data Manager Reference Guide(MDM Platform 03.02.00 Reference Guide.pdf)

• Master Data Manager Studio User Guide(MDM Platform 03.02.00 Studio User Guide.pdf)

• Master Data Manager Server Guide(MDM Platform 03.02.00 Server Guide.pdf)

• Master Data Manager LRDM Server Guide(MDM Platform 03.02.00 LRDM Server Guide.pdf)

• Master Data Manager CRDM User Guide(MDM Platform 03.02.00 CRDM User Guide.pdf)

The above Teradata documents/publications are available at http://www.TeradataAtYourService.com.

For assistance with any of the above documents/ publications, check with your Teradata customer representative.

Documentation Accessibility

To read the .pdf files, you must have Adobe Acrobat Reader, version 4.0 or higher. If you do not have Acrobat Reader on your machine, you can download it from Adobe’s Web site at http://www.adobe.com.

To read the Help files, you must have one of the following browsers:

• Internet Explorer, version 5.0 or higher. You can download this software from the Microsoft Web site at http://www.microsoft.com/.

• Netscape, version 4.0 or higher. You can download this software from the Netscape Web site at http://home.netscape.com/.

Customer Support

Customer support is available at the Teradata customer support Web site ((http://www.teradata.com/services-support), where you can:

• Request shipment of software.

viii Master Data Manager Installation Guide

http://www.teradata.com/services-support

PrefaceDocumentation Feedback

• Download software documentation.• Submit new issues or cases.• Track the status of current issues or cases.

Documentation Feedback

We value your comments and suggestions about our documentation. If you have comments about this book or the online help, please enter them at http://www.info.teradata.com/eFeedback.cfm. We will use your feedback in our plans to improve Teradata documentation.

Master Data Manager Installation Guide ix

http://www.info.teradata.com/eFeedback.cfm

http://www.info.teradata.com/eFeedback.cfm

PrefaceDocumentation Feedback

x Master Data Manager Installation Guide

Table of Contents

Table of Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiAbout Teradata Master Data Manager (MDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iiiAbout This Book. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Target Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivWhat You Should Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivDocument Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivChanges to This Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ivConventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .vii

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiDocumentation Accessibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viiiDocumentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Chapter 1: MDM System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . 1

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Database User Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

MDM and the Use of the Teradata Data Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Fallback on MDM Database Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Database Topology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Chapter 2: MDM and CRDM Installation . . . . . . . . . . . . . . . . . . . . . . . . . 11

Packaging Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installing MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Installing CRDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing MDM Sample Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Master Data Manager Installation Guide xi

Table of Contents

Chapter 3: MDM Database Preparation . . . . . . . . . . . . . . . . . . . . . . . . . 47

Preparing Database for MDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Manually Executing SQLs Generated by MDM Schema Generation Process . . . . . . . . 50

Troubleshooting MDM Database Preparation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Files to Execute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Override Changes on Base Toolkit (MDM) Tables and Scripts . . . . . . . . . . . . . . . . . . . 53

Overriding Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Overriding Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Chapter 4: MDM WebClient Deployment. . . . . . . . . . . . . . . . . . . . . . . . 57

WebClient Deployment in IBM WebSphere . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57General Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Installing the Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Setting up JVM Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Globalization (UTF-8) Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Save and Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

WebClient Deployment in BEA WebLogic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62WebClient Deployment on Tomcat 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Pre-requisites. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Deployment Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Application Startup and Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 5: Launch MDM Server and Client . . . . . . . . . . . . . . . . . . . . . 67

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter 6: MDM Silent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Silent Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Silent Mode Installation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Creating a Silent Mode Installation Property File for MDM . . . . . . . . . . . . . . . . . . . . . 70Starting the Silent Mode Installation Process on Windows System . . . . . . . . . . . . . . . . 72Start the Server and Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

xii Master Data Manager Installation Guide

Table of Contents

Chapter 7: MDM Deployment Manager . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Deploying Custom/Sample/CRDM Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Changing Database Password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Debugging Deployment Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Chapter 8: MDM Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

MDM Patch Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Chapter 9: MDM Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Custom Application Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Backdown Procedure for MDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Chapter 10: MDM Uninstallation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Appendix A: Silent Installer Property Files . . . . . . . . . . . . . . . . . . . . 109

Silent Installer Property File without Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Silent Installer Property File with Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Appendix B: MDM Database Sizing Guidelines . . . . . . . . . . . . . . . . 113

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Sizing Requirements for Table Class/Source Combination Defined on MDM Facets . . . . 113

Class=MASTER Source=Backend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Class=Master Source=Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Class=Transaction Source=Backend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114MDM User Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Master Data Manager Installation Guide xiii

Table of Contents

Global Temporary Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Version (VER) Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Data Growth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Spool Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

xiv Master Data Manager Installation Guide

List of Figures

List of Figures

Figure 1: Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 2: License Agreement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Figure 3: LRDM Control Framework Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 4: Multiple LRDM Map Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 5: LRDM Map Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 6: JDK Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 7: MDM Install Location. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 8: MDM Shortcut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Figure 9: Port Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 10: E-Mail Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 11: Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 12: WebLogicConfigurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 13: Install Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 14: Installing Teradata MDM Platform 3.02.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Figure 15: Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 16: Error/Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 17: Error/Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Figure 18: Names for Staging Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 19: Warnings Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 20: Schema Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 21: Install Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 22: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 23: Choose MDM Server Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 24: Choose Applications to Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 25: Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 26: Installing Teradata MDM CRDM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 27: Install Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 28: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 29: Choose MDM Server Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 30: Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 31: Install Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 32: Solution Setup—Select Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Master Data Manager Installation Guide xv

List of Figures

Figure 33: Solution Setup—Generate Schema and Setup Static Data Panel. . . . . . . . . . . . . 49Figure 34: Solution Setup—Generate Schema Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 35: Override Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 36: WebSphere Console - Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 37: WebSphere Console - Application Server -Additional Properties. . . . . . . . . . . . 60Figure 38: WebSphere Console - Application Server -Additional Properties. . . . . . . . . . . . 61Figure 39: Environment Variables—Java_Home Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 40: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 41: Deploy Custom Application/Sample Application/Change Password . . . . . . . . . 75Figure 42: Choosing MDM Server installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Figure 43: Database Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 44: Incorrect DB Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 45: Enter Project ID & Your Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Figure 46: Please Choose Mode of Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 47: Database Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Figure 48: Import the rolled-up data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 49: Rolled-up Service/Table Names. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 50: Install Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Figure 51: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 52: Deploy Custom Application/Sample Application/Change Password . . . . . . . . . 85Figure 53: Choosing MDM Server installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 54: Enter New Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Figure 55: Password Changed Successfully . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 56: Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 57: Choose MDM Server Installation Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Figure 58: Database Upgradation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Figure 59: Install Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Figure 60: Upgrade Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 61: Uninstall Teradata MDM Platform 3.02.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Figure 62: Uninstall Complete. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

xvi Master Data Manager Installation Guide

List of Tables

List of Tables

Table i: Typographic conventions used in this document . . . . . . . . . . . . . . . . . . . . . . . . . . .viiTable 1: Hardware Requirements for Typical Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Table 2: Hardware Requirements for Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Table 3: Windows Workstation with Apache Tomcat, WebLogic Server or IBM WebSphere2Table 4: Windows Server with Apache Tomcat, WebLogic Server or IBM WebSphere . . . . 2Table 5: VMware ESXi Platform Support for MDM Server . . . . . . . . . . . . . . . . . . . . . . . . . . 3Table 6: SUSE Linux Platform support for MDM Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Table 7: AIX Platform support with WebSphere Application for MDM Server . . . . . . . . . . . 5Table 8: Solaris Platform with Apache Tomcat support for MDM Server . . . . . . . . . . . . . . . 5Table 9: MDM Silent Mode Installation Property Values . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Master Data Manager Installation Guide xvii

List of Tables

xviii Master Data Manager Installation Guide

Chapter 1: MDM System RequirementsSystem Requirements

CHAPTER 1 MDM System Requirements

What’s In This Chapter

This chapter provides information about MDM system requirements and supported platforms.

Topics include:

• System Requirements• Database User Requirements

System Requirements

Table 1 and Table 2 lists platform and system requirements for typical workstation (development environment) and Server (production environment) respectively:

Table 3 lists system requirements for MDM Studio and MDM Server on Windows XP Pro, Windows 7 or Windows Server 2003/2008 R2 with Apache Tomcat, Oracle WebLogic Server or IBM WebSphere Application Server.

Note: In case of Teradata Database Version 13.10 installation, make sure to install the Teradata database patch version 13.10.01.05.

Table 1: Hardware Requirements for Typical Workstation

Hardware Recommended

Processor 1 CPU (Dual Core)

Memory 4.0 GB

Disk Space 100 GB

Table 2: Hardware Requirements for Server

Hardware Recommended

Processor 2 CPU (Dual Core)

Memory 12.0 GB

Disk Space 200 GB

Master Data Manager Installation Guide 1


Table 4 lists system requirements for MDM Server on Windows Server Platform with Apache Tomcat, Oracle WebLogic Server or IBM WebSphere Application Server.

Table 3: Windows Workstation with Apache Tomcat, WebLogic Server or IBM WebSphere

Components Software Version Required For

Operating System Windows XP Pro, Windows 7 or Windows 2003/2008 R2

MDM Studio and Server

Development Environment Eclipse IDE for Java EE (Helios v 3.6 or Indigo v3.7)

MDM Studio

Application Server and JDK Oracle WebLogic Server 10.3 with Sun Java 6 (JDK)

Or

Oracle WebLogic Server (9.2 0r 10) with Sun Java 5 (JDK) Or

Or

IBM WebSphere Application Server 7.0 with IBM Java 6 (JDK)

Or

Apache Tomcat 6.0 Application Server with Sun Java 6 (JDK)

MDM Server

Database Server TD 13.0 or

TD 13.10 or

TD 14.0 (Including Express Versions)

Database Host

Database Client Teradata JDBC 13.10.00.03 or

Teradata JDBC 14.0 and TTU 14.0 BTEQ

MDM Server

Browser IE 7.0, 8.0, 9.0 or compatible or

Firefox 9.0

Adobe Flash Player 9 or higher

User Machine

Hierarchy Manager and Viewer as well as for soft error reports.

Table 4: Windows Server with Apache Tomcat, WebLogic Server or IBM WebSphere


Operating System Windows Server 2003/2008 R2 MDM Server

2 Master Data Manager Installation Guide


Table 5 lists system requirements for MDM Server on a VMware ESXi platform with Windows Server 2003/2008 R2 or SUSE Linux 10/11 and Apache Tomcat or BEA WebLogic running as a virtual machine.

Application Server and JDK Oracle WebLogic Server 10.3 with Sun Java 6 (JDK)

Or

Oracle WebLogic Server (9.2 0r 10) with Sun Java 5 (JDK) Or

Or


Or

Apache Tomcat 6.0 Application Server with Sun Java 6 (JDK)

MDM Server


TD 13.10 or


Database Host



MDM Server


Firefox 9.0


User Machine


Table 4: Windows Server with Apache Tomcat, WebLogic Server or IBM WebSphere


Table 5: VMware ESXi Platform Support for MDM Server


Virtual machine VMware ESX1 3.5 VM Host

Operating System Windows Server 2003/2008 R2 or SUSE Linux 10 MDM Server

Application Server and JDK BEA WebLogic Server 10.3 with Sun Java 6 (JDK)

Or

Apache Tomcat 6.0 Application Server with Sun Java 6 (SDK)

MDM Server


TD 13.10 or


Database Host



Table 6 lists system requirements for MDM Server on SUSE Linux Platform with Oracle WebLogic Server or IBM WebSphere Application Server.

Table 7 lists system requirements for MDM Server on AIX Platform with IBM WebSphere Application Server.



MDM Server


Firefox 9.0


User Machine


Table 5: VMware ESXi Platform Support for MDM Server


Table 6: SUSE Linux Platform support for MDM Server


Operating System SUSE Linux (SLES 9 or 10 or 11) MDM Server

Application Server and JDK Oracle WebLogic Server (9.2 or 10) with Sun Java 5 (JDK)

Oracle WebLogic Server 10.3 with Sun Java 6 (JDK)

Or

Apache Tomcat 6.0 Application Server with Sun Java 6 (SDK)

Or


MDM Server


TD 13.10 or


Database Host



MDM Server


Firefox 9.0


User Machine




Table 8 lists system requirements for MDM Server on Solaris Platform with Apache Tomcat Application Server.

Table 7: AIX Platform support with WebSphere Application for MDM Server


Operating System AIX 5.3, 6.1 MDM Server

Application Server and JDK IBM WebSphere Application Server 6.1 with IBM Java 5 (JDK)

Or


Or


MDM Server


TD 13.10 or


Database Host



MDM Server


Firefox 9.0


User Machine


Table 8: Solaris Platform with Apache Tomcat support for MDM Server


Operating System Solaris 10 MDM Server

Application Server and JDK Apache Tomcat 6.0 Application Server with Sun Java 6 (SDK)

MDM Server


TD 13.10 or

TD 14.0

Database Host

Database Client Teradata JDBC 13.10.00.03 or or


MDM Server


Firefox 9.0


User Machine



Chapter 1: MDM System RequirementsDatabase User Requirements

Note:• It is required to run MDM in Teradata mode by setting the mode in xserver.xml and

xserverweb.xml files as below:<db-url Value="jdbc:teradata://demotdat/TMODE=TERA"/>Default value for TMODE is set to TERA during the Teradata MDM Installation.

• Enable the browser to use Java 1.5.0_13 for applets. On Internet Explorer, click on Tools > Internet Options > Advanced tab > select the “Use JRE 1.5.0_13 for <applet>” option.

• When the Viewpoint is upgraded, the context.xml file on the Viewpoint server will be overwritten and the MDM <Resource> tags must be added back to the context.xml file.

• MDM application is best viewed with the below settings:Display resolution: 1024x768Display color: 65536 colors (minimum).Browser Type: Internet Explorer 7.0.8.0 and 9.0

Database User Requirements

The following user requirements and privileges are the minimal requirement for MDM to be installed on Teradata.

• Requires a USER database with a minimum of 12GB permanent space, 5GB spool space and 5GB temp space.Note: The MDM installer would check for a minimum of 200MB perm space, 50MB spool and temp space for the MDM user and 50MB perm space for all the MDM staging databases used in the MDM installation excluding Publication and Publication Audit. For CRDM Sandbox staging database, minimum perm space should be 200MB.Example:CREATE USER mdm AS PASSWORD=temppwd, PERM=12884901888, SPOOL=5368709120, TEMPORARY=5368709120;

• Database privileges• Grant the following rights as shown in the below example.

Example:GRANT CREATE MACRO, CREATE TABLE, CREATE VIEW, DELETE, DROP MACRO, DROP TABLE, DROP VIEW, INSERT, RETRIEVE, SELECT, UPDATE ON mdm TO mdm;

GRANT EXECUTE PROCEDURE, ALTER PROCEDURE, CREATE PROCEDURE, DROP PROCEDURE, EXECUTE ON mdm TO mdm;

Note: After MDM installation, the following rights can be revoked by the user. CREATE MACRO, DROP MACRO, CREATE PROCEDURE AND DROP PROCEDURE.

Note: The above listed access rights are required for schema generation or upgrade on MDM.



• For MDM Database User—on databases used for MDM topology based installation, grant the following rights as in the below example.Example: GRANT CREATE TABLE, CREATE VIEW, DELETE, DROP TABLE, DROP VIEW,

INSERT, SELECT, UPDATE ON mdm TO mdm;

• Grant select on all objects under dbc to the user (to be run as dbc)By default, MDM user would not require any explicit privileges on DBC, as user PUBLIC has select access to following DBC objects:COLUMNS, TABLES, INDICES, ALL_RI_CHILDREN, All_RI_PARENTS, DATABASES, ERRORMSGS, SHOWCOLCHECKS, SHOWTBLCHECKS, RI_DISTINCT_CHILDREN, DISKSPACE, DBCINFO, TABLESIZE, ALLRIGHTS, TRIGGERS, USERS

These are the only DBC objects that MDM would query.If PUBLIC has been explicitly revoked access on DBC then one needs to issue:GRANT SELECT ON dbc TO mdm; orGrant select on the listed above tables to mdm;

• For Geospatial access right—MDM database user Grant UDTUsage on SYSUDTLIB to <MDM_DB_User> with grant option.

• Publication: Requires a Publication Service DATABASE. This database should have enough space to hold the master data you may want to publish and can be a database that already exists in your Teradata EDW.Example:CREATE DATABASE mdm_PUB as PERM=100000000;

• Access rights—CRDM Sandbox GRANT CREATE TABLE, CREATE VIEW, DELETE, DROP TABLE, DROP VIEW, INSERT, SELECT, UPDATE ON <CRDM SANDBOX> to <MDM USER>;

Note: For any view with table referencing to a different database (X_DB), the CRDM SANDBOX should have SELECT, UPDATE, INSERT, DELETE WITH GRANT OPTION access on X_DB.

• Access rights—Non MDM • Source Registration—No access rights required for registering an external source.

Select access rights should be given for data profiling.GRANT SELECT ON <DB selected>.<Table_Name selected> TO <MDM USER>;

• Cleansing and StandardizationGRANT SELECT, UPDATE ON <NON MDM> TO <MDM USER>;

Note:1. Cleansing and Standardization rules work only on Simple Views.2. For any NON MDM view with table referencing to a different database (X_DB), the Non MDM DB should have SELECT and UPDATE WITH GRANT OPTION access on X_DB.

• MatchingGRANT SELECT ON <NON MDM> TO <MDM USER>;



• Survivorship GRANT SELECT ON <NON MDM> TO <MDM USER>;

• Configurable UIGRANT SELECT, UPDATE,INSERT,DELETE ON <NON MDM> TO <MDM USER> ;

Note:1. UPDATE, INSERT, DELETE operations work only on Simple Views2. For any NON MDM view with table referencing to a different database (X_DB), the Non MDM DB should have SELECT, UPDA.TE, INSERT, DELETE WITH GRANT OPTION access on X_DB

MDM and the Use of the Teradata Data Dictionary

MDM refers to few DBC metadata for its operation as most of the processing in MDM is dynamic and requires DBC metadata for constructing run time queries and processing logic.

In a large Teradata database system, performance issues would arise when MDM tries to access the DBC’s.

A solution to the above problem is implemented from MDM 2.01.01, by maintaining locally in MDM all the required DBC metadata (specific to a particular MDM installation). MDM access the following DBC tables either while copying the data locally or during the SG/ISG process.

• COLUMNS• TABLES• INDICES• ALL_RI_CHILDREN• ERRORMSGS• SHOWCOLCHECKS• DATABASES• All_RI_PARENTS• DBCINFO• TABLESIZE• ALLRIGHTS• TRIGGERS• DISKSPACE• USERS• SHOWTBLCHECKS• RI_DISTINCT_CHILDREN

The following list provides the MDM equivalent tables of the above DBC’s.

• SYS_DBC_COLUMNS• SYS_DBC_TABLES• SYS_DBC_INDICES



• SYS_DBC_ALL_RI_CHILDREN• SYS_DBC_ERRORMSGS• SYS_DBC_SHOWCOLCHECKS• SYS_DBC_DATABASES• SYS_DBC_ALL_RI_PARENTS

The following list provides the MDM views pointing to DBC objects directly.

Note: Local copy of the following tables are not created, as these tables are accessed occasionally and the data in these tables are very transient.• SYS_DBC_DBCINFO• SYS_DBC_TABLESIZE• SYS_ DBC_ALLRIGHTS• SYS_DBC_TRIGGERS• SYS_DBC_DISKSPACE• SYS_DBC_USERS

Certain MDM features like Schema Generation (SG), Incremental Schema Generation (ISG) and import from relational database directly refer to the DBC object due to its feature requirements.

By default, the SYS_DBC copies are refreshed (delete/insert) during ISG and SG, but can also be refreshed outside of SG/ISG because of the availability of the run time object creation feature in MDM.

Perform one of the following steps to refresh the MDM DBC copies:

• Execute REFRESH_SYS_DBC stored procedure using Admin UI after creating database objects.

• Or call refreshSysDBC x-rule from <MDM_Install_Directory>\cfg\xservice\toolkit\data\refreshSysViews.xml to execute REFRESH_SYS_DBC stored procedure.

• If views/versioned views are created in MDM outside of SG/ISG process for relational object then execute populateSysViewMap.bat/sh from <MDM_Install_Directory>\bin after performing above mentioned steps.

Note: Access right privileges from ‘Database roles’ are not checked while validating MDM users privileges.

Fallback on MDM Database Tables

You can enable fallback on MDM database tables using any of the following procedure:

• On the MDM Teradata Administrator, in Tools menu, point to Create and select Database. In the Create Database/User window, select the option Fallback. By default, the Fallback option would be selected.



• To directly enable fallback through MDM, run SG/ISG with NO-Run option. This generates the SQLs but does not execute them. The SQLs can then be edited to enable FALLBACK and schema can be generated thereafter.

Database Topology

The MDM database instance will contain separate and distinct databases to house the various permutations of tables as they are related to different services.

It is required to have a database user with the above mentioned permissions, access rights, and grant options. This database user may have other databases beneath it for MDM services: Input Staging, Output Staging, Master, Net Change, Publication Service, and Hierarchy Manager. These databases require all the necessary grant options from the database user.

By default, all staging services will be created under the user database. If desired, you can specify different databases for staging services, publication services and hierarchy manager service.

Note: It is mandatory to have a separate database for the Publication Service. See Figure 18 in chapter 2: “MDM Installation”.


Chapter 2: MDM and CRDM InstallationPackaging Overview

CHAPTER 2 MDM and CRDM Installation


This chapter provides guidelines for installing MDM.

Topics include:

• Packaging Overview• Installing MDM• Installing CRDM• Installing MDM Sample Application

Packaging Overview

The Teradata MDM Platform 03.02.00 package contains an MDM installation CD consisting of Teradata Software.

The CRDM solution will be available as an additional installer with MDM 03.02.00 release software. CRDM solution executable will load CRDM Solution package (Data model, specific party type UIs/workflows and seed data) and Sample applications into user selected database. User can then deploy the CRDM solution using the Deployment Manager.

Installing MDM

This section gives you step-by-step instructions for installing MDM from the Teradata Master Data Manager (MDM) 3.02.00 CD. Prior to installing MDM on your computer, make sure that you have the required hardware and software installed. See Chapter 1: “MDM System Requirements”.

Notes:

• If upgrading from previous version of Teradata MDM, see Chapter 9: “MDM Upgrade” before installing Teradata MDM 3.02.00.01.

• For TD Express 12.00.00, supported JDBC version is Teradata JDBC 12.00.00.01. In this case, replace existing Teradata jars at <MDM_Install_Directory>/lib with the three jar files (tdgssconfig.jar, tdgssjava.jar and terajdbc4.jar).

• In case of Teradata Database Version 13.10 installation, make sure to install the Teradata database patch version 13.10.01.05.


Chapter 2: MDM and CRDM InstallationInstalling MDM

• To enable CRDM features (Cleansing and Standardization, Matching and Survivorship) on database version 13.10 and above, perform the following steps:• Rename the following files keeping a backup of the existing MDMSPList.txt and

MDMBaseSPList.txt files.• <MDM_Install_Dir>/bin/ MDMSPList_13_10.txt to <MDM_Install_Dir>/bin/

MDMSPList.txt• <MDM_Install_Dir>/sql/teradata/ MDMBaseSPList_13_10.txt to

<MDM_Install_Dir>/sql/teradata/ MDMBaseSPList.txt.• Run the batch file <MDM_Install_Dir>/bin/compile_MDM_SP.bat/.sh.• Call the stored procedure: REFRESH_SYS_DBC().Note: CRDM features (Cleansing and Standardization, Matching and Survivorship) will not work on database version 13.00 and below.

• To enable web services, perform the following steps after installation:

a Extract the jar file 3rdPartyWebServiceJars.zip from <MDM_Install_Directory> and copy the jars from the "lib" and "module" to <MDM_Install_Directory>\web\mdmclient\WEB-INF/lib and <MDM_Install_Directory>\web\mdmclient\WEB-INF/modules respectively.

b Open web.xml from the location <MDM_Install_Directory>\web\mdmclient\WEB-INF and uncomment the following:<servlet>

<servlet-name>AxisServlet</servlet-name>

<servlet-class>org.apache.axis2.transport.http.AxisServlet</servlet-class>

<load-on-startup>1</load-on-startup>

</servlet>

<servlet-mapping>

<servlet-name>AxisServlet</servlet-name> <url-pattern>/services/*</url-pattern>

</servlet-mapping>

c For WebLogic 9.2, 10.3 and 10.3.1 apply the required patch. For WebLogic 9.2.3, no patch is required.You can download the patch from smart update. The Patch ID for different WebLogic version is given below:For WebLogic 10.3GA, Patch ID is IQXVFor WebLogic 9.2, Patch ID is VZEFFor WebLogic 9.2MP1, Patch ID is TP27.

For Tomcat 6 and above, perform the following steps:

a Copy activation.jar from <MDM_Install_Directory>/lib to <Tomcat_Install>\lib folder.



Note: For Tomcat with collapsed tier setup, copy activation.jar from <MDM_Install_Directory>/lib to <MDM_Install_Directory>/web/mdmclient/WEB-INF/lib folder along with the above step.

b Download httpcore-4.0.jar from http://hc.apache.org/downloads.cgi and copy to <Tomcat>/lib folder.

Note: Web services will not be available in MDM Analytical Installers.

Set the “Java” VM to be used by the installer: The installer is a Java based installer, hence requires a JDK to run the installation process. The installer looks for JDK versions in using JAVA_HOME variables and PATH variables. Refer to system requirements for the exact version of JDK to be used.

You can perform MDM installation with the help of the Wizard.

1 Double click the mdminstall executable to begin installation.• To install MDM on windows run mdminstall.exe.• To install MDM on AIX/LINUX run mdminstall.bin.

Note: Ensure to have sufficient free memory in /tmp folder for successful installation on AIX platform.

The Installer extracts all the files required for installation.The Welcome window (Figure 1) is displayed.


http://hc.apache.org/downloads.cgi


Figure 1: Welcome

2 On the Welcome window, read the information and click Next. Click Cancel to cancel installation.The License Agreement window (Figure 2) is displayed.



Figure 2: License Agreement

3 On the License Agreement window, read the agreement carefully and select I accept the terms of the License Agreement and then click Next. Click Previous to return to the previous screen.The LRDM Control Framework Integration window (Figure 3) is displayed.



Figure 3: LRDM Control Framework Integration

4 On the LRDM Control Framework Integration window (Figure 3), you can select the option to install control framework integration with MDM and click Next.Refer to MDM Platform Server Guide for more details on LRDM control framework integration.The Multiple LRDM Map Tables window (Figure 4) is displayed.



Figure 4: Multiple LRDM Map Tables

5 On the Multiple LRDM Map Tables window (Figure 4), • If you select No and click Next.

The JDK Location window (Figure 6) is displayed.• If you select Yes to configure multiple LRDM map tables and click Next.

The LRDM Map Tables (Figure 5) is displayed.



Figure 5: LRDM Map Tables

On the The LRDM Map Tables (Figure 5), enter the number of LRDM map tables and click Next.Notes:• If multiple table option is selected, make sure to enter multi table value in multiple

of 10 having maximum of 100. Default value is 10. Installation may take a bit longer based on the number of multi tables selected during the installation.

• If you are upgrading from the previous MDM 3.1.0.1 version, make sure to enter 100 for multi table value, in case if you have installed MDM 3.1.0.1 with multiple table option.

• The number of multiple tables cannot be changed post installation accompanied by schema generation. A fresh installation will be required if the number of tables need to be changed.

The JDK Location window (Figure 6) is displayed.



Figure 6: JDK Location

6 On the JDK Location window, specify the path of the JDK folder. For detailed information about the platform-specific JDK versions, see Chapter 1: “MDM System Requirements”. Either manually enter the location or click Choose to select the location and then click Next.Note: Ensure that you select JDK path not the JRE path. JDK is required to execute jar command during installation.The MDM Install Location window (Figure 7) is displayed.



Figure 7: MDM Install Location

7 On the MDM Install Location window, select the folder where you would like to install Teradata MDM. Click Choose to select the required folder and click Next.By default, C:\Teradata\MDM\3.02.00 folder is displayed.Note: A service parameter MDM_INSTALL_DIR in <MDM_Install_Directory>\cfg\properties\xserver.xml and <MDM_Install_Directory>\cfg\properties\xserverweb.xml holds the absolute MDM installation directory path. This parameter value can be retrieved and used from within the MDM PGL UI workflow or X-rules.Note: Skip step 8 for MDM installation on AIX/Linux machines.The MDM Shortcut window (Figure 8) is displayed.



Figure 8: MDM Shortcut

8 On the MDM Shortcut window, select the option to create product icons or select Don’t create icons and click Next.Note: Select Create Icons For All Users checkbox only if shortcut icons must be available to all users logging into the machine. Otherwise, the icons will be available only to the user installing the product.The Port Numbers window (Figure 9) is displayed.



Figure 9: Port Numbers

9 On the Port Numbers window, enter the port numbers for the MDM Locator and Server and click Next. By default, the numbers displayed are used. To edit the port numbers, refer to Chapter 2 Admin Tasks in the MDM Platform Server Guide.The E-Mail Configurations window (Figure 10) is displayed.



Figure 10: E-Mail Configurations

10 On the E-Mail Configurations window, enter the SMTP Host and the From Address (e-mail address) that will be used by MDM while generating emails and click Next.The Application Server window (Figure 11) is displayed.



Figure 11: Application Server

11 On the Application Server window, select WebLogic or WebSphere or Other (Manual Deployment) for Tomcat Server deployment and click Next.Note: Skip step 12 for Other (Manual Deployment).The WebLogic Configurations window (Figure 12) is displayed.



Figure 12: WebLogicConfigurations

12 On WebLogic Configurations window, enter the following:• enter the path for WebLogic config.xml file or click Choose to select the path.

Note: The default search performed by the installer may be time-consuming. It can hence be cancelled at any point by clicking Choose. The installer edits the config.xml file present in the specified directory. If the specification is incorrect, then the edit will not occur and the client will not start. Ensure that you enter the following just above the </Domain> tag in the config.xml file.

For Windows:<app-deployment> <name>mdmclient</name> <target>AdminServer</target> <module-type>war</module-type> <source-path>C:\Teradata\MDM\web\mdmclient</source-path> <security-dd-model>DDOnly</security-dd-model> </app-deployment> <admin-server-name>AdminServer</admin-server-name>

• enter the path for WebLogic startup script or click Choose to select the path.• enter the path for WebLogic stop script or click Choose to select the path.• enter the server name of the WebLogic instance.

The WebLogic server name (by default, it is “AdminServer”) should be in-sync with the Weblogic domain’s server name, else the Weblogic server will throw an error.



To use a different Weblogic server name, perform the following steps:

i create a new Weblogic domain and update the admin server’s name from default “AdminServer” to “TestServer” for example.

ii run the MDM installer. Choose Weblogic as the Application Server in step 11.

iii enter the server name of the Weblogic instance as TestServer and proceed with the installation.

• click Next.The Install Summary window (Figure 13) is displayed.

Figure 13: Install Summary

13 On the Install Summary window, all selected components and size requirements are displayed. Verify the displayed information for accuracy. If you want to make any changes, click Previous to return to a previous window to make the necessary changes and click Install.The Installing Teradata MDM Platform 3.02.00 (Figure 14) window is displayed.



Figure 14: Installing Teradata MDM Platform 3.02.00

Once the installation is successfully completed, the Database Settings window (Figure 15) is displayed.



Figure 15: Database Settings

14 On the Database Settings window, enter the Database Host Name, Database User and Database Password and click Next.The MDM database user details are required to login to database system where you want to install with separate staging databases.If the Encrypt Password option is selected, the password will be encrypted in the property file.The hostname alias can be found in the C:\WINDOWS\system32\drivers\etc\hostsExample:127.0.0.1 localhost12.105.248.20 tdv5 tdv5cop112.105.248.17 tdv6 tdv6cop110.20.17.14 localv6 localv6cop1

Here, localv6 is the host alias for the Teradata node 10.20.17.14.The Please Wait window is displayed. It checks for the database settings and perm/spool/temp space and Geospatial access rights. If no errors/warnings, then the The Names for Staging Databases window (Figure 18) is displayed.The warnings would be displayed in case if any warnings encountered. Figure 16 and Figure 17 display some sample warning messages. Correct the warnings and then continue with the installation to avoid errors during schema generation.



Note: Warning on Geospatial (SYSUDTLIB) usage gets displayed during MDM Installation, if the MDM database user does not have UDT usage access right on SYSUDTLIB database. Please provide the required access right if Geospatial data type support is required else ignore these warnings and schema generation process will continue.

Figure 16: Error/Warnings

Figure 17: Error/Warnings



Figure 18: Names for Staging Databases

15 On the Names for Staging Databases window, enter the names for physical databases for predefined staging areas as per your naming conventions and click Next.Note: These physical databases must already exist in your Teradata system and have the appropriate permissions granted. See “Chapter 1 MDM System Requirements.”The predefined staging areas are used as repositories as below:• Master—repository for storing MDM Master staging tables.• Input—repository for storing MDM Input staging tables.• Output—repository for storing MDM Output staging tables. • Version—repository for storing MDM Version staging tables.• Netchange—repository for storing MDM Netchange staging tables.• Publishing Service—repository for storing publishing target tables.• Publishing Audit—repository for storing publishing audit history tables.• Hierarchy Manager—repository for storing Hierarchy and hierarchy version related

tables.• CRDM Sandbox—repository for storing CRDM Source tables and Match process

results tables.



Note: MDM installation will progress only if you provide a valid database name for CRDM Sandbox and MDM databases cannot be used as CRDM Sandbox. The MDM user should have DDL and DML rights on CRDM Sandbox.

The Please Wait window would be displayed. It checks for any database and access rights. If no errors/warnings then the Schema Generation window (Figure 20) is displayed.If any warnings/errors encountered, the warning messages would be displayed. Figure 19 displays sample warning messages.

Figure 19: Warnings Window

Correct the warnings and then continue with the installation to avoid errors during schema generation.



Figure 20: Schema Generation

Note: Preparing a database for use by MDM is an optional post-installation operation that is performed by the installer.This action consists of creating the MDM schema and loading system data into the database specified in the previous step.

16 On the Schema Generation window, select Yes or No depending on whether this action is required to be performed now or later and click Done.Note: Preparing the database is a pre-requisite for MDM Server to start.For detailed instructions on manually preparing the database before attempting to start the server, see Chapter 3: “MDM Database Preparation”.The database preparation program uses the MDM Xcore Server which uses the other parameters specified in the previous step to connect to the database. Ensure that the specified information is correct; else the database preparation program will fail.Note: During the Service Setup process, you may get warnings as below under Validating Model set section (output of Model Validator process).These warnings can be ignored and schema generation process can continue to perform with these warnings. Please check if there are any other errors apart from below list to correct them in custom model.• AttributeSet's name is a RESERVED word• AttributeSet's name is a RESERVED word• GroupClass's name is a RESERVED word



• GroupClass's name is a RESERVED word• GroupMaster's name is a RESERVED word• GroupMaster's name is a RESERVED word• GroupingRule's name is a RESERVED word• GroupingRule's name is a RESERVED word• QueryExecutionLog's result is a RESERVED word• QueryExecutionLog's result is a RESERVED word• QueryParam's parameter is a RESERVED word• QueryParam's sequence is a RESERVED word• QueryParam's parameter is a RESERVED word• QueryParam's sequence is a RESERVED word• RelationalObjProperties's Name is a RESERVED word• RelationalObjProperties's Nullable is a RESERVED word• RelationalObjProperties's Name is a RESERVED word• RelationalObjProperties's Nullable is a RESERVED word• SystemProperties's type is a RESERVED word• SystemProperties's type is a RESERVED wordThe Install Complete window (Figure 21) is displayed.



Figure 21: Install Complete

17 On the Install Complete window, click Done. If errors/warnings occurred during the install, the installation log file path is displayed to check the errors. If no errors/warnings during installation, then the Install log file would display as below:DB Status-------------No Warnings/Errors.For space/access rights warnings, the following would be displayed in the install log file:DB Status-------------Character Set: Default character set to LATIN.User Space Status: Insufficient Perm/Spool/Temp space for user. Insufficient Perm Space for User, Required 200 MB Min. Please assign minimum space stated above to avoid potential schema generation failures.Access Rights on User: mdm_latest having access rights.Access Rights on DBC: mdm_latest having sufficient access rights on DBC.Access Rights on Staging Databases: Having default access rights on Staging Databases.


Chapter 2: MDM and CRDM InstallationInstalling CRDM

Minimum required Space for Staging Databases: Insufficient Perm Space for staging database. Insufficient Perm Space for mdm_hm. Please assign Minimum 50 MB Perm space for staging database/s stated above to avoid potential schema generation failures.

Installing CRDM

This section gives you step-by-step instructions for installing CRDM from the Teradata Master Data Manager (MDM) 3.02.00 CD. Prior to installing CRDM on your computer, make sure that you have installed base MDM.

Note: After CRDM installation, make sure to override changes on base MDM, if mutliple LRDM tables option was seleted during base MDM installation. For detailed steps on override changes, see Section : “Override Changes on Base Toolkit (MDM) Tables and Scripts”.

You can perform CRDM installation with the help of the Wizard.

1 Double click the mdminstall executable to begin installation.• To install MDM on windows run crdminstall.exe.• To install MDM on AIX/LINUX run crdminstall.bin.

Note: Ensure to have sufficient free memory in /tmp folder for successful installation on AIX platform.

The Installer extracts all the files required for installation.The Introduction window (Figure 22) is displayed.



Figure 22: Introduction

2 On the Introduction window (Figure 22), read the information and click Next. Click Cancel to cancel installation.The Choose MDM Server Installation Folder window (Figure 23) is displayed.



Figure 23: Choose MDM Server Installation Folder

3 On the Choose MDM Server Installation Folder window (Figure 23), specify the base MDM installation location and click Next.The Choose Applications to Upload window (Figure 24) is displayed.



Figure 24: Choose Applications to Upload

4 On the Choose Applications to Upload window (Figure 24), select the required application to upload to the database by clicking the corresponding checkbox and then click Next.The Database Settings window (Figure 25) is displayed.




5 On the Database Settings window (Figure 25), enter the Teradata data system name, Database Name, Database User and Database Password and click Install.The MDM database user details are required to login to database system. The Installing Teradata MDM CRDM window (Figure 26) is displayed.



Figure 26: Installing Teradata MDM CRDM

If any warnings/errors encountered, the warning messages would be displayed. The Install Complete window (Figure 27) is displayed.


Chapter 2: MDM and CRDM InstallationInstalling MDM Sample Application


6 On the Install Complete window (Figure 27), click Done. Once the CRDM installation is complete, use Deployment Manager to load the CRDM data. See Chapter 7: “MDM Deployment Manager” for more details.

Installing MDM Sample Application

This section gives you step-by-step instructions for installing sample application. Prior to installing sample application on your computer, make sure that you have installed base MDM.

You can perform sample application installation with the help of the Wizard.

1 Double click the platformsampleapplication executable / runtimesampleappplication executable to begin installation.• To install MDM on windows run platformsampleapplication.exe /

runtimesampleapplication.exe from the <MDM_Installtion_Directory>/bin.The Installer extracts all the files required for installation.The Introduction window (Figure 28) is displayed.




2 On the Introduction window (Figure 28), read the information and click Next. Click Cancel to cancel installation.The Choose MDM Server Installation Folder window (Figure 29) is displayed.




3 On the Choose MDM Server Installation Folder window (Figure 29), specify the base MDM installation location and click Next.The Database Settings window (Figure 30) is displayed.




4 On the Database Settings window (Figure 30), enter the Teradata data system name, Database Name, Database User and Database Password and click Install.The MDM database user details are required to login to database system. The Install Complete window (Figure 31) is displayed.




5 On the Install Complete window (Figure 31), click Done. Once the MDM sample application installation is complete, use Deployment Manager to load the sample data. See Chapter 7: “MDM Deployment Manager” for more details.


Chapter 3: MDM Database PreparationPreparing Database for MDM

CHAPTER 3 MDM Database Preparation


This chapter provides information about MDM schema generation and incremental schema generation recommended approach.

Topics include:

• Preparing Database for MDM• Troubleshooting MDM Database Preparation

Preparing Database for MDM

While preparing the database for MDM, you may face with two possible database scenarios: empty database or database with existing MDM schema.

1 Empty database: schema generation on empty database can be achieved by general database processes. Based on the review process, there are two possible cases:• Create schema without reviewing DDLs

You can create schema without any review using any of the below methods:

i During MDM installation, select generate database option. This will create the required schema and populate data into it.

ii During MDM installation, select no database option. After the installation is complete, open <MDM_Install_Directory>\bin folder. Add user Id, password and JDBC URL to dbadd.txt and run the script call_tk_gendb.bat/ call_tk_gendb.sh.

iii During MDM installation, select no database option. After the installation is complete, open MDM Studio and select Solution Setup. Ensure that the services appear in the same order as in gen_schema.bat as in Figure 32.



Figure 32: Solution Setup—Select Services

Select Generate Schema options as in Figure 32. To populate the static data and create remaining tables and views, select Upload Service Static Data in the Setup Static Data panel and complete the process. This process creates the schema.

• Review DDLs before creating schema



During MDM installation, select no database option. After the installation is complete, open MDM Studio and select Solution Setup. Ensure that the services appear in the same order as in gen_schema.bat and select Generate Schema options as in Figure 32.Update the generateTable tag value to false, <generateTables Value="false" /> in the xservice files at the below locations and perform solution setup. <MDM_Install_Directory>/cfg/properties and<MDM_Install_Directory>/custom/<AppName>/cfg/propertiesThis process creates SQL files in <MDM_Install_Directory>/db and/or <MDM_Install_Directory>/custom/<AppName>/db folderfolder containing DDLs, triggers, views and stored procedures. See Section : “Manually Executing SQLs Generated by MDM Schema Generation Process”.

2 Database containing existing MDM schemaModifications to existing data model can be persisted using Incremental Schema Generation. Based on the review process, there are two possible cases:• Execute DDLs without review

You can execute DDLs without review using any of the below methods:

i Run the script call_incr_gendb.bat/ call_incr_gendb.sh from <MDM_Install_Directory>\bin.

ii Open MDM Studio and select Solution Setup. In the Generate Schema panel, select the option Generate Incremental Schema and Run and if need to upload static data, select Upload Service Static Data in the Setup Static Data panel as in Figure 33 and complete the process.

Figure 33: Solution Setup—Generate Schema and Setup Static Data Panel

• Review DDLs before executingOpen MDM Studio and select Solution Setup. In the Generate Schema panel, select the option Generate Incremental Schema SQL only as in Figure 34 and complete the process.



Figure 34: Solution Setup—Generate Schema Panel

This process creates SQL files in <MDM_Install_Directory>/db and/or <MDM_Install_Directory>/custom/<AppName>/db folder containing DDLs, triggers, views and stored procedures. See Section : “Manually Executing SQLs Generated by MDM Schema Generation Process”.If you need to run/upload static data, then refresh static data and recreate the remaining tables and views. On Windows, open incr_gendb.bat and comment the below lines:

echo Started Creating Incr Schema......call incr_gen_schema.bat

sleep 15

On Unix based system, open incr_gendb.sh and comment the below lines:echo Started Creating Incr Schema......

. ./incr_gen_schema.sh

sleep 15

Note: To comment a line in script files use REM in case of Windows and # in case of Unix.Run the script call_incr_gendb.bat/call_incr_gendb.sh. This will in turn call the scripts incr_static_data_upload.bat/incr_static_data_upload.sh and incr_gen_tables_and_views.bat/incr_gen_tables_and_views.sh.The script incr_gen_tables_and_views.bat/incr_gen_tables_and_views.sh calls the following procedures which can be reviewedCREATE_SNAPSHOTSCREATE_GTTCREATE_AUTHORIZATION_VIEWSREFRESH_SYS_DBC

Note: Refer to the SQL file generated during the ISG/Solution Setup for comments of type Errors or Warnings. If there are comments for errors or warnings in the SQL file, resolve the errors or ensure that it does not lead to data loss.

Manually Executing SQLs Generated by MDM Schema Generation Process

Note: MDM application must create DDL when publishing target tables and while rendering hierarchies.

Schema generation process creates SQL files in <MDM_Install_Directory>\db folder containing DDLs, triggers, views and stored procedures. Each SQL file will correspond to


Chapter 3: MDM Database PreparationTroubleshooting MDM Database Preparation

each service participating in schema generation process. For example, for BCM_MASTER, the output SQL file will be generated in <MDM_Install_Directory>\db folder as below:

1 Whatever file name given (../db/master.sql) mentioned in the service file in case of schema generation process from Script files or Incremental Schema Generation process of Studio.

Review those SQL files and execute them on database using any database client like SQL Assistant or BTEQ.

Note: While performing solution setup from Studio on empty schema, xserver.sql file will be generated for all documents defined in the xserver.xml. Execute xserver.sql file before executing SQLs for below services in that case.

Execution order of the SQL files should correspond to the following order of services:

• BPE_META• BCM_MASTER• E2E• BCM_OUTPUT_STAGING• BCM_INPUT_STAGING• BCM_NET_CHANGE• USER_SECURITY• MESSAGING• DATA_PROFILING• DATAUPLOAD• OMS_MESSAGE_SERVICE• BPE_UI• TIMER_SINK• VALIDATION• UI_WORKFLOW• ADMIN_UI• MDM_HM• BCM_VERSION_STAGING

Troubleshooting MDM Database Preparation

If you chose not to prepare the database during the installation process, or if you have selected Yes in Figure 20 in chapter 2 MDM Installation, but encountered errors during the process, then follow the steps described in this section, before attempting to start the server.

In case the database parameters specified during installation were incorrect, the following file need to be modified with correct database parameters.



1 Editing the dbadd.txt file. These following parameters must be corrected:In <MDM_Install_Directory>\bin\dbadd.txt. Replace tokens DB_USER, DB_PASSWORD, DB_HOST, with corresponding values of the target database.db.userId=DB_USERdb.userPassword=DB_PASSWORDdb.url= jdbc:teradata://DB_HOSTencrypt=Truedb.driver= com.teradata.jdbc.TeraDriverdb.meta-info-file= com/teradata/xcore/dblib/tera.xml

For example:db.userId=mdmdb.userPassword=mdmdb.url=jdbc:teradata://10.20.17.15encrypt=Truedb.driver=com.teradata.jdbc.TeraDriverdb.meta-info-file=com/teradata/xcore/dblib/tera.xml

Files to Execute

Execute one of the following program files as per the installation type that you have selected, once you have edited the files as described above.

For Windows:

Execute <MDM_Install_Directory>\bin\call_tk_gendb.bat

For UNIX:

If you chose Toolkit installation, execute <MDM_Install_Directory>/bin/call_tk_gendb.sh

These files write logs called tk_gendb.log in the <MDM_Install_Directory>/logs directory during the runs. At the end of the run, tk_gendb will be merged into a single file called gendb.log.

Check the messages displayed on the console. Ensure that no error messages exist in the logs. The most common error message to watch for is: “Unable to connect to database”. This message results when some of the database parameter specified above are incorrect. Repeat the above steps until the program executes without errors.

Note: To use database objects created in MDM outside of SG/ISG process to manage object from MDM has to follow this procedure:• Execute REFRESH_SYS_DBC stored procedure using Admin UI after creating database

objects.• Or you can call refreshSysDBC x-rule from

<MDM_Install_Directory>\cfg\xservice\toolkit\data\refreshSysViews.xml to execute REFRESH_SYS_DBC stored procedure.

• If views/versioned views are created in MDM outside of SG/ISG process for relational object then execute populateSysViewMap.bat/sh from <MDM_Install_Directory>\bin after performing above mentioned steps.



Override Changes on Base Toolkit (MDM) Tables and Scripts

MDM upgrade process provides easy and controlled access to migration from one MDM release to another. There will be cases that base MDM schema or the operation scripts will be changing between releases to cater enhancements, issues or new requirements.

Perform below steps to override base model if there are any changes to base MDM schema before performing upgrade or preparing database for custom application. Ideally this should be performed before doing Schema Generation or Incremental Schema Generation to avoid errors in database preparation.

Please check MDM Release Definition for any schema or scripts related changes for underlying MDM release.

Overriding Schema

Perform the following steps to override schema:

1 Open the required custom MDM application in MDM Studio.2 On the MDM Studio, expand Services, expand BCM_MASTER, right click on Model

Instances and click Override Dictionary to override any dictionary changes as in Figure 35.



Figure 35: Override Changes

3 Right click on Model Instances and click Override Document to override any schema changes.

4 Perform step2 and step3 for Custom models created using Toolkit model and if there are any changes to the custom model.

5 Perform Service Setup either from Studio or using out of the box Schema/Incremental Generation Scripts.

6 Perform Solution Setup either from Studio (refer to chapter 7 Custom Application in MDM Platform Developer Guide.pdf) or using the out of the box Schema/Incremental Generation Scripts.



For more details on solution setup and service setup, refer to chapter 7 Custom Application in MDM Platform Developer Guide.pdf and chapter 4 Process Modelling in MDM Platform Studio Guide.pdf

Overriding Scripts

Please check MDM Release Definition for any schema or scripts related changes for underlying MDM release.

1 Compare the scripts for any such changes for the underlying MDM release.2 Make the necessary changes to the scripts mentioned in the MDM Release Definition.3 Make the necessary changes to the custom scripts if any, used for Schema Generation or

Incremental Schema Generation to sync the scripts with base MDM scripts.Note: If publication objects are created on base MDM tables, then while performing upgrade to newer version of MDM, publication objects are required to be recreated to the newer MDM version.


Chapter 4: MDM WebClient DeploymentWebClient Deployment in IBM WebSphere

CHAPTER 4 MDM WebClient Deployment


This chapter provides information about MDM Webclient deployment.

Topics include:

• WebClient Deployment in IBM WebSphere• WebClient Deployment in BEA WebLogic• WebClient Deployment on Tomcat 6.0

WebClient Deployment in IBM WebSphere

The MDM WebClient is deployed on AIX 5.3 using IBM WebSphere 6.1.

General Instructions

1 Install WebSphere and note the default admin port, transport port, and application server name.

2 The installer copies the mdmclient.war file to <MDM_Install_Directory>/web/websphere/mdmclient.

3 Install Teradata client on the server where you installed WebSphere.4 After the installation, run the WebSphere Admin Server.

/opt/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1 depending on the WebSphere profile used (AppSrv01, AppSrv02 etc).Specify the server name as server1 after the startServer.sh file, where server1 is the default server.

Installing the Application

1 Log into the WebSphere Administration User Interface. On the left navigation menu, click Applications and Install New Application.

2 Select the Remote file system and specify the location of the mdmclient.war file. (For example <MDM_Install_Directory>/web/mdmclient/mdmclient.war).

3 Enter the Context Root as mdm and click Next.The Select Installation Options screen is displayed.

4 Select the Distribute Application option.5 Specify the application name as mdm.



6 Deselect the Create MBeans for Resources option.7 Retain default values for the rest of the properties and click Next.8 In the Map modules to servers screen, select MDM and click Next.9 In the map virtual host for Web modules screen, leave the default value default_host.10 Select MDM and click Next.11 In the Summary window, click Finish.

This will install the application.12 After successful installation of the MDM application, click on the “Save to Master

Configuration” link and on the next screen, click Save.You will now be on the home page of the Administration User Interface.

Setting up JVM Properties

1 On the left navigation menu, click Servers --> Application Servers --> <your WebSphere application server name> to launch the server details on the right hand side of the page.

2 In the Configuration tab, go to Server Infrastructure Section > Java & Process Management > Process Definition Link

3 In the Additional Properties section, select Java Virtual Machine.4 On the Java Virtual Machine window, set the General Properties --> Initial Heap Size and

Maximum Heap Size properties to 512 and 1024 respectively.5 In the Java Virtual Machine window, select Custom Properties and set the following two

properties:"Name=javax.xml.parsers.DocumentBuilderFactoryValue= org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"Name = javax.xml.transform.TransformerFactoryValue = org.apache.xalan.processor.TransformerFactoryImpl

6 Save these properties.

Globalization (UTF-8) Setting

Note: This is an optional step and is required only if user has special characters that are not part of the Latin character set.

1 On the WebSphere Admin console, in the left navigation menu, click Servers --> Application Servers --> <your WebSphere application server name> (example, server1) to launch the server details on the right hand side of the page.

2 Under the Configuration tab, go to Server Infrastructure Section > Java & Process Management > Process Definition Link as in Figure 36.



Figure 36: WebSphere Console - Application Server

3 In the Additional Properties section, select Java Virtual Machine as in Figure 37.



Figure 37: WebSphere Console - Application Server -Additional Properties

4 On the Java Virtual Machine window, in the Generic JVM arguments field, enter -Dclient.encoding.override=UTF-8 as in Figure 38.



Figure 38: WebSphere Console - Application Server -Additional Properties

5 Restart the server


Chapter 4: MDM WebClient DeploymentWebClient Deployment in BEA WebLogic

Save and Run

1 After saving all configurations when prompted, logout of the Administration Console. From the command line stop the WebSphere Application Server by executing the following command./opt/WebSphere/AppServer/profiles/AppSrv01/bin/stopServer.sh server1 depending on the WebSphere profile used (AppSrv01, AppSrv02 etc).

2 Run the below command to start MDM Server and Locator:<MDM_Install_Directory>/bin>./startAll.sh or <MDM_Install_Directory>/bin>sh startAll.sh on AIX/UNIX<MDM_Install_Directory>/bin>startAll.bat on WINDOWS

3 Start the WebSphere Application Server by executing the following command./opt/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1 depending on the WebSphere profile used (AppSrv01, AppSrv02 etc).Note: Ensure that the MDM Server and Locator are up and running before starting the WebSphere Application Server.

4 In the log files, ensure that there are no Teradata, x2, or WebSphere errors.5 After the server is up with no errors, enter the following URL:

http://<host>:<port>/mdmWhere host is the host and port is the HTTP Transport port of the WebSphere instance to which MDM is connected. Note that the port number is different for the administration console and the application URL. By default, the user name and password for the administrator are admin.By default, port number of first WebSphere profile (appsrv01) is 9080 that is, value of <port> will be 9080 for the first profile created. Please note down <port> number while creating new profile on WebSphere 6.1.

Note: In Linux, after setting support for UTF-8 and UTF-16, displays the result in incorrect format. The workaround is given below. Perform the following steps in Linux: • In Linux console, enter edit ~/.bashrc• Check whether the command “export LC_CTYPE=en_US” is written to the file, else

enter the command and save it by pressing Esc+:+wq.• If the command already exists, close the file without saving by pressing Esc+q+!• Run the installer or either run extracti18n_new.sh from location

<MDM_Install_Directory>\web\mdmclient\bin• Restart the MDM server and Application server to see the required changes.

WebClient Deployment in BEA WebLogic

The MDM WebClient is deployed using WebLogic 9.2. The installer performs the necessary configuration to WebLogic’s config.xml properties file, such that the MDM Web Client starts (or stops) whenever WebLogic is started (or stopped).


Chapter 4: MDM WebClient DeploymentWebClient Deployment on Tomcat 6.0

Note: If using WebLogic 10 for Webclient deployment, the below warning message would be displayed on the WebLogic console.

“javax.xml.parsers.FactoryConfigurationError: Provider org.apache.xerces.jaxp.SAXParserFactoryImpl could not be instantiated: java.lang.NullPointerException”

Workaround: Add xercesImpl.jar and xml-apls.jar from MDM 3rd party jars to <WEBLOGIC10>\user_projects\domains\<DOMAIN_NAME>\lib.

The following entry is made by the installer in config.xml (where the value of attribute Path depends on the location of the MDM installation):

For Windows:<app-deployment>

<name>mdmclient</name> <target>AdminServer</target> <module-type>war</module-type> <source-path><MDM_Install_Directory>\web\mdmclient</source-path> <security-dd-model>DDOnly</security-dd-model>

</app-deployment> <admin-server-name>AdminServer</admin-server-name>

Finally, launch the UI by starting a browser, and entering the following URL:

http://<host>:<port>/mdmWhere host is the host and port is the port of the WebLogic instance to which MDM is connected.

Login with User ID and Password as ‘admin’.

To avoid ‘Out of Memory’ errors in WebLogic, modify JVM startup parameters in startWeblogic.cmd to setup the heap size and other attributes.

Note: To install two instances of MDM, you must setup two domains on the WebLogic Server.

WebClient Deployment on Tomcat 6.0

Starting from MDM 2.01.02 product release, MDM installer will provide support to deploy the MDM web client on any other required application server.

Pre-requisites

Following list provides the pre-requisites:

1 JDK 1.5 should be installed.2 MDM 3.01.00 should be installed with database generated.3 Tomcat 6.0 application server should be installed.4 JAVA_HOME environment variable should be set as in



Figure 39: Environment Variables—Java_Home Setting

Deployment Steps

Note: Please take back up of installed web component <MDM_Install_Directory>\web folder before performing below changes.

1 Changes to Tomcat 6.0 for MDM web client deploymentBelow listed configuration changes required for Tomcat application server files for successful MDM web client deployment.• Setting up context for MDM (<Tomcat_Install>\conf\catalina\localhost)

Create below listed folder structure in Tomcat installation:• <Tomcat_Install>\conf\catalina\localhost

localhost should be hostname.• Create [context].xml for MDM application and copy at above location.

[context] should be application context (that is mdm etc.). Below is the mdm.xml file for reference.<?xml version='1.0' encoding="UTF-8"?><Context path="/mdm" debug="4" privileged="true" docBase="<MDM_Install_Directory>/web/mdmclient" crossContext="true"> <Manager pathname="" maxInactiveInterval="-1" maxIdleBackup="-1"/></Context>



• Changes to web.xml of (<TOMCAT_INSTALL>\conf) Update web.xml with below snippet.<servlet> <servlet-name>jsp</servlet-name> <servlet-class>org.apache.jasper.servlet.JspServlet</servlet-class> <init-param> <param-name>fork</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>compilerSourceVM</param-name> <param-value>1.5</param-value> </init-param> <init-param> <param-name>xpoweredBy</param-name> <param-value>false</param-value> </init-param> <init-param> <param-name>tagpoolMaxSize</param-name> <param-value>0</param-value> </init-param> <load-on-startup>3</load-on-startup> </servlet>

• By default, port number for Tomcat is 8080.• Copy activation.jar from <MDM_Install_Directory>/lib to <Tomcat_Install>\lib

folder.Note: For Tomcat with collapsed tier setup, copy activation.jar from <MDM_Install_Directory>/lib to <MDM_Install_Directory>/web/mdmclient/WEB-INF/lib folder along with the above step.

• Download httpcore-4.0.jar from http://hc.apache.org/downloads.cgi and copy to <Tomcat>/lib folder.

Application Startup and Login

1 Start the Locator and MDM server using startup scripts provided with MDM 3.01.00 release.

2 Start the Tomcat Application Server using startup.bat/.sh from Tomcat Install.3 Launch MDM web UI by starting a browser and entering the following URL: http://

<host>:<port>/mdmwhere host is the host and port is the port of the Tomcat instance to which MDM is connected.

4 Login to MDM Web UI with user name and password as “admin”.Note: To avoid ‘Out of Memory’ errors in Tomcat, modify JVM startup parameters in catalina.bat to setup the heap size and other attributes.

Log Files

1 MDM log files are generated under <MDM_Install_Directory>\log folder.2 For Admin_UI and UI_Workflow MDM services, log files are generated under

<Tomcat_Install_DIR>\bin folder.


http://hc.apache.org/downloads.cgi


3 Refer to Server.log of Tomcat Server for detailed log information.


Chapter 5: Launch MDM Server and ClientServer

CHAPTER 5 Launch MDM Server and Client


This chapter provides detailed information about starting the MDM server and client.

Topics include:

• Server• Client

Server

On Windows, the MDM Server can be started (or stopped) from the Program Group that was created for MDM during the installation.

Navigate to Start > Programs > Teradata MDM Platform <version no> > Start Teradata MDM Server (or Stop Teradata MDM Server).

The underlying batch programs can be alternatively used to start and stop the server.

On Windows, they are <MDM_Install_Directory>\bin\startAll.bat and <MDM_Install_Directory>\bin\stopAll.bat respectively.

On UNIX, they are <MDM_Install_Directory>/bin/startAll.sh and <MDM_Install_Directory>/bin/stopAll.sh respectively.

Note: The MDM server must be started before starting the client. The default memory heap size settings for the MDM server have been specified as “-Xms256m -Xmx512m “. You can modify these as required by configuring the startServices.sh or startServices.bat files located at <MDM_Install_Directory>/bin.

Client

On Windows (for WebLogic):

1 Start the MDM Client from the program group that was created for MDM during the installation.

2 Navigate to Start > Programs > Teradata MDM Platform <version no> > Start WebLogic Server.

3 Click Start WebLogic Server from the MDM Program Group.


Chapter 5: Launch MDM Server and ClientClient

This internally triggers the startWeblogic.cmd program located in the WebLogic directory specified during installation.

On Windows (for Tomcat):

1 Navigate to <Tomcat_Install_DIR>\bin.2 Double Click on startup.bat/sh script to Start Tomcat Server.

On UNIX (for WebSphere):

1 Start the WebSphere Application Server by executing the following command./opt/WebSphere/AppServer/profiles/AppSrv01/bin/startServer.sh server1 depending on the WebSphere profile used (AppSrv01, AppSrv02 etc).


Chapter 6: MDM Silent InstallationSilent Installation

CHAPTER 6 MDM Silent Installation


This chapter describes the procedure for setting up Teradata Master Data Manager installer to run in the silent installation mode.

Topics include:

• Silent Installation• Silent Mode Installation Process

Silent Installation

Silent Installation is a mode of installation where in, you do not monitor the setup and provide input via dialog boxes. All inputs required by the product installer are read from an external text file (usually called a “silent install properties file”). Silent installation is recommended, only if a product needs to be reinstalled on multiple machines or on the same machine. Once the properties file is setup, the silent installation runs without user intervention.

Silent Mode Installation Process

Silent mode installation process has two main steps:

1 Create a properties file with settings for properties as listed in Table 9. See Appendix A: “Silent Installer Property Files” for sample properties files.For the detailed procedure, see “Creating a Silent Mode Installation Property File for MDM”.

2 Start the silent-mode installation process and use the values specified in the property file. For the detailed procedure, see “Starting the Silent Mode Installation Process on Windows System”.Note: 1. Silent mode installation requires the same temporary disk space and uses the same temporary storage directories as a standard installation. The installation program does not prompt you if there is no enough space in the temporary directory.2. A silent mode installation takes the same amount of time as a standard installation. At the beginning of the silent mode installation, an initial installation program window or message appears briefly indicating that the installation has started. No message is displayed to indicate the installation progress or for successful completion.


Chapter 6: MDM Silent InstallationSilent Mode Installation Process

Creating a Silent Mode Installation Property File for MDM

When you install Teradata MDM in silent mode, the installation program uses a property file (See Appendix A) to determine the installation options. Before you run the installation program in silent mode, you must create the silentInstaller properties file with your installation options.

Note: During silent mode installation, the installation program does not validate entries in the silentInstaller properties file. If there are errors in the silentInstaller properties file, the installation would fail.

To create property file in the silent mode installation:

1 Copy the contents of the property file (Appendix A) and save it as a text file named silentInstaller.properties in the directory containing the Teradata MDM installer.

2 In the silentInstaller.properties file, modify the values for the keywords as in Table 9.

Table 9: MDM Silent Mode Installation Property Values

Variable Required Example

INSTALLER_UI Yes Silent

USR_JAVA_HOME Yes C:\\Program Files\Java\jdk1.5.0_13

USER_INSTALL_DIR Yes C:\\Teradata\MDM

USER_SHORTCUTS Yes C:\\Documents and Settings\BB185047\Start Menu\Programs\Teradata MDM Platform 2.0.0 - for Windows only not for Linux.

PORTS Yes \”12005\”,\”14446\”

PORTS_1 Yes 12005

PORTS_2 Yes 14446

PORTS_BOOLEAN_1 No

PORTS_BOOLEAN_2 No

EMAIL_INFO (optional) No \”relay1.daytonoh.teradata.com\”,\”[email protected]

EMAIL_INFO1 (optional) No relay1.daytonoh.teradata.com

EMAIL_INFO2 (optional) No [email protected]

EMAIL_INFO_BOOLEAN_1 No

EMAIL_INFO_BOOLEAN_2 No

SERVER_INFO Yes, if WebLogic is chosen as application server

\”Weblogic\”,\”\”

SERVER_INFO_1 Yes, if Weblogic is chosen as application server

Weblogic



SERVER_INFO_2 Yes, if WebSphere is chosen as application server

WebSphere

SERVER_INFO_3 Yes, if Manual (others) deployment is chosen as application server

Others

SERVER_INFO_BOOLEAN_1 Yes, if WebLogic is chosen as application server

1 - Incase of Weblgoic

0 - Incase of Others

SERVER_INFO_BOOLEAN_2 Yes 1- Incase of WebSphere

0- Incase of Others

SERVER_INFO_BOOLEAN_3 Yes 1- Incase of Others

0- Incase of Weblogic/WebSphere

CONFIG_XML Yes, if WebLogic is chosen as application server

Config.xml

CONFIG_XML_DIR Yes, if WebLogic is chosen as application server

C:\\bea9.2\user_projects\domain\newdomain\config\

In case of Linux, provide the required path.

START_WLS Yes, if WebLogic is chosen as application server

startWeblogic.cmd


START_WLS_DIR Yes, if WebLogic is chosen as application server

C:\\bea9.2\user_projects\domain\newdomain\bin


STOP_WLS Yes, if WebLogic is chosen as application server

stopWeblogic.cmd


STOP_WLS_DIR Yes, if WebLogic is chosen as application server

C:\\bea9.2\user_projects\domain\newdomain\bin


WEBLOGIC_SERVER_NAME Yes, if WebLogic is chosen as application server

\”AdminServer\”

WEBLOGIC_SERVER_NAME_1 Yes, if WebLogic is chosen as application server

AdminServer

DB_INFO_1 Yes qauser09

DB_INFO_2 Yes qauser09

DB_INFO_3 Yes batgirl.td.teradata.com

ENCRYPT Yes 1

ENCRYPT No 0





Starting the Silent Mode Installation Process on Windows System

To start the silent mode installation process on Windows system:

1 Login to the Windows system.2 Open an MS-DOS command prompt.3 Navigate to the directory that contains the installation file and start the installation

procedure by entering the following command. Ensure to specify the full pathname of the silent install property file:filename.exe -f path_to_silent_install_.properties

For example:mdminstall.exe -fC:\Teradata\properties\silentInstaller.properties

Start the Server and Client

See Chapter 5: “Launch MDM Server and Client”.

STG_DB_NAME_1 Yes master

STG_DB_NAME_2 Yes input

STG_DB_NAME_3 Yes output

STG_DB_NAME_4 Yes netchange

STG_DB_NAME_5 Yes publication

STG_DB_NAME_6 Yes pubaudit

STG_DB_NAME_7 Yes hierarchy

STG_DB_NAME_8 Yes version

PREPARE_DATA Yes, if you want to generate schema

\”Yes\”,\”\” for schema generation

\”\”,\” No\” for schema generation

PREPARE_DATA_1 Yes, if you want to generate schema

Yes

PREPARE_DATA_2 Yes, if you don’t want to generate schema

No

PREPARE_DATA_BOOLEAN_1=1 Yes 1- Incase of schema generation

0- Incase of no schema generation

PREPARE_DATA_BOOLEAN_2=0 Yes 0 - Incase of schema generation

1 - Incase of no schema generation




Chapter 7: MDM Deployment ManagerDeploying Custom/Sample/CRDM Application

CHAPTER 7 MDM Deployment Manager


The MDM Deployment Manager provides the ability to create a runtime deployment package from a Studio MDM application project and move/deploy this code from ‘development’ to ‘QA’ to ‘production’ environments.

MDM Deployment Manager addresses the deployment of applications built in Studio to other servers within a customer’s Teradata environment. It does not address the installation of MDM Studio, Server or Database, as that is still handled by the MDM installation and schema generation.

Topics include:

• Deploying Custom/Sample/CRDM Application• Changing Database Password• Debugging Deployment Process

Deploying Custom/Sample/CRDM Application

The MDM Deployment Manager consists of two parts:

1 A function within Studio to package the directories and files created in Studio for an MDM application and then insert the CLOB into the MDM Deployment database and table(s).

2 An InstallAnywhere executable for retrieving the application package from the database and deploying it to an existing MDM installation on another system. InstallAnywhere provides a GUI for ease-of-use installation on any platform (Windows, AIX and Linux in our case).

For details on the 1st part, refer to MDM Platform Studio User Guide.

Perform the following steps to retrieve an application package from the Deployment database and to deploy it to an existing MDM installation on another system:

1 Double click the Deployment Manager executable to begin installation. • To deploy an application on windows run DeploymentMgr.exe. • To deploy an application on AIX/LINUX run DeploymentMgr.bin.The Introduction window (Figure 40) is displayed.




2 On the Introduction window (Figure 40), read the information and click Next.The Deploy Custom Application/Sample Application/Change Password window (Figure 41) is displayed.Note: 1. On the production environment, as the xserver.xml and xserverweb.xml files are not packaged with the deployment manager, it is the responsibility of the user to manually Activate the wsdl and add an entry in the xserver.xml and xserverweb.xml file under <wsdl-client-config> as shown in the code snippet below:<wsdlLocations>

<wsdlLocation Value="..\wsdl\Test\GoogleSearchService.wsdl" Group="Test" Version="2"/></wsdlLocations>

The above changes must be done before you do the custom Application deployment using deployment manager, so that when coloc.jar is generated for collapsed mode it will always have the wsdl added/activated.2. If the deployment mode is collapsed then the wsdl files needs to be copied to the Application Server. For Tomcat and Weblogic deployments, copy the whole wsdl folder from the development environment to the production environment under <AppServer_Install_Directory>.



Figure 41: Deploy Custom Application/Sample Application/Change Password

3 On the Deploy Custom Application/Sample Application/Change Password window (Figure 41), select the option Deploy Custom / Sample Application by clicking the corresponding radio button and click Next.The Choose MDM Server Installation Folder window (Figure 42) is displayed.



Figure 42: Choosing MDM Server installation Folder

4 On the Choose MDM Server Installation Folder window (Figure 42), select the location of the MDM platform installation and click Next.The Database Setting window is displayed.




5 On the Database Setting window, enter the required details for the deployment database and click Next.• Teradata Data System Name -> refers to the Teradata Database system hostname

(mdmSystem/mdm etc.) where your projects (Custom MDM applications) are stored.• Database Name -> refers to the database (within MDM User) where your custom

project are stored (using MDM Studio). Deployment Manager refers to this database to fetch the list of archived/stored MDM custom Projects.

• Database User and Password -> refers to the MDM database user where you want to login to refer to above Database.

Note: You can have your custom projects under different Databases (can be staging database as well). Deployment Manager refers to this database to fetch archived/stored (using MDM Studio) MDM custom Projects. Note: If the entered details on the Database Setting window are not correct, the connection fails and the Incorrect DB Information window is displayed as in Figure 44. Re-enter the details and try again to establish the connection.



Figure 44: Incorrect DB Information

The Enter Project ID & Your Name window (Figure 45) is displayed. Displays the list of all the versions of all the projects that have been deployed in the Deployment database.

Figure 45: Enter Project ID & Your Name

6 On the Enter Project ID & Your Name window (Figure 45), enter your name and enter the ID of the project that needs to be deployed onto the target system and click Next.The name is required for auditing purpose as this information will be logged under DEPLOY_LOG table to audit who deployed which application etc.The Please Choose Mode of Deployment window (Figure 46) is displayed.



Figure 46: Please Choose Mode of Deployment

7 On the Please Choose Mode of Deployment window (Figure 46), select the appropriate deployment mode and click Next. Note: For collapsed mode, the following jars have to be explicitly added to the application server (Websphere/Weblogic/Tomcat) classpath in the same order.1. <MDM_Install_Diectory>/web/mdmclient/WEB-INF/lib/customcoloc.jar (in case of custom/sample application, this has to be added first). 2. <MDM_Install_Diectory>/web/mdmclient/WEB-INF/lib/coloc.jarFor details on manual collapsed mode setup, refer to Appendix Collapsed Tier Setup in MDM Platform Studio User Guide.The Database Preparation window (Figure 47) is displayed.



Figure 47: Database Preparation

8 On the Database Preparation window (Figure 47), select the required option and click Next.The Import the rolled-up data window (Figure 48) is displayed.



Figure 48: Import the rolled-up data

9 On the Import the rolled-up data window (Figure 48), select Yes to import the rolled-up data and click Done.If the MDM data is exported using the Deployment Manager on Studio, select yes to import. By default, the No option is selected. If Yes is selected, the Deployment Manager calls the loadRolledupData.bat/sh file toupload the documents available in the rolledupData folder.A log file rolledupData.log is created at:<MDM_Install_Directory>\custom\AppName\log.The Rolled-up Services/Tables Names window (Figure 49) is displayed.



Figure 49: Rolled-up Service/Table Names

10 On the Rolled-up Services/Tables Names window (Figure 49), click Next.The Install Complete pop-up (Figure 50) is displayed.




11 On the Install Complete pop-up, click Done. Refer to Section B-Sample Application in MDM Platform Developer Guide.pdf for detailed steps on how to create a custom application.Note: 1. The file that deployment manager executes to generate the schema must be named as call_incr_custom_gendb.bat for Windows and call_incr_custom_gendb.sh for UNIX. This is the file that will be called when Schema Generation is selected as Yes. The other required files have been listed in Chapter Deployment Manager of MDM Platform Studio User Guide.Deployment Manager always deploys an application incrementally. The assumption is that base MDM has been installed and the base MDM schema is already present.Note: 2. The log file to log the output of the custom schema generation and seed data load process must be named as incr_custom_gendb.log so that the deployment manager can check the successful completion of the process.Note: 3. For verification, refer to Teradata MDM Deployment Manager Install.log in the <MDM_Install_Directory> once the deployment is complete.


Chapter 7: MDM Deployment ManagerChanging Database Password

Changing Database Password

In MDM, a password change option has been introduced through deployment manager. If database password needs to be updated because of corporate policy to change passwords on a periodic basis, through deployment manager it can be done without any manual change of file.

Perform the following steps to change the database password.

1 Double click the Deployment Manager executable.• To deploy an application on windows run DeploymentMgr.exe.• To deploy an application on AIX/LINUX run DeploymentMgr.bin.The Introduction window (Figure 51) is displayed.


2 On the Introduction window (Figure 51), read the information and click Next. The Deploy Custom Application/Sample Application/Change Password window (Figure 52) is displayed.



Figure 52: Deploy Custom Application/Sample Application/Change Password

3 On the Deploy Custom Application/Sample Application/Change Password window (Figure 52), select the option Change Password by clicking the corresponding radio button and click Next.The Choose MDM Server Installation Folder window (Figure 53) is displayed.



Figure 53: Choosing MDM Server installation Folder

4 On the Choose MDM Server Installation Folder window (Figure 53), select the location of the MDM platform installation and click Next.The Enter New Password window (Figure 54) is displayed.



Figure 54: Enter New Password

5 On the Enter New Password window (Figure 54), enter the new password and click Next.The Password Changed Successfully (Figure 55) is displayed.


Chapter 7: MDM Deployment ManagerDebugging Deployment Process

Figure 55: Password Changed Successfully

6 On the Password Changed Successfully window, click Done.Note: In case of Websphere deployment, after performing change password process, regenerate coloc.jar manually using the below steps: • Unwar the mdmclient.war file from <MDM_Install_Directory>/web.• Replace the xserver.xml and xserverweb.xml file with xserver.xml and

xserverweb.xml file from <MDM_Install_Directory>/cfg/properties.• Execute mkcoloc.bat/mkcoloc.sh from <MDM_Install_Directory>/web/mdmclient/

bin.• Redeploy mdmclient.war into Websphere.

Debugging Deployment Process

While deploying custom/sample application, a deployment debug log (Teradata MDM Deployment Manager_<sampleapplication>_debug.log) file is created in the MDM base Installation folder. The debug log file lists the deployment stages along with the errors and warnings if any as below:

• Displays error if any while changing permissions for custom/sample_project and its sub folder.



• Display information if bcmenv.bat/.sh does not exist• Displays information if /cfg/properties/<PROJ_NAME>.xml / <PROJ_NAME>-

input.xml / <PROJ_NAME>-output.xml / <PROJ_NAME>-version.xml / <PROJ_NAME>-netchange.xml does not exist

• Displays error if calling /bin/call_custom_incr_gendb.bat / .sh prior to execution.• Displays the status of schema generation.• Displays error if calling /bin/loadRolledupData.bat / .sh prior to execution.

Note: In case of the Collapsed Tier deployment, below mentioned file path are relative to <MDM_Install_Directory>.

• Displays error if any on Backup of xserver.xml• Displays error if any while copying cfg/properties to /web/mdmclient/WEB-INF/bcm/cfg/

properties• Displays error if any while copying mdm-spec-gen.xml meta-enabled-srvc-filenames.xml

from bin to WEB-INF\bcm\cfg\properties• Displays error if any while renaming xserver.xml.bkp as xserver.xml• Displays error if any while copying cfg/xservice to /web/mdmclient/WEB-INF/bcm/cfg/

xservice• Displays error if any while copying x2_unix.properties as x2.properties • Displays error if any while copying x2.properties as x2_coloc.properties• Displays error if any while calling mkcolocjar.bat / .sh. prior to execution.• Displays error if any while calling mkcustomcolocjar.bat / .sh prior to execution.• Displays the status of inserting deployment details in database.• Displays the status of MDM Client WAR file creation for Websphere Deployment and any

error if encountered.• Displays installation successful if there is no error as below.


Chapter 8: MDM Patch InstallationMDM Patch Installation

CHAPTER 8 MDM Patch Installation


This chapter provides information on MDM patch installation.

Topics include:

• MDM Patch Installation

MDM Patch Installation

The MDM patch installer provides the ability to install patches of MDM using Install Anywhere executable. It comes as MDMPatchInstaller.exe/bin for both Windows/Unix platforms and applies the patch on top of the appropriate MDM installations.

Note: Prior to installing the MDM patch on your computer, make sure that you have the appropriate base MDM installed. Ensure to read the Readme document of the patch before proceeding with the patch installation.

You can perform MDM patch installation with the help of the Wizard.

1 Double click the MDMPatchInstaller executable to begin installation.The Introduction window (Figure 56) is displayed.




2 On the Introduction window, read the information and click Next.The Choose MDM Server Installation Folder window (Figure 57) is displayed.




3 On the Choose MDM Server Installation Folder window, specify the path of the base MDM and click Install.The Installer extracts all the files required for installation.The Database Upgradation window (Figure 58) is displayed.



Figure 58: Database Upgradation

4 On the Database Upgradation window, choose Yes or No depending on whether this action is required to be performed now or later and then click Next.Note: If you select No, refer to readme document for manually upgrading the database.The Install Complete window (Figure 59) is displayed.




5 On the Install Complete window, click Done.Note: The build_info_<version number>.xml file in the <MDM_Install_Diectory> contains all the build information.The Teradata MDM Patch <version number> Install.txt file in the <MDM_Install_Diectory> contains all the log details.Note: If the MDM base installation is deployed in collapsed tier mode, the patch will also be applied in the collapsed mode.Note: If WebLogic is used as the Web application server: Clear the cache from <WL_HOME>\domains\<DOMAIN_NAME>\servers\AdminServer\tmp and <WL_HOME>\domains\<DOMAIN_NAME>\servers\AdminServer\stage. Delete all the folders from these two locations and then restart the MDM and WebLogic servers.If WebSphere is used as the Web application server: the MDM war (mdmclient.war) need to be redeployed. See Chapter 4: “MDM WebClient Deployment” for deployment instructions.Clear the IE browser cache (Tools->Internet Options->Delete Files, check the box "Delete all offline content").


Chapter 9: MDM UpgradeIntroduction

CHAPTER 9 MDM Upgrade


This chapter provides information on MDM server software and database upgrade process.

Topics include:

• Introduction• Custom Application Upgrade• Upgrade Process

Introduction

Figure 60 displays the consistent upgrade process.

Figure 60: Upgrade Process

The following list provides the upgrade steps:

1 Perform Pre-Upgrade SetupThis step can be performed anytime prior to the actual upgrade execution.

2 Execute appropriate Backups (Database and Application as required)This step must be performed prior to the actual upgrade execution.

3 Perform Pre-Upgrade Validations 4 Perform Database Upgrade (Stored Procedures Compilation and Database Changes)5 Perform Application Metadata Upgrade6 Perform Application Upgrade Validation

This step must be performed after the actual upgrade execution.7 Perform Post-Upgrade Cleanup


Chapter 9: MDM UpgradeCustom Application Upgrade

This step can be performed anytime after the actual upgrade execution, although a Backup is recommended to be performed immediately.

Custom Application Upgrade

The following are the pre-requisites for upgrading a Custom Application:

1 Installed MDM 3.01.01 with Custom Application (Working installation)2 Install MDM 3.02.00.01 pointing to 3.01.01 database with No_Schema

In order to upgrade a custom MDM application to Teradata MDM 3.02.00.01 release, perform the following steps:

1 Copy Custom application from <MDM_3.1.1_Install>\custom\CustomAppName to <MDM_3.2.0.1_Install>\custom\CustomAppName• Copy Custom application files from

<MDM_3.1.1_Install>\web\mdmclient\custom\CustomAppName to <MDM_3.2.0.1_Install>\web\mdmclient\custom\CustomAppName

• Copy Custom application files from <MDM_3.1.1_Install>\web\mdmclient\WEB-INF\custom\CustomAppName to <MDM_3.2.0.1_Install>\web\mdmclient\WEB-INF\custom\CustomAppName

2 Perform the below mentioned upgrade process to complete the upgrade. Make sure to override Base MDM and Custom Application model/dictionary using MDM Studio if there are any model changes and then perform the service setup before performing Schema generation for Custom Application.Note: Refer to the MDM Platform 3.02.00 Release Definition for the list of files changed for base MDM.

Upgrade Process

The MDM 3.02.00.01 upgrade process consist of the following steps:

• Pre Upgrade Check• The Actual Upgrade• Post Upgrade Check• Back Down ProcedureNote:• Please read section Section : “Backdown Procedure for MDM,” before running the

upgrade process.• This upgrade procedure from MDM 3.01.01 to MDM 3.02.00.01 is not RESTARTABLE.• Please see Chapter 1: “MDM System Requirements,” for database user access rights.


Chapter 9: MDM UpgradeUpgrade Process

1 Pre Upgrade CheckPerform below steps before executing upgrade steps:

a Take MDM database backup using backdown procedure as in section “Backdown Procedure for MDM”.

b Install MDM 3.02.00.01 in a new location. Make sure to select the same options (that is, Multitable and Control Framework) during installation as MDM 3.01.01 installation.

c During MDM 3.02.00.01 installation, point to the previous existing (3.01.01) MDM database.

d Choose Generate Schema as NO.

e Unzip the contents of Upgrade_3_2_0_1.zip into the <MDM_3.02.00.01_Install_Directory>. Please extract the UpgradeScripts_MDM_3.02.00.zip to the present folder using the "Extract Here" option.

f Before running the upgrade process, please update LOGIN_INFO.SQL file with the TDPID and the MDM DB username and Password.

g Before running the upgrade process, please update <ENTER_CRDM_SANDBOX_DB_NAME> and <ENTER_FM_MATCH_DB_NAME> parameters in Insert_Db_Param.sql file with the Cleansing Sandbox database and the FM_Match database names respectively. Please note that both of these database names are same as provided at MDM3.2 install time for Cleansing Sandbox database.Location: <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\LOGIN_INFO.SQLthat is, logon TDPID/MDMDBUSER,MDMDBUSERPWD;

2 Actual UpgradePerform the below listed upgrade steps:

a Migrate/Deploy Custom Application from MDM 3.01.01 to MDM 3.02.00.01 install directory using the (<MDM_3.02.01_Install_Dir>\bin\DeploymentMgr.exe) deployment manager.

b During Custom Application deployment 3.02.00.01 installation, point to the previous existing (3.01.01 CustomApp's Project ID) Custom Application without ISG.The MDM Studio Plug-in for Eclipse is updated with MDM 3.02.00.01 release. Please replace the existing MDM Studio plug-in.

c Compile stored procedure <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Upgrade_3_2\UPGRADE_THREE_TWO.sql

d Compile stored procedure <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Drop_Obsolete_tabl



es\UPGRADE_THREE_TWO_DROP_UNUSED.sql (optional: in case user wants to perform step 10)

e Navigate to <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Pre_Upgrade_Check and run Pre_Upgrade_Check.bat/shA file gets created with report PRE_UPGRADE_DBSCHEMAINFO.TXT. Read the report and proceed with Upgrade if Report is positive, else follow the steps mentioned in the report.

f Navigate to <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Upgrade_3_2\ and run UPGRADE_THREE_TWO.bat/sh. Verify the log file (UPGRADE_THREE_TWO_BTEQ) created for no failures.

g In case you choose to perform the step "i" you need to delete GPM directory from the following location<MDM_3.02.00.01_Install_Dir>\cfg\xservice\toolkit\model-instance\models\Toolkit Models\<MDM_3.02.00.01_Install_Dir>\models\Toolkit\models\Toolkit Models\<MDM_3.02.00.01_Install_Dir>\web\mdmclient\WEB-INF\bcm\cfg\xservice\toolkit\model-instance\models\Toolkit Models\<MDM_3.02.00.01_Install_Dir>\custom\custom_toolkit\cfg\xservice\custom_toolkit\model-instance\models\Toolkit Models\

h Navigate to <MDM_3.02.00.01_Install_Dir>\custom\custom_toolkit\bin and Run call_custom_incr_gendb.bat/sh to perform the Custom ISG.

i Delete obsolete tables. This is optional step.Navigate to <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Drop_Obsolete_tables\ and Run Drop_Obsolete_tables.bat/shMake sure with the list of tables (mentioned below) that will be dropped. This can be done before or after ISG. Tables that will be dropped includes:DQ_TEMPTAB_CNT,

ERR_ATTRIBUTE_SET,ERR_ATTRIBUTE_SET_DETAIL,ERR_GROUP_CLASS,ERR_GROUP_GPM_ATTRIBUTE,ERR_GROUP_MASTER,ERR_GROUP_MEMBER,ERR_GROUPING_RULE,ERR_GRP_CLSS_GPM_ATTR_SET,ERR_SVRTY_CNT_TEMP,ERR_VALID_GRP_DIMENSIONS,FAVORITE_DETAILS,GT_ATTRIBUTE_SET,



GT_ATTRIBUTE_SET_DETAIL,GT_GROUP_CLASS,GT_GROUP_GPM_ATTRIBUTE,GT_GROUP_MASTER,GT_GROUP_MEMBER,GT_GROUPING_RULE,GT_GRP_CLSS_GPM_ATTR_SET,GT_VALID_GRP_DIMENSIONS,MST_ATTRIBUTE_SET,MST_ATTRIBUTE_SET_DETAIL,MST_GROUP_CLASS,MST_GROUP_GPM_ATTRIBUTE,MST_GROUP_MASTER,MST_GROUP_MEMBER,MST_GROUPING_RULE,MST_GRP_CLSS_GPM_ATTR_SET,MST_VALID_GRP_DIMENSIONS,OUT_ATTRIBUTE_SET,OUT_ATTRIBUTE_SET_DETAIL,OUT_GROUP_CLASS,OUT_GROUP_GPM_ATTRIBUTE,OUT_GROUP_MASTER,OUT_GROUP_MEMBER,OUT_GROUPING_RULE,OUT_GRP_CLSS_GPM_ATTR_SET,OUT_VALID_GRP_DIMENSIONS,VER_ATTRIBUTE_SET,VER_ATTRIBUTE_SET_DETAIL,VER_GROUP_CLASS,VER_GROUP_GPM_ATTRIBUTE,VER_GROUP_MASTER,VER_GROUP_MEMBER,VER_GROUPING_RULE,VER_GRP_CLSS_GPM_ATTR_SET,

VER_VALID_GRP_DIMENSIONS

Verify the log file(Drop_Obsolete_tables) created for no failures

j Static Data migration • Start the MDM locator and server from the base MDM installation (that is,

<MDM_3.02.00.01_Install_Dir>\bin)• Execute file

<MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Upgrade_3_2\Call_Upgrade_Static_Data_3_02.bat/sh to upload MDM 3.02 static data.A file gets created with log Upgrade_3_02.log

• If Control Framework is enabled, execute file <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Upgrade_3_2\Ca



ll_Upgrade_CTLFW_Statc_data_3_02 .bat/sh to upload MDM 3.02 Control Framework static data.A file gets created with log Upgrade_CTLFW_Statc_data_3_02.logNote:1. Please bring down the MDM and Locator server and restart again.2. Static Data Migration must be performed only once.

k If you have custom left navigation data created for your custom application, you need to follow the readme provided at <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Left Nav Migration.zip.

l Navigate to <MDM_3.02.00.01_Install_Dir>\Upgrade_Scripts_3_02_00_01\Post_Upgrade_Check and run Post_Upgrade_Check.bat/shPOST_UPGRADE_DBSCHEMAINFO.TXT will provide you with the Report of UPGRADE

m Clean Weblogic/WebSphere/Tomcat application cache and start application server.In case of Weblogic server, clear cache from:<WL_HOME>\user_projects\domains\<my_domain>\servers\AdminServer\tmp

3 Post Upgrade CheckLogin to MDM and verify that everything is working correctly.

Backdown Procedure for MDM

This section describes how to restore the MDM database in case of any upgrade failures or otherwise.

Before every major change to the database or as a standard practice of data warehousing maintenance, any Applications database including MDM will generally be backed-up periodically using Teradata B.A.R solutions.

As the solution described below is a Teradata Arcmain solution, so before performing this step, refer the Arcmain manuals for more details.

Note: Use the same MDM database user for Restore/Copy process unlike the standard practice of using ADMIN Id's. It is assumed that, the user id used for Archive/restore has been given the archive and restore access rights.

For detailed information on database user requirements, see “Chapter 1 MDM System Requirements”

1 Using Arcmain, archive all the data tables belonging to the MDM user ( including the underlying database’s if database topology is used, you could use the "ALL" option, if the database's used in the MDM installation are descendents of the MDM USER). The backup media could be data disks, tapes or any other industry standard solutions.

2 Ensure that step 1 is successful by verifying backed up media for its correctness.



3 Perform an Arcmain RESTORE for all the archived database's after cleaning up the database's (you could use delete database command in the script as well).Note that RESTORE is different from COPY. When a database is restored, all the database objects, including triggers and PK/FK links are copied unlike copy, which DOESN'T COPY the Trigger's and PK-FK links. If ARC copy is employed then, you will have to manually copy or write scripts to create triggers and referential integrity constraints.

4 Run Revalidate references command to validate the restore/copy, this could be done from the Restore/copy script as well.

5 Verify that the restore is successful by comparing the archived and restored database.6 Verify the entries in SYS_DB_MAP are right, if not update appropriately.7 If everything runs correctly till step 6, try to point the MDM application to this restored

database. All the MDM functionality should continue to work as before.


Chapter 10: MDM UninstallationWindows

CHAPTER 10 MDM Uninstallation


This chapter discusses MDM uninstallation process.

Topics include:

• Windows• UNIX

To uninstall the MDM application, follow the steps according to the appropriate operating system headings below. For additional information, contact your System Administrator.

Uninstalling prior versions of the Master Data Manager application is not mandatory in order to install the current version.

Note: Uninstalling after using the “Silent Install” will also be “Silent”. No prompts will be given.

Windows

To uninstall MDM on Windows:

1 Navigate to Start > Programs > Teradata MDM Platform 3.02.00 > Uninstall Teradata MDM Platform 3.02.00The Uninstall Teradata MDM Platform 3.02.00 window is displayed.


Chapter 10: MDM UninstallationWindows

Figure 61: Uninstall Teradata MDM Platform 3.02.00

2 On the Uninstall Teradata MDM Platform 3.02.00, click Uninstall.The Uninstall Complete window is displayed.


Chapter 10: MDM UninstallationUNIX

Figure 62: Uninstall Complete

3 On the Uniinstall Complete window, click Done.

UNIX

Uninstalling Master Data Manager in UNIX

1 Execute the uninstaller program located in <MDM_Install_Directory>. From the command prompt, run the following file:./ <MDM_Install>/Uninstall_Teradata_MDM/Uninstall_Teradata_MDM_Platform_3.02.00

2 Stop the WebSphere application server.Note: While uninstalling, installer comments out the application configuration entry that it makes inside Config.xml of WebLogic during installation. If MDM is not uninstalled properly, this step will not happen. This may lead to issues when starting WebLogic after reinstallation of MDM.


Chapter 10: MDM UninstallationUNIX


APPENDIX A Silent Installer Property Files

What’s In This Appendix

This appendix provides the silent installer property files.

Topics include:

• Silent Installer Property File without Schema• Silent Installer Property File with Schema

Silent Installer Property File without Schema

The following section provides the silent installer property file without schema.

To install MDM with control framework integration, setCTLFW_YES=1 CTLFW_NO=0

To install MDM without control framework integration, set

CTLFW_YES=0 CTLFW_NO=1

To configure multiple BMAP tables, set

BMAP_YES=1BMAP_NO=0

Enter number of BMAP tables,

NO_OF_BMAPS=10(enter multi table value in multiple of10 having maximum of 100. Default value is 10)

To configure single BMAP table, set

BMAP_YES=0BMAP_NO=1

INSTALLER_UI=silentUSR_JAVA_HOME=C:\\Program Files\\Java\\jdk1.5.0_13

USER_INSTALL_DIR=C:\\Teradata\\MDM27_Property

USER_SHORTCUTS=C:\\Documents and Settings\\BB185047\\Start Menu\\Programs\\Teradata MDM Platform <version no.>

PORTS=\"12005\",\"14446\"PORTS_1=12005PORTS_2=14446PORTS_BOOLEAN_1=


Appendix A: Silent Installer Property FilesSilent Installer Property File with Schema

PORTS_BOOLEAN_2=

EMAIL_INFO=\"smtpserver.com\",\"[email protected]\"EMAIL_INFO_1=smtpserver.comEMAIL_INFO_2=myName@myCompany.comEMAIL_INFO_BOOLEAN_1=EMAIL_INFO_BOOLEAN_2=

SERVER_INFO=\"Weblogic\",\"\"SERVER_INFO_1=WeblogicSERVER_INFO_2=SERVER_INFO_BOOLEAN_1=1SERVER_INFO_BOOLEAN_2=0

CONFIG_XML=config.xmlCONFIG_XML_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\config\\

START_WLS=startWebLogic.cmdSTART_WLS_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\bin\\

STOP_WLS=stopWebLogic.cmdSTOP_WLS_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\bin\\

WEBLOGIC_SERVER_NAME=\"AdminServer\"WEBLOGIC_SERVER_NAME_1=AdminServerWEBLOGIC_SERVER_NAME_BOOLEAN_1=

DB_INFO_1=qauser09DB_INFO_2=qauser09DB_INFO_3=batgirl.td.teradata.comENCRYPT_YES=1ENCRYPT_NO=0

STG_DB_NAME_1=masterSTG_DB_NAME_2=qauser09STG_DB_NAME_3=qauser09STG_DB_NAME_4=qauser09STG_DB_NAME_5=pub_serSTG_DB_NAME_6=pub_audSTG_DB_NAME_7=hierar

PREPARE_DATA=\"\",\"Yes\"PREPARE_DATA_1=YesPREPARE_DATA_2=PREPARE_DATA_BOOLEAN_1=0PREPARE_DATA_BOOLEAN_2=1

Silent Installer Property File with Schema

This section provides the silent installer property file with schema.

If you want control framework, setCTLFW_YES=1 CTLFW_NO=0

If you don’t want control framework, set



CTLFW_YES=0 CTLFW_NO=1

If you want multiple BMAP tables, set

BMAP_YES=1BMAP_NO=0

Enter number of BMAP tables,

NO_OF_BMAPS=10(enter multi table value in multiple of10 having maximum of 100. Default value is 10)

If you don’t want multiple BMAP tables, set

BMAP_YES=0BMAP_NO=1

INSTALLER_UI=silentUSR_JAVA_HOME=C:\\Program Files\\Java\\jdk1.5.0_13

USER_INSTALL_DIR=C:\\Teradata\\MDM27_Property

USER_SHORTCUTS=C:\\Documents and Settings\\BB185047\\Start Menu\\Programs\\Teradata MDM Platform <version no.>

PORTS=\"12005\",\"14446\"PORTS_1=12005PORTS_2=14446PORTS_BOOLEAN_1=PORTS_BOOLEAN_2=

EMAIL_INFO=\"smtpserver.com\",\"[email protected]\"EMAIL_INFO_1=smtpserver.comEMAIL_INFO_2=myName@myCompany.comEMAIL_INFO_BOOLEAN_1=EMAIL_INFO_BOOLEAN_2=

SERVER_INFO=\"Weblogic\",\"\"SERVER_INFO_1=WeblogicSERVER_INFO_2=SERVER_INFO_BOOLEAN_1=1SERVER_INFO_BOOLEAN_2=0

CONFIG_XML=config.xmlCONFIG_XML_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\config\\

START_WLS=startWebLogic.cmdSTART_WLS_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\bin\\

STOP_WLS=stopWebLogic.cmdSTOP_WLS_DIR=C:\\bea9.2\\user_projects\\domains\\NewDomain\\bin\\

WEBLOGIC_SERVER_NAME=\"AdminServer\"WEBLOGIC_SERVER_NAME_1=AdminServerWEBLOGIC_SERVER_NAME_BOOLEAN_1=

DB_INFO_1=qauser09DB_INFO_2=qauser09DB_INFO_3=batgirl.td.teradata.com



ENCRYPT_YES=1ENCRYPT_NO=0

STG_DB_NAME_1=masterSTG_DB_NAME_2=qauser09STG_DB_NAME_3=qauser09STG_DB_NAME_4=qauser09STG_DB_NAME_5=pub_serSTG_DB_NAME_6=pub_audSTG_DB_NAME_7=hierar

PREPARE_DATA=\"Yes\",\"\"PREPARE_DATA_1=YesPREPARE_DATA_2=PREPARE_DATA_BOOLEAN_1=1PREPARE_DATA_BOOLEAN_2=0


APPENDIX B MDM Database Sizing Guidelines

What’s In This Appendix

This appendix provides information on MDM database sizing guidelines.

Topics include:

• Introduction• Sizing Requirements for Table Class/Source Combination Defined on MDM Facets

Introduction

The MDM installer does not provide database creation feature, it is the duty of the Database Administrator to create the set of databases that comprise an instance of MDM. Logically, MDM is arrayed into distinct logical staging areas that contain the tables based upon their declared Class and Source values on MDM Sys Table Map Facet tab. These logical staging areas are physically represented through a set of databases. The Database Administrator has the privilege to create either one database (for publication feature) and as many as eight databases to contain the data. One USER (database) serves as the entry point for the MDM software as well as the container for the metadata, views, tables, global temporary tables, and stored procedures.

Sizing Requirements for Table Class/Source Combination Defined on MDM Facets

The classification of declared class and source signify whether a given table has an instance created in each of the logical/physical staging area. The most common classification is Class=MASTER, Source=BACKEND. This implies that MDM will maintain the MASTER but the data that provides the updates reside in a system external to MDM. A good example would be subscribed data such as AM BEST, Demographic information, or internally produced reference data such as Vendors. Class=MASTER, Source=MASTER implies that MDM is the system of record for this data and the MASTER is maintained via direct entry into the MASTER via a custom UI, Table Editor or a Workflow. Class=Transaction, Source =Backend serves merely as a method of storing data in MDM that is transactional in nature.

The storage requirements for each Class and Source combination is given below:


Appendix B: MDM Database Sizing GuidelinesSizing Requirements for Table Class/Source Combination Defined on MDM Facets

Class=MASTER Source=Backend

Tables of this classification need instances in the Input, Net Change, Master, Output, and Error staging area. Additionally Audit and Publish capabilities could be specified as options. Global Temporary tables resident in the User Database also are used. MDM control columns are appended to each row and add ~ 40 bytes on average to each row. For a given table of size S the MDM space occupancy space will be between 2S and 3S. If Output staging snapshots are used space would increase to 3 - 4S. Audit is a cumulative function starting at base S with increments as a function of the rows inserted/changed. In the short term maybe 1 - 1.5S. Publishing copies the table to Publish staging so another S. Publishing audit is cumulative as it preserves the published state of the table at the time of publishing. XS where X = # of publishing cycles.

For the full complement of MDM storage capabilities per table without publish audit would be in the range of 5-6S. Publish audit would extend that 1S for each publish cycle.

Class=Master Source=Master

Tables of this classification imply that MDM is the System of Record for this information. These tables only have Master and Error staging area. Total space occupancy would be 1-1.5S.

Class=Transaction Source=Backend

Tables of this classification have no supplied MDM processes that operate on these tables, therefore the storage component would be 1S.

MDM User Database

The User Database space requirement is relatively small as it is the container for most of the metadata, stored procedures, etc. Space allocations in the range of 100Mb should be more than adequate to store the requisite information.

Global Temporary Tables

This table classification for MASTER tables is used primarily for uploads from the MDM server either through interactions with the UI or Excel uploads. The space allocation is charged to the Temporary storage for the USER Database. The amount of upload activity will dictate sizing for this space classification. Usually the default designation on creation of the User Database would cover any anticipated use. This may be site dependent.

Version (VER) Tables

This class of table is currently reserved for the Hierarchical metadata and master data to catalogue version changes. The tables are partitioned such that versions changes will populate the “next” partition with the previous version. The size of version tables would be a function of the number of versions deployed. So XS where X=version.



Data Growth

A periodic assessment of the actual growth versus the planned growth of the tables under the MDM application is required. The expectation is that most of the data under MDM’s control is fairly static and that data growth is small. This however is site dependent.

Spool Space

Few of the spool heavy activities within MDM would be calculation of Net Change, Hierarchy/Relationship viewer and data profiling etc., hence a good spool space to assign to MDM user to start with would be 5x, the largest table under MDM control. The spool space usage could be reviewed and adjusted later by looking at peak spool values in dbc.diskspace or by reviewing DBQL for the particular MDM user.


Index


Index

DDatabase

Change password 84Preparing database for MDM 47

Database containing existing MDM sche-ma 49

Empty database 47Topology 10Troubleshooting MDM database preparation

51User requirements 6

DeploymentCRDM Application 73Custom Application 73Sample Application 73

Deployment Manager 73Debug deployment process 88

Documentation viiiFFallback

Database Tables 9IIBM 57Installing

CRDM 35Log file details 34MDM 11, 41MDM Path Installation 91MDM Sample Application 41Silent Installation 69

LLRDM Control framework 15, 36, 42MMultiple LRDM Map Tables 16, 37, 38Oorder of services 51PPurpose iiiSSchema 50

StartingClient 67Server 67

StudioArchitecture 109, 113

System requirements 1AIX 5Linux 4, 5VMware 3Windows 2

TTeradata

Data Dictionary 8UUninstall 105Uninstall MDM 105

UNIX 98, 107Windows 105

UNIX 107Upgrade 98

Cutsom Application 98Process 98

WWebclient Deployment

BEA WebLogic 62IBM WebSphere 57Tomcat 63

XXOperation

Remote 110

master data manager 3.2.0.1 installation guide

Documents

registered trademarks

sanbox trademarks

registered trademark

united states

teradata source experts

teradata decision experts

windows nt

windows server