Configuring a record store merger

You configure a record store merger by referencing the merger and all other CAS components in the file config/cas/last-mile-crawl.xml. The following table lists and describes the properties of last-mile-crawl.xml that you must specify for your particular application; you can accept the default for properties not listed.

Property

Description

Example

dataRecordStores

The name or names of the product data record stores. Each name must be configured in the custom script that creates your product data record store(s).

Discover-data

dimensionValueRecordStores

The name or names of the dimension value record stores. Each name must be configured in the custom script that creates your product data record store(s).

For information about how to specify the names of record stores, see Creating record stores using a custom script .

Discover-dimvals

inputDirectory

The directory in which MDEX configuration files must be stored. These files include search config and a few others (search chars, stemming, languages).

C:/Endeca/apps/Discover/config/mdex

outputDirectory

The directory to which the record store merger writes Endeca records and configuration data for use by dgidx. The name of this directory must be specified in the /config/script/DataIngest.xml file.

C:/Endeca/apps/Discover/data/cas_output

dimensionValueIdManagerInstanceName

The name of the dimension value ID manager used by this application. Note that an application can use only one dimension value ID manager.

For information about how to configure this name, see Creating record stores using a custom script .

Discover-dimension-value-id-manager

configRepositoryHost

The name of the server on which the ECR is hosted.

KPMLG0208

configRepositoryPort

The name of the port through which the ECR communicates.

8006

configRepositorySite

Used to access configuration data from the ECR, which is stored per EAC application.

Discover

jpsConfigPath

Used to locate the credential stores (Oracle Wallet) for pulling the admin password to connect to pull config

The path to the Oracle Wallet configuration file, jps-config.xml. For more information, refer to the Oracle Commerce Guided Search Security Guide.

C:\Endeca\ToolsAndFrameworks\11.3.0\server\workspace\credential_store\jps-config.xml

useSsl

Set to true or false to enable the use of Secure Sockets Layer for communication. For more information, refer to the Oracle Commerce Workbench User's Guide and the Oracle Commerce Guided Search Security Guide

false

For example, the following excerpt from last-mile-crawl.xml references two record stores, Discover-data and Discover-dimvals: 

<sourceConfig>
  <moduleId>
    <id>com.endeca.cas.source.RecordStoreMerger</id>
  </moduleId>
  <moduleProperties>
    <moduleProperty>
      <key>dataRecordStores</key>
      <value>Discover-data</value>
    </moduleProperty>
    <moduleProperty>
      <key>dimensionValueRecordStores</key>
      <value>Discover-dimvals</value>
    </moduleProperty>
  </moduleProperties>
  ...
</sourceConfig>

You can create additional record stores using the CAS component-manager-cmd.[bat|sh] create-component task. You can update the configuration for these record stores using the CAS recordstore-cmd.sh set-configuration task. For information about these tasks, refer to the Oracle Commerce Content Acquisition System Developer's Guide.

Copyright © Legal Notices