Creating a custom handler for address standardization

If your business needs require that you use a custom address standardization handler, use this procedure.


  1. Make sure that the IBM® WebSphere® Application Server is running and the operational server-side applications are deployed successfully.
    1. Open the IBM WebSphere Application Server administrative console.
    2. Select Applications > All Applications.
    3. Select the applications and select Start from the menu.
    4. Select Submit Action.
  2. In InfoSphere® MDM Workbench, create a new configuration project.
  3. In the Configuration editor, select Member Types and go to the Attributes tab.
  4. Add new attributes to store the standardized address for the selected member type.
  5. In the Configuration editor, select Handlers.
  6. In the Handler editor, click Add.
    1. Type a handler name.
    2. Use the sequence number default.
    3. In the Callback field, select pre-interaction.
    4. In the Interaction code field, select MEMPUT.
    5. Enter your handler arguments. Input must in the format of attrCode1:attrCode2, attrCode1:attrCode2,…. The format is case-sensitive and must not have any spaces in between.
  7. Click Generate to generate the OSGi bundle and CBA projects for this new handler. The Java source file for the interaction handler, inside the bundle project, is automatically opened.
  8. Deploy the operational server configuration (with the new attribute codes and handler definition) to the MDM database.
  9. In the Java™ source file, write the code to perform the address standardization. You can use the Java source for the prepackaged default handler for reference. If Project > Build Automatically is turned on, your Java source file compiles automatically. Verify that your code compiles without errors.
  10. Right-click the CBA project and click Export.
  11. Select the export destination OSGi > OSGi Composite Bundle (CBA).
    Verify that the bundles you are exporting include your operational server module bundle.
  12. Click Browse and choose a location to save the CBA file, then click Finish.
  13. Open the IBM WebSphere Application Server admin console and, in the navigation frame, click Environment > OSGi bundle repositories > Internal bundle repository, then click New.
  14. Select the local file system and browse to where you saved the CBA you exported from the MDM Workbench, then click OK, then click Save directly to the master configuration.
  15. In the navigation frame, click Applications > Application Types > Business-level applications and click on the InfoSphere MDM application ( and select the EBA deployed asset (
    This step can take several minutes.
  16. Click Extensions for this composition unit, then click Add.
  17. Select the check box next to the imported CBA, then click Add.
    It can take a few minutes to load the next page
  18. Click Save directly to the master configuration.
    Completing this action returns you to the composition unit page.
  19. Click the button labelled Update to latest deployment to examine the preview of changes and then click OK.
    For your extension CBA, it should show it changing from Not deployed to a version number.
  20. Click Next through the options wizard, accepting the default options on each page, then click Finish.
  21. Click Save directely to the master configuration.
  22. Restart the server.
  23. Add the URL for the IBM Information Server location where the InfoSphere QualityStage® job runs.
    1. Use a database client to view the contents of the CONFIGELEMENT table.
    2. Locate the record with the NAME field set as /IBM/ThirdPartyAdapters/IIS/providerURL. A default value for this name is set in the DEFAULT_VALUE field. Add the IIS server URL in the VALUE field.
      You can modify this sample SQL statement to add the URL:
      UPDATE configelement SET value = 'http://<<IIS server host name>>:<<portnumber>>', last_update_dt = current timestamp WHERE name =  '/IBM/ThirdPartyAdapters/IIS/providerURL'
  24. Confirm that the input and output attribute mappings in the CONFIGELEMENT table are correctly set.
    1. Use a database client and view the contents of the CONFIGELEMENT table.
    2. Locate the records for which NAME starts with /IBM/ThirdPartyAdapters/IIS/StandardizeAddress/VirtualMDM/AttributesMap.
    3. Make sure that the input and output attribute maps are set correctly to match the handler arguments in the handler definition.
  25. IBM WebSphere Application Server and the operational server must be restarted to use the new configuration and CONFIGELEMENT table updates.
    1. Open IBM WebSphere Application Server administrative console and select Servers.
    2. Select the name of your MDM operational server.
    3. Click Stop.
    4. Click Start.