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 -o all

get-config

index_config_cmd.bat get-config

Defining Precedence Rule

"precedenceRules" : {

 "ServicesRule" : {

 "targetDimension" : "serviceTypes",

 "triggerDimension" : "Services",

 "isLeafTrigger" : false

 }

when we are defining the Precedence Rule, we are defining that the ServiceTypes Dimension is trigerred only when the Dimension Services got Selected.

Enabling Record Filters and Rollup key in ATG /Endeca 11.1

go to C:\Endeca\Apps\ATGen\config\index_config\index-config.json

"product.repositoryId": {

  "propertyDataType": "ALPHA",

  "mergeAction": "UPDATE",

  "isRollupKey": true, ---> Field for Enabling Rollup key

  "jcr:primaryType": "endeca:property",

  "isRecordFilterable": True --->Field for Enabling the Record Filter.

  }

Once the Following Fields are included and set, then it is enabled for the Current EAC application.