This procedure describes how to back up CAS configurations from 11.1 before upgrading. CAS configuration includes crawl configurations, Record Store configurations, Web crawler configuration, CAS extensions, and so on.
To back up CAS:
Retrieve and save your crawl configurations by doing the following:
Open a Command Prompt and navigate to
<install path>\CAS\<old version>\binon Windows or<install path>/CAS/<old version>/binon UNIX.Run
cas-cmdand thegetAllCrawlstask. Specify a path to an XML file to store the crawl configurations.The syntax for the
getAllCrawlstask is:cas-cmd getAllCrawls [-f
FileName.xml] [-hHostName] [-pPortNumber]
(You later import this XML file to recreate your crawl configurations.)
If you created unmanaged Record Store instances or if you modified the configuration of a Record Store instance, retrieve and export these Record Store instances including configurations and contents by doing the following:
Open a Command Prompt and navigate to
<install path>\CAS\<old version>\bin on Windowsor<install path>/CAS/<old version>/binon UNIX.For each Record Store instance, run
recordstore-cmdand the get-configuration task. Specify a path to an XML file for the Record Store instance configuration.The syntax for the get-configuration task is:
recordstore-cmd get-configuration -a RecordStoreInstanceName -f ConfigurationFileName.xml [-h HostName] [-n] [-p PortNumber]
To migrate existing 11.1 data to 11.2, run
recordstore-cmdand the read-baseline task for each Record Store instance. Specify a path to an XML file for the Record Store instance contents.The syntax for the read-baseline task is:
recordstore-cmd read-baseline -a RecordStoreInstanceName -f RecordStoreuOtputFileName.xml [-h HostName] [-p PortNumber]
If you have any CAS plug-ins installed in
<install path>/CAS/<old version>/lib/cas-server-plugins, copy the directory containing the plug-in JAR or JARs, to a location outside the CAS installation.Note
Copy only your plug-in directory. You do not need to back up
<install path>/CAS/<old version>/lib/cas-server-plugins/cas.If you have any custom Web Crawler plug-ins installed in
<install path>/CAS/<old version>/lib/web-crawler/plugins, copy the directory containing the JAR andplugin.xml, to a location outside the CAS installation.If you made any changes to
<install path>/CAS/<old version>/bin/cas-service, orcas-service-wrapper.conf, copy the files to a location outside the CAS installation.This is typically necessary if you customized the JVM settings that CAS uses.
Back up the
workspacedirectory or leave it in place for the installation program to back up automatically.The
workspacedirectory contains CAS configuration files and state information such asDocumentConversionFilters.xml, logging configuration files, and so on.
