| Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components | |
| Close Print View | |
| Upgrading: Step 5: Update the Master Controller |
|
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 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
The Threshold file is upgraded by copying the text of the file
to the service-enabled project and then updating certain portions of the file. There are
only minor differences between the Threshold file in the Repository-based project and master.xml
in the service-enabled project. In addition to updating the package name and XSD
location, you can also update the file to take advantage of the new
distributed transaction capabilities in Sun Master Index.
master.xml.master.xml in the service-enabled application.Configuration element near the top of the file, change "sbyn:SeeBeyond/eView/schema/master.xsd" to
"schema/master.xsd". execute-match element, add a new element named transaction. Set the value
of this element to LOCAL, CONTAINER, or BEAN.
LOCAL means transactions are not distributed. Using this option gives you the same behavior as in previous versions.
CONTAINER means transaction are distributed across applications.
BEAN means transaction are distributed within the master index application.