Table of Contents

Search

  1. Introduction
  2. Configuring Hub Console Tools
  3. Building the Data Model
  4. Configuring the Data Flow
  5. Executing Informatica MDM Hub Processes
  6. Configuring Application Access
  7. MDM Hub Properties
  8. Viewing Configuration Details
  9. Search with Solr
  10. Row-level Locking
  11. MDM Hub Logging
  12. Table Partitioning
  13. Collecting MDM Environment Information with the Product Usage Toolkit
  14. Glossary

Run the Background Cleanup Process

Run the Background Cleanup Process

You can run the background cleanup process to delete match tokens that are not valid from the match key tables. The background cleanup batch process identifies match tokens that have
invalid_ind=1
and deletes these match tokens. The background cleanup process does not rebuild the indexes in the match key table after the deletion of match tokens.
  1. To enable the background cleanup process to run, add the related Hub Server properties to the properties file.
    1. Open the
      cmxserver.properties
      file in the following directory:
      On UNIX.
      <infamdm install directory>/hub/server/resources
      On Windows.
      <infamdm install directory>\hub\server\resources
    2. Add the following properties in the
      cmxserver.properties
      file:
      Property
      Description
      cmx.server.strp_clean.execution_mode
      Configures the scope of operation of the background cleanup process on the match key table.
      Specify one of the following values for the scope of operation:
      • ALL. Deletes match tokens that have
        invalid_ind=1
        from all the match key tables on all the registered Operational Reference Stores.
      • CONFIGURED_ORS. Deletes match tokens that have
        invalid_ind=1
        from all the match key tables on the Operational Reference Stores that you specify. If you set the scope of operation to
        CONFIGURED_ORS
        , add the
        cmx.server.strp_clean.ors
        property to the
        cmxserver.properties
        file.
      • CONFIGURED_STRP. Deletes match tokens that have
        invalid_ind=1
        from the match key tables of specific base objects in specific Operational Reference Stores. If you set the scope of operation to
        CONFIGURED_STRP
        , add the
        cmx.server.strp_clean.strp
        property to the
        cmxserver.properties
        file.
      cmx.server.strp_clean.ors
      Specifies the names of the Operational Reference Stores on which the background cleanup process must run to delete match tokens that are not valid. For example, to delete match tokens that have
      invalid_ind=1
      from all the match key tables in cmx_ors1 and cmx_ors2, add
      cmx.server.strp_clean.ors=cmx_ors1,cmx_ors2
      .
      cmx.server.strp_clean.strp
      Specifies the Operational Reference Store and base object combinations for which the background cleanup process must run to clean up match key tables. For example, to delete match tokens that have
      invalid_ind=1
      from the match key tables for BO1 in cmx_ors1 and BO2 in cmx_ors2, add
      cmx.server.strp_clean.strp=cmx_ors1.C_BO1,cmx_ors2.C_BO2
      .
      cmx.server.strp_clean.delete_records_count
      Specifies the number of records to clean up from the match key table.
      cmx.server.strp_clean.retry_sec
      Specifies the time duration in seconds for which you want the MDM Hub to search for records with match tokens that are not valid in the match key table. Default is
      60
      .
      cmx.server.strp_clean.threads_count
      Specifies the number of threads that the MDM Hub uses when it searches for records with match tokens that are not valid in the match key table. Default is
      20
      .

0 COMMENTS

We’d like to hear from you!