| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Administering: Modifying Master Index Configuration Files (Repository) |
|
Administering the Sun Business Process Manager Database
Using the Sun Business Process Manager Worklist Manager for User Activities
Maintaining Sun Master Indexes (Repository)
Defining Master Index Security (Repository)
To Create a Master Index User Account
Master Index User Roles (Repository)
Learning About Master Index Reports (Repository)
Master Index Command Line Reports (Repository)
Master Index Report Configuration (Repository)
Creating Custom Master Index Reports (Repository)
Masked Data in Master Index Reports (Repository)
Master Index Production Reports (Repository)
Master Index Activity Reports (Repository)
Master Index Database Indexes (Repository)
Working With Master Index Command Line Reports (Repository)
Configuring the Master Index Report Environment (Repository)
Configuring Master Index Command Line Reports (Repository)
Master Index Command Line Report Properties (Repository)
Running Master Index Command Line Reports (Repository)
Maintaining the Master Index Database (Repository)
Backing up the Master Index Database
Restoring the Master Index Database
Implementing Changes to the Master Index Project (Repository)
Modifying Standard Master Index Project Components (Repository)
Modifying the Master Index Database (Repository)
Modifying Master Index Security (Repository)
Modifying the Local ID Format (Repository)
Working With the EDM for Sun Master Patient Index
Working With the EDM for Sun Master Index
Working With the Master Index Data Manager
Maintaining Sun Master Indexes
Over time, you might need to make changes to your configuration files, such as adding fields or objects to the object structure, changing queries, or fine-tuning the matching process. Whenever you make a change to a master index configuration file, you must disable the master index server project, regenerate the application, and then redeploy the project. If any Java Collaborations in client projects reference the master index application, you must re-import the regenerated .jar files from the master index server project into the Java Collaboration.
This section provides tips for updating components of the configuration files. In order for any of these changes to take affect, you must regenerate the application and rebuild and redeploy the project.
If you make any changes to the object structure, keep the following in mind.
If you want the new fields or objects to appear on the EDM, make sure to add them to the first section of the Enterprise Data Manager file and to any of the page definitions later in the file (this includes search pages).
If the new fields require normalization, parsing, or phonetic encoding, define the new structures in the Match Field file.
If a new field will be used for matching, add it to the blocking query used for match processing as well as to the match string in the Match Field file.
If the new fields or objects will be included in incoming messages, add them to the inbound OTD structure (the outbound OTD will be updated when you regenerate the application).
If you define normalization, standardization, or phonetic encoding for fields that are not currently defined in the Match Field file, or if you change existing standardization structures, make sure to do the following.
Use the appropriate standardization type, domain selector, and field IDs.
Add the new fields that will store the standardized versions of the original field value to the appropriate objects in the Object Definition file.
Add new columns to the database to store the standardized field values.
If you make changes to the match string, update the database indexes and the blocking query in the Candidate Select file accordingly. For example, if you remove a field from the match string, you might also want to remove that field from the blocking query and database indexes. If you add a field to the match string, add the field to the blocking query and to the appropriate database index to maintain performance.