Creating a New Index or Importing an Existing CES 6 Index Configuration

After installing CES on the Coveo Master server the first time, you need to create a new empty CES 7 index or import the configuration of an existing CES 6 index. The CES installer automatically opens the Administration Tool Create Index page at the end of the first CES 7 installation.

Note: The Administration Tool Create Index page is only accessible at the initial setup or in the extreme case where you start the Administration Tool after deleting or renaming the [Index_Path] folder.

Important: You can import your CES 6 index configuration, but because the CES 7 index has been improved and its format is not compatible with that of CES 6, you will need to rebuild all your sources in CES 7.

To create a new index or import an existing CES 6 index

1. In the Create index page of the Administration Tool that appears at the end of the CES first time installation, under Index Creation, select one of the following two options:

   • Create a new index

     Choose this option when you are installing CES on a new server.

     

     1. Under Index Files Location, in the Index Folder box, click to browse or type the path where you want to store the index files on the server. The default is C:\CES7.

        Important: It is recommended to create the index files on a physical disk other than the one where the operating system resides to maximize CES performances (see Coveo Platform Hardware and Software Requirements).

        Example: You installed a D: drive on the server for the index files. Enter D:\CES7 to create the index on this drive rather than on the OS and programs C: drive.

        Note: The folder entered in this box is referred to as the [Index_Path] in the documentation.

     2. Expand Advanced Options to review and adapt default paths for various CES configuration folders.

     3. Under Advanced Options, enter the full path for each of the specific file types.

        Important: For large index sizes, it is recommended to dedicate a disk or set of disks to the non index files (see Non Index Files).

        It is recommended to use the default file paths but to change the drive letter to match the one of the dedicated disks.

        CES 7.0.7022+ (September 2014) It is recommended to configure the Near Real-Time Indexing Folder and Near Real-Time Indexing Cache Folder on the same dedicated disk (see Near Real-Time Indexing Disk).

        Example: You installed a E: drive on the server for the non index files. In the Log Files Folder box, click to browse or type E:\CES7\Log. Repeat the edit for all other Advanced Options folders.

     4. In the Services Port box, change the default Coveo Search Web Service port (52810) only when this port is used by another process on the server (see Search SOAP API Home).

        Note: The Coveo Search Web Service was introduced with CES 7.0. You can therefore use the default port even when a CES 6 instance is present on the server.

     5. Click Create Index.

   OR

   • Convert an existing CES 6 index configuration

     Choose this option when you are migrating from CES 6 and want to rebuild the index in CES 7 using the sources defined in the configuration of the existing CES 6.

     

     Under Conversion Parameters, perform the following steps:

     1. In the CES 6 Index Folder box, click to browse or type the path of the existing CES 6 index on this server.

        Note: When your CES 6 index configuration is on another server, make a copy of the CES 6 configuration on this server (see Moving the CES Configuration Folder).

     2. In the CES 7 Index Folder box, use the default path (C:\CES7) or click to browse or type a new path name where the new CES 7 index will be created.

        Important: The index performance is better when the index is created on a physical hard disk other than the one where the operating system and the swap files reside (see Coveo Platform Hardware and Software Requirements).

     3. Click Create Index.

   Note: Because the index folder may be different from one implementation to another, it is referred to as the [Index_Path] variable in the documentation.