If you want maintain a Record Store instance separately from its associated crawl configuration, you can disable automatic management of the Record Store instance by the CAS Server and move a Record Store instance to another host as necessary. This may be useful if storage space for a Record Store instance is a concern and in some migration scenarios.
The
isManaged
property in a crawl configuration determines
whether a Record Store instance is created or deleted at the same time as its
associated data source configuration. The
isManaged
property has a value of
true
by default. This means that:
If you disable the
isManaged
property by setting it to
false
, a Record Store instance is not created when
you create the crawl configuration. You must create the Record Store instance
manually, or configure the crawl to send output to a file. Likewise, any Record
Store instance that you create for a crawl configuration is not deleted when
you delete the crawl configuration.
To disable automatic management of a Record Store instance:
From a command prompt, run the
getCrawl
task of the CAS Server Command-line Utility. Use the-f <arg>
flag to specify the name of the XML file to write the configuration to.For example, you might specify
-f configuration.xml
.In the
configuration.xml
file for the crawl configuration, set theisManaged
property tofalse
as shown in the following example:.... <crawlConfig> .... <outputConfig> <moduleId> <id>Record Store</id> </moduleId> <moduleProperties> <moduleProperty> <key>isManaged</key> <value>false</value> </moduleProperty> </moduleProperties> </outputConfig> .... </crawlConfig> ....
Run the
updateCrawls
task of CAS Server Command-line Utility and pass in the crawl configuration file as input. For example:updateCrawls --f configuration.xml