•Configure ServerConfig.xml

<Exalead BaseCommandUrlV5="http://servername:10010/search-api/search"  
BasePapiServerUrlV5="http://servername:10002" />

Where servername is your server’s name, this is valid for all other command in this section.

Attention: the root port number after servername: must match the base port number used for the installation. If the service was installed, for example, on base port 20000 the ports to use are 10 and 2 adding 20000, so 20010 and 20002.

Re-import the modified ServerConfig.xml

•Configure appSettings.xml

     <add key="Db.FullTextEngine" value="ExaleadV5" />

•If you are upgrading, backup first your cloudview index config folder (eg:

     E:\Exalead_Cloudview\data\config)

•Launch srv4 configure index command (out parameter must be cloudview index config folder path)

     srv4 configureindex -out e:\ Exalead_cloudview\data\config

The command will update cloudview configuration files reflecting Tark4/GN4 full-text schema configuration

•Test new configuration with cloudview command line executable (in …cloudview\data\bin)

     cvcommand servername:10011 command testConfig

•If no errors are shown, the configuration can be applied

     cvcommand servername:10011 command applyConfig applyPostRestarts=true

This command do not fire any output.

Warning: last command will restart CloudView services.

•If new fields are added, indexes must be scratched

     cvcommand servername:10011 /mami/indexing scratchBuildGroup buildGroup=bg0

Then it will be possible to re-index all objects with srv4 index command using a search condition looking for folderObject, like:

 srv4 index -conditions SearchConditions.xml

Once completed, log in to the admin interface, click home and in the “Build groups” area click “Force indexing”.

See also Reset the CloudView configuration before applying a new configureindex.