| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Upgrading: Step 13: Finalizing the Upgrade |
|
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 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 14 (Optional): Update the Master Index API in Client Projects
Finalizing the project includes building the project, verifying the custom plug-ins, and finally deploying the project. You can also take advantage of the new query, matching, and SBR filtering feature described in Filtering Default Values From Master Index Processes in Configuring Sun Master Indexes . Note that adding this feature might cause inconsistencies with the way records were previously matched, but can also prevent the incorrect matching of records or flagging them as potential duplicates.
Building will compile the custom plug-ins you added previously.
Note - For more information about this process, see Broadcasting Master Index Updates to External Systems.
midm-security.xml or security.xml, add
those roles to web.xml and sun-web.xml. These files are located in the
ProjectName-war project under Web Pages > WEB-INF.