Importing Endeca CAS Data
Some Times in our Local Machine/SIT Machine where less infrastructure is maintained, Indexing takes lot of time, when it fails in the Middle Due to the Network issue or Endeca...
Showing posts with label CAS. Show all posts
Showing posts with label CAS. Show all posts
Thursday, 8 September 2016
About index_config_cmd.bat
During baseline update processing, the Content Acquisition System merges and processes index configuration from all owners into a consolidated set of MDEX-compatible output files. If multiple import owners modify the same attribute, the configuration from the system owner always overrides other import owners during the merge process. Setting up Index-config Make sure your file C:\Endeca\Apps\ATGen\config\index_config/index-config.json has no Parsing Errors Then Execute the Below Command Windows Set-config C:\Endeca\Apps\ATGen\control> and Execute index_config_cmd.bat set-config -f C:\Endeca\Apps\ATGen\config\index_config\index-config.json...
Tuesday, 22 December 2015
Basics of EAC Application
About Record Store and Record Generations A set of records that has been committed to a Record Store instance is a record generation. For example, if you perform a full file system crawl, all the records returned from the crawl are written to the Record Store and a commit is done. After the commit is done, the Record Store has one generation of records. A subsequent crawl, either full or incremental, results in a second generation of records. Each record that is read in contains a unique ID. CAS uses that unique ID as the value of the idPropertyName Record Store configuration property. If a record already exists with that unique ID during later CAS crawls, then the later version replaces the earlier one. This ensures that when you run an incremental crawl, you always get the latest version of any given record. A record generation is removed from a Record Store instance by the clean task after the generation becomes stale. A stale generation is a generation that has been in a Record Store instance for a period of time that exceeds the value of the generationRetentionTime Record Store configuration property. Command for creating the RecordStore C:\Endeca\CAS\11.1.0\bin\cas-cmd.bat createDimensionValueIdManager -h localhost -p 8500 -m ATGen-dimension-value-id-manager with the CAS we can do the following tasks C:\Endeca\CAS\<version>\bin>cas-cmd.bat --help usage: cas-cmd <task-name> [options] [Inspecting Installed Modules] getAllModuleSpecs getModuleSpec listModules [Managing Crawls] createCrawls deleteCrawl getAllCrawls getCrawl getCrawlIncrementalSupport listCrawls...
