Product DocsMenu

Coveo Platform 7.0 >
Administrator Help > Coveo Enterprise Search 7.0 > Installation > Migration > Coveo Platform 6 to 7 Migration Overview

Coveo Platform 6 to 7 Migration Overview

The Coveo Platform 7.0 comes with numerous new features (see What's New - Coveo Platform 7 Introduction). With the software installers and import tools of the Coveo Platform 7, you can smoothly migrate your index and .NET search interface configurations.

The format of the CES 7.0 index changed to reduce its footprint, improve performances, and implement several key new features. The index format change implies that you must re-index all your sources with the new CES 7.0 instance.

Important: The side-by-side installation of Coveo Platform 6.x and 7.0 instances on the same server (or set of servers like Master and Mirror servers) is not supported.

When your Coveo Platform 6.x implementation includes customized components developed by Coveo Professional Services or by your own personnel, before starting the migration process, contact the Coveo Support or the Coveo Professional Services to determine how to migrate the customized components.

To migrate a Coveo Platform implementation from version 6.x to 7.0

  1. Revise your current Coveo server topology (see Coveo Scalability Model, Planning Repositories to Index, and Planning .NET Search Hubs and Search Interfaces).

  2. Provision a new set of servers that fulfill the hardware requirements for your selected server topology or ensure that your current Coveo servers have sufficient free resources to run both versions concurrently (see Coveo Platform Hardware and Software Requirements).

    Example: You can use new servers for back-end components and consider sharing the front-end servers as the query rate typically transfers from the original instance to the new one.

  3. Install CES on your Master server (see Installing CES on the Master Server).

  4. Import your Coveo Platform 6.x configuration (see Creating a New Index or Importing an Existing CES 6 Index Configuration).

    This step is important to smoothly import the configuration for all your collections, sources, connectors, user identities, and many other aspects that you configured from the Administration Tool and the Interface Editor so that you do not have to reconfigure everything manually.

  5. With CES 7, all sources must use a security provider. When starting the first time, CES 7 automatically revises the imported configuration and creates security providers as needed for all sources.

    When your implementation includes one or more SharePoint sources, for this type of repository, you however need to manually add the crawling user identity to the SharePoint security provider (see Creating a Security Provider for the SharePoint Legacy Connector).

  6. For a topology with multiple back-end servers:

    1. When your topology includes one or more Mirror servers, install the Coveo Mirror components (see Installing CES Mirror Components).

      Note: By default, the remote converter components are installed on a Mirror server.

    2. When your topology includes one or more Remote Converter servers, install the Coveo Remote Converter components (see Installing CES Remote Converter Components).

    3. When two or more Master/Mirror servers are available, consider setting them up in a network load-balancing configuration (see Configuring Coveo Servers in a Network Load-Balancing Cluster).

  7. Install the Front-End components:

    Note: Starting with the Coveo Platform 7, the front-end components (Coveo .NET Front-End 12) are distributed, installed and versioned separately from the back-end components (Coveo Enterprise Search 7).

    1. Install the Coveo .Net Front-End 12 components on all Front-End servers of your selected topology. In the case of a one server topology, simply run the installer on the Master server (see Installing Coveo .NET Front-End).

    2. Import the CES 6.5 .NET search interface settings.

      In step 4, the customized .NET search interface settings were imported from the CES 6.x index configuration file ([Index_Path]\config\congfig.txt) to the same file for the CES 7 instance. With the Coveo .Net Front-End 12 however, the customized .NET search interface settings are no longer stored in the index configuration file but rather in XML files located in the [.Net_Front-End_Path]\Web\Coveo\Skins folder. You can easily perform this configuration transfer from the Interface Editor (see Importing CES 6.x .NET Search Interface Settings).

    3. In the case of multiple Front-End servers, use the Interface Editor deployment tool to replicate the .NET search interface configurations to all servers (see Deploying Search Interface Settings).

      Note: With the Coveo Platform 6.x, the .NET search interface settings were stored centrally in the index configuration file. Changes were automatically applied to all Coveo Front-End servers but this scheme did not allow to easily set up a staging Front-End server.
      With the Coveo .NET Front-End 12, the search interface settings are rather saved in XML files on each Coveo Front-End server, allowing you to develop and test settings on one server, and then easily replicate them to one or more production Front-End servers.

    4. When your topology includes two or more Front-End servers, consider setting them up in a network load-balancing configuration (see Configuring Coveo Servers in a Network Load-Balancing Cluster).

    5. Update the Coveo integration with repositories:

    6. When you were using the Usage Analytics module with CES 6.x, run the appropriate Usage Analytics database migration scripts (see Updating the Usage Analytics Database Format).

    7. You can take advantage of the URL shortener optional new feature (see Deploying the .NET Search Interface URL Shortener Database).

People who viewed this topic also viewed