Informatica MDM Multidomain Edition for Oracle (Version HotFix 8) Installation Guide for WebLogic

Transcription

1 Informatica MDM Multidomain Edition for Oracle (Version HotFix 8) Installation Guide for WebLogic

2 Informatica MDM Multidomain Edition for Oracle Installation Guide for WebLogic Version HotFix 8 February 2015 Copyright (c) Informatica Corporation. All rights reserved. This software and documentation contain proprietary information of Informatica Corporation and are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright law. Reverse engineering of the software is prohibited. No part of this document may be reproduced or transmitted in any form, by any means (electronic, photocopying, recording or otherwise) without prior consent of Informatica Corporation. This Software may be protected by U.S. and/or international Patents and other Patents Pending. Use, duplication, or disclosure of the Software by the U.S. Government is subject to the restrictions set forth in the applicable software license agreement and as provided in DFARS (a) and (a) (1995), DFARS (1)(ii) (OCT 1988), FAR (a) (1995), FAR , or FAR (ALT III), as applicable. The information in this product or documentation is subject to change without notice. If you find any problems in this product or documentation, please report them to us in writing. Informatica, Informatica Platform, Informatica Data Services, PowerCenter, PowerCenterRT, PowerCenter Connect, PowerCenter Data Analyzer, PowerExchange, PowerMart, Metadata Manager, Informatica Data Quality, Informatica Data Explorer, Informatica B2B Data Transformation, Informatica B2B Data Exchange Informatica On Demand, Informatica Identity Resolution, Informatica Application Information Lifecycle Management, Informatica Complex Event Processing, Ultra Messaging and Informatica Master Data Management are trademarks or registered trademarks of Informatica Corporation in the United States and in jurisdictions throughout the world. All other company and product names may be trade names or trademarks of their respective owners. Portions of this software and/or documentation are subject to copyright held by third parties, including without limitation: Copyright DataDirect Technologies. All rights reserved. Copyright Sun Microsystems. All rights reserved. Copyright RSA Security Inc. All Rights Reserved. Copyright Ordinal Technology Corp. All rights reserved.copyright Aandacht c.v. All rights reserved. Copyright Genivia, Inc. All rights reserved. Copyright Isomorphic Software. All rights reserved. Copyright Meta Integration Technology, Inc. All rights reserved. Copyright Intalio. All rights reserved. Copyright Oracle. All rights reserved. Copyright Adobe Systems Incorporated. All rights reserved. Copyright DataArt, Inc. All rights reserved. Copyright ComponentSource. All rights reserved. Copyright Microsoft Corporation. All rights reserved. Copyright Rogue Wave Software, Inc. All rights reserved. Copyright Teradata Corporation. All rights reserved. Copyright Yahoo! Inc. All rights reserved. Copyright Glyph & Cog, LLC. All rights reserved. Copyright Thinkmap, Inc. All rights reserved. Copyright Clearpace Software Limited. All rights reserved. Copyright Information Builders, Inc. All rights reserved. Copyright OSS Nokalva, Inc. All rights reserved. Copyright Edifecs, Inc. All rights reserved. Copyright Cleo Communications, Inc. All rights reserved. Copyright International Organization for Standardization All rights reserved. Copyright ejtechnologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright International Business Machines Corporation. All rights reserved. Copyright yworks GmbH. All rights reserved. Copyright Lucent Technologies. All rights reserved. Copyright (c) University of Toronto. All rights reserved. Copyright Daniel Veillard. All rights reserved. Copyright Unicode, Inc. Copyright IBM Corp. All rights reserved. Copyright MicroQuill Software Publishing, Inc. All rights reserved. Copyright PassMark Software Pty Ltd. All rights reserved. Copyright LogiXML, Inc. All rights reserved. Copyright Lorenzi Davide, All rights reserved. Copyright Red Hat, Inc. All rights reserved. Copyright The Board of Trustees of the Leland Stanford Junior University. All rights reserved. Copyright EMC Corporation. All rights reserved. Copyright Flexera Software. All rights reserved. Copyright Jinfonet Software. All rights reserved. Copyright Apple Inc. All rights reserved. Copyright Telerik Inc. All rights reserved. Copyright BEA Systems. All rights reserved. Copyright PDFlib GmbH. All rights reserved. Copyright Orientation in Objects GmbH. All rights reserved. Copyright Tanuki Software, Ltd. All rights reserved. Copyright Ricebridge. All rights reserved. Copyright Sencha, Inc. All rights reserved. Copyright Scalable Systems, Inc. All rights reserved. Copyright jqwidgets. All rights reserved. This product includes software developed by the Apache Software Foundation ( and/or other software which is licensed under various versions of the Apache License (the "License"). You may obtain a copy of these Licenses at Unless required by applicable law or agreed to in writing, software distributed under these Licenses is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the Licenses for the specific language governing permissions and limitations under the Licenses. This product includes software which was developed by Mozilla ( software copyright The JBoss Group, LLC, all rights reserved; software copyright by Bruno Lowagie and Paulo Soares and other software which is licensed under various versions of the GNU Lesser General Public License Agreement, which may be found at The materials are provided free of charge by Informatica, "as-is", without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. The product includes ACE(TM) and TAO(TM) software copyrighted by Douglas C. Schmidt and his research group at Washington University, University of California, Irvine, and Vanderbilt University, Copyright ( ) , all rights reserved. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (copyright The OpenSSL Project. All Rights Reserved) and redistribution of this software is subject to terms available at and This product includes Curl software which is Copyright , Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at Permission to use, copy, modify, and distribute this software for any purpose with or without fee is hereby granted, provided that the above copyright notice and this permission notice appear in all copies. The product includes software copyright ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at license.html. The product includes software copyright , The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at This product includes ICU software which is copyright International Business Machines Corporation and others. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at kawa/software-license.html. This product includes OSSP UUID software which is Copyright 2002 Ralf S. Engelschall, Copyright 2002 The OSSP Project Copyright 2002 Cable & Wireless Deutschland. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by Boost ( or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at / This product includes software copyright University of Cambridge. Permissions and limitations regarding this software are subject to terms available at This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at and at This product includes software licensed under the terms at license.html, asm.ow2.org/license.html, httpunit.sourceforge.net/doc/ license.html,

3 license.html, license-agreement; /copyright-software ; forge.ow2.org/projects/javaservice/, license.html; protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto; current/doc/mitk5license.html; blob/master/license; and This product includes software licensed under the Academic Free License ( the Common Development and Distribution License ( the Common Public License ( the Sun Binary Code License Agreement Supplemental License Terms, the BSD License ( the new BSD License ( licenses/bsd-3-clause), the MIT License ( the Artistic License ( and the Initial Developer s Public License Version 1.0 ( This product includes software copyright Joe WaInes, XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at This product includes software developed by the Indiana University Extreme! Lab. For further information please visit This product includes software Copyright (c) 2013 Frank Balluffi and Markus Moeller. All rights reserved. Permissions and limitations regarding this software are subject to terms of the MIT license. This Software is protected by U.S. Patent Numbers 5,794,246; 6,014,670; 6,016,501; 6,029,178; 6,032,158; 6,035,307; 6,044,374; 6,092,086; 6,208,990; 6,339,775; 6,640,226; 6,789,096; 6,823,373; 6,850,947; 6,895,471; 7,117,215; 7,162,643; 7,243,110; 7,254,590; 7,281,001; 7,421,458; 7,496,588; 7,523,121; 7,584,422; 7,676,516; 7,720,842; 7,721,270; 7,774,791; 8,065,266; 8,150,803; 8,166,048; 8,166,071; 8,200,622; 8,224,873; 8,271,477; 8,327,419; 8,386,435; 8,392,460; 8,453,159; 8,458,230; 8,707,336; 8,886,617 and RE44,478, International Patents and other Patents Pending. DISCLAIMER: Informatica Corporation provides this documentation "as is" without warranty of any kind, either express or implied, including, but not limited to, the implied warranties of noninfringement, merchantability, or use for a particular purpose. Informatica Corporation does not warrant that this software or documentation is error free. The information provided in this software or documentation may include technical inaccuracies or typographical errors. The information in this software and documentation is subject to change at any time without notice. NOTICES This Informatica product (the "Software") includes certain drivers (the "DataDirect Drivers") from DataDirect Technologies, an operating company of Progress Software Corporation ("DataDirect") which are subject to the following terms and conditions: 1. THE DATADIRECT DRIVERS ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NON-INFRINGEMENT. 2. IN NO EVENT WILL DATADIRECT OR ITS THIRD PARTY SUPPLIERS BE LIABLE TO THE END-USER CUSTOMER FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL OR OTHER DAMAGES ARISING OUT OF THE USE OF THE ODBC DRIVERS, WHETHER OR NOT INFORMED OF THE POSSIBILITIES OF DAMAGES IN ADVANCE. THESE LIMITATIONS APPLY TO ALL CAUSES OF ACTION, INCLUDING, WITHOUT LIMITATION, BREACH OF CONTRACT, BREACH OF WARRANTY, NEGLIGENCE, STRICT LIABILITY, MISREPRESENTATION AND OTHER TORTS. Part Number: MDM-OIG HF8-0001

4 Table of Contents Preface Informatica Resources Informatica My Support Portal Informatica Documentation Informatica Web Site Informatica How-To Library Informatica Knowledge Base Informatica Multimedia Knowledge Base Informatica Global Customer Support Chapter 1: Introduction Before You Begin Installation Overview Designing the MDM Hub Installation Single MDM Hub Version Requirement Supported Locales Installation Language Installation Environments Example Installations Documenting an Installation Installation and Post-Installation Documentation Create an Installation Documentation Directory Chapter 2: Hub Store Installation Hub Store Installation Overview About the Hub Store Master Database and Operational Reference Store (ORS) Oracle RAC Considerations Overview of Steps to Install the Hub Store Install and Configure Oracle for the MDM Hub Install and Configure Oracle Disable the Oracle Recycle Bin Set Oracle PL/SQL Compiler Flags for Oracle 10gR Configure the init.ora Parameters Create an Oracle Database Instance Create Tablespaces Creating the CMX_DATA Tablespace Creating the CMX_INDX Tablespace Creating the CMX_TEMP Tablespace Configuring the DEFERRED_SEGMENT_CREATION Parameter Table of Contents

5 Create the Hub Store About the setup.sql Script Create the Hub Store (UNIX) Create the Hub Store (Windows) Ensure Access to Required Oracle Components Test the Database Connection Create a Proxy User Creating a Proxy User (UNIX) Creating a Proxy User (Windows) Create an Additional ORS Database About the setup_ors.sql Script Adding an ORS (UNIX) Adding an ORS (Windows) Chapter 3: Hub Server Installation Hub Server Installation Overview About the Hub Server Application Server and Connection Pooling Manually Configuring Message Queues for Asynchronous SIF Requests Post-Installation Setup Installing the Hub Server On UNIX Installation Overview Step 1. Preparing for Installation Step 2. Running the Hub Server Installer Step 3. Configuring the Hub Server Step 4. Performing Post-Installation Tasks Installing the Hub Server On Windows Installation Overview Step 1. Preparing for Installation Step 2. Running the Hub Server Installer Step 3. Configuring the Hub Server Step 4. Performing Post-Installation Tasks Changing Passwords After Installation Changing the Password for the CMX_SYSTEM User Changing the Password for the CMX_ORS User Chapter 4: Cleanse Match Server Installation Cleanse Match Server Installation Overview About the Cleanse Match Server Supported Cleanse Match Engines Post-Installation Setup Installing the Cleanse Match Server On UNIX Installation Overview Table of Contents 5

6 Step 1. Preparing for Installation Step 2. Running the Cleanse Match Server Installer Step 3. Configuring the Cleanse Match Server Step 4. Performing Post-installation Tasks Installing the Cleanse Match Server On Windows Installation Overview Step 1. Preparing for Installation Step 2. Running the Cleanse Match Server Installer Step 3. Configuring the Cleanse Match Server Step 4. Performing Post-installation Tasks Enabling Match Population Chapter 5: Launching the Hub Console Overview of the Hub Console About the Hub Console Starting the Hub Console Post-setup Tasks Chapter 6: Clustering Overview of Clustering Installing the Hub Server into a WebLogic Server Cluster (UNIX) Installation Overview Step 1. Creating a WebLogic Cluster Step 2. Installing and Deploying the Hub Server Step 3. Installing and Deploying the Cleanse Match Server Installing the Hub Server into a WebLogic Server Cluster (Windows) Installation Overview Step 1. Creating a WebLogic Cluster Step 2. Installing and Deploying the Hub Server Step 3. Installing and Deploying the Cleanse Match Server Configuring JBoss Cache Chapter 7: Uninstalling Informatica MDM Hub Overview of Uninstalling Informatica MDM Hub Uninstalling Informatica MDM Hub (WebLogic / UNIX) Step 1. Uninstalling the Cleanse Match Server Step 2. Uninstalling the Hub Server Step 3. Uninstalling the Hub Store from Oracle Uninstalling Informatica MDM Hub (WebLogic / Windows) Step 1. Uninstalling the Cleanse Match Server Step 2. Uninstalling the Hub Server Step 3. Uninstalling the Hub Store from Oracle Table of Contents

7 Chapter 8: Troubleshooting Informatica MDM Hub Log Files Informatica MDM Hub Log Files (UNIX) Informatica MDM Hub Log Files (Windows) Bypassing Prerequisite Installation Updating Parameters After Installation Updating the Hub Server Parameters After Installation Updating the Cleanse Match Server Parameters After Installation Checking the Hub and Cleanse Match Server Silent Install Checking the Hub Server and Cleanse Match Server Silent Install (UNIX) Checking the Hub Server and Cleanse Match Server Silent Install (Windows) Post-Installation Failure MATCH Process Error: VerifyNeedToStrip VerifyNeedToStrip (UNIX) VerifyNeedToStrip (Windows) Inaccurate Start/Stop Timestamp for ORS major.minor Version Errors When Loading the Cleanse Match Server Low Cleanse/Match Application Server Performance Hub Server Cache Timeout Exception Troubleshooting (WebLogic / UNIX) Changing the Hub Server Parameters (WebLogic/UNIX) Changing the Cleanse Match Server Parameters (WebLogic/UNIX) Changing the Hub Server Parameters for the Database (WebLogic/UNIX) Manually Redeploying Hub Server Application On UNIX Manually Undeploying the Cleanse Match Server (WebLogic/UNIX) Setting the JVM Stack Size (WebLogic/UNIX) Troubleshooting (WebLogic / Windows) Changing the Hub Server Parameters (WebLogic/Windows) Changing the Cleanse Match Server Parameters (WebLogic/Windows) Changing the Hub Server Parameters for the Database (WebLogic/Windows) Manually Redeploying Hub Server Application On Windows Manually Undeploying the Cleanse Match Server (WebLogic/Windows) Setting the JVM Stack Size (WebLogic/Windows) Appendix A: Installing from the Command Line Overview of Installing from the Command Line Preparing for Installation Installing from the Command Line (WebLogic/UNIX) Installing the Hub Server Installing the Cleanse Match Server Silent Installation from the Command Line Considerations When Using Silent Installation Table of Contents 7

8 Properties Files for Silent Installation Creating the Properties File for the Hub Server Creating the Properties File for the Cleanse Match Server Running the Silent Install Troubleshooting the Silent Install Appendix B: Manually Configuring Informatica System Message Queues Manually Configuring Informatica System Message Queues Overview MDM Hub Message Queues Configuring JMS Message Queues for JBoss Step 1. Create a Connection Factory Step 2. Create a JMS Message Queue Step 3. Verify the JMS Message Queue Configuration Step 4. Add a Message Queue Server Step 5. Add a Message Queue Configuring Message Queues for WebLogic Creating a Message Queue Step 5. Add a Message Queue Server Step 6. Add a Message Queue Configuring Additional Message Queues Configuring Message Queues for WebSphere Creating a Message Queue Step 4. Add a Message Queue Server Step 5. Add a Message Queue Configuring Additional Message Queues Index Table of Contents

9 Preface Welcome to the Informatica MDM Hub Installation Guide. This guide explains how to perform a first-time installation of Informatica MDM Hub Server and the Cleanse Match Server. This guide is intended for database administrators, system administrators, and implementers who are responsible for installing and setting up Informatica MDM Hub. System administrators must be familiar with their target operating system. Database administrators must be familiar with the database environment on which they are installing the Informatica MDM Hub. Knowledge of Oracle administration is particularly important. Other administration and configuration tasks are described in the Informatica MDM Hub Configuration Guide. Informatica Resources Informatica My Support Portal As an Informatica customer, you can access the Informatica My Support Portal at The site contains product information, user group information, newsletters, access to the Informatica customer support case management system (ATLAS), the Informatica How-To Library, the Informatica Knowledge Base, Informatica Product Documentation, and access to the Informatica user community. Informatica Documentation The Informatica Documentation team makes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through at infa_documentation@informatica.com. We will use your feedback to improve our documentation. Let us know if we can contact you regarding your comments. The Documentation team updates documentation as needed. To get the latest documentation for your product, navigate to Product Documentation from Informatica Web Site You can access the Informatica corporate web site at The site contains information about Informatica, its background, upcoming events, and sales offices. You will also find product and partner information. The services area of the site includes important information about technical support, training and education, and implementation services. 9

10 Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes articles and interactive demonstrations that provide solutions to common problems, compare features and behaviors, and guide you through performing specific real-world tasks. Informatica Knowledge Base As an Informatica customer, you can access the Informatica Knowledge Base at Use the Knowledge Base to search for documented solutions to known technical issues about Informatica products. You can also find answers to frequently asked questions, technical white papers, and technical tips. If you have questions, comments, or ideas about the Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Multimedia Knowledge Base As an Informatica customer, you can access the Informatica Multimedia Knowledge Base at The Multimedia Knowledge Base is a collection of instructional multimedia files that help you learn about common concepts and guide you through performing specific tasks. If you have questions, comments, or ideas about the Multimedia Knowledge Base, contact the Informatica Knowledge Base team through at KB_Feedback@informatica.com. Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the Online Support. Online Support requires a user name and password. You can request a user name and password at The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at 10 Preface

11 C H A P T E R 1 Introduction This chapter includes the following topics: Before You Begin, 11 Installation Overview, 11 Designing the MDM Hub Installation, 12 Documenting an Installation, 14 Before You Begin This chapter summarizes the installation process and describes steps that you must complete before proceeding with the MDM Hub installation. Before you begin, complete the following tasks: 1. Read the Informatica MDM Hub Release Notes for requirements and more information about preinstallation preparation. 2. Install and configure the cleanse engine according to the vendor instructions. 3. Read the Informatica MDM Hub Overview for an introduction to the product architecture and key components. For more information about product requirements and supported platforms, see the Product Availability Matrix on the Informatica My Support Portal: Installation Overview To install the MDM Hub, complete the following steps: 1. Install the Hub Store in your Oracle database. 2. Install the Hub Server software. 3. Install and configure one or more Cleanse Match Servers. 4. Launch the Hub Console and verify your installation. 11

12 Designing the MDM Hub Installation Before you install the MDM Hub, you must decide how to set up the components of the Informatica MDM Hub implementation. Single MDM Hub Version Requirement All the components of the MDM Hub implementation must be of the same MDM Hub version. If you have multiple versions of the MDM Hub, each version must be installed in a separate environment. Supported Locales You must set the same operating system locale for the MDM Hub Server, the MDM Hub Store, and the MDM Hub console. Choose one of the following locales for the MDM Hub components: en_us fr_fr de_de ja_jp Installation Language You can install the MDM Hub in English, French, German, and Japanese. In Oracle, the NLS_LANG environment variable must be set to the appropriate value for your installation language. When you run the database setup scripts to create the database schemas, you must run the database installation from the following setup folder for your installation language: database\oracle\<language> where <language> is the abbreviation for the installation language such as fr or en. The seed schemas are created in the language that you choose during installation and cannot be changed after the installation is complete. The language you choose for the schemas also determines the language in which many elements of the MDM Hub console display and the language in which error messages are reported. When you install the MDM Hub Server and the Cleanse Match Server, you are prompted to select the installation language. The language you select does not affect the language used for MDM log files. The log files are in English regardless of the installation language. Note: For Japanese language installations, ensure you are using Shift_JIS encoding before you run the setup.sql script to install the Hub Store. Installation Environments You can install the MDM Hub in multiple environments, such as development, test, and production. Each type of environment comes with its own set of unique requirements and priorities. Therefore, the installation design differs for each environment. 12 Chapter 1: Introduction

13 Example Installations You can set up the MDM Hub components in multiple ways. The following examples of MDM Hub installations provide general principles to consider while designing an installation. They are not recommendations. All Components on a Single Host In the following example, all MDM Hub core components are installed on a single host machine: This layout simplifies communication among the components within a single host environment. Designing the MDM Hub Installation 13

14 Components Distributed on Multiple Hosts In the following example, the MDM Hub components are distributed among multiple host machines: You can deploy Hub Server machines in a clustered application server environment for failover purposes. You can install Cleanse Match Server machines in a clustered environment for scalability purposes. Note: You must install an Oracle client on the Hub Server and the Cleanse Match Server. RELATED TOPICS: Clustering on page 81 Documenting an Installation Document the details of an MDM Hub setup during and after installation in case you encounter issues in the environment. Use this information for verification and troubleshooting. If necessary, you can provide copies of this information to Informatica Global Customer Support. 14 Chapter 1: Introduction

15 Installation and Post-Installation Documentation You can consult the following sources of information about the MDM Hub installation: Information About ORS metadata Configuration settings Database changes Installation process Hub Server and Cleanse Match Server Hub Console Information Source The Validation Results report from the Repository Manager tool in the Hub Console. Documents ORS metadata after installation. For more information, see the Informatica MDM Hub Repository Manager Guide. The Environment Report from the Enterprise Manager tool in the Hub Console. Document the Hub Server, Cleanse Match Server, Master Database, and ORS database information after installation. For more information, see the Informatica MDM Hub Configuration Guide. Database debug log. Logs database events for the Hub Store after an ORS is registered in the Hub Console. The MDM Hub Installer log files which capture events that occur during the Hub Server and the Cleanse Match Server installation. The Hub Server and the Cleanse Match Server log files which capture run-time events after these components are running. The Hub Console log files which capture activity while using the Hub Console. Important: Capture and save installation-related information for future reference. RELATED TOPICS: Enabling Debug Logging on an Operational Reference Store Database on page 96 Create an Installation Documentation Directory Create a directory to store copies of installation artifacts, such as the Validation Results and Environment reports, the database debug log, and log files. For example, you can create the directory install_doc. Important: If problems occur with your installation, create an archive file of the installation documentation directory and send it to Informatica Global Customer Support for analysis. Documenting an Installation 15

16 C H A P T E R 2 Hub Store Installation This chapter includes the following topics: Hub Store Installation Overview, 16 About the Hub Store, 16 Overview of Steps to Install the Hub Store, 19 Install and Configure Oracle for the MDM Hub, 19 Create an Oracle Database Instance, 20 Create Tablespaces, 21 Create the Hub Store, 22 Ensure Access to Required Oracle Components, 28 Test the Database Connection, 30 Create a Proxy User, 30 Create an Additional ORS Database, 31 Hub Store Installation Overview You can install the Hub Store on Oracle in a UNIX or Windows environment. The Oracle database administrator must perform the Hub Store installation tasks. About the Hub Store The Informatica MDM Hub stores and consolidates business data in the Hub Store. Master Database and Operational Reference Store (ORS) The Hub Store is a collection of databases. 16

17 The following table describes the databases in the Hub Store: Database Master Database Operational Reference Store (ORS) Description Database that contains the MDM Hub environment configuration settings, such as user accounts, security configuration, ORS registry, and message queue settings. Each MDM Hub environment can have only one Master Database. The default name of the Master Database is CMX_SYSTEM. Database that contains the master data, content metadata, the rules for processing the master data, the rules for managing the set of master data objects, and the processing rules and auxiliary logic that define the best version of the truth (BVT). The default name of an ORS is CMX_ORS. The MDM Hub contains one Master Database and zero or more ORS databases. If no ORS exists, then only the Configuration workbench tools are available in the Hub Console. The MDM Hub might have multiple ORSs in the following cases: Separate ORSs for development and production environments Separate ORSs for different geographical locations Separate ORSs for different parts of the organization You can access and manage multiple ORSs from the Master Database. The Master Database stores the connection settings and properties for each ORS. You can distribute ORS databases across multiple server machines. Note: An ORS is typically registered with one Master Database. You create user accounts to access Hub Store databases. You create user accounts in the Master Database, and then assign the user accounts to specific ORSs. Oracle RAC Considerations You can install Hub Store databases on Oracle RAC. If you use Oracle RAC, you must complete manual configuration steps to use features and optimize the environment for performance. Note: Oracle RAC load-balanced connections are not supported for some MDM Hub components. Use of Oracle Service Names You can use Oracle service names instead of Oracle SIDs for RAC and non-rac installations. Use Oracle service names for a more flexible method to specify the connection and to dynamically reallocate database servers. About Oracle RAC Load-Balanced Connections You can use Oracle RAC to specify a connection to an Oracle service that is enabled with load balancing and high availability. Oracle RAC distributes the workload among all available nodes in the cluster. If a node becomes unavailable, the work fails over to a new node. Use Oracle RAC load-balanced connections in a fail-safe environment to ensure that a database connection is available even when one or more RAC nodes become unavailable. About the Hub Store 17

18 Informatica MDM Hub Components and Load-Balanced Connections Most Informatica MDM Hub components use load balancing and available nodes. Informatica MDM Hub components that build their own direct JDBC connection cannot use load balancing. These components do not know the virtual IPs of the Oracle RAC nodes. The following table describes the Informatica MDM Hub components that use Oracle RAC load balancing: Component Batch Jobs Services Integration Framework API Connections Cleanse Server Repository Manager Description Use load balancing when batch jobs are called from a command line because batch jobs use the tnsnames.ora settings. Use load-balanced JDBC connections from the application server connection pool. Uses load-balanced JDBC connections from the cleanse server connection pool. Uses load-balanced JDBC connections from the application server connection pool when only DML is required. The following table describes the Informatica MDM Hub components that do not use Oracle RAC load balancing: Component Batch Jobs Repository Manager Description Cannot use load balancing when called from the Hub Console. Cannot use load balancing when DDL is required because DDL uses a direct JDBC connection. Setting Up Oracle RAC with Informatica MDM Hub Use the same procedure that you use for a single Oracle database instance to configure the MDM Hub with Oracle RAC. The only difference is that you must specify all RAC nodes of the database cluster in the tnsnames.ora file. The following tnsnames.ora entry example shows you how to specify the multiple RAC nodes for an Oracle service called mdm_service.domain.com: MDM_SERVICE.DOMAIN.COM = (DESCRIPTION = (ADDRESS_LIST= (ADDRESS= (PROTOCOL = TCP)(HOST = server1-vip)(port = 1521)) (ADDRESS= (PROTOCOL = TCP)(HOST = server2-vip)(port = 1521)) (ADDRESS= (PROTOCOL = TCP)(HOST = server3-vip)(port = 1521)) (FAILOVER = on) (LOAD_BALANCE = on) ) (CONNECT_DATA= (SERVICE_NAME = mdm_service.domain.com) ) Connections to mdm_service are load-balanced between the RAC nodes on server1, server2, or server3. After the MDM Hub installation is complete, use the Databases tool in the Hub Console to configure the JDBC connection to connect to the load-balanced Oracle service. For more information, see the Informatica MDM Hub Configuration Guide. 18 Chapter 2: Hub Store Installation

19 Overview of Steps to Install the Hub Store To install the Hub Store, complete the following steps: 1. Install and configure Oracle. 2. Create an Oracle database for the Hub Store. 3. Create the Oracle tablespaces required for the Hub Store. 4. Create the Hub Store, including the Master Database and ORS database(s). 5. Ensure access to required Oracle components in a custom Oracle environment, if required. 6. Test the database connection. 7. Optionally, create a proxy user. 8. Optionally, add more ORS databases to your Hub Store. After you install the MDM Hub, you must complete post-setup tasks. You will complete the following postsetup tasks for the Hub Store: Register the newly-created ORS database using the Databases tool in the Hub Console. Enable database logging for the ORSs using the Enterprise Manager tool in the Hub Console. Install and Configure Oracle for the MDM Hub You must install Oracle before you can create the Hub Store databases. After you install Oracle, you must perform the following Oracle configuration tasks: Turn off the Oracle recycle bin. Set the PL/SQL compiler flags to prepare Oracle for the MDM Hub. Install and Configure Oracle Install and configure Oracle on a machine that meets the hardware and software requirements. You must install the following software on every machine on which you will run the Hub Server: Oracle client Oracle Java utilities SQL*Loader Note: Ensure that you install Oracle with all Java options selected. Disable the Oracle Recycle Bin You must disable the Oracle Recycle Bin to use MDM Hub. The Oracle Recycle Bin is enabled by default. The Oracle Recycle Bin can interfere with the MDM Hub processes. Disable the Oracle Recycle Bins, USER_RECYCLEBIN and DBA_RECYCLEBIN, for the Hub Store. You can disable the recycle bins at the system or session level. Also, explicitly purge any existing objects in the recycle bin. To disable the Recycle Bin, set RECYCLEBIN=OFF. For more information, see the Oracle documentation. Overview of Steps to Install the Hub Store 19

20 Set Oracle PL/SQL Compiler Flags for Oracle 10gR2 If you use Oracle 10gR2, you must set the PL/SQL compiler flags. To successfully compile the MDM Hub packages, set PLSQL_COMPILER_FLAGS to INTERPRETED. The default value is NATIVE. Complete the following steps to set the Oracle PL/SQL compiler flags: 1. Log in to Oracle with DBA privileges or as the SYSTEM user. 2. Launch SQL*Plus. 3. Run the following commands from the command prompt: SHOW PARAMETER plsql_compiler_flags; ALTER SYSTEM SET plsql_compiler_flags=interpreted; 4. Close the connection to Oracle. Configure the init.ora Parameters. You must configure the init.ora parameters for the production environment of the MDM Hub installation. For information about Oracle database settings required for a production environment, see the article Recommended Oracle Database Initialization Settings for a Baseline MDM Hub Installation in the Informatica Knowledge Base. Create an Oracle Database Instance After you install and configure the Oracle database, create an Oracle database instance. Note: If the MDM Hub will have multiple ORS databases distributed across different host servers, create an Oracle database instance on each server. Also, save the following information about each database instance you create for subsequent Hub Store setup: Oracle server TNS name Oracle connection type Oracle SERVICE or SID name Oracle listener port number Oracle database server name Oracle Connect URL for SERVICE connection type only Oracle SYSTEM username Oracle SYSTEM password 20 Chapter 2: Hub Store Installation

21 Create Tablespaces You must create the following Oracle tablespaces for the Hub Store: Default Tablespace Name CMX_DATA CMX_INDX CMX_TEMP Description Default tablespace for the ORS schema. Important: Do not change the default tablespace name of CMX_DATA for your Hub Store. Contains indexes created and used by Informatica MDM Hub. Contains temporary tables for Informatica MDM Hub. Used for stored procedures. You must create enough space for the CMX_TEMP tablespace and ORACLE TEMP tablespace. When you create the tablespaces, adjust the default tablespace sizes and number of data files based on the volume of data to be loaded into the MDM Hub. Creating the CMX_DATA Tablespace Create the CMX_DATA tablespace. Create it as a permanent tablespace that is managed locally. To create the tablespace, log into Oracle as the database administrator or user with SYSTEM privileges, and then run the command from SQL*Plus. The following example shows the command you can use to create the CMX_DATA tablespace: CREATE BIGFILE TABLESPACE CMX_DATA NOLOGGING DATAFILE '<Oracle install directory>/cmx_data1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL; Creating the CMX_INDX Tablespace Create the CMX_INDX tablespace. Create it as a permanent tablespace that is managed locally. To create the tablespace, log into Oracle as the database administrator or user with SYSTEM privileges, and then run the command from SQL*Plus. The following example shows the command you can use to create the CMX_INDX tablespace: CREATE BIGFILE TABLESPACE CMX_INDX NOLOGGING DATAFILE '<Oracle install directory>/cmx_indx1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL; If you do not use the default tablespace name, you must set the DEFERRED_SEGMENT_CREATION parameter to false to prevent Repository Manager validation errors. Creating the CMX_TEMP Tablespace Create the CMX_TEMP tablespace. Create it as a permanent tablespace that is managed locally. To create the tablespace, log into Oracle as the database administrator or user with SYSTEM privileges, and then run the command from SQL*Plus. Important: Do not create the tablespace as an Oracle TEMPORARY tablespace. Create Tablespaces 21

22 The following example shows the command you can use to create the CMX_TEMP tablespace: CREATE BIGFILE TABLESPACE CMX_TEMP NOLOGGING DATAFILE '<Oracle install directory>/cmx_temp1.dbf' SIZE 2048M REUSE EXTENT MANAGEMENT LOCAL; If you do not use the default tablespace name, you must set the DEFERRED_SEGMENT_CREATION parameter to false to prevent Repository Manager validation errors. Configuring the DEFERRED_SEGMENT_CREATION Parameter If you use a custom tablespace name for CMX_INDX or CMX_TEMP, set the DEFERRED_SEGMENT_CREATION parameter to false to prevent Repository Manager validation errors. 1. To set the DEFERRED_SEGMENT_CREATION parameter to false, run the following SQL command: ALTER SYSTEM SET DEFERRED_SEGMENT_CREATION=FALSE SCOPE=BOTH; 2. Restart the database. Create the Hub Store You must create the Hub Store and its databases. A Hub Store consists of the Master Database and optionally ORS databases. Run the setup.sql script to create the Hub Store. Note: When you create the Hub Store on a Japanese locale, ensure that you use the Shift_JIS encoding before you run the setup.sql script. About the setup.sql Script The MDM Hub distribution includes a setup.sql script that you run to create the Hub Store. Optionally, after you create the Hub Store, you can run the setup_ors.sql script to add more ORS databases. The setup.sql script performs the following functions: Drops users called CMX_SYSTEM or CMX and their contents. Creates the Master Database with the default name CMX_SYSTEM. You cannot change the CMX_SYSTEM master database name. Imports the initial metadata from the cmx_system.dmp file, which contains REPOS tables and other objects that the MDM Hub requires in the Hub Store. Drops any schema that has the same name as the name you specify for the ORS database. Creates a proxy user called CMX. You cannot change the CMX user name. Creates an additional user, CMX, that contains only grants and synonyms to the CMX_SYSTEM. Creates an ORS database with a default name CMX_ORS. Imports the initial repository metadata from the cmx_ors.dmp file that contains REPOS tables, other objects and seeded data needed for the ORS. Creates the PROXY_ROLE when it creates cmx_ors. The cmx_ors user owns this role. This role contains privileges on all REPOS tables, views, sequences, procedures, packages, and functions. 22 Chapter 2: Hub Store Installation

23 RELATED TOPICS: Create an Additional ORS Database on page 31 Create the Hub Store (UNIX) You can create the Hub Store after you install and configure Oracle for the MDM Hub and create the required tablespaces. 1. Create a temporary directory on the Oracle database server or on a client workstation that has the Oracle client installed with Oracle utilities (imp). 2. Copy all the files from the Informatica MDM Hub distribution directory to the directory you created. 3. Change directory to the database/oracle/<language> directory in the temporary directory you just created. <language> is your installation language such as en_us or fr. 4. Start SQL*PLUS and connect to the server as SYSTEM or as a user with DBA privileges. 5. Run the setup.sql script that is located in the database/oracle/<language> directory. Use one of the following commands to run the start setup.sql 6. Enter the following information at the prompts: Note: The prompt displays default text in brackets. Press Enter to accept the default values and go to the next prompt. Prompt Enter Oracle Server TNS name: Enter Oracle Connection Type (SERVICE, SID): Enter Oracle SERVICE name: Enter Oracle SID Name: Enter Oracle Listener Port number: Enter Oracle database server name: Description Name by which the Oracle database is known on your network. The TNS Name is set during Oracle installation and has the following format: mydatabase.mycompany.com For more information about TNS names, see your Oracle documentation. Connection type. Use one of the following values: - SERVICE. Uses the service name to connect to Oracle. - SID. Uses the Oracle System ID to connect to Oracle. Default is SERVICE. For more information about SERVICE and SID names, see your Oracle documentation. Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE. Name of the Oracle SID. This prompt is displayed if the selected Oracle connection type is SID. Port number used by the Oracle listener. Default is Name of the host running Oracle. Create the Hub Store 23