Installing Upgrading Designing Configuring Deploying Monitoring Administering Troubleshooting Reference JBI Components
Close Print View
Upgrading: Step 5: Update the Master Controller
 

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 5: Update the Master Controller

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.

To Update master.xml
  1. In the service-enabled project, delete the text of master.xml.
  2. Copy and paste the text of the Threshold file from the Repository-based master index application to master.xml in the service-enabled application.
  3. In the Configuration element near the top of the file, change "sbyn:SeeBeyond/eView/schema/master.xsd" to "schema/master.xsd".
  4. Change all instances of "com.stc.eindex" to "com.sun.mdm.index".
  5. After the 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.

  6. Save and close the file.