Step 2: Migrate any Custom Plug-ins

If any custom plug-ins were created for the project you are upgrading, you need to migrate those Java classes to the service-enabled project. You create the new custom plug-in files manually in the ProjectName-ejb project, and then copy the text of the existing custom plug-ins into the new files. Minor text changes are also required.

To Migrate Custom Plug-ins

1. For each Java package used for the custom plug-ins in the master index project you are migrating, do the following:
   1. In the Projects window, expand the ProjectName-ejb project associated with the new service-enabled master index project.
   2. In the ProjectName-ejb project, right-click Source Packages, point to New, and then select Java Packages.
   3. On the New Java Package Wizard, enter the name of the Java package for the custom plug-in.

      Note - In Repository-based master index projects, Java package names begin with “com.stc.eindex”. In the service-enabled projects, they begin with “com.sun.mdm.index”. You should update the custom plug-in package names accordingly.

   4. Click Finish.
2. For each custom plug-in to be migrated, do the following:
   1. Under Source Packages, right-click the Java package to which the custom plug-in belongs.
   2. Point to New and then click Java Class.
   3. On the New Java Class Wizard, enter the name of the Java class for the custom plug-in.
   4. Click Finish.
   5. Delete the default text in the new file.
   6. Copy the text of the corresponding custom plug-in from the Repository-based project to the new file.
   7. In the new file, update the package name for the new custom plug-in.
   8. In the new file, update any package names by replacing all instances of “com.stc.eindex” with “com.sun.mdm.index”.

   Note - When you first create the custom plug-ins, there will be several context errors. They should be resolved once you generate and build the master index application later in the migration process.