Migrating HTTP- and File System-based Collections


Thes instructions guide you through migrating a collection built with the Verity Developer's Kit (VDK) V2.x to make it compatible with VDK V4.5 so that it can be updated, managed and searched.

Notes

NOTE: Only collections built with InXight locales can be migrated. Collections built with other locales must be re-created with V4.5 style files and re-indexed with a V4.5 Verity gateway.

This may affect the ordering of results. For example, previously you could have had the following results returned:


Score Title
0.77 Document 1
0.77 Document 2
0.77 Document 3
With the addition of two significant digits, your results might be reordered as follows:


Score Title
0.7704 Document 2
0.7721 Document 3
0.7755 Document 1

Instructions

1. Backup your existing collections.

For example, if your V2.x collections are in /colls, copy them to /backup_colls.

NOTE: If you want to maintain your collection names and locations, make another copy of your collections to a directory such as /working_colls so that you can:

The examples provided in the rest of these instructions will assume you are following this advice.

2. Copy the 2.x collection's style files to a new location.

In this new style directory, you will be adding and editing files. You will then refer to this directory with the -style option of the upgrade command-line tool.

For example, if you had a collection named collv2 located in /working_colls/, you would do the following:

%cp /working_colls/collv2/style/*.* /styles/collv2

NOTE: The example for upgrade in step 5 will use the information given in the example for this step.

3. For HTTP collections, copy into your new style directory the following files from verity/prdname/k2/common/vdkstyle:

If these files already exist, make sure you allow the versions from verity/prdname/k2/common/vdkstyle to over-write the older files.

NOTE: verity/prdname is the user-definable portion of the installation directory that you specified when you installed K2 V4.5.

4. Edit the specified style files as described in the following table. These edits apply to both File System and HTTP collections.

For this style file...
Do this...
style.uni
1. Comment out the following line as shown:
# autorec: "flt_rec"
2. Make sure the following line is not commented out as shown:
autorec: "flt_kv -recognize"
3. Change the following line:
/format-filter="flt_pdf4"
to:
/format-filter="flt_pdf"

style.sfl
Make sure the following line is commented out as shown:
# varwidth: _ParentID ddh

style.lex
Make sure the following line is commented out as shown(if it appears in your style.lex file):
# token: TAB "\t+" # tab

style.*
For any style file (style.*) that contains the following line,
constant: _DBVERSION text "vdk111"
Change the line to appear as follows:
worm: _DBVERSION text

The following table describes the changes you must make only for HTTP collections.

For this style file...
Do this...
style.vgw
1. Comment out the following line as shown:
# $include vgwfsys.vgw
2. Make sure the following line is not commented out as shown:
$include vgwhttp.vgw

style.xfl
1. Comment out the following line as shown:
# $include vgwfsys.gfl
2. Make sure the following line is not commented out as shown:
$include vgwhttp.gfl

5. If your collection was build without locales, run the upgrade command-line tool as shown. The command must be entered as a single, continuous command; it is broken up here due to the margins.

%upgrade -srccoll /working_colls/collv2 -dstcoll /colls/collv2
-style /styles/collv2

NOTES

6. If your collection was built with InXight locales, run upgrade again with the -locale option. The command must be entered as a single, continuous command;it is broken up here due to the margins.

%upgrade -locale localename -srccoll /working_colls/collv2
-dstcoll /colls/collv2 -style /styles/collv2

where localename is one of the InXight locales such as englishx.

NOTE: upgrade detects the locale and character set of the 2.x collection. The locale from the 2.x location is carried over and the collection is convered to the newly appropriate character set.

For more information on locales and their relevant character sets, see

7. If your collection contained an ngram index (style.ngm) or a spanning word list (style.wld), you must rebuild them using the new version of the mkvdk command-line tool. For more information on mkvdk, see the Verity K2 Indexers Guide V4.5.

8. If you are upgrading a collection for use with the K2 Dashboard, you must register and attach the collection with a K2 Server.

For more information, see the Verity K2 Dashboard User's Guide V4.5.





Copyright © 2002, Verity, Inc. All rights reserved.