Informatica MDM Multidomain Edition (Version 9.6.1) Resource Kit Guide

Informatica MDM Multidomain Edition (Version 9.6.1) Resource Kit Guide

Informatica MDM Multidomain Edition Resource Kit Guide Version 9.6.1 September 2013 Copyright (c) 1998-2013 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 227.7202-1(a) and 227.7702-3(a) (1995), DFARS 252.227-7013 (1)(ii) (OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (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 1986. All rights reserved. Copyright ej-technologies GmbH. All rights reserved. Copyright Jaspersoft Corporation. All rights reserved. Copyright is 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 2003-2010 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. This product includes software developed by the Apache Software Foundation (http://www.apache.org/), 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 http://www.apache.org/licenses/. 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 (http://www.mozilla.org/), software copyright The JBoss Group, LLC, all rights reserved; software copyright 1999-2006 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 http://www.gnu.org/licenses/lgpl.html. 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 ( ) 1993-2006, 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 http://www.openssl.org and http://www.openssl.org/source/license.html. This product includes Curl software which is Copyright 1996-2013, Daniel Stenberg, <daniel@haxx.se>. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://curl.haxx.se/docs/copyright.html. 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 2001-2005 ( ) MetaStuff, Ltd. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.dom4j.org/license.html. The product includes software copyright 2004-2007, The Dojo Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://dojotoolkit.org/license. 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 http://source.icu-project.org/repos/icu/icu/trunk/license.html. This product includes software copyright 1996-2006 Per Bothner. All rights reserved. Your right to use such materials is set forth in the license which may be found at http:// www.gnu.org/software/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 http://www.opensource.org/licenses/mit-license.php. This product includes software developed by Boost (http://www.boost.org/) or under the Boost software license. Permissions and limitations regarding this software are subject to terms available at http://www.boost.org/license_1_0.txt. This product includes software copyright 1997-2007 University of Cambridge. Permissions and limitations regarding this software are subject to terms available at http:// www.pcre.org/license.txt. This product includes software copyright 2007 The Eclipse Foundation. All Rights Reserved. Permissions and limitations regarding this software are subject to terms available at http://www.eclipse.org/org/documents/epl-v10.php and at http://www.eclipse.org/org/documents/edl-v10.php. This product includes software licensed under the terms at http://www.tcl.tk/software/tcltk/license.html, http://www.bosrup.com/web/overlib/?license, http://www.stlport.org/doc/ license.html, http://asm.ow2.org/license.html, http://www.cryptix.org/license.txt, http://hsqldb.org/web/hsqllicense.html, http://httpunit.sourceforge.net/doc/license.html, http://jung.sourceforge.net/license.txt, http://www.gzip.org/zlib/zlib_license.html, http://www.openldap.org/software/release/license.html, http://www.libssh2.org, http://slf4j.org/ license.html, http://www.sente.ch/software/opensourcelicense.html, http://fusesource.com/downloads/license-agreements/fuse-message-broker-v-5-3- license-agreement; http://antlr.org/license.html; http://aopalliance.sourceforge.net/; http://www.bouncycastle.org/licence.html; http://www.jgraph.com/jgraphdownload.html; http://www.jcraft.com/ jsch/license.txt; http://jotm.objectweb.org/bsd_license.html;. http://www.w3.org/consortium/legal/2002/copyright-software-20021231; http://www.slf4j.org/license.html; http:// nanoxml.sourceforge.net/orig/copyright.html; http://www.json.org/license.html; http://forge.ow2.org/projects/javaservice/, http://www.postgresql.org/about/licence.html, http://

www.sqlite.org/copyright.html, http://www.tcl.tk/software/tcltk/license.html, http://www.jaxen.org/faq.html, http://www.jdom.org/docs/faq.html, http://www.slf4j.org/license.html; http://www.iodbc.org/dataspace/iodbc/wiki/iodbc/license; http://www.keplerproject.org/md5/license.html; http://www.toedter.com/en/jcalendar/license.html; http:// www.edankert.com/bounce/index.html; http://www.net-snmp.org/about/license.html; http://www.openmdx.org/#faq; http://www.php.net/license/3_01.txt; http://srp.stanford.edu/ license.txt; http://www.schneier.com/blowfish.html; http://www.jmock.org/license.html; http://xsom.java.net; and http://benalman.com/about/license/; https://github.com/ CreateJS/EaselJS/blob/master/src/easeljs/display/Bitmap.js; http://www.h2database.com/html/license.html#summary; http://jsoncpp.sourceforge.net/license; http:// jdbc.postgresql.org/license.html; and http://protobuf.googlecode.com/svn/trunk/src/google/protobuf/descriptor.proto. This product includes software licensed under the Academic Free License (http://www.opensource.org/licenses/afl-3.0.php), the Common Development and Distribution License (http://www.opensource.org/licenses/cddl1.php) the Common Public License (http://www.opensource.org/licenses/cpl1.0.php), the Sun Binary Code License Agreement Supplemental License Terms, the BSD License (http://www.opensource.org/licenses/bsd-license.php) the MIT License (http://www.opensource.org/licenses/mit-license.php), the Artistic License (http://www.opensource.org/licenses/artistic-license-1.0) and the Initial Developer s Public License Version 1.0 (http://www.firebirdsql.org/en/initial-developer-spublic-license-version-1-0/). This product includes software copyright 2003-2006 Joe WaInes, 2006-2007 XStream Committers. All rights reserved. Permissions and limitations regarding this software are subject to terms available at http://xstream.codehaus.org/license.html. This product includes software developed by the Indiana University Extreme! Lab. For further information please visit http://www.extreme.indiana.edu/. 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,820,077; 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; 7676516; 7,720, 842; 7,721,270; and 7,774,791, 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-RKG-96100-0001

Table of Contents Preface.... iii Informatica Resources.... iii Informatica My Support Portal.... iii Informatica Documentation.... iii Informatica Web Site.... iii Informatica How-To Library.... iii Informatica Knowledge Base.... iv Informatica Support YouTube Channel.... iv Informatica Marketplace.... iv Informatica Velocity.... iv Informatica Global Customer Support.... iv Chapter 1: Introduction.... 1 Overview.... 1 Informatica Resource Kit Documentation.... 1 Informatica Sample ORS.... 2 Sample Applications and Utilities.... 2 LookupWebServiceExample.... 2 IDD Demo.... 2 BDDUserExit.... 2 SSO.... 3 PartyWebServiceExample.... 3 SAMProvidersExample.... 3 Business Process Management (BPM).... 3 MetCommand Utility.... 3 WsCodeGenPlugin.... 3 CleanseAdapterExample.... 3 MetModelConverter.... 4 Password Encryption Tool Utility.... 4 siperian-common.jar.... 4 BPM SDK.... 4 SIF SDK.... 4 Javadocs.... 5 SSA-NAME3.... 5 Jaspersoft.... 5 Chapter 2: Installing the Informatica MDM Hub Resource Kit.... 6 Overview.... 6 Table of Contents i

System Requirements.... 6 Set Environment Variables.... 6 Preparing to Install the Sample Applications.... 7 Setting Up the Informatica MDM Hub Sample Operational Reference Store On Oracle.... 7 Setting Up the Informatica MDM Hub Sample Operational Reference Store On IBM DB2.... 10 Registering the Informatica MDM Hub Sample Operational Reference Store.... 10 Installing the Informatica MDM Hub Resource Kit.... 14 Troubleshooting Your Installation.... 17 Uninstalling the Informatica MDM Hub Resource Kit.... 17 Modifying and Redeploying Applications.... 18 Running the postinstallsetup Process Manually.... 18 Appendix A: Using the Password Encryption Tool.... 20 Overview.... 20 System Requirements.... 20 Running the Password Encryption Tool.... 20 Encrypting a New Password.... 21 Updating the ORS Database Password.... 21 Updating the System Database Password.... 21 Appendix B: Silent Installation.... 22 Silent Installation from the Command Line.... 22 Properties Files for Silent Installation.... 22 Creating Properties File for Resource Kit.... 23 Running the Silent Installation.... 26 Index.... 28 ii Table of Contents

Preface This guide describes how to install, configure, and use the Informatica MDM Hub Resource Kit. Note: This guide is written for a technical audience: service developers, database administrators, system administrators, and other implementers who are responsible for Informatica MDM Hub installation and setup tasks. Familiarity with the database environment on which you are installing the Resource Kit and knowledge of Oracle administration is assumed. See the Informatica MDM Hub Configuration Guide for Informatica MDM Hub administration and configuration information. Informatica Resources Informatica My Support Portal As an Informatica customer, you can access the Informatica My Support Portal at http://mysupport.informatica.com. 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 takes every effort to create accurate, usable documentation. If you have questions, comments, or ideas about this documentation, contact the Informatica Documentation team through email 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 http://mysupport.informatica.com. Informatica Web Site You can access the Informatica corporate web site at http://www.informatica.com. 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. Informatica How-To Library As an Informatica customer, you can access the Informatica How-To Library at http://mysupport.informatica.com. The How-To Library is a collection of resources to help you learn more about Informatica products and features. It includes iii

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 http://mysupport.informatica.com. 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 email at KB_Feedback@informatica.com. Informatica Support YouTube Channel You can access the Informatica Support YouTube channel at http://www.youtube.com/user/infasupport. The Informatica Support YouTube channel includes videos about solutions that guide you through performing specific tasks. If you have questions, comments, or ideas about the Informatica Support YouTube channel, contact the Support YouTube team through email at supportvideos@informatica.com or send a tweet to @INFASupport. Informatica Marketplace The Informatica Marketplace is a forum where developers and partners can share solutions that augment, extend, or enhance data integration implementations. By leveraging any of the hundreds of solutions available on the Marketplace, you can improve your productivity and speed up time to implementation on your projects. You can access Informatica Marketplace at http://www.informaticamarketplace.com. Informatica Velocity You can access Informatica Velocity at http://mysupport.informatica.com. Developed from the real-world experience of hundreds of data management projects, Informatica Velocity represents the collective knowledge of our consultants who have worked with organizations from around the world to plan, develop, deploy, and maintain successful data management solutions. If you have questions, comments, or ideas about Informatica Velocity, contact Informatica Professional Services at ips@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 http://mysupport.informatica.com. The telephone numbers for Informatica Global Customer Support are available from the Informatica web site at http://www.informatica.com/us/services-and-training/support-services/global-support-centers/. iv Preface

C H A P T E R 1 Introduction This chapter includes the following topics: Overview, 1 Informatica Resource Kit Documentation, 1 Informatica Sample ORS, 2 Sample Applications and Utilities, 2 BPM SDK, 4 SIF SDK, 4 Javadocs, 5 SSA-NAME3, 5 Jaspersoft, 5 Overview The Informatica MDM Hub Resource Kit is a set of examples and utilities that assist you in integrating the Informatica MDM Hub into your applications and workflows. Informatica Resource Kit Documentation The Informatica MDM Hub Resource Kit includes the following documentation for the Informatica MDM Resource Kit: Sample application documentation These files are located in the Resource Kit in the specific sample application folders (for example, BPM) within the samples folder. 1

Informatica Sample ORS The Informatica Sample ORS is used by the various sample applications included with the Informatica Resource Kit. The Informatica Sample ORS includes the scripts, PLB files, mdm_sample.dmp, and related files that you require to create a sample ORS schema. Note: Install the Informatica Sample ORS in your database and register it with the Informatica MDM Hub Server before you install the sample applications. Sample Applications and Utilities The Informatica MDM Hub Resource Kit includes the following set of sample applications and utilities: LookupWebServiceExample idd Demo BDDUserExit SSO PartyWebServiceExample SAMProvidersExample Business Process Management (BPM) MetCommand Utility WsCodeGenPlugin CleanseAdapterExample MetModelConverter Password Encryption Tool Utility siperian-common.jar Note: For more information, see the readme.txt file for each sample application or utility. ReadMe files are located in the Resource Kit Samples and Utilities folder. LookupWebServiceExample LookupWebServiceExample is an example of a web service for exposing the cross reference services for the entities managed by the hub and code translation services for the lookup codes defined in the hub. IDD Demo The IDD Demo is a sample of the Informatica Data Director (IDD), which is a data governance application for Informatica MDM Hub. Business users can use IDD to effectively create, manage, consume, and monitor master data. Use the sample configuration file, IDDConfig.xml, and the configuration tool, to set up an IDD interface for the sample schema that is included in the Resource Kit. BDDUserExit The BDDUserExit is a set of sample user exits that you can use as a template to build user exit JAR files. You can use user exits to add custom business logic to standard IDD operations. 2 Chapter 1: Introduction

SSO SSO contains a set of sample modules that you can build in IDD or the MDM Hub. Use SSO samples to allow thirdparty application users to use external Single-Sign-On provider to log in to IDD. The Resource Kit includes SSO sample modules for Google and Salesforce. The Google SSO module uses redirection to an external form for authentication. The Salesforce SSO module authenticates through a secured connection to the Salesforce application. PartyWebServiceExample PartyWebServicesExample is an example of a set of composite web services built around the Informatica Sample Schema. The web services are built using the Axis web services framework and the SIF APIs are used to access the hub. SAMProvidersExample The SAMProvidersExample shows the basics of building custom SAM providers. The jar file that is built by this sample application is installed through the Console in the Security Providers tool. For additional information regarding the process of installing a provider, refer to Managing Provider Files, in the Informatica MDM Hub Configuration Guide Business Process Management (BPM) The Business Process Management (BPM) sample describes how a developer can create an integration between a workflow tool and the Informatica MDM Hub. The IDD-Interstage integration requires the IDD-InformaticaFujitsuLibrary.bar file. This file is located in the samples/bpm/fujitsu directory within the Resource Kit. MetCommand Utility MetCommand is a simple command-line wrapper for the Informatica MDM Hub Repository Manager APIs. These APIs are used to manage the metadata (export, import, validate) in the Informatica MDM Hub. It can be used in situations where it is desirable to execute these APIs as part of a script - to automate the promotion of design objects from one ORS to another. WsCodeGenPlugin The Eclipse Web Services Code Generator (WsCodeGen) is an Eclipse plug-in for generating the skeleton of a Web Service for use with Informatica MDM SIF services. Components generated by WsCodeGen include Java beans, the WSDL, Castor mapping file, WSDD and other property files required to create a Web Service. The plug-in enables the user to focus on creating and adding business logic code to the framework. CleanseAdapterExample The CleanseAdapterExample allows you to create cleanse adapters to work with your specific, non-supported cleanse engine. For more information about supported cleanse adapters, see the Informatica MDM Hub Cleanse Adapter Guide. Sample Applications and Utilities 3

MetModelConverter MetModelConverter is a command-line utility that converts Common Warehouse Metamodel to Informatica MDM Hub Change List XML format. It demonstrates how Informatica MDM Hub Repository Manager can be used to integrate 3rd party software like ERWIN. Password Encryption Tool Utility The Password Encryption tool is a command-line utility for encrypting your secured database passwords. Instructions for using this utility are located in the Appendix A, Using the Password Encryption Tool on page 20 siperian-common.jar The siperian-common.jar file contains resources such as Hub exception classes, language bundles, and licensing utilities. The siperian-common.jar file is used by the MDM Hub components including custom applications that call SIF APIs. BPM SDK The Informatica MDM Hub Resource Kit installer provides the option to install the BPM SDK. The BPM SDK is installed at the following location: <Resourcekit_Home>\bpmsdk The SDK lets you develop adapters using the BPM SDK interfaces to integrate to an external workflow engine. The BPM adapters developed using the BPM SDK can be uploaded to the MDM Hub. The adapter implementation can be used by the Hub and IDD to communicate with a BPM engine. For more information on BPM adapter implementation, refer to the BPM Adapter SDK Implementation Guide. SIF SDK The Informatica MDM Hub Resource Kit installer also installs the Services Integration Framework (SIF). The SIF is the part of Informatica MDM Hub that interfaces with client programs. Logically, it serves as a middle tier in the client/ server model. It enables you to implement request/response interactions using any of the following architectural variations: Loosely coupled web services using the SOAP protocol. Tightly coupled Java remote procedure calls based on Enterprise JavaBeans (EJBs). Asynchronous Java Message Service (JMS)-based messages. XML documents going back and forth via Hypertext Transfer Protocol (HTTP). Each of the above SIF protocols sits on top of the native Informatica MDM Hub protocol, which accepts requests in the form of XML documents or EJBs and returns responses the same way. You copy the SIF SDK to any client system on which you wish to develop and run programs to interact with Informatica MDM Hub via SIF. If you can run a Java virtual machine (JVM) on the client system, you can use the Java classes included in the SIF SDK. The SDK installs the SIF-SDK in the following location: <Resourcekit_Home>\sdk\sifsdk 4 Chapter 1: Introduction

You can configure the SDK to use any SIF protocol. If you cannot run a JVM, then you must explicitly use web services (for example, on a pure.net system) or JMS (for example, on a mainframe system), or XML over HTTP. For a complete description of the Informatica SIF-SDK, refer to the Informatica MDM Hub Services Integration Framework Guide. This guide refers to these Java classes by the name of the first class you must instantiate, SiperianClient. Javadocs The Informatica MDM Hub Resource Kit installer installs the java documentation for the SIF API in the following locations: <Resourcekit_Home>\sdk\sifsdk\javadoc <Resourcekit_Home>\sdk\sip-plugin\javadoc You can view the associated java packages and classes using the index.html file. The index.html file is located in the following directory: <Resourcekit_Home>\sdk\sifsdk\javadoc\index.html Open index.html to see a right-hand frame and two left-hand frames. The left frames provide links to the pages for all packages and all classes. The lower left frame displays the links associated with the package you select in the upper left frame. You can select All Classes in the upper left frame to see a combined list of classes from all packages in the lower left frame. The right frame changes to show the pages you select. Begin by exploring the classes of the com.siperian.sif.message package. Most of the classes used in application programs are in this package and its sub-packages. SSA-NAME3 The Informatica MDM Hub Resource Kit installer provides the option to install SSA-NAME3. It provides the libraries that are required to use the Population Override Manager and the SSA-Name3 Edit Rules Wizard to customize match population. SSA-Name3 resources are copied to the following location: <Resourcekit_Home>\ssaname3 You can use SSA-NAME3 to enable application programs to search and match records in databases using people s names, organization names, addresses, identity numbers, dates and other identification data. Jaspersoft The Informatica MDM Hub Resource Kit installer provides the option to copy the resources for installing Jaspersoft. The resources for installing Jaspersoft are copied to the following location: <Resourcekit_Home>\jaspersoft You can use Jaspersoft, which is a Business Intelligence (BI) tool, to develop and analyze reports for the Informatica MDM Hub. Javadocs 5

C H A P T E R 2 Installing the Informatica MDM Hub Resource Kit This chapter includes the following topics: Overview, 6 System Requirements, 6 Preparing to Install the Sample Applications, 7 Installing the Informatica MDM Hub Resource Kit, 14 Uninstalling the Informatica MDM Hub Resource Kit, 17 Modifying and Redeploying Applications, 18 Overview The Informatica MDM Hub Resource Kit installer installs the Resource Kit components. Important: Before you run the Informatica MDM Hub Resource Kit installer, the Informatica MDM Hub must be installed and configured for your environment. In addition, you need to install and register the Informatica MDM Hub Sample ORS, and you must have purchased a license for the Informatica MDM Hub Hierarchy Manager. System Requirements For more information about product requirements and supported platforms, see the Product Availability Matrix on the Informatica Customer Portal: https://communities.informatica.com/community/my-support/tools/product-availability-matrices Set Environment Variables Set the environment variables before you install the MDM Hub Resource Kit. You must set the JAVA_HOME environment variable to point to JDK 1.7.0_25 or later. 6

Preparing to Install the Sample Applications The Informatica MDM Hub Server must be installed and configured for your environment before you begin using the Informatica MDM Hub sample applications. You must have: A valid installation of the Informatica MDM Hub (Hub Store Master and Informatica MDM Hub Server / Process Server) Purchased a license for the Informatica MDM Hub Hierarchy Manager For a complete description of how to install the Informatica MDM Hub Server, refer to Informatica MDM Hub Installation Guide. In addition, you need to install the sample schema and register the ORS prior to installing the sample applications. Setting Up the Informatica MDM Hub Sample Operational Reference Store On Oracle You must set up the MDM Hub sample Operational Reference Store before you can use it. To set up the MDM Hub sample Operational Reference Store, create an Operational Reference Store and import mdm_sample into it. 1. Create a temporary directory on the Oracle database server or on a client workstation that has an Oracle client installed with the Oracle import utility, imp.exe. 2. Copy all the files from the Informatica MDM Hub distribution directory to the temporary directory. 3. Navigate to the following location in the distribution directory: On UNIX. <distribution directory>/database/bin On Windows. <distribution directory>\database\bin 4. Run the following command: On UNIX. sip_ant.sh create_ors On Windows. sip_ant.bat create_ors 5. Answer the following prompts: Prompts Enter database type (ORACLE, MSSQL, DB2) Enter Oracle Connection Type (service, sid). [service] Description Database type. Specify ORACLE. 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. Enter the Operational Reference Store database host name [localhost] Name of the host that is running the database. Default is localhost. Preparing to Install the Sample Applications 7

Prompts Enter the Operational Reference Store database port number [1521] Enter the Operational Reference Store database service name [orcl] Enter Oracle Net connect identifier (TNS Name) [orcl] Master Database Connect URL: "jdbc:oracle:thin:@// <host_name>:<port>/<service_name>". Do you want to change the connect URL (y/n) [n] Enter database SID [orcl] Enter the Operational Reference Store database user name [cmx_ors] Enter the Operational Reference Store database user password Enter locale name from the list: de, en_us, fr, ja, ko. [en_us] Enter the DBA user name [SYS] Enter the DBA password Enter the name of the MDM index tablespace [CMX_INDX] Enter the name of the MDM temporary tablespace (Not an Oracle temporary tablespace) [CMX_TEMP] Enter the name of the Oracle temporary tablespace [TEMP] Description Port number that the database listener uses. Default is 1521. Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE. Oracle TNS name to connect to the Oracle database. Default is orcl. Connect URL for the Oracle connection type SERVICE. You can type y to change the default connect URL. To use the default connect URL, type n. Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID. Default is orcl. Name of the Operational Reference Store database. Specify mdm_sample. Password to access the Operational Reference Store. Operating system locale. Default is en_us. User name of the administrative user. Default is SYS. Password of the administrative user. Name of the tablespace to contain the index components for the Operational Reference Store. Default is CMX_INDX. Name of the tablespace to contain the temporary components for the Operational Reference Store. Default is CMX_TEMP. Name of the Oracle temporary tablespace. Default is TEMP. The mdm_sample Operational Reference Store is created. 6. In a command prompt, change to the following directory: On UNIX. <distribution directory>/database/resources/database/oracle On Windows. <distribution directory>\database\resources\database\oracle 7. Run the following command to import data into the mdm_sample Operational Reference Store: imp system/<password of system user>@<tns name> file=mdm_sample.dmp fromuser=mdm_sample touser=mdm_sample 8 Chapter 2: Installing the Informatica MDM Hub Resource Kit

8. If you use a localized version of the MDM Hub distribution directory, perform the following steps: a. Open a command prompt and change to the following directory: On UNIX. <distribution directory>/database/bin On Windows. <distribution directory>\database\bin b. Run the following command: On UNIX. sip_ant.sh localize_ors On Windows. sip_ant.sh localize_ors c. Answer the localized versions of the following prompts: Prompts Enter database type (ORACLE, MSSQL, DB2) Enter Oracle Connection Type (service, sid). [service] Description Database type. Specify ORACLE. 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. Enter the Operational Reference Store database host name [localhost] Enter the Operational Reference Store database port number [1521] Enter the Operational Reference Store database service name [orcl] Enter Oracle Net connect identifier (TNS Name) [orcl] Master Database Connect URL: "jdbc:oracle:thin:@//<host_name>:<port>/ <service_name>". Do you want to change the connect URL (y/n) [n] Enter database SID [orcl] Enter the Operational Reference Store database user name [cmx_ors] Name of the host that is running the database. Default is localhost. Port number that the database listener uses. Default is 1521. Name of the Oracle service. This prompt is displayed if the selected Oracle connection type is SERVICE. Oracle TNS name to connect to the Oracle database. Default is orcl. Connect URL for the Oracle connection type SERVICE. You can type y to change the default connect URL. To use the default connect URL, type n. Name of the Oracle System ID. This prompt is displayed if the selected Oracle connection type is SID. Default is orcl. Name of the Operational Reference Store database. Specify mdm_sample_<locale>. Preparing to Install the Sample Applications 9

Prompts Enter the Operational Reference Store database user password Enter locale name from the list: de, en_us, fr, ja, ko. [en_us] Description Password to access the Operational Reference Store. Operating system locale. Default is en_us. After you set up the MDM Hub sample Operational Reference Store, use the MDM Hub Console to register the sample Operational Reference Store. Setting Up the Informatica MDM Hub Sample Operational Reference Store On IBM DB2 You must set up the MDM Hub sample Operational Reference Store before you can use it. 1. Create the mdm_sample user on the machine on which the database is installed. 2. Add the mdm_sample user to the DB2ADMNS and DB2USERS user groups. 3. Open a IBM DB2 command window and change to the following directory: <distribution_directory>\database\resources\database\db2 4. Run the following command: db2 restore db mdmsmpl redirect generate script restore_mdmsmpl.db2 5. Create a directory such as C:\MDMSMPL\LOGS. 6. Edit the restore_mdmsmpl.db2 script. The restore_mdmsmpl.db2 script is in the following directory: <distribution_directory>\database\resources\database\db2 a. Uncomment the following line and change the path to point to the directory that you created in Step 5: -- NEWLOGPATH 'D:\DB2_01\NODE0000\SQL00007\SQLOGDIR\' b. Change all paths from E:\MDMSMPL\... to the path that you specify for the MDMSMPL directory in Step 5. 7. Run the following command: db2 -tvf restore_mdmsmpl.db2 Registering the Informatica MDM Hub Sample Operational Reference Store After you set up the MDM Hub sample Operational Reference Store, you must register it. You can register the MDM Hub sample Operational Reference Store through the Hub Console. 1. Start the Hub Console. The Change database dialog box appears. 2. Select the MDM Hub Master database, and click Connect. 3. Start the Databases tool under the Configuration workbench. 4. Click Write Lock > Acquire Lock. 5. Click the Register database button. The Informatica MDM Hub Connection Wizard appears and prompts you to select the database type. 10 Chapter 2: Installing the Informatica MDM Hub Resource Kit

6. Select the type of database, and click Next. 7. Configure connection properties for the database. Configure connection properties for the Oracle database: 1. Select an Oracle connection method, and click Next. The following table describes the Oracle connection methods that you can select: Connection Method Service SID Description Connect to Oracle by using the service name. Connect to Oracle by using the Oracle System ID. The Connection Properties page appears. 2. Specify the connection properties for the connection type that you select, and click Next. The following table lists and describes the connection properties: Property Database Display Name Machine Identifier Database hostname SID Service Port Oracle TNS Name Schema Name Description Name for the Operational Reference Store that must appear in the Hub Console. Prefix given to keys to uniquely identify records from the Hub Store instance. IP address or name of the server that hosts the Oracle database. Oracle System Identifier that refers to the instance of the Oracle database running on the server. The SID field appears if you selected the SID connection type. Name of the Oracle SERVICE used to connect to the Oracle database. The Service field appears if the you selected the Service connection type. The TCP port of the Oracle listener running on the Oracle database server. The default is 1521. Name by which the database is known on your network as defined in the TNSNAMES.ORA file of the application server. For example: mydatabase.mycompany.com. You set the Oracle TNS name when you install the Oracle database. For more information about the Oracle TNS name, see the Oracle documentation. Name of the Operational Reference Store. Specify mdm_sample. Preparing to Install the Sample Applications 11

Property User name Password Description User name for the Operational Reference Store. By default, this is the user name that you specify in the script that you use to create the Operational Reference Store. This user owns all of the Operational Reference Store database objects in the Hub Store. If a proxy user is configured for the Operational Reference Store, then you can specify the proxy user instead. Password associated with the user name for the Operational Reference Store. For Oracle, the password is not case sensitive. By default, this is the password that you specify when you create the Operational Reference Store. If a proxy user is configured for the Operational Reference Store, then you specify the password for the proxy user instead. The Summary page appears. 3. Review the summary, and specify additional connection properties. The following table lists additional connection properties that you can configure: Property Connection URL Description Connect URL. The Connection Wizard generates the connect URL by default. The following list shows the format of the connect URL for the Oracle connection types: Service connection type jdbc:oracle:thin:@//database_host:port/ service_name SID connection type jdbc:oracle:thin:@//database_host:port/sid For a service connection type only, you have the option to customize and later test a different connection URL. Create datasource after registration Select to create the datasource on the application server after registration. Note: If you do not select the option, you must manually configure the data source. 4. For a service connection type, if you want to change the default URL, click the Edit button, specify the URL, and then click OK. Configure connection properties for the IBM DB2 database: 1. Specify the connection properties, and click Next. 12 Chapter 2: Installing the Informatica MDM Hub Resource Kit

The following table lists and describes the connection properties: Property Database Display Name Machine Identifier Database server name Database name Database hostname Schema Name User name Password Description Name for the Operational Reference Store that must appear in the Hub Console. Prefix given to keys to uniquely identify records from the Hub Store instance. IP address or name of the server that hosts the IBM DB2 database. Name of the database that you create. IP address or name of the server that hosts the IBM DB2 database. Name of the Operational Reference Store. User name for the Operational Reference Store. By default, this is the user name that you specify in the script that you use to create the Operational Reference Store. This user owns all the Operational Reference Store database objects in the Hub Store. If a proxy user is configured for the Operational Reference Store, then you can specify the proxy user instead. Password associated with the user name for the Operational Reference Store. For IBM DB2, the password is case sensitive. By default, this is the password that you specify when you create the Operational Reference Store. If a proxy user is configured for the Operational Reference Store, then you specify the password for the proxy user instead. The Summary page appears. 2. Review the summary, and specify additional connection properties. The following table lists additional connection properties that you can configure: Property Connection URL Description Connect URL. The Connection Wizard generates the connect URL by default. The following example shows the format of the connect URL: jdbc:db2:@//database_host:port/service_name Create datasource after registration Select to create the datasource on the application server after registration. Note: If you do not select the option, you must manually configure the data source. 8. Click Finish. The Registering Database dialog box appears. 9. Click OK. The MDM Hub registers the MDM Hub sample Operational Reference Store. Preparing to Install the Sample Applications 13

10. Select the MDM Hub sample Operational Reference Store that you registered, and click the Test database connection button to test the database settings. The Test Database dialog box displays the result of the database connection test. 11. Click OK. The Operational Reference Store is registered, and the connection to the database is tested. Installing the Informatica MDM Hub Resource Kit You can install the MDM Hub Resource Kit in graphical mode. Note: You must complete a full installation in order to upgrade to a newer version of the Informatica MDM Hub Resource Kit. There is no patch install for the Resource Kit. 1. Start the application Server. 2. Run the MDM Hub Resource Kit installer from the distribution directory. By default the installer is in the following directory: On Windows. <distribution directory>\windows\mrmresourcekit On UNIX. <distribution directory>/<operating system name>/mrmresourcekit 3. Select the installation language and click OK. The Introduction window appears. 4. Click Next. The License Agreement window appears. 5. Select the I accept the terms of the License Agreement option and click Next. The Installation Feature window appears. 6. Select the Resource Kit features that you want to install and click Next. Option Sample Schema Samples and Utilities SIF SDK and Javadocs BPM SDK Jaspersoft SSA-NAME3 Description Select this option to install the Sample Schema. You must create a sample schema and register it with the Informatica MDM Hub Server before installing the sample applications. Cancel the installation and see Setting Up the Informatica MDM Hub Sample Operational Reference Store On Oracle on page 7 for instructions. Select this option to install the sample applications and utilities. The list of sample applications deployed is stored in the build.properties file. This file is located in the following directory: <Resourcekit_Home>\samples Select this option to install the javadocs, libraries, and resources associated with the SIF SDK. Select this option to install the resources associated with the BPM SDK. Select this option to copy the Jaspersoft installer to the Resource Kit home. Select this option to copy the SSA-NAME3 installer to the Resource Kit home. The Choose Install Folder window appears. 14 Chapter 2: Installing the Informatica MDM Hub Resource Kit

7. Select the location of the Hub Server installation. To choose the default location, click Next. To enter a path, type the path to the installation folder, and click Next. Note: The installation fails if you specify a path that has spaces in the directory or folder names. To return to the default installation location, click Restore Default Folder. To choose another location, click Choose, and then click Next. On UNIX, the Choose Link Folder window appears. On Windows, the Choose Shortcut Folder window appears. 8. On UNIX, choose a link folder or select the option to not create links and click Next. On Windows, select the location to create a product icon or select the option not to create a product icon. The Configuration Selection window appears. 9. Select a configuration option and click Next. Option Configure Samples Source Only Description Configures the samples. Installs the sources of samples. If you select Configure samples, the Resource Kit App Server window appears. If you select Source only, then the Pre-Installation Summary window appears. 10. From the Resource Kit App Server window, select the application server on which you want to install the Informatica MDM Hub Resource Kit, and click Next. The Application Server Home window for the application server that you select appears. 11. Configure the application server settings. Configure the following JBoss settings: 1. Specify the application server installation directory, and then click Next. The JBoss Application Server Configuration Name window appears. 2. Specify the Configuration Name, and then click Next. The default value is standalone. 3. Specify the remote port. Configure the following WebLogic Server settings: 1. Choose a path to the WebLogic domain installation directory for the domain you want to use for the MDM Hub, and click Next. The WebLogic Application Server Login window appears. 2. Enter WebLogic Server login information. Installing the Informatica MDM Hub Resource Kit 15

The following table describes the login parameter fields: Field Name Host Server User Name Password Port Number Description Name of the host computer that has the WebLogic installation. Name of the WebLogic Server instance in the domain on which WebLogic is deployed. Name of the user for the WebLogic installation. Password that corresponds to the WebLogic user. Port number on which the WebLogic Server is listening. Configure the following WebSphere settings: 1. Choose a path to the WebSphere application server and click Next. The Reminder window appears. 2. Ensure that you have fulfilled the prerequisites and click OK. The WebSphere Security Selection window appears. 3. Select whether WebSphere is security enabled or not and click Next. If you select No, and then click Next, the WebSphere Application Server Port window appears. Default is No. Set the server name, and the RMI and SOAP ports for the WebSphere application server. In a clustered environment, enter one of the cluster server names and its corresponding SOAP and RMI port information. If you select Yes, and then click Next, the WebSphere Application Server Port and User Credentials window appears. Specify the WebSphere user name and the WebSphere password. The Informatica MDM Hub Server window appears. 12. Enter the information for the Hub Server installation, and click Next. Field Name Server Name Server HTTP Port Informatica MDM Administrative password Description Name of the server that hosts the Hub Server. Port number of the Hub Server. Password to access the MDM Hub. The Resource Kit ORS ID window appears. 13. Select a Resource Kit ORS ID from the list, and click Next. The drop down list contains the Operational Reference Store IDs that you created. Select an Operational Reference Store ID related to the Sample Schema. If you have not registered the sample schema, you will not see the Operational Reference Store ID for the Sample schema. Register the sample Operational Reference Store, then restart the installation. The Deployment Selection window appears. 16 Chapter 2: Installing the Informatica MDM Hub Resource Kit

14. Select one of the following options and click Next: Option Yes, run it during this installation. No, it can be deployed later. Description Deploys and configures the MDM Hub Resource Kit during the installation. Select this option to deploy and configure manually at a later time. If you chose to install the Samples and Utilities feature, then you must deploy and configure the Resource Kit in this installation step to be able to make changes and redeploy the samples using the postinstallsetup script provided in the MDM Hub Resource Kit. If you choose to run the post-install setup manually, then you cannot deploy the EAR file using the postinstallsetup script at a later time. You must manually edit the EAR file and deploy it to make any changes to your installation. The Pre-Installation Summary window appears. 15. Review the Pre-Installation Summary to confirm your installation choices, and click Install. When the installation completes, the Install Complete window appears. 16. Click Done to exit the MDM Hub Resource Kit installer. Troubleshooting Your Installation Log files are useful for troubleshooting your Informatica sample application installation. Save these files after a failure and provide them when you call Informatica Support: <ResourceKit_Home> \Infamdm_Hub_Resource_Kit_InstallLog.xml contains the messages for the installation. <ResourceKit_Home> \deploy\logs\postinstallsetup.log contains the messages for the postinstallsetup script. Application server log files Uninstalling the Informatica MDM Hub Resource Kit Use the Informatica uninstaller program to remove the Resource Kit. To uninstall the Resource Kit: 1. Click the Start button and select Programs > Informatica > Hub > ResourceKit > Uninstall Informatica MDM Resource Kit. Or navigate to the following directory and double-click Uninstall_Infamdm_Hub_Resource Kit.exe: <ResourceKit_Home>\deploy\UninstallerData Which by default is: C:\infamdm\hub\resourcekit\deploy\UninstallerData Uninstalling the Informatica MDM Hub Resource Kit 17

The Uninstall Informatica MDM Hub Resource Kit screen is displayed. 2. Click Uninstall to begin. The Uninstall Complete screen is displayed. 3. Click Done. Modifying and Redeploying Applications To modify and redeploy the existing sample applications, perform the following steps: 1. Make the desired changes. 2. Recompile the application. 3. Rerun the postinstallsetup script that is located in the following location: C:\infamdm\hub\resourcekit\deploy Running the postinstallsetup Process Manually The postinstallsetup process packages the EAR file that is subsequently deployed on the Application Server. By default, the postinstallsetup script is located in the following directory: <ResourceKit_Home>\deploy To run the post-install script manually: For the WebLogic application server, run the following command from a command prompt: postinstallsetup.bat -Dweblogic.password=<your_password> - Ddatabase.password=<your_database_password> where <your_password> is the password for your WebLogic application server. A typical way of running this script for WebLogic is as follows: C:\infamdm\hub\resourcekit\deploy>postInstallSetup.bat -Dweblogic.password=weblogic - Ddatabase.password=!!cmx!! 18 Chapter 2: Installing the Informatica MDM Hub Resource Kit

For the WebSphere and JBoss application servers, run the following command from a command prompt: postinstallsetup.bat Modifying and Redeploying Applications 19

A P P E N D I X A Using the Password Encryption Tool This appendix includes the following topics: Overview, 20 System Requirements, 20 Running the Password Encryption Tool, 20 Overview The Password Encryption tool is a command-line utility that is used to encrypt your secured database passwords. Note: See the sample folders for more information about the additional samples and utilities included in the Resource Kit. System Requirements You need to make sure Siperian-common.jar is installed under the Utilities directory. In addition, you must have Java installed and have the jar file to be able to run this utility. Running the Password Encryption Tool In order to successfully change the schema password, you must change it in several places. The first area in which you must change the schema password is in the data sources defined in the application server. This password is not encrypted as the application server protects it. Both username and password are stored in the cmxserver.properties file, and the password must be entered in encrypted form. The parameters are stored in cmxserver.properties as: [databaseid].username=username [databaseid].password=encryptedpassword 20

In addition to the data sources on the application server, Informatica requires the password to be encrypted and stored in various tables. Encrypting a New Password To encrypt the new password, go to the Utilities folder (for example, C:\infamdm\hub\resourcekit\utilities), and execute the following command from the prompt: java -classpath siperian-common.jar com.siperian.common.security.blowfish [key_type] plain_text_password where key_type is either DB_PASSWORD_KEY (default) or PASSWORD_KEY. The results are echoed to the terminal window: Plaintext Password: your_new_password Encrypted Password: encrypted password For example, if admin is your the new password, the command is: java -classpath siperian-common.jar com.siperian.common.security.blowfish PASSWORD_KEY admin The results are displayed as follows: Plaintext Password: admin Encrypted Password: A75FCFBCB375F229 Updating the ORS Database Password Execute the following commands to update the passwords for your ORS databases: To update your ORS database password: UPDATE C_REPOS_DB_RELEASE SET DB_PASSWORD = ''; COMMIT; Updating the System Database Password Execute the following commands to update the passwords for your System databases: To update your CMX_SYSTEM database password: UPDATE C_REPOS_DATABASE SET PASSWORD = '' WHERE USER_NAME = '' Running the Password Encryption Tool 21

A P P E N D I X B Silent Installation This appendix includes the following topics: Silent Installation from the Command Line, 22 Properties Files for Silent Installation, 22 Creating Properties File for Resource Kit, 23 Running the Silent Installation, 26 Silent Installation from the Command Line You can run a silent installation of the Resource Kit from the command line on UNIX and Windows systems. The silent installation procedure, does not display screens or messages associated with the installation. You can use a silent installation if you need to perform multiple installations or install on a machine cluster. The silent installation procedure does not validate your settings. The silent installation process may complete successfully even if you provide incorrect settings, such as a wrong application server path or an incorrect port setting. Such problems might become known only after completing the silent installation, when you use the Resource Kit. Properties Files for Silent Installation To run a silent installation of the Resource Kit, you must create a silent properties file. The following is a sample silent properties file: INSTALLER_UI=silent SIP.INSTALL.TYPE=SIPERIAN_SAMPLE_INSTALL #Installation Features #0=Do not install #1=Install SIP.INSTALL.DOCS=1 SIP.INSTALL.SAMPLE.SCHEMA=1 SIP.INSTALL.SAMPLES=1 SIP.INSTALL.SIF.SDK=1 SIP.INSTALL.UTILITIES=1 SIP.INSTALL.BMP.SDK=1 ## Resource Kit Install directory. USER_INSTALL_DIR=C\:\\infamdm\\hub\\resourcekit ## If you want to configure samples as a part of the silent installation, then set the following 22

property. RUN_CONFIGURE_SETUP="Configure Samples" ## If you want to install only source samples as a part of the silent installation, then set the following property. #RUN_CONFIGURE_SETUP="Source only" ## Following are the properties for application servers JBoss, WebSphere, WebLogic. ## Properties for only one applicaton server should be set. ## Properties for the JBoss application server SIP.AS.CHOICE="JBoss" SIP.AS.HOME=C\:\\jboss-4.0.3SP1 JBOSS.AS.PORT_1=1099 SIP.JBOSS.CONFIGURATION_NAME=production ## Properties for the WebSphere application server SIP.AS.CHOICE="WebSphere" SIP.AS.HOME=C\:\\Program Files\\WebSphere\\AppServer SIP.WEBSPHERE.SECURITY.ENABLED=No SIP.AS.SERVER=server1 SIP.AS.PORT_2=2809 SIP.AS.PORT_3=8880 SIP.AS.PROFILENAME=AppSrv01 # if SIP.WEBSPHERE.SECURITY.ENABLED is 'Yes', following two properties need to be set SIP.APPSERVER.USERNAME=username SIP.APPSERVER.PASSWORD=password ## Properties for the WebLogic application server SIP.AS.CHOICE="WebLogic" SIP.AS.HOME=C\:\\bea\\user_projects\\domains\\base_domain SIP.APPSERVER.HOST=localhost SIP.APPSERVER.SERVER=AdminServer SIP.APPSERVER.USERNAME=weblogic SIP.APPSERVER.PASSWORD=weblogic WEBLOGIC.AS.PORT=7001 ## Properties for the Siperian Hub Server SIP.SERVER.NAME=localhost SIP.SERVER.HTTP.PORT=7001 SIP.ADMIN.PASSWORD=admin #sip ors id from hub server SIP.ORS.ID=mmizrahi~-755-orcl-MDM_SAMPLE ## If you want to run postinstallsetup as a part of silent install, then set the following property. RUN_DEPLOYMENTSETUP="Yes" You must modify the sample silent properties file according to your environment. Note: In the silent properties file, backslashes (\)and foreslashes (/) are special characters, so you must enter two of each when you enter information in this file, such as when you enter an installation path. For example, to enter the path to the Resource Kit directory (\u1\infamdm\hub\resourcekit), you must enter: \\u1\\infamdm\\hub\ \resourcekit. Creating Properties File for Resource Kit Important: The silent installer does not validate the settings in your properties file. You must ensure that you specify the correct settings and verify them before you run the silent installer. Create the silentinstallresourcekit_sample.properties file for the Resource Kit. You can rename this file and it can be located anywhere in the machine. Creating Properties File for Resource Kit 23

The following tables contain the properties to be set for Resource Kit silent installation. Install Directory Set the following properties for the install directory and installation type: Property INSTALLER_UI USER_INSTALL_DIR SIP.INSTALL.TYPE SIP.INSTALL.DOCS SIP.INSTALL.SAMPLE.SCHEMA SIP.INSTALL.SAMPLES SIP.INSTALL.SIF.SDK SIP.INSTALL.BPM.SDK SIP.INSTALL.UTILITIES Value Set the value to silent. Directory to install Hub Server. Example: <infamdm_install_directory>//hub// resourcekit Specify the installation type, such as SIPERIAN_SAMPLE_INSTALL. Specify if the Informatica MDM Hub documentation needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Specify if the Sample Schema needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Specify if the Samples needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Specify if SIF SDK needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Specify if BPM SDK needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Specify if Utilities needs to be installed. Set one of the following values: - 0=Do not install - 1=Install Application Server Properties Set properties for only one application server: JBoss, WebSphere, or WebLogic. 24 Appendix B: Silent Installation

JBoss Properties Set the following properties for JBoss: Property SIP.AS.CHOICE SIP.AS.HOME Value Application server name: JBoss Path to JBoss home JBOSS.AS.PORT_1 Your JBoss port number. Example: 8080 SIP.JBOSS.CONFIGURATION_NAME Configuration name. Default is production. WebLogic Properties Set the following properties for WebLogic: Property SIP.AS.CHOICE SIP.AS.HOME SIP.APPSERVER.HOST SIP.APPSERVER.SERVER SIP.APPSERVER.USERNAME SIP.APPSERVER.PASSWORD Value Application server name: WebLogic Path to WebLogic home. Example: //bea// user_projects//domains//base_domain Host name. Example: localhost Admin Server name. Example: AdminServer User name. Example: weblogic Password. Example: weblogic WEBLOGIC.AS.PORT Application server port. Example: 7001 WebSphere Properties Set the following properties for WebSphere: Property SIP.AS.CHOICE SIP.AS.HOME SIP.AS.SERVER Value Application server name: WebSphere Path to WebSphere home. Example: //WebSphere// AppServer Server name. Example: server1 SIP.AS.PORT_2 Port 2 (RMI port). Example: 2809 SIP.AS.PORT_3 Port 3 (SOAP port). Example: 8880 Creating Properties File for Resource Kit 25

Property SIP.AS.PROFILENAME SIP.WEBSPHERE.SECURITY.ENABLED (No or Yes) Value Application server profile name. Example: AppSrv01 If SIP.WEBSPHERE.SECURITY.ENABLED is 'Yes', following two properties must be set SIP.APPSERVER.USERNAME=username SIP.APPSERVER.PASSWORD=password MDM Hub Server Properties Set the following properties for the MDM Hub Server: Property SIP.SERVER.NAME SIP.SERVER.HTTP.PORT SIP.ADMIN.PASSWORD Value Hub Server server location. Example: localhost Hub Server port. Example: 7001 Hub Server password. Example: admin PostInstallSetup Properties If you want to run postinstallsetup as part of a silent install, set this property: Property RUN_DEPLOYMENT_FLAG Value Set this to 1 if you want to run postinstallsetup. Set to 0 if you do not want to run postinstallsetup at the end of the installation. Running the Silent Installation Once you have created the properties files for the Resource Kit, you can run the silent installation. To run the silent installation: 1. Ensure that your application server is started and running correctly. 2. Run the following command from the command prompt: For Windows:.\hub_resourcekit_install.exe -f <location_of_silent_properties_file_for_resourcekit> For UNIX:./hub_resourcekit_install.bin -f <location_of_silent_properties_file_for_resourcekit> 26 Appendix B: Silent Installation

3. After installation, check the postinstallsetup.log file to see if the installation was successful. If you set the RUN_DEPLOYMENT_FLAG property to 0, then look for the <infamdm_install_directory>/logs/ postinstall.log file. If you set the RUN_DEPLOYMENT_FLAG property to 1, then check to see that <infamdm_install_directory>/logs/ postinstallsetup.log has BUILD SUCCESSFUL (or failure if the install was not successful) at the end of the log file. Running the Silent Installation 27

I N D E X A applications, sample prerequisites before installing 7 J Javadocs index.html file location 5 B BDDUserExit 3 BPM sample application, about 3 BPM SDK 4 Business Process Management about 4 Business Process Management (BPM) about 4 sample application, about 3 C checking after Resource Kit installation 17 L log files 17 LookupWebServiceExample sample application, about 2 M modifying sample applications 18 O ORS database using the Password Encryption Tool to update the passwords 21 E encrypting a new password 21 G GWTSampleApp sample application, about 2 H Hub Server installing 14 I index.html location (for Javadoc) 5 Infamdm_Hub_Server_InstallLog.xml file 17 installation command line 22 silent 22 installing Resource Kit 14 P PartyWebServicesExample sample application, about 3 password using the Password Encryption Tool 21 Password Encryption Tool encrypting a new password 21 ORS database 21 running 20 System database 21 using 4, 20 postinstallsetup.log file 17 R redeploying sample applications 18 Resource Kit installing 14 log files 17 system requirements 6 uninstalling 17 S Sample application installation prerequisites 14 sample applications modifying and redeploying 18 prerequisites before installing 7 28

Sample installation log files checking 17 postinstallsetup.log file 17 Sample Schema installing 7, 10 registering 10 SAMProvidersExample sample application, about 3 Services Integration Framework about 4 Services Integration Framework (SIF) about 4 silent installation 22 Siperian-common.jar 20 SiperianClient class 4 System database using the Password Encryption Tool to update the passwords 21 system requirements installing Resource Kit 6 X XML over HTTP 4 Index 29