Migrate from a Contenta 4.2 or earlier Server on Windows to Linux by migrating all of your customized adapter files, custom tools and custom triggers.
Procedure
- Use the delivered Contenta installation and upgrade documents to install Contenta on your systems, including the Linux 5.6 Contenta Server.
- Copy and save (back up) the delivered encaps/ subdirectory of your Contenta home directory installed on the new 5.6 server.
- If your Contenta Server contains customized adapter files that need to be migrated to Linux, migrate them. To find and identify these files, do the following:
- Look for customized filenames. Typically, the names of such files will include your company's initials, name or identifier. For example, if your company is called Acme, you would see files such as CustomGetDocCatAcme.pm. These customized files may be in the same directory with the delivered files, in Contenta_home/encaps/adapters/custom, but may be isolated in a separate directory—for example /work/apps/adaptersAcme/custom. Specifically, you are looking for customized versions of one or more of the following files:
- CustomGetDocCat.pm
- CustomGetDocCatClassic.pm
- CustomGetDocCatTweak.pm
- CustomGetDocCatView.pm
- CustomGetDocCatViewClassic.pm
- CustomGetDocDefClassic.pm
- CustomGetDocDefault.pm
- CustomGetDocFetch.pm
- CustomGetDocFetchDefault.pm
Important: Do not modify or migrate any of the above delivered files.
- Check for such customized files in the encaps/adapters/custom subdirectory of your Contenta home directory. or, failing that, in a separate directory, for example, /work/apps/adaptersAcme/custom.
- If your Contenta Server contains custom tools and triggers (that is, files) under the encaps/ subdirectory of your Contenta home directory, migrate those files also. To find such files, check for files in your encaps/ directory that are not present in the corresponding Linux Server location.