You must make your existing version 3.5 Verity
collections available for upgrading to K2 collections to complete
the Content Engine data upgrade.
To set the Verity collections permissions:
- Locate the directories that contain the collections and
change the directory permissions to allow access to the following
users:
- The Content Engine operating
system user, which is ce_os_user
- The K2 operating system user, which is k2_os_user
- For each directory that contains version 3.5 content-search
indexes (Verity collections) that you want to upgrade to 4.5.1 index
areas (K2 collections), make the collections readable by Verity by
opening the Verity.cfg file and entering the
following information:
- aliasn
- a path count number that increments for each path you list
- mappingn
- the full path to the collections directory
- dirmoden
- a permission value that you must set to wr (write
and read).
- Open the Verity configuration file in a text editor:
C:\ProgramFiles\filenet\contentengine\verity\k2\common\verity.cfg
- Modify the next available alias settings by entering
the information for each collections directory to be upgrade.
For example, if the next available settings are number 6
and you want to upgrade collections on
myserver,
located in
FileStores\myfilestore\index, you
would change alias6, mapping6, and dirmode6 to the following values:
alias6=path1
mapping6=\\myserver\FileStores\myfilestore\index
dirmode6=wr
To add another directory,
myotherserver\collections\index,
you would modify the settings for number 7 as follows:
alias7=path2
mapping7=\\myotherserver\collections\index
dirmode7=wr
Important: If the upgraded 4.5.1
Content Engine Server is UNIX, be sure
to specify the UNIX mount to the 3.5 content-search indexes, for example:
mapping6=/opt/CE_35_filestore_mount/index