Upgrading to Sun Master Index

Step 1: Create the Service-Enabled Master Index

The first step to migrating a master index project is to create a service-enabled master index project. This project should be similar to the project being upgraded, but does not need to be identical because you will copy over the configuration of the project you are upgrading before you generate the new master index application.

ProcedureTo Create the Service-Enabled Master Index

  1. If you are migrating from version 5.1.3 or earlier, export the master index client and server projects from your 5.1.3 Repository and import them into your Java CAPS 6 Repository.

    This is described in Upgrading to Java CAPS 6. You can export and import the Environments along with the projects.

  2. If you are upgrading from a version earlier than 5.1.3, update the master index project as required for the version from which you are upgrading.

    These updates are described in the Sun SeeBeyond eView Studio Upgrade Guide, Release 5.1.3, available at http://docs.sun.com/app/docs/doc/820-0965.

  3. Create a new, service-enabled master index application using the wizard, as described in Creating a Master Index Application in Developing Sun Master Indexes .


    Tip –

    Follow these guidelines when creating the new master index application:

    • The application name and parent object name need to be the same for the new service-enabled master index as for the Repository–based master index. They also need to be the same as each other.

    • You can accept the defaults for the deployment environment in the wizard since these values will be populated when you update the configuration files.

    • To make it simpler, you can create the object structure using one of the predefined templates.

    • For the final step of the wizard, you do not need to generate all remaining files.


  4. After you create the master index application, make backup copies of the configuration files. They are located in NetBeansProjects/ProjectName/src/Configuration.