MDM Multidomain Edition (Version 9.0.1) Cleanse Adapter Guide

Transcription

1 MDM Multidomain Edition (Version 9.0.1) Cleanse Adapter Guide

2 Informatica MDM Multidomain Hub - Version September 2010 Copyright (c) 2010 Informatica. 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 is 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 and Siperian 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. This product includes software developed by the Apache Software Foundation ( and other software which is licensed under the Apache License, Version 2.0 (the License ). You may obtain a copy of the License at LICENSE-2.0. Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. This product includes software which is licensed under 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. This product includes software which is licensed under the CDDL (the License ). You may obtain a copy of the License 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. See the License for the specific language governing permissions and limitations under the License. This product includes software which is licensed under the BSD License (the License ). You may obtain a copy of the License 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. See the License for the specific language governing permissions and limitations under the License. This product includes software Copyright (c) , Terence Parr, all rights reserved which is licensed under the BSD License (the License ). You may obtain a copy of the License 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. See the License for the specific language governing permissions and limitations under the License. This product includes software Copyright (c) The Legion Of The Bouncy Castle ( which is licensed under a form of the MIT License (the License ). You may obtain a copy of the License 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. See the License for the specific language governing permissions and limitations under the License. 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 non-infringement, 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 ) may include 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 NOTLIMITED 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.

3 Contents Preface Intended Audience...vii Contents...viii Learning About Informatica MDM Hub...ix Informatica Global Customer Support...xii Informatica Resources...xiii Informatica Customer Portal...xiii Informatica Documentation...xiii Informatica Web Site...xiii Informatica How-To Library...xiv Informatica Knowledge Base...xiv Informatica Multimedia Knowledge Base...xiv Chapter 1: Introduction Supported Cleanse Engines...1 Prerequisites...2 Chapter 2: Informatica IDQ Cleanse Engine About Informatica IDQ Integration...4 Prerequisites...4 Related Information...4 Process Overview...4 Run-time Behavior...6 Considerations...6 Adding an IDQ Library in the Cleanse Functions Tool...7 Configuring Generated Libraries...12 Enabling a Generated Library...13 iii

4 Properties File Syntax Example Properties File Editing a Generated Properties File Chapter 3: AddressDoctor Cleanse Engine Configuring the AddressDoctor Cleanse Engine Obtaining the Required Files Editing the Properties File Upgrading the AddressDoctor Cleanse Engine Obtaining the Required Files Editing the Properties File Checking the Jade Library Version Configuring the JVM Settings Chapter 4: FirstLogic Direct Cleanse Engine About FirstLogic Direct Integration Installing the Components Configuring FirstLogic Direct Configuring Informatica MDM Hub to Use the Adapter Using Your FirstLogic Direct Library About Transactional Mode About the Transactional Mode Sample...39 Chapter 5: Trillium Director Cleanse Engine About Trillium Director Integration Before You Install Configuring Trillium Director 7 Series and the Cleanse Match Server Configuring Trillium Director 11 Cleanse Engine in the Console on Windows Testing Your Trillium Director Configuration About the Default Configuration File Using Your Trillium Director Projects with the Adapter Upgrading Trillium Director iv Informatica MDM Hub Cleanse Adapter Guide

5 Configuring Trillium Director for Multithreading...50 Setting the Threading Pool...51 Increasing the Number of Network Connection Retries...51 Chapter 6: SAP Data Services XI Cleanse Engine About SAP Data Services XI Integration...54 Prerequisites...54 Related Information...54 Process Overview...54 Run-time Behavior...55 Considerations...56 Adding an SAP Library in the Cleanse Functions Tool...57 Configuring Generated Libraries...63 Enabling a Generated Library...63 Properties File Syntax...63 Example Properties File...64 Editing a Generated Properties File...65 Chapter 7: Troubleshooting AddressDoctor Initialization Issues...71 Cleanse Engine Initialization Fails...72 Trillium Errors...73 Initialization Fails for MRM Console...73 Remote Initialization Fails...73 Trillium Director Integration...74 About Trillium Director Working Files...74 Setting the Work File Parameters...74 Using DnB to Access External Sites that Require a Proxy Server...75 Contents v

6 vi Informatica MDM Hub Cleanse Adapter Guide

7 Preface Welcome to the Informatica MDM Hub Cleanse Adapter Guide. This guide explains how to configure your Informatica MDM Hub system to use Informatica cleanse adapters and supported cleanse engines. Chapter Contents Intended Audience Contents Learning About Informatica MDM Hub Informatica Global Customer Support Informatica Resources Intended Audience This guide has been written for database administrators, system administrators, and other implementers who are responsible for the setup tasks required for cleanse adapters and engines. System administrators must be familiar with the Windows and UNIX platforms. Knowledge of Oracle administration is particularly important. Other administration and configuration tasks are described in the Informatica MDM Hub Administrator Guide. vii

8 Contents Contents This guide contains the following chapters: Introduction Informatica IDQ Cleanse Engine AddressDoctor Cleanse Engine FirstLogic Direct Cleanse Engine Trillium Director Cleanse Engine SAP Data Services XI Cleanse Engine Troubleshooting Provides an introduction to the cleanse adaptors. Explains how to use the Informatica IDQ cleanse engine Explains how to use the Address Doctor cleanse engine. Explains how to use the Business Objects DQ XI cleanse engine. Explains how to use the Trillium Director Adapter and cleanse engine. Explains how to use the SAP Data Services XI cleanse engine Describes known troubleshooting issues. viii Informatica MDM Hub Cleanse Adapter Guide

9 Learning About Informatica MDM Hub Learning About Informatica MDM Hub What s New in Informatica MDM Hub The What s New in Informatica MDM Hub describes the new features in this Informatica MDM Hub release. Informatica MDM Hub Release Notes The Informatica MDM Hub Release Notes contain important information about this release of Informatica MDM Hub. Read the Informatica MDM Hub Release Notes before installing Informatica MDM Hub. Informatica MDM Hub Overview The Informatica MDM Hub Overview introduces Informatica MDM Hub, describes the product architecture, and explains core concepts that all users need to understand before using the product. Informatica MDM Hub Installation Guide The Informatica MDM Hub Installation Guide for your platform explains how to install Informatica MDM Hub and Cleanse Match Server. There is one Informatica MDM Hub Installation Guide covering all of the supported platforms. Informatica MDM Hub Upgrade Guide The Informatica MDM Hub Upgrade Guide explains to installers how to upgrade a previous Informatica MDM Hub version to the most recent version. Informatica MDM Hub Cleanse Adapter Guide The Informatica MDM Hub Cleanse Adapter Guide explains to installers how to configure Informatica MDM Hub to use the supported adapters and cleanse engines. ix

10 Learning About Informatica MDM Hub Informatica MDM Hub Data Steward Guide The Informatica MDM Hub Data Steward Guide explains how to use Informatica MDM Hub. It provides a description of the Informatica MDM Hub platform through a discussion of Informatica MDM Hub concepts and tasks. Data stewards and users who are new to Informatica MDM Hub should read the Informatica MDM Hub Data Steward Guide first. Informatica MDM Hub Administrator Guide The Informatica MDM Hub Administrator Guide explains how to configure, administer, and manage a Informatica MDM Hub implementation. It provides a description of the Informatica MDM Hub platform through a discussion of Informatica MDM Hub concepts, services, tools, and databases. Administrators should read the Informatica MDM Hub Administrator Guide first. Informatica MDM Hub Services Integration Framework Guide The Informatica MDM Hub Services Integration Framework Guide explains how to use the Informatica MDM Hub Services Integration Framework (SIF) to integrateinformatica MDM Hub functionality with your applications and how to create applications using the data provided by Informatica MDM Hub. SIF allows you to integrate Informatica MDM Hub smoothly with your organization's applications. Informatica MDM Hub Metadata Manager Guide The Informatica MDM Hub Metadata Manager Guide explains how to use the Informatica MDM Hub Metadata Manager tool to validate their organization s metadata, promote changes between repositories, import objects into repositories, export repositories, and related tasks. x Informatica MDM Hub Cleanse Adapter Guide

11 Learning About Informatica MDM Hub Informatica MDM Hub Resource Kit Guide The Informatica MDM Hub Resource Kit Guide explains how to install and use the Informatica MDM Hub Resource Kit, which is a set of utilities, examples, and libraries that assist developers with integrating the Informatica MDM Hub into their applications and workflows. This document provides a description of the various sample applications that are included with the Resource Kit. Informatica Training and Materials Informatica provides live, instructor-based training to help you become a proficient user as quickly as possible. From initial installation onward, a dedicated team of qualified trainers ensure that your staff is equipped to take advantage of this powerful platform. To inquire about training classes or to find out where and when the next training session is offered, please visit our website or contact Informatica directly. xi

12 Informatica Global Customer Support Informatica Global Customer Support You can contact a Customer Support Center by telephone or through the WebSupport Service. WebSupport requires a user name and password. You can request a user name and password at Use the following telephone numbers to contact Informatica Global Customer Support: North America / South America Toll Free North America Brazil Mexico Standard Rate North America Europe / Middle East / Africa Toll Free United Kingdom or France Netherlands Germany Switzerland Israel Spain Portugal Italy Standard Rate Belgium France Germany Netherlands Switzerland Asia / Australia Toll Free Australia New Zealand Singapore Standard Rate India xii Informatica MDM Hub Cleanse Adapter Guide

13 Informatica Resources Informatica Resources Informatica Customer Portal As an Informatica customer, you can access the Informatica Customer Portal site 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, the Informatica Multimedia Knowledge Base, Informatica Documentation Center, 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 at infa_ 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 the Informatica Documentation Center 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. xiii

14 Informatica Resources 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. xiv Informatica MDM Hub Cleanse Adapter Guide

15 Introduction This guide describes how to configure cleanse engines to work with the Informatica MDM Hub and Informatica MDM adapters. The guide also provides prerequisites and test procedures for each adapter. Chapter Contents Supported Cleanse Engines Prerequisites Supported Cleanse Engines The following table displays the cleanse engines that Informatica MDM Hub supports and the Informatica MDM adapters that they work with: Cleanse Engine IDQ AddressDoctor FirstLogic DirectI Trillium SAP Data Services XI Informatica MDM Hub Adapter Informatica IDQ Adapter AdressDoctor Adapter FirstLogic Data Quality Adapter Trillium Director Adapter SAP Data Services XI Adapter Note: Check the Informatica MDM Hub9.0.1 Release Notes for current cleanse engine versions. 1

16 Prerequisites Prerequisites Before you can use your cleanse engines, you might need to do the following, depending on which cleanse engine you are using: Obtain a license with cleanse adapter enabled from Informatica. Install the Hub, application server, Cleanse Match Server, and cleanse adapter. In some cases, you must install the Cleanse Match Server and the cleanse adapter on the same server. Configure the cleanse engine and Informatica MDM Hub. See individual chapters of this guide more information. Test your cleanse-engine configuration. For more information, see your cleanse engine documentation, your application server documentation, the Informatica MDM Hub9.0.1 installation guides, and the Informatica MDM Hub release notes. 2 Informatica MDM Hub Cleanse Adapter Guide

17 2 Informatica IDQ Cleanse Engine One of the ways to access data cleansing functionality in the Informatica Data Quality product is via Web services that Informatica publishes. This chaper describes how, in your Informatica MDM Hub implementation, to set up and use the MDM Cleanse Adapter for Informatica Data Quality (Web Services) to access cleanse functions that are published as Web services. This functionality allows you add a new type of cleanse library - an IDQ cleanse library - to your Informatica MDM Hub implementation, and then integrate cleanse functions in the IDQ library into your mappings, just as you would integrate any other type of cleanse function available in your Informatica MDM Hub implementation. Informatica MDM Hub acts as a Web service client application that consumes Informatica Web services. If you do not use the Informatica IDQ cleanse engine, you can skip this chapter. Chapter Contents About Informatica IDQ Integration Adding an IDQ Library in the Cleanse Functions Tool Configuring Generated Libraries 3

18 About Informatica IDQ Integration About Informatica IDQ Integration Prerequisites To use this functionality, you must have installed the following software: Informatica MDM Hub or later Informatica Data Quality (IDQ) or higher Informatica PowerCenter Informatica MDM license that enables IDQ cleanse library functionality (siperian.informatica_dq=yes in the configuration file) Related Information Process Overview For more information, see: Chapter 12, Configuring Data Cleansing, in the Informatica MDM Hub Administrator Guide (this chapter provides supplemental information to that chapter) Informatica Data Quality product information (including setup instructions) To use these Web services in your Informatica MDM Hub implementation, complete thefollowing steps: 1. Create a mapping in IDQ or PowerCenter. See PowerCenter Web Services Provider Guide available at the Informatica MySupport website for information on how to create WSDL files for web services. Obtain the Informatica Web Services Description Language (WSDL) file for the Web service(s) that you want to consume. Use the WSDL you created n Informatica PowerCenter. 2. In the Cleanse Functions tool of the Informatica MDM Hub Console, add an IDQ library and specify the URI of the Web Services Description Language (WSDL) file as well as connection information (service and port) to hosted Web services. For 4 Informatica MDM Hub Cleanse Adapter Guide

19 About Informatica IDQ Integration instructions, see Adding an IDQ Library in the Cleanse Functions Tool on page 7. The Cleanse Functions tool builds the IDQ library based on the WSDL, and then displays the list of cleanse functions defined in the WSDL. Each cleanse function represents a separate Web service. 3. Enable a generated library according to the instructions in Enabling a Generated Library on page In the Mappings tool of the Informatica MDM Hub Console, use the available cleanse functions in your mappings as required. You must configure the inputs and outputs just as you would configure any other mappings. For performance reasons, the IDQ function should be the only one used in the mapping. You can have direct column-to-column mappings in the same mapping as an IDQ function, but you should not use other functions or conditional execution components in the same mapping as an IDQ function. See Run-time Behavior on page 6 for more information. For more information, see the documentation for the Mappings tool in Chapter 11, Configuring the Stage Process, in the Informatica MDM Hub Administrator Guide. Informatica IDQ Cleanse Engine 5

20 About Informatica IDQ Integration Run-time Behavior Considerations At run time, the cleanse engine evaluates the number of records to be cleansed. If only one (1) record has been sent for cleansing, then the web service is invoked for that single record. If there are multiple records to be cleansed, then the cleanse server will batch a set of records together and pass that batch to the web service. This reduces latency on the web service call and results in better performance. The maximum number of records included in a batch is determined by a parameter in the cmxcleanse.properties file: cmx.server.cleanse.number_of_recs_batch= nnn The default value for that parameter is 50. Web service invocations are synchronous only. Asynchronous invocations are not supported. By default, web service invocations typically operate on a single record at a time. However, the MDM Hub cleanse engine will batch together records for cleansing to improve the performance. It can only do this if all the data transformation logic resides in the IDQ web service. If any transformation logic is defined in the MDM map, then the cleanse engine will not be able to use batching logic and the calls to the web service will revert to being single record invocations of the web service The IDQ function must contain all transformation logic. This is so that no other functions are needed in the MDM map, thus allowing batches of records to be passed to IDQ for processing. The purpose of using the Web services is strictly to transform data that is passed in the request according to the associated cleanse function. Other types of Web services, such as publish/subscribe services, are not supported. If the Web service returns an error, Informatica MDM Hub moves the record to the reject table and saves a description of the problem (including any error information returned from the Web service). 6 Informatica MDM Hub Cleanse Adapter Guide

21 Adding an IDQ Library in the Cleanse Functions Tool If the Web service is published on a remote system, the infrastructure must be in place for Informatica MDM Hub to connect to the Web service (such as a network that accesses the Internet). When using cleanse functions that are implemented as Web services, run-time performance of Web service invocations depends on some factors that are external to Informatica MDM Hub, such as availability of the Web service, the time required for the Web service to process the request and return the response, and network speed. You can run WSDL cleanse function with multi-threading. To enable this, change the thread count on the Informatica MDM Hub Cleanse Match Server. Make sure that there is a sufficient number of instances of the IDQ Web Service to handle the multiple Informatica MDM cleanse threads; otherwise, records might be rejected due to timeouts. WSDL files must comply with the Axis2 Databinding Framework (ADB). Non-compliant WSDL files are not supported. When you configure mappings, you must ensure that the inputs and outputs are appropriate for the Web service you are calling. The Mappings tool does not validate your inputs and outputs this is done by the Web service instead. If you have invalid inputs or outputs, the Web service will return an error response and any processed record(s) will be moved to the reject table with an explanation of the error. Adding an IDQ Library in the Cleanse Functions Tool Once you have installed the prerequisite software and obtained an IDQ WSDL file, you use the Cleanse Functions tool in the Informatica MDM Hub Console to add the IDQ library to your Informatica MDM Hub implementation. 1. Launch the Informatica MDM Hub Console, if it is not already running. 2. Start the Cleanse Functions tool. 3. Obtain a write lock (Write Lock > Acquire Lock). 4. Select the Cleanse Functions (root) node. Right click. Informatica IDQ Cleanse Engine 7

22 Adding an IDQ Library in the Cleanse Functions Tool 5. Choose Cleanse Functions > Add IDQ Library. 6. In the Add IDQ Library dialog, specify the following settings: Setting Library Name IDQ WSDL URI IDQ WSDL Service IDQ WSDL Port Description Description Name of this IDQ library. You can assign any arbitrary name that helps you classify and organize the collection of IDQ cleanse functions. Consider having "IDQ" in the name to distinguish this from other cleanse function libraries. This name will appear as the folder name in the Cleanse Functions list. URI (location) of the IDQ WSDL to implement. Service of the IDQ WSDL to implement. Port of the IDQ WSDL to implement. Descriptive text for this library that you want displayed in the Cleanse Functions tool. Note: Simple WSDLs often have only one Service and one Port. You can refer to the IDQ WSDL for the values to specify for these settings. The following figure shows sample settings for an IDQ WSDL that invokes default name and address cleansing. 8 Informatica MDM Hub Cleanse Adapter Guide

23 Adding an IDQ Library in the Cleanse Functions Tool 7. Click OK to add the metadata definition for this new IDQ library to the local ORS repository. Informatica IDQ Cleanse Engine 9

24 Adding an IDQ Library in the Cleanse Functions Tool 8. Click the Refresh button to generate the IDQ library. The Cleanse Functions tool retrieves the latest IDQ WSDL, generates the IDQ library, and displays any available cleanse functions in the Cleanse Functions list. If the Cleanse Functions tool cannot consume the IDQ WSDL file (for example, due to a syntax error), then it displays an error message instead. You need to fix the IDQ WSDL file or obtain a valid one. If changes in the IDQ WSDL file affect any existing mappings, the Cleanse Functions tool displays an error. You must fix the affected mappings before running the cleanse process. 9. Click a cleanse function to display its properties. 10 Informatica MDM Hub Cleanse Adapter Guide

25 Adding an IDQ Library in the Cleanse Functions Tool 10. Test the function by clicking the Test tab and then clicking the Test button. 11. At this point, you can add these cleanse functions to your mappings in the Mappings tool, as shown in the Process Overview earlier in this chapter. Informatica IDQ Cleanse Engine 11

26 Configuring Generated Libraries Configuring Generated Libraries When the Cleanse Functions tool generates a library, it creates a set of properties files in the SIP_HOME/cleanse/lib directory with the following naming format: siperian-cleanse-<servicename>_<functionname>.properties.new Note: File names must be unique (service name + function name) within this directory. 12 Informatica MDM Hub Cleanse Adapter Guide

27 Configuring Generated Libraries Enabling a Generated Library To enable a generated library, remove the.new extension from the file name. Properties File Syntax Example Properties File # endpointoverride = # # Inputs for <functionname> # #<wsdl_in_param1> = name, description #<wsdl_in_param2> = name, description # # Outputs for <functionname> # #<wsdl_out_param1> = name, description #<wsdl_out_param2> = name, description Below is an example code listing. #endpointoverride = # # Inputs for name_address # Req_Name_DITypeVarchar1024 = Req_Name_DITypeVarchar1024, Req_Name_ DITypeVarchar1024 Req_State_DITypeVarchar1024 = Req_State_DITypeVarchar1024, Req_State_DITypeVarchar1024 Req_Address_DITypeVarchar1024 = Req_Address_DITypeVarchar1024, Req_Address_DITypeVarchar1024 Req_City_DITypeVarchar1024 = Req_City_DITypeVarchar1024, Req_City_ DITypeVarchar1024 Req_Pcode_DITypeVarchar1024 = Req_Pcode_DITypeVarchar1024, Req_Pcode_DITypeVarchar1024 # # Outputs for name_address # Res_Address_DITypeVarchar1024 = Res_Address_DITypeVarchar1024, Res_Address_DITypeVarchar1024 Informatica IDQ Cleanse Engine 13

28 Configuring Generated Libraries Res_Name_DITypeVarchar1024 = Res_Name_DITypeVarchar1024, Res_Name_ DITypeVarchar1024 Res_State_DITypeVarchar1024 = Res_State_DITypeVarchar1024, Res_State_DITypeVarchar1024 Res_City_DITypeVarchar1024 = Res_City_DITypeVarchar1024, Res_City_ DITypeVarchar1024 Res_Pcode_DITypeVarchar1024 = Res_Pcode_DITypeVarchar1024, Res_Pcode_DITypeVarchar1024 Editing a Generated Properties File You would edit a generated properties file for the following reasons: to change the connection endpoint to rename or remove extraneous parameters To edit a generated properties file: 1. Remove the.new from the end of the file name to enable it. 2. Open the file in a text editor. 3. Make the changes you want to the file, then save the file. 4. In the Cleanse Functions tool, select the IDQ library, then click the Refresh button to activate these changes in the properties file. Note: When you click Refresh to generate a library from a WSDL, the Cleanse Functions tool regenerates the file with the.new name. Changes made to a file that has been renamed (.new was removed) will not be overwritten when the library is refreshed. Adding a Different Connection Endpoint If the communication endpoint for a Web service changes, or if you need to point to a different environment, you can edit the properties file and provide the alternate endpoint URL as an override: # endpointoverride = This setting overrides the configured endpoint setting for this IDQ library. 14 Informatica MDM Hub Cleanse Adapter Guide

29 Configuring Generated Libraries You might need to do this, for example, when moving from a development/test environment to a production environment, or when (in a production environment) it might not be feasible to perform a refresh on the adapter. Managing Input and Output Parameters The names generated from the WSDL can sometimes be long and difficult to read, or in an uncommon order, as shown in the following example. You can edit the generated parameter file and rename parameters to make them easier to read and recognize. In fact, if you encounter an error indicating that one or more names are too long to be stored in the ORS repository (> 100 characters), then you will need to shorten these names. You can simplify the library by removing extraneous parameters that are not needed for your Web service invocations. You can also reorder parameters. Informatica IDQ Cleanse Engine 15

30 Configuring Generated Libraries To edit parameter names: For required parameters (parameters that you want to use in your cleanse functions), uncomment by removing the # character. Any parameter that is not uncommented will be removed from the function. Edit parameter names and descriptions as required. You cannot have duplicate parameter names in one function (duplicates will be ignored). The library will need to be refreshed for the changes to the properties file to take effect. In the Cleanse Functions tool, select the library and click Refresh. For example, the following figure shows the default generated output for an IDQ library. To rename a parameter, change its name setting as shown in the following example: <parameter> = name, description 16 Informatica MDM Hub Cleanse Adapter Guide

31 Configuring Generated Libraries Save changes to the file and then, in the Cleanse Functions tool, click Refresh to update the modified cleanse function settings. Once refreshed, be sure to test the cleanse function to verify its operation. Informatica IDQ Cleanse Engine 17

32 Configuring Generated Libraries 18 Informatica MDM Hub Cleanse Adapter Guide

33 3 AddressDoctor Cleanse Engine Integration between Informatica MDM Hub and the AddressDoctor cleanse engine occurs through the Informatica MDM Hub AddressDoctor Adapter. This adapter is an optional component. This chapter explains how to configure your Informatica MDM Hub system to use the AddressDoctor Adapter and the AddressDoctor Cleanse Engine. This chapter assumes that you are knowledgeable about configuring and using the AddressDoctor software. To learn more about AddressDoctor, see your AddressDoctor documentation. Note: The Informatica MDM Hub requires a very specific AddressDoctor build of the AddressDoctor Cleanse Engine. Check the release notes for the most current information about this build. Chapter Contents Configuring the AddressDoctor Cleanse Engine Upgrading the AddressDoctor Cleanse Engine Checking the Jade Library Version Configuring the JVM Settings 19

34 Configuring the AddressDoctor Cleanse Engine Configuring the AddressDoctor Cleanse Engine Before you can use the AddressDoctor Cleanse Engine as your cleanse engine, you must complete the following tasks: 5. Contact Informatica Support to obtain the following: Correct unlock codes. License file (with the AddressDoctor cleanse adapter enabled). The license must include the AddressDoctor adapter. 6. Download additional DLLs, if required. See the Informatica MDM Hub Release Notes. 7. Obtain the required files for configuration. 8. Edit the cleanse properties file. 9. Configure the application server JVM settings. Note: The Informatica MDM Hub requires a very specific AddressDoctor build of the AddressDoctor Cleanse Engine. Check the release notes for the most current information about this build. This chapter discusses how to obtain the required files, how to edit the properties file, and how to configure the application server JVM settings. 20 Informatica MDM Hub Cleanse Adapter Guide

35 Configuring the AddressDoctor Cleanse Engine Obtaining the Required Files The tables in this section describe the files that are required for your AddressDoctor cleanse engine configuration. Windows and UNIX: File Name Source/Location Note AD40USA.MD AD40CUSA.MD AD40CZIP.MD CASS Early Warning System (EWS) AddressDoctor install directory, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor AddressDoctor install directory, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor AddressDoctor install directory, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor If this file is not there, send an to This reference database file is required for US addresses. If this file is not there, send an to This reference database file is required for US addresses if you are using CASS certification. If this file is not there, send an to This reference database file is required for US addresses if you are using CASS certification. This file is required to use the CASS_EWS_Flag field. (The file name is generally of the format EWS*****.ZIP, although the USPS can change this convention at their discretion.) Download the early warning file, unzip it into your AddressDoctor installation directory, and rename the unziped EWS file EWS.EWS. AddressDoctor Cleanse Engine 21

36 Configuring the AddressDoctor Cleanse Engine UNIX / LINUX: Platform Solaris HP-UX Suse Linux Redhat Linux File Name ADD_JAVA_SOS zip ADD_JAVA_HPU zip ADD_JAVA_SUS zip ADD_JAVA_RHT zip 1. In your AddressDoctor distribution, find the database files for the country whose data you want to cleanse. 2. Unzip these files into a new folder, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor 3. Copy the addressformat.cfg file to the same folder with the database files. For example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor Editing the Properties File To edit the properties file: 1. Open the cmxcleanse.properties file for editing. This file is located in: Windows: <infamdm_install_directory>\hub\cleanse\resources UNIX: <infamdm_install_directory>/hub/cleanse/ resources 2. Add the cleanse.library.addressdoctor.property.addressdoctor.databasepath property and set it to your AddressDoctor installation directory. This value points to the location of the AD40CUSA.MD file. 22 Informatica MDM Hub Cleanse Adapter Guide

37 Configuring the AddressDoctor Cleanse Engine Here is an example of the cmxcleanse.properties file for an AddressDoctor Cleanse Engine: cleanse.library.addressdoctor.property.addressdoctor.unlockcode=< your_unlock_code> cleanse.library.addressdoctor.property.addressdoctor.databasepath =/u1/addressdoctor cleanse.library.addressdoctor.property.addressdoctor.optimization =ADDRESSES_SORTED_BY_COUNTRIES cleanse.library.addressdoctor.property.addressdoctor.memorymb=600 cleanse.library.addressdoctor.property.addressdoctor.correction_ Type=CORRECT_ONLY cleanse.library.addressdoctor.property.addressdoctor.preload.cert IFIED.PRELOAD_PART=US cleanse.library.address.property.addressdoctor.preload.certified. PRELOAD_FULL= Here, <your_unlock_code> is the unlock code that Informatica Support provided you. 3. Add the preload properties to the properties file. Setting these values instructs the AddressDoctor library to preload the database files. Using these settings increases memory usage and startup time for the application server that runs Hub Cleanse Match. Using these settings also improves performance of Hub Cleanse Match. All of these values are a comma-delimited list of country codes. For Informatica MDM Hub XU SP2, US is the only supported value for CERTIFIED. Since there are both correction and certification values, you can set one correction property and one certification value to US. When you are working with the properties file, observe the following conventions: If there is an equals sign (=) at the beginning of the code, do not remove it. Use the following escape characters: Windows: When using a backslash character (\), add another backslash character (\) in front. That is, change \ to \\. UNIX/Linux: When using a forwardslash character (/), add a backslash (\) character in front. That is, change / to \/. AddressDoctor Cleanse Engine 23

38 Configuring the AddressDoctor Cleanse Engine UNIX/Linux: When using special characters, such as $, add a backslash character (\) in front. That is, change $ to \$. Make sure that there are no spaces at the end of the unlock code. Here s an example of the cmxcleanse.properties file for an AddressDoctor cleanse engine that includes some of these properties. Windows: cleanse.library.addressdoctor.property.addressdoctor.unlockcode= <your_unlock_code> cleanse.library.addressdoctor.property.addressdoctor.databasepath= C:\addressDoctor cleanse.library.addressdoctor.property.addressdoctor.optimization= ADDRESSES_SORTED_BY_COUNTRIES cleanse.library.addressdoctor.property.addressdoctor.memorymb=600 cleanse.library.addressdoctor.property.addressdoctor. CorrectionType=CERTIFY_ONLY. cleanse.library.addressdoctor.property.addressdoctor.preload. CERTIFIED.PRELOAD_PART=US cleanse.library.addressdoctor.property.addressdoctor.preload. CERTIFIED.PRELOAD_FULL= cleanse.library.addressdoctor.property.addressdoctor.preload. CORRECTION_ONLY.PRELOAD_PART=CA, US cleanse.library.addressdoctor.property.addressdoctor.preload. CORRECTION_ONLY.PRELOAD_FULL= UNIX: cleanse.library.addressdoctor.property.addressdoctor.unlockcode= <your_unlock_code> cleanse.library.addressdoctor.property.addressdoctor.databasepath= /u2/addressdoctor cleanse.library.addressdoctor.property.addressdoctor.optimization= ADDRESSES_SORTED_BY_COUNTRIES cleanse.library.addressdoctor.property.addressdoctor.memorymb=600 cleanse.library.addressdoctor.property.addressdoctor. CorrectionType=CERTIFY_ONLY. cleanse.library.addressdoctor.property.addressdoctor.preload. CERTIFIED.PRELOAD_PART=US cleanse.library.addressdoctor.property.addressdoctor.preload. CERTIFIED.PRELOAD_FULL= cleanse.library.addressdoctor.property.addressdoctor.preload. CORRECTION_ONLY.PRELOAD_PART=CA, US cleanse.library.addressdoctor.property.addressdoctor.preload. 24 Informatica MDM Hub Cleanse Adapter Guide

39 Configuring the AddressDoctor Cleanse Engine CORRECTION_ONLY.PRELOAD_FULL= <your_unlock_code> is the unlock code that AddressDoctor provided you. Important: Do not put a space after the unlock code. A space causes errors. You can change many of these settings to increase product performance. For example, preloading can dramatically increase the speed that the cleanse engine processes the cleanse functions. The PRELOAD_FULL property tells AddressDoctor to load the entire database specified to be loaded on startup and cached in memory. Note that the larger databases, particularly the US databases, might take up too much memory, so using the PRELOAD_PART property might be the better option in such cases. Preloading can dramatically increase the speed that the cleanse engine processes the cleanse functions. cleanse.library.addressdoctor.property.addressdoctor.preload.certified.prelo AD_PART=CA,US This property preloads a certification database of frequently used countries. cleanse.library.addressdoctor.property.addressdoctor.preload.certified.prelo AD_FULL= PRELOAD_FULL tells AddressDoctor to load the entire database specified to be loaded on startup and cached in memory. Note that the larger databases, particularly the US database, may take up too much memory, so a PRELOAD_ PART may be the better option in such cases. The use of the PRELOAD_PART property will perform a partial load of the database declared in the parameter value. The database is arranged in hierarchical levels and the partial load will cache, starting with the highest level of the country hierarchy, such as state. Then the load continues until it reaches the point where the current hierarchy is loaded successfully, but for which the next level would not be possible to completely load, so it therefore does not load any of the next level. This property loads a full load of certification databases of frequently used countries. Setting this property to full load is not recommended, due to high performance impact. cleanse.library.addressdoctor.property.addressdoctor.preload.correction_ ONLY.PRELOAD_PART=CA,US AddressDoctor Cleanse Engine 25

40 Configuring the AddressDoctor Cleanse Engine This property preloads databases of frequently used countries. cleanse.library.addressdoctor.property.addressdoctor.preload.correction_ ONLY.PRELOAD_FULL= This property loads a full load of databases of frequently used countries. 4. Find the following line in the cmxcleanse.properties file: cleanse.library.addressdoctor.property.addressdoctor.correctiontyp e=correct_only Change the default value CORRECT_ONLY to CERTIFY_ONLY. The valid values are: CERTIFY_CORRECT Use this if your input data fits the field definitions well. Note that use of some input fields may automatically change the process to CORRECT_CERTIFY, which performs the same functions as running a CERTIFY_ONLY, but, in addition, uses the results as input to perform a second sweep that uses CORRECT_ONLY. CORRECT_CERTIFY Use this if your input data would benefit from being cleaned up before certification. Take both your data and your performance requirements into account when deciding to correct before or after certification. Tests with subsets of your data are the best way to determine which is best for your implementation. CORRECT_CERTIFY performs the same function as CORRECT_ONLY, but, in addition, uses the result as input to perform a second sweep that uses CERTIFY_ONLY. CORRECT_ONLY This is the default and will correct the addresses according to the AddressDoctor database for the country specified. CERTIFY_ONLY Use this to have your addresses certified against the Post Office database. For example, in the U.S., addresses are certified against the CASS database (AD40CUSA.MD). During this process, the mail delivery address for the address input (which includes appending the IP with four digits to make ZIP + 4) becomes part of the record. The CERTIFY_ONLY choice will not correct US addresses. Only some input and output fields are used. You can override this setting for individual records by using the input parameter CorrectionType. 26 Informatica MDM Hub Cleanse Adapter Guide

41 Configuring the AddressDoctor Cleanse Engine If you specify a Correction Type that includes the phrase CERTIFY, you must have the files AD40CUSA.MD, AD40CZIP.MD, and EWS. The CASS output properties are enabled only when you specify CERTIFY_ONLY, CERTIFY_ CORRECT, or CERTIFY_CERTIFY. See the Informatica MDM Hub Administrator Guide for more on using these output properties. Save and close the properties file. 5. Find the following line in the cmxcleanse.properties file: cleanse.library.addressdoctor.property.addressdoctor. CorrectionType=CORRECT_ONLY 6. Change the default value CORRECT_ONLY to CERTIFY_ONLY. 7. Save and close the properties file. 8. Start SQL*PLUS and connect to the server as <ors_name> with DBA privileges. Execute the following script to enable AddressDoctor in your ORS database, using AddressDoctor as the value for &1 and On as the value for &2: -- Feature Name Options: AddressDoctor -- Set Value Options: On, Off DECLARE IN_CL_FEATURE_NAME VARCHAR2(200); IN_CL_SET_VALUE VARCHAR2(50); OUT_ERROR_MSG VARCHAR2(200); RC NUMBER; BEGIN IN_CL_FEATURE_NAME := '&1'; IN_CL_SET_VALUE := '&2'; OUT_ERROR_MSG := NULL; RC := NULL; CMXUT.SET_CLEANSE_FEATURE ( IN_CL_FEATURE_NAME, IN_CL_SET_VALUE, OUT_ERROR_MSG, RC ); DBMS_OUTPUT.PUT_LINE ( 'OUT_ERROR_MSG= ' OUT_ERROR_MSG ); END; / COMMIT; AddressDoctor Cleanse Engine 27

42 Upgrading the AddressDoctor Cleanse Engine 9. Restart your application server. The AddressDoctor library is displayed in the Hub Console. 10. Verify that the application server started up properly with no errors. Update your JVM settings as explained Configuring the JVM Settings on page 31. This increases resources available to the JVM. Upgrading the AddressDoctor Cleanse Engine If you are upgrading your Informatica MDM installation, you need to also upgrade your AddressDoctor Cleanse Engine. The following sections cover configuration information for upgrading the AddressDoctor Cleanse Engine. The AddressDoctor Cleanse Engine libraries are included as part of the Informatica MDM Hub XU SP2 upgrade. If you intend to use AddressDoctor Cleanse Engine as your cleanse engine, contact Informatica Support for the correct unlock codes. To configure AddressDoctor: 1. Obtain the required files (unlock codes and other files). 2. Edit the Hub Cleanse Match properties file. (See Editing the Properties File on page 22.) 3. Configure the application server JVM settings. (See Configuring the JVM Settings on page 31.) 28 Informatica MDM Hub Cleanse Adapter Guide

43 Upgrading the AddressDoctor Cleanse Engine Obtaining the Required Files The following table describes the files that are required for your AddressDoctor cleanse engine upgrade. File Name Source/Location Note AD40USA.MD AD40CUSA.MD CASS Early Warning System (EWS) ADD_JAVA_ W32.zip file and addressformat.cfg AddressDoctor install directory, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor AddressDoctor install directory, for example: Windows: C:\AddressDoctor UNIX: /u1/addressdoctor AddressDoctor If this file is not there, send an to This reference database file is required for US addresses. If this file is not there, send an to This reference database file is required for US addresses if you are using CASS certification. This file is required to use the CASS_EWS_ Flag field. (The file name is generally of the format EWS*****.ZIP, although the USPS can change this convention at their discretion.) Download the early warning file, unzip it into your AddressDoctor installation directory, and rename the unziped EWS file EWS.EWS. Unzip the ADD_JAVA_W32 zip file into the AddressDoctor distribution (<infamdm_install_ directory>\hub\lib\upgrade \AddressDoctor). Copy the addressformat.cfg file to the same folder that contains the database files. For example, C:\AddressDoctor, or \u1\addressdoctor. AddressDoctor Cleanse Engine 29

44 Upgrading the AddressDoctor Cleanse Engine Editing the Properties File Verify that the information in your cmxcleanse.properties files is still valid. See Editing the Properties File on page 22. Checking the Jade Library Version This section only applies if you are upgrading the AddressDoctor cleanse engine. If the Jade library file is in use when you start the upgrade, the application server replaces the existing version with the new version, since the Application Server has the new version locked. After you upgrade, you must confirm that you have the correct version. Windows: To check the Jade library version: 1. Go to the release notes that correspond to the version you want to upgrade. Check the Jade library version that you should be using. 2. On the Hub Cleanse Match machine, go to the following directory: <infamdm_install_directory>\cleanse\lib 3. Right-click on the Jade.dll file and choose Properties. 4. Click the Version tab. The version should be the same as the version that is listed in the Release Notes. If the version is the same, you can skip the next three steps. 5. If the version is not the same, shut down the Hub Cleanse Match server. 6. Search for the jade.dll file on the server in the following directory: <infamdm_install_directory>\lib\upgrade\addressdoctor Backup the file to another folder, then replace it with a newer jade.dll file to the following directory: <infamdm_install_directory>\cleanse\lib\ 7. Restart the Hub Cleanse Match server. 30 Informatica MDM Hub Cleanse Adapter Guide

45 Configuring the JVM Settings UNIX (Solaris, AIX, HP UX, and Linux platforms): The installer replaces the old libjade.so library. You only have to follow the directions below to restart the application server: To restart the application server: 1. Make sure that you are logged in with the same user name as is currently running the application server. 2. Restart the application server. 3. Check that no exceptions occur while starting the application server. Configuring the JVM Settings If you are using AddressDoctor as your cleanse engine to run any batch process, you must make sure that the stack size for the JVM is sufficient. If the stack size is set incorrectly for your application server, AddressDoctor might: Cause an initialization failure when you start the Cleanse Server. Throw an exception during a cleanse operation when the Cleanse Server is up and running. Setting the JVM Size for WebSphere on Windows/UNIX To set the JVM size for WebSphere: 1. Open the WebSphere Console 2. Navigate to Servers> Application Server> <Your Server> >Process Definition> Java Virtual Machine 3. Add the following parameters to the Generic JVM Arguments: -Xss1024k - Parameter to set JVM stack size of 1 Mb -Xms512m - Parameter to set JVM heap with a start (minimum) size of 512 Mb -Xmx1024m - Parameter to set JVM heap to allow growth to maximum of 1 Gb 4. Save the configuration. AddressDoctor Cleanse Engine 31

46 Configuring the JVM Settings 5. Re-start the server. Setting the JVM Size for WebLogic Server on Windows To set the JVM size for the WebLogic server on Windows: 1. Go to your WebLogic home directory. 2. Open setdomainenv.cmd in a text editor. 3. Set the MEM_ARGS variable as follows: set MEM_ARGS=%MEM_ARGS% -Xmx1024m 4. Save and close the setdomainenv.cmd file. Setting the JVM Size for WebLogic Server on HP-UX and Solaris To set the JVM size for WebLogic server on HP-UX and Solaris: 1. Go to your WebLogic home directory. 2. Open setdomainenv.sh in a text editor. 3. Set the MEM_ARGS variable as follows: set MEM_ARGS=$MEM_ARGS -Xmx1024m 4. Save and close the setdomainenv.sh file. Setting the JVM Size for JBoss on Windows To set the JVM size for the JBoss server on Windows: 1. Go to your JBoss home directory. 2. Navigate to the bin directory. 3. Open run.bat in a text editor. 4. Set the JAVA_OPTS variable as follows: JAVA_OPTS=%JAVA_OPTS% -Xmx1024m 5. Save and close the run.bat file. 32 Informatica MDM Hub Cleanse Adapter Guide

47 Configuring the JVM Settings Setting the JVM Size for JBoss on HP-UX and Solaris To set the JVM size for JBoss on HP-UX and Solaris: 1. Go to your JBoss installation directory. 2. Navigate to the bin directory. 3. Open run.sh in a text editor. 4. Set the JAVA_OPTS variable as follows: JAVA_OPTS="$JAVA_OPTS -Xmx1024m 5. Save and close the run.sh file. After you have made these configuration changes, restart your Informatica MDM Hub and Cleanse Match servers. AddressDoctor Cleanse Engine 33

48 Configuring the JVM Settings 34 Informatica MDM Hub Cleanse Adapter Guide

49 4 FirstLogic Direct Cleanse Engine Integration between Informatica MDM Hub and the FirstLogic Direct cleanse engine takes place through the Informatica MDM Hub FirstLogicDirect Adapter. This adapter is an optional component. This chapter explains how to configure your Informatica MDM Hub system to use the FirstLogicDirect Adapter and the FirstLogic Direct cleanse engine on both the Windows and UNIX platforms. The information in this chapter pertains to both platforms unless otherwise specified. This chapter assumes that you are knowledgeable about configuration and using the FirstLogic Direct software. To learn more about FirstLogic Direct, see your FirstLogic Direct documentation. Chapter Contents About FirstLogic Direct Integration Installing the Components Configuring FirstLogic Direct Configuring Informatica MDM Hub to Use the Adapter Using Your FirstLogic Direct Library 35

50 About FirstLogic Direct Integration About FirstLogic Direct Integration Informatica MDM Hub integrates with FirstLogic Direct by treating FirstLogic Direct transaction-type projects as cleanse functions. The process of integration with FirstLogic Direct involves both Informatica MDM Hub and FirstLogic Direct. To integrate the FirstLogic Direct cleanse engine with Cleanse Match Server: 1. Install the components of the Cleanse Match Server and the cleanse engine, as explained in Installing the Components on page Configure FirstLogic Direct as explained in Configuring FirstLogic Direct on page Configure Informatica MDM Hub to use the adapter, as explained in Configuring Informatica MDM Hub to Use the Adapter on page 38. Note: You must obtain a license (with cleanse adapter and Business Objects DQ XI enabled) from Informatica. Once these steps have been successfully completed, you are ready to use the FirstLogic Direct functions in the Cleanse Match Server, as explained in Using Your FirstLogic Direct Library on page 38. Installing the Components Before you configure the adapter, make sure that you have installed the components: 1. Install the application server you intend to use for the Cleanse Match Server. 2. Install FirstLogic Direct. To learn more, see your FirstLogic Direct documentation. See the Informatica MDM Hub Release Notes for the supported versions of FirstLogic Direct. 3. Install the Cleanse Match Server as explained in the Informatica MDM Hub Installation Guide. Cleanse Match Server and FirstLogic Direct can be on the same machine or different machines. 36 Informatica MDM Hub Cleanse Adapter Guide

51 Configuring FirstLogic Direct Configuring FirstLogic Direct This table describes the actions required to configure your Business Objects DQ XI to work with the Informatica MDM Hub. File or Component Name Action Notes SQLPlus script System environment variable JAVA_HOME Business Objects DQ XI server Use the following SQLPlus script to enable FirstLogic Direct in your ORS. -- Feature Name Options: FIRSTLOGICDIRECT -- Set Value Options: 'On' or 'Off' DECLARE IN_CL_FEATURE_NAME VARCHAR2(200); IN_CL_SET_VALUE VARCHAR2(50); OUT_ERROR_MSG VARCHAR2(200); RC NUMBER; BEGIN IN_CL_FEATURE_NAME:= 'FIRSTLOGICDIRECT'; IN_CL_SET_VALUE:= On'; OUT_ERROR_MSG:= NULL; RC:= NULL; CMXUT.SET_CLEANSE_FEATURE (IN_CL_FEATURE_NAME, IN_CL_SET_VALUE, OUT_ERROR_MSG, RC); DBMS_OUTPUT.PUT_LINE ('OUT_ERROR_MSG= ' OUT_ERROR_ MSG); END;/ COMMIT; Make sure that this variable: Points to the correct (supported) Java version (see the Release Notes compatibility information). Is found on the PATH variable before other Java versions. Start the FirstLogic Direct server. Windows: Go to: Start > Control Panel > Administrative Tools > Services. UNIX: Go to <dqxi_install_dir>/bin. Type this command to start the dqxi service: execute start_dqxiserver.sh FirstLogic Direct must specify its own Java version. FirstLogic Direct Cleanse Engine 37

52 Configuring Informatica MDM Hub to Use the Adapter Configuring Informatica MDM Hub to Use the Adapter In order to integrate FirstLogic Direct with Informatica MDM Hub, you must configure Informatica MDM Hub for the adapter. All parameters are set in during the cleanse match server installation. and can be modified inside FLD_default_config.txt file. This file is located in the following directory: Windows:<infamdm_install_directory>\cleanse\resources\ firstlogicdirect UNIX:<infamdm_install_directory>/cleanse/resources/firstLogicDirect When the parameters are set, Informatica MDM Hub imports the project list and adds each transaction type as an Informatica MDM Hub cleanse function. On every load of the library in the Hub Console or on every refresh of the FirstLogic DQXI SDK cleanse functions, the FirstLogicDirect Adapter: Does a lookup to the FirstLogic Direct server. Retrieves all transactional projects, with their input and output parameters. Displays those projects as FirstLogic Direct functions in the Informatica MDM Hub cleanse tool. Using Your FirstLogic Direct Library You can use your FirstLogic Direct transactional project in Informatica MDM Hub s cleanse tool just as you would use any other cleanse function. The FirstLogicDirect Adapter will list all your transactional projects in Informatica MDM Hub s cleanse tool. When you create new projects in FirstLogic Direct, or modify a project s inputs or outputs, you must refresh the view in Informatica MDM Hub s cleanse tool to see the updates. 38 Informatica MDM Hub Cleanse Adapter Guide

53 Using Your FirstLogic Direct Library About Transactional Mode In order to use FirstLogic Direct in transactional mode, the project must be of type Transaction. An example of a transactional project is in the FirstLogic Direct blueprints: By default, these files are located in the following directory: Windows: <dqxi_install_dir>\repository\configuration_rules\projects\ blueprints\transactional_address_data_cleanse_us.xml UNIX: <dqxi_install_dir>/repository/configuration_rules/projects/ blueprints/transactional_address_data_cleanse_us.xml By default, this project uses inputs Address Line 1 through 4, and outputs as delivery-address, city, region, postcode, etc. You can create additional output fields by adding fields to the SOAP Writer component in the Output Field Options group. Specific values can be derived from the Output Field Options of the USA Multi-line component. About the Transactional Mode Sample Your distribution includes a sample FirstLogic Direct project for the Cleanse Match Server. This was created by customizing the FirstLogic Direct blueprint : The blueprint is found in the following directory: Windows: <dqxi_install_dir>\repository\configuration_rules\projects\ blueprints\trans_address_data_cleanse_usa.xml UNIX: <dqxi_install_dir>/repository/configuration_rules/projects/ blueprints/trans_address_data_cleanse_usa.xml FirstLogic Direct Cleanse Engine 39

54 Using Your FirstLogic Direct Library The sample transactional project is configured to input up to four (4) fields of address data and up to eight (8) fields of non-address data in an XML string, cleanse the address, name, firm, SSN (U.S.only), date, phone, and data, and output discrete cleansed fields in an XML string. 40 Informatica MDM Hub Cleanse Adapter Guide

55 5 Trillium Director Cleanse Engine Integration between Informatica MDM Hub and the Trillium Director cleanse engine occurs through the Trillium Director Adapter. This adapter is an optional component. This chapter explains how to configure your Informatica MDM Hub system to use the Trillium Director Adapter and the Trillium Director cleanse engine. This chapter assumes that you are knowledgeable about configuring and using the Trillium Director software. To learn more about Trillium Director, see your Trillium Director documentation. Note: Make sure that you have the latest Trillium patches installed before you work with the Trillium Director Adapter. Contact Support for more information. Chapter Contents About Trillium Director Integration Before You Install Configuring Trillium Director 7 Series and the Cleanse Match Server Configuring Trillium Director 11 Cleanse Engine in the Console on Windows Upgrading Trillium Director Configuring Trillium Director for Multithreading Setting the Threading Pool Increasing the Number of Network Connection Retries 41

56 About Trillium Director Integration About Trillium Director Integration Informatica MDM Hub integrates with Trillium Director by treating Trillium Director projects as cleanse functions. Informatica MDM Hub uses a Trillium Director configuration file to determine the Trillium Director projects that are available for integration into the Hub Console library. The default files are: td_default_config.txt td_default_config_global.txt td_default_config_us_detail.txt td_default_config_us_summary.txt By default, these files are located in the following directory: Windows: <infamdm_install_directory>\cleanse\resources\ Trillium\samples\director\ UNIX: <infamdm_install_directory>/cleanse/resources/ Trillium/samples /director/ The process of integrating with Trillium Director involves installing and configuring Trillium Director for use with Informatica MDM Hub. To integrate the Trillium Director cleanse engine with Cleanse Match Server: 1. See prerequisites for Trillium Director Adapter in Before You Install on page Install Trillium Director. To learn more, see your Trillium Director documentation. Important: We recommend that you install the Cleanse Match Server and Trillium Director on the same machine for improved performance. 3. Install your application server. To learn more, see your application server documentation. 4. Install Cleanse Match Server as explained in the Informatica MDM Hub guide. 5. Configure Trillium Director to use the Informatica MDM Hub. To learn more, see Configuring Trillium Director 7 Series and the Cleanse Match Server on page Check your installation and configuration. To learn more, see Testing Your Trillium Director Configuration on page Informatica MDM Hub Cleanse Adapter Guide

57 Configuring Trillium Director 7 Series and the Cleanse Match Server Before You Install Before you install: Make sure that your Informatica MDM Hub license has the cleanse adapter and the Trillium Director Adapter enabled. Contact Informatica support to obtain this license. Ensure that the following Trillium Director components are installed on the same machine as Cleanse Match Server: Trillium Director Server Trillium Director data files for the countries with which you are working. Contact Trillium for these files. Configuring Trillium Director 7 Series and the Cleanse Match Server In order to successfully integrate Trillium Director 7 Series with the Informatica MDM Hub, you must configure both Trillium Director 7 Series and the Cleanse Match server to work together. To configure Trillium Director and the Cleanse Match server: 1. Change the default Trillium Director port from 4444 to something that does not conflict with any other port that is used on this machine such as port To learn more, see your Trillium Director documentation. 2. Go to the following directory: Windows: <Cleanse_Install_Directory>\resources \Trillium\samples\director\ UNIX: <Cleanse_Install_Directory>/resources /Trillium/samples/director/ Check to make sure you have the following files: td_default_config.txt td_default_config_global.txt td_default_config_us_detail.txt td_default_config_us_summary.txt Trillium Director Cleanse Engine 43

58 Configuring Trillium Director 7 Series and the Cleanse Match Server These files define the Trillium Director projects you use with the Cleanse Match server. If you do not have these files, contact Informatica support. 3. Open the following file for editing: Windows: <Cleanse_Match_Server_Install_Dir>\resources \cmxcleanse.properties UNIX: <Cleanse_Match_Server_Install_Directory>/ resources/cmxcleanse.properties Check the following values: Windows: # Trillium Director Properties cleanse.library.trilliumdir.property.config.file.1=c:/<infamdm_ cleanse_install_home>/hub/cleanse/resources/trillium/samples /director/td_default_config_global.txt cleanse.library.trilliumdir.property.config.file.2=d:/<infamdm_ cleanse_install_home>/5488jb/cleanse/resources/trillium/ samples/director/td_default_config_us_detail.txt cleanse.library.trilliumdir.property.config.file.3=d:/<infamdm_ cleanse_install_home>/5488jb/cleanse/resources/trillium/ samples/director/td_default_config_us_summary.txt UNIX: # Trillium Director Properties cleanse.library.trilliumdir.property.config.file.1=/u1/<infamdm_ cleanse_install_home>/hub/cleanse/resources/trillium/ samples/director/td_default_config_global.txt cleanse.library.trilliumdir.property.config.file.2=d:/<infamdm_ cleanse_install_home>/trillim/cleanse/resources/trillium/ samples/director/td_default_config_us_detail.txt cleanse.library.trilliumdir.property.config.file.3=d:/<infamdm_ cleanse_install_home>/trillim/cleanse/resources/trillium/ samples/director/td_default_config_us_summary.txt Save and close the properties file. 4. Run the following SQL script to enable Trillium Director for Cleanse Match Server: -- Feature Name Options: 'TrilliumDir' -- Set Value Options: 'On' or 'Off' DECLARE 44 Informatica MDM Hub Cleanse Adapter Guide

59 Configuring Trillium Director 7 Series and the Cleanse Match Server IN_CL_FEATURE_NAME VARCHAR2(200); IN_CL_SET_VALUE VARCHAR2(50); OUT_ERROR_MSG VARCHAR2(200); RC NUMBER; BEGIN IN_CL_FEATURE_NAME := 'TrilliumDir'; IN_CL_SET_VALUE := 'On'; OUT_ERROR_MSG := NULL; RC := NULL; CMXUT.SET_CLEANSE_FEATURE ( IN_CL_FEATURE_NAME, IN_CL_SET_VALUE, OUT_ERROR_ MSG, RC ); DBMS_OUTPUT.PUT_LINE ( 'OUT_ERROR_MSG= ' OUT_ERROR_MSG ); END; / COMMIT; 5. Add the Trillium Director bin directory path to both the CLASSPATH and the PATH environment variables. This is the default bin directory location: Windows: C:\tril7v8\Director\bin UNIX: /u1/tril7v8/director/bin 6. Also check that the TRILLDIRPORT and TRILLDIRADDR environment variables are set to an appropriate value. For example: TRILLDIRADDR=localhost TRILLDIRPORT= Obtain the latest data files from Trillium. 8. If you have not done so already, start the Trillium Director and Trillium Cleansing Server services. 9. Start your application server and start Cleanse Match Server. To check to make sure that the Trillium Director library is correctly configured, see Testing Your Trillium Director Configuration. Trillium Director Cleanse Engine 45

60 Configuring Trillium Director 11 Cleanse Engine in the Console on Windows Configuring Trillium Director 11 Cleanse Engine in the Console on Windows Before you can display the cleanse engine in the console, you must run the following script: DECLARE IN_CL_FEATURE_NAME VARCHAR2(200); IN_CL_SET_VALUE VARCHAR2(50); OUT_ERROR_MSG VARCHAR2(200); #Configuring Trillium Director and the Cleanse Match Server #Trillium Director Cleanse Engine 39 RC NUMBER; BEGIN IN_CL_FEATURE_NAME := 'TrilliumDir11'; IN_CL_SET_VALUE := 'On'; OUT_ERROR_MSG := NULL; RC := NULL; CMXUT.SET_CLEANSE_FEATURE ( IN_CL_FEATURE_NAME, IN_CL_SET_VALUE, OUT_ERROR_ MSG, RC ); DBMS_OUTPUT.PUT_LINE ( 'OUT_ERROR_MSG= ' OUT_ERROR_MSG ); END; / COMMIT; Use these values for Feature Name: 'TrilliumDir11', and these values for CL_SET_ VALUE: 'On' or 'Off' Add the following properties to the cmxcleanse.properties file: # Trillium Director Properties cleanse.library.trilliumdir11.classname=com.siperian.mrm.cleanse.tri lliumdir11.library cleanse.library.trilliumdir11.property.config.file.1=<infamdm_ install_directory>/hub/cleanse/resources/trillium/samples /director/td_default_config_global.txt 46 Informatica MDM Hub Cleanse Adapter Guide

61 Configuring Trillium Director 11 Cleanse Engine in the Console on Windows Testing Your Trillium Director Configuration To test your Trillium Director configuration: 1. Go to the Informatica MDM Hub console. 2. Choose the Cleansing tool from the workbench. 3. Choose cleansing functions. 4. Refresh the Trillium Director library. You should see your Trillium Director functions. If you do not see those functions, check to make sure that you have successfully completed the steps in Configuring Trillium Director 7 Series and the Cleanse Match Server on page 43. You can now use these functions to make a mapping and cleanse your data. About the Default Configuration File The default configuration file (td_default_config.txt) is located in the following directory: Windows: <infamdm_install_directory>\cleanse\ resources\trillium\samples\director\ UNIX:<infamdm_install_directory>/cleanse/ resources/trillium/samples/director/ This configuration file contains such information as: function name function description input parameters output parameters update parameters The following listing is an example of a configuration file: TD_FUNCT_NAME = TrilliumDirectorTest TD_FUNCT_DESCR = Trillium Director adapter test. Trillium Director Cleanse Engine 47

62 Configuring Trillium Director 11 Cleanse Engine in the Console on Windows TD_SYSTEM_ID = G TD_SERVER_NAME = Cleanser TD_INPUT_PARAM_0 = Line1 TD_INPUT_PARAM_1 = Line3 TD_INPUT_PARAM_2 = Line9 TD_INPUT_PARAM_4 = FirstName TD_INPUT_PARAM_3 = HouseNo TD_INPUT_PARAM_5 = StreetAddress TD_INPUT_PARAM_6 = City TD_INPUT_PARAM_7 = State TD_INPUT_PARAM_8 = PostalCode TD_INPUT_PARAM_9 = Country TD_OUTPUT_PARAM_0 = prstreetname TD_OUTPUT_PARAM_1 = prhousenumber TD_OUTPUT_PARAM_3 = prcityname TD_OUTPUT_PARAM_2 = drstreetname TD_OUTPUT_PARAM_4 = drhousenumber TD_OUTPUT_PARAM_5 = drcityname TD_OUTPUT_PARAM_6 = drstateprovcityname TD_OUTPUT_PARAM_7 = gmstatecode TD_OUTPUT_PARAM_8 = gmzipcode TD_OUTPUT_PARAM_9 = prpostalcode TD_UPD_PARAM_0 = pr_gout_str_name TD_UPD_PARAM_1 = pr_gout_house_number TD_UPD_PARAM_2 = pr_city_name TD_UPD_PARAM_3 = dr_street_name TD_UPD_PARAM_4 = dr_house_number TD_UPD_PARAM_5 = dr_city_name TD_UPD_PARAM_6 = dr_st_prov_cty_name TD_UPD_PARAM_7 = gm_gaci_state_code TD_UPD_PARAM_8 = gm_gaci_zipcode TD_UPD_PARAM_9 = pr_gout_postal_code 48 Informatica MDM Hub Cleanse Adapter Guide

63 Configuring Trillium Director 11 Cleanse Engine in the Console on Windows The following table describes the entries in this configuration file: Name TD_FUNCT_NAME TD_FUNCT_DESCR TD_SYSTEM_ID TD_SERVER_NAME TD_INPUT_PARAM_* TD_OUTPUT_PARAM_* TD_UPD_PARAM_* Value The name of your Trillium Director function A description of the function. This appears when you look at the available functions using the Cleansing Tool. The Trillium Director system ID. This defines which Trillium Director process to use. The name of the server process within the Trillium Director system indicated in TD_SYSTEM_ID. This is the name of the Trillium Director server that is running the project you are using. This is the Cleanser instance where your project was deployed. This is a group of entries, one for each input parameter for the function. This is a group of entries, one for each output parameter for the function. This is a group of entries, one for each update parameter for the function. Using Your Trillium Director Projects with the Adapter To use your Trillium Director projects with the adapter, instead of the sample project: 1. Open the td_default_config.txt file for editing. The file is usually found at: Windows: <infamdm_install_directoryy>\cleanse\ resources\trillium\samples\director UNIX:<infamdm_install_directory>/cleanse/ resources/trillium/samples/director 2. Make the following changes in the td_default_config.txt file: Change the TD_SYSTEM_ID value to your Trillium Director system ID. Change the TD_SERVER_NAME value to the name of the server process within Trillium Director that is running your project. Change the TD_FUNCT_NAME value to the name of your Trillium Director function. Trillium Director Cleanse Engine 49

64 Upgrading Trillium Director Change the TD_FUNCT_DESCR value to a description of your Trillium Director function. Change the TD_INPUT_PARAM_*, TD_OUTPUT_PARAM_*, and TD_UPD_PARAM_* values to match the inputs, outputs, and updates for your Trillium Director function. Add or remove entries as necessary. 3. Save and close the td_default_config.txt file. Upgrading Trillium Director If you are upgrading your Informatica MDM installation, you may also need to also upgrade your Trillium Director cleanse engine. To configure Trillium Director: 1. Obtain the required files (unlock codes and other files). 2. Edit the Hub Cleanse Match properties file. See Configuring Trillium Director 7 Series and the Cleanse Match Server on page 43 for details. Configuring Trillium Director for Multithreading If you have the Trillium Director installed on a machine with more than one processor, you can use multithreading to take advantage of your hardware. To configure your Trillium Director for performance: Turn on caching for performance benefits. By default, Trillium Director is set to be single-threaded. Trillium Director will revert to this default if you set an invalid value for the number of threads, such as a number equal to or less than 0 or a very large number. Set the number of threads to equal the number of CPUs in the machine where Trillium Director is installed. You can confirm the thread settings by turning debug on. This will show you threads that are spawned and other information. To learn more, see your Trillium Director documentation. 50 Informatica MDM Hub Cleanse Adapter Guide

65 Increasing the Number of Network Connection Retries Important: Turn debug off when you are in a production environment. Debug can have a significant negative effect on performance. Setting the Threading Pool When the Trillium adapter works with large data sets, it uses thread-pool connections in the application server. These threads are shared by all the jobs that the server handles. The thread-pool level is designated in the following property: cleanse.library.trilliumdir.property.td.project.pool.maxactive=nn, where nn is the same or slightly higher than the total thread count of all jobs running in parallel. The default setting for the MaxActive property allows as many connections as are requested. To restrict the number of connections, reset the MaxActive property value. Increasing the Number of Network Connection Retries When network traffic is heavy and a high number of cleanse threads are being used, the network connection for a thread between the Informatica MDM Hub and the Trillium server can time out while a record is being processed. The server automatically tries to restart the connection five times, and issues an error message after the fifth try if the connection attempt fails. Note: The batch cleanse will still run through, with the record marked as rejected. The number of restart tries is determined by the following property, which can be added to the cmxcleanse.properties file: cleanse.library.trilliumdir.property.set_maximum_retry_count=15 The default value for this property is five (5). To ensure that the Hub tries to establish the network connection enough times to account for network traffic, set this property to a high number (such as 15). Trillium Director Cleanse Engine 51

66 Increasing the Number of Network Connection Retries 52 Informatica MDM Hub Cleanse Adapter Guide

67 6 SAP Data Services XI Cleanse Engine One of the ways to access data cleansing functionality in the SAP Data Services XI product is via Web services that the SAP product publishes. This chaper describes how, in your Informatica MDM Hub implementation, to set up and use the Informatica MDM Cleanse Adapter for SAP (Web Services) to access cleanse functions that are published as Web services. This functionality allows you add a new type of cleanse library - an SAP cleanse library - to your Informatica MDM Hub implementation, and then integrate cleanse functions in the SAP library into your mappings, just as you would integrate any other type of cleanse function available in your Informatica MDM Hub implementation. Informatica MDM Hub acts as a Web service client application that consumes Web services published by SAP Data Services XI. If you do not use the SAP Data Services XI cleanse engine, you can skip this chapter. Chapter Contents About SAP Data Services XI Integration Adding an SAP Library in the Cleanse Functions Tool Configuring Generated Libraries 53

68 About SAP Data Services XI Integration About SAP Data Services XI Integration Prerequisites To use this functionality, you must have installed the following software: Siperian Hub XU SP2 Patch B or later SAP BusinessObjects Data Services XI 3.2 or higher Informatica MDM license that enables SAP Data Services XI functionality (siperian.sap_=yes in the configuration file) Related Information Process Overview For more information, see: Chapter 12, Configuring Data Cleansing, in the Informatica MDM Hub Administrator Guide (this chapter provides supplemental information to that chapter) Informatica MDM Hub Cleanse Adapter Guide (this guide) SAP BusinessObjects Data Services XI 3.2 product information (including setup instructions). Refer to the following URL: map_en.pdf To use these Web services in your Informatica MDM Hub implementation, complete thefollowing steps: 1. Obtain a SAP Web Services Description Language (WSDL) file for the Web service(s) that you want to consume. Use the WSDL generated by SAP BusinessObjects Data Services XI 3.2. You need to add to the WSDL any Webservices that you want to consume. 2. In the Cleanse Functions tool of the Informatica MDM Hub Console, add an SAP library and specify the URI of the Web Services Description Language (WSDL) file as well as connection information (service and port) to hosted Web services. For 54 Informatica MDM Hub Cleanse Adapter Guide

69 About SAP Data Services XI Integration instructions, see Adding an SAP Library in the Cleanse Functions Tool later in this chapter. The Cleanse Functions tool builds the SAP library based on the WSDL, and then displays the list of cleanse functions defined in the WSDL. Each cleanse function represents a separate Web service. 3. Enable a generated library according to the instructions in Enabling a Generated Library later in this chapter. 4. In the Mappings tool of the Informatica MDM Hub Console, use the available cleanse functions in your mappings as required. You must configure the inputs and outputs just as you would configure any other mappings. Run-time Behavior For more information, see the documentation for the Mappings tool inchapter 11, Configuring the Stage Process, in the Informatica MDM Hub Administrator Guide. At run time, each time a cleanse function is fired: SAP Data Services XI Cleanse Engine 55

70 About SAP Data Services XI Integration Considerations Informatica MDM Hub submits the request to the associated Web service, passing the input parameters from the currently-processed record as defined in the mapping. Informatica MDM Hub handles the response from the Web service, retrieving output parameters as defined in the mapping, and writing the appropriate changes to the record. Web service invocations are synchronous only. Asynchronous invocations are not supported. Web service invocations operate on a single record at a time. Batch processing of multiple records in a single service invocation is not supported. The purpose of using the Web services is strictly to transform data that is passed in the request according to the associated cleanse function. Other types of Web services, such as publish/subscribe services, are not supported. If the Web service returns an error, Informatica MDM Hub moves the record to the reject table and saves a description of the problem (including any error information returned from the Web service). If the Web service is published on a remote system, the infrastructure must be in place for Informatica MDM Hub to connect to the Web service (such as a network that accesses the Internet). When using cleanse functions that are implemented as Web services, run-time performance of Web service invocations depends on some factors that are external to Informatica MDM Hub, such as availability of the Web service, the time required for the Web service to process the request and return the response, and network speed. 56 Informatica MDM Hub Cleanse Adapter Guide

71 Adding an SAP Library in the Cleanse Functions Tool You can run WSDL cleanse function with multi-threading. To enable this, change the thread count on the Informatica MDM Hub Cleanse Match Server. Make sure that there is a sufficient number of instances of the SAP Web Service to handle the multiple Informatica MDM cleanse threads; otherwise, records might be rejected due to timeouts. WSDL files must comply with the Axis2 Databinding Framework (ADB). Non-compliant WSDL files are not supported. When you configure mappings, you must ensure that the inputs and outputs are appropriate for the Web service you are calling. The Mappings tool does not validate your inputs and outputs this is done by the Web service instead. If you have invalid inputs or outputs, the Web service will return an error response and any processed record(s) will be moved to the reject table with an explanation of the error. The Cleanse Functions tool displays cleanse function parameters but nodocumentation, if specified, in the WSDL file (embedded <annotation> or <documentation> tags). Adding an SAP Library in the Cleanse Functions Tool Once you have installed the prerequisite software and obtained an SAP WSDL file, you use the Cleanse Functions tool in the Informatica MDM Hub Console to add the SAP library to your Informatica MDM Hub implementation. 1. Launch the Informatica MDM Hub Console, if it is not already running. 2. Start the Cleanse Functions tool. 3. Obtain a write lock (Write Lock > Acquire Lock). 4. Select the Cleanse Functions (root) node. SAP Data Services XI Cleanse Engine 57

72 Adding an SAP Library in the Cleanse Functions Tool 5. Choose Cleanse Functions > Add SAP Data Services XI Library. 6. In the Add SAP Library dialog, specify the following settings: Setting Library Name SAP Data Services XI WSDL URI SAP Data Services XI WSDL Service SAP Data Services XI WSDL Port Description Description Name of this SAP Data Services XI library. You can assign any arbitrary name that helps you classify and organize the collection of SAP cleanse functions. Consider having "SAP" in the name to distinguish this from other cleanse function libraries. This name will appear as the folder name in the Cleanse Functions list. URI (location) of the SAP WSDL to implement. Service of the SAP WSDL to implement. Port of the SAP WSDL to implement. Descriptive text for this library that you want displayed in the Cleanse Functions tool. Note: Simple WSDLs often have only one Service and one Port. You can refer to the SAP WSDL for the values to specify for these settings. 58 Informatica MDM Hub Cleanse Adapter Guide

73 Adding an SAP Library in the Cleanse Functions Tool The following figure shows sample settings for an SAP WSDL that invokes default SAP name and address cleansing. 7. Click OK to add the metadata definition for this new SAP library to the local ORS repository. SAP Data Services XI Cleanse Engine 59

74 Adding an SAP Library in the Cleanse Functions Tool 8. Click the Refresh button to generate the SAP library. The Cleanse Functions tool retrieves the latest SAP WSDL, generates the SAP library, and displays any available cleanse functions in the Cleanse Functions list. If the Cleanse Functions tool cannot consume the SAP WSDL file (for example, due to a syntax error), then it displays an error message instead. You need to fix the SAP WSDL file or obtain a valid one. If changes in the SAP WSDL file affect any existing mappings, the Cleanse Functions tool displays an error. You must fix the affected mappings before running the cleanse process. 9. Click a cleanse function to display its properties. 60 Informatica MDM Hub Cleanse Adapter Guide

75 Adding an SAP Library in the Cleanse Functions Tool 10. At this point, you can add these cleanse functions to your mappings in the Mappings tool, as shown in the Process Overview earlier in this chapter. SAP Data Services XI Cleanse Engine 61

76 Adding an SAP Library in the Cleanse Functions Tool 11. Test the function by clicking the Test tab and then clicking the Test button. 62 Informatica MDM Hub Cleanse Adapter Guide

77 Configuring Generated Libraries Configuring Generated Libraries When the Cleanse Functions tool generates a library, it creates a set of properties files in the SIP_HOME/cleanse/lib directory with the following naming format: siperian-cleanse-<servicename>_<functionname>.properties.new Note: File names must be unique (service name + function name) within this directory. Enabling a Generated Library To enable a generated library, remove the.new extension from the file name. Properties File Syntax # endpointoverride = # # Inputs for <functionname> # #<wsdl_in_param1> = name, description #<wsdl_in_param2> = name, description # # Outputs for <functionname> # SAP Data Services XI Cleanse Engine 63

78 Configuring Generated Libraries Example Properties File #<wsdl_out_param1> = name, description #<wsdl_out_param2> = name, description Below is an example code listing. #endpointoverride = # # Inputs for name_address # Req_Name_DITypeVarchar1024 = Req_Name_DITypeVarchar1024, Req_Name_ DITypeVarchar1024 Req_State_DITypeVarchar1024 = Req_State_DITypeVarchar1024, Req_State_DITypeVarchar1024 Req_Address_DITypeVarchar1024 = Req_Address_DITypeVarchar1024, Req_Address_DITypeVarchar1024 Req_City_DITypeVarchar1024 = Req_City_DITypeVarchar1024, Req_City_ DITypeVarchar1024 Req_Pcode_DITypeVarchar1024 = Req_Pcode_DITypeVarchar1024, Req_Pcode_DITypeVarchar1024 # # Outputs for name_address # Res_Address_DITypeVarchar1024 = Res_Address_DITypeVarchar1024, Res_Address_DITypeVarchar1024 Res_Name_DITypeVarchar1024 = Res_Name_DITypeVarchar1024, Res_Name_ DITypeVarchar1024 Res_State_DITypeVarchar1024 = Res_State_DITypeVarchar1024, Res_State_DITypeVarchar1024 Res_City_DITypeVarchar1024 = Res_City_DITypeVarchar1024, Res_City_ DITypeVarchar1024 Res_Pcode_DITypeVarchar1024 = Res_Pcode_DITypeVarchar1024, Res_Pcode_DITypeVarchar Informatica MDM Hub Cleanse Adapter Guide

79 Configuring Generated Libraries Editing a Generated Properties File To edit a generated properties file: 1. Remove the.new from the end of the file name to enable it. 2. Open the file in a text editor. 3. Make the changes you want to the file, then save the file. 4. In the Cleanse Functions tool, select the SAP library, then click the Refresh button to activate these changes in the properties file. Note: When you click Refresh to generate a library from a WSDL, the Cleanse Functions tool regenerates the file with the.new name. Changes made to a file that has been renamed (.new was removed) will not be overwritten when the library is refreshed. You would edit a generated properties file for the following reasons: to change the connection endpoint to rename or remove extraneous parameters Adding a Different Connection Endpoint If the communication endpoint for a Web service changes, or if you need to point to a different environment, you can edit the properties file and provide the alternate endpoint URL as an override: # endpointoverride = This setting overrides the configured endpoint setting for this SAP library. You might need to do this, for example, when moving from a development/test environment to a production environment, or when (in a production environment) it might not be feasible to perform a refresh on the adapter. SAP Data Services XI Cleanse Engine 65

80 Configuring Generated Libraries Managing Input and Output Parameters The names generated from the WSDL can sometimes be long and difficult to read, or in an uncommon order, as shown in the following example. You can edit the generated parameter file and rename parameters to make them easier to read and recognize. In fact, if you encounter an error indicating that one or more names are too long to be stored in the ORS repository (> 100 characters), then you will need to shorten these names. You can simplify the library by removing extraneous parameters that are not needed for your Web service invocations. You can also reorder parameters. 66 Informatica MDM Hub Cleanse Adapter Guide

81 Configuring Generated Libraries To edit parameter names: For required parameters (parameters that you want to use in your cleanse functions), uncomment by removing the # character. Any parameter that is not uncommented will be removed from the function. Edit parameter names and descriptions as required. You cannot have duplicate parameter names in one function (duplicates will be ignored). The library will need to be refreshed for the changes to the properties file to take effect. In the Cleanse Functions tool, select the library and click Refresh. For example, the following figure shows the default generated output for an SAP library. To rename a parameter, change its name setting: <parameter> = name, description SAP Data Services XI Cleanse Engine 67

82 Configuring Generated Libraries The following example shows renamed parameters. In addition, you can change the order of the parameters, as shown in the following example. 68 Informatica MDM Hub Cleanse Adapter Guide

83 Configuring Generated Libraries Save changes to the file and then, in the Cleanse Functions tool, select the library and click Refresh to update the modified cleanse function settings. The changes are reflected in Function Inputs and Function Outputs. SAP Data Services XI Cleanse Engine 69

84 Configuring Generated Libraries Once refreshed, be sure to test the cleanse function to verify its operation. 70 Informatica MDM Hub Cleanse Adapter Guide