3 Replies Latest reply: Dec 20, 2012 6:55 AM by Gopinath Ramasamy RSS

    Endeca and price integration

    972185
      Hi all

      We are trying to integrate Endeca with ATG10.1.1 and I have next question:

      How can we configure indexing process, to generate dimension and dimension values from price list?
      The result what I want to achieve is to get something like:

      Price Range:
      +$5 to $10 (6)+
      +$10 to $20 (50)+
      +...+

      at endeca_jspref application.

      Thanks

      Edited by: 969182 on 19/12/2012 8:05
        • 1. Re: Endeca and price integration
          Gopinath Ramasamy
          Hi,

          Please check if the below documentation is helpful to you.

          http://docs.oracle.com/cd/E35318_02/Platform.10-1-1/ATGEndecaIntegrationGuide/html/s0502pricelistmappropertyaccessor01.html

          Thanks,
          Gopinath Ramasamy
          • 2. Re: Endeca and price integration
            972185
            Hi

            I'm familiar with ATG Endeca Integration Guide but there is no answer for my question.
            There mentioned how to generate record properties, but in general for all projects we need to generate dimension and dimension values, to be able to navigate through price ranges.

            Thanks,
            Vitalii
            • 3. Re: Endeca and price integration
              Gopinath Ramasamy
              Hi,

              In the dimensions.xml that is used by your pipeline, specify a dimension for the sale price of your product. Sample is as given below.

              <DIMENSION NAME="SalePrice" SRC_TYPE="INTERNAL">
              <DIMENSION_ID ID="1"/>
              <DIMENSION_NODE>
              <DVAL TYPE="EXACT">
              <DVAL_ID ID="1"/>
              <SYN CLASSIFY="FALSE" DISPLAY="TRUE" SEARCH="FALSE">SalePrice</SYN>
              </DVAL>
              <DIMENSION_NODE>
              <DVAL TYPE="RANGE">
              <DVAL_ID ID="3"/>
              <SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">$5 - $10</SYN>
              <LBOUND>
              <BOUND CLOSURE="CLOSED" TYPE="FLOAT" VALUE="5.00"/>
              </LBOUND>
              <UBOUND>
              <BOUND CLOSURE="CLOSED" TYPE="FLOAT" VALUE="10.00"/>
              </UBOUND>
              </DVAL>
              </DIMENSION_NODE>

              <DIMENSION_NODE>
              <DVAL TYPE="RANGE">
              <DVAL_ID ID="4"/>
              <SYN CLASSIFY="TRUE" DISPLAY="TRUE" SEARCH="TRUE">$10 - $20</SYN>
              <LBOUND>
              <BOUND CLOSURE="CLOSED" TYPE="FLOAT" VALUE="10.00"/>
              </LBOUND>
              <UBOUND>
              <BOUND CLOSURE="CLOSED" TYPE="FLOAT" VALUE="20.00"/>
              </UBOUND>
              </DVAL>
              </DIMENSION_NODE>
              </DIMENSION_NODE>
              </DIMENSION>


              For more details on dimensions.xml, endeca pipelines and the attributes used in this xml, please refer to the Endeca documentations.

              Hope this helps.

              Thanks,
              Gopinath Ramasamy