Table of Contents

Search

  1. Preface
  2. Introduction
  3. Informatica IDQ Cleanse Engine
  4. Informatica Address Verification Cleanse Engine
  5. FirstLogic Direct Cleanse Engine
  6. Trillium Director Cleanse Engine
  7. SAP Data Services XI Cleanse Engine
  8. Troubleshooting

Adding an IDQ Library in the Cleanse Functions Tool

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. You can right click anywhere in the Cleanse Functions tool to see more options.
  3. Obtain a write lock (
    Write Lock
    >
    Acquire Lock
    ).
  4. Select the
    Cleanse Functions
    (root) node. Right click.
  5. Choose
    Cleanse Functions
    > Add
    IDQ Library
    .
  6. In the Add IDQ Library dialog, specify the following settings:
    Setting
    Description
    Library Name
    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 appears as the folder name in the Cleanse Functions list.
    IDQ WSDL URI
    URI (location) of the IDQ WSDL to implement.
    IDQ WSDL Service
    Service of the IDQ WSDL to implement.
    IDQ WSDL Port
    Port of the IDQ WSDL to implement.
    Description
    Descriptive text for this library that you want displayed in the Cleanse Functions tool.
    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:
    You must ensure that the IDQ WSDL response definition does not specify an array by setting the maxOccurs attribute value to " 1" , as shown in the sample:
    <xsd:element minOccurs="1" maxOccurs="1" name="Street" type="xsd:string"/>
  7. Click
    OK
    to add the metadata definition for this new IDQ library to the local ORS repository.
  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.
    An error message is displayed in the following cases:
    • 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 must fix the IDQ WSDL file or obtain a valid one.
      Ensure that the IDQ WSDL file does not contain an array in its response definition. You must set the maxOccurs attribute in the WSDL file to '1'.
    • 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. 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.

0 COMMENTS

We’d like to hear from you!