Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Upgrading: Step 11: Update Match and Standardization Engine Files
 

Classic Java CAPS

Upgrading to Java CAPS 6

Upgrading to Sun Master Index

About the Upgrade Paths to Sun Master Index

Upgrading From eView Studio to Sun Master Index (Repository)

To Upgrade to Sun Master Index (Repository)

Migrating to Service-Enabled Sun Master Index

Step 1: Create the Service-Enabled Master Index

Step 2: Migrate any Custom Plug-ins

Step 3: Update the Object Definition

Step 4: Update midm.xml

Step 5: Update the Master Controller

Step 6: Update the Matching and Standardization Configuration

Step 7: Update Query Definitions

Step 8: Update the Survivor Calculator

Step 9: Update Field Validations

Step 10: Validate the Configuration Files

Step 11: Update Match and Standardization Engine Files

Step 12: Upgrade the Database Connection and Security

Step 13: Finalizing the Upgrade

Step 14 (Optional): Update the Master Index API in Client Projects

Troubleshooting

JBI Based Components

Migrating From eTL to Sun Data Integrator

Step 11: Update Match and Standardization Engine Files

The match engine configuration file has not changed since the previous release, and can be copied directly into the service-enabled project. Some of the standardization files were changed extensively. If you want to use the previous configuration for the person name standardization files, you will need to reformat the files.

To Update Match Engine Files
To Update Standardization Engine Files
  1. If any Address or Business Name files were customized in the Repository-based project, copy the text of those files and paste it into the corresponding service-enabled files, replacing the existing text.

    File names have changed as indicated in the following table. Any Address or Business Name files not listed here have the same name in both versions. Make sure you when you update the files that you update the correct country set.

    Repository-Based File Name
    Service-Enabled File Name
    addressClueAbbrev*.dat
    clues.dat
    addressMasterClues*.dat
    masterClues.dat
    addressPatterns*.dat
    patterns.dat
    addressConstants*.cfg
    Obsolete
    addressInternalConstants*.cfg
    Obsolete
    addressOutPatterns.dat
    Obsolete
    bizConstants.cfg
    Obsolete
    bizRemoveSpecChars.dat
    Obsolete
  2. If any Person Name files were customized in the Repository-based project, do one of the following:
    • Manually make the changes to the service-enabled version.

      File names have changed for this release, as indicated in the following table. The following files are obsolete: personNamePatt.dat, personConstants.cfg, personFirstNameDash.dat, personRemoveSpecChars.dat, personThree*.dat, personTwo*.dat, personLastNamePrefix*.dat, and personConjon*.dat.

      Repository-Based File Name
      Service-Enabled File Name
      personFirstName*.dat
      givenNameNormalization.txt and givenName.txt
      personGenSuffix*.dat and person.OccupSuffix*.dat
      generationNormalization.txt and generation.txt
      personTitle.dat
      titleNormalization.txt and title.txt
    • Copy the text from the Repository-based files and paste it into the corresponding service-enabled files, replacing the existing text. Make sure to copy the text into the correct country files. Then reformat the file based on the new two-column format, as shown below:
      STEVE|STEPHEN
      STEWART|STUART
      STEW|STUART
      STU|STUART
      SUE|SUSAN
      SULLY|SULLIVAN

      Note - For more information about the new standardization files, see FSM-Based Person Name Configuration, in Understanding the Master Index Standardization Engine.

  3. You can customize the following new Person Name files: salutationNormalization.txt, salutation.txt, surnameNormalization.txt, and surname.txt.