Unnecessary Supplemental Objects Returned For Some Cartridges in Either ATG Assembler or Endeca Assembler (Doc ID 1610952.1)

Last updated on JANUARY 05, 2017

Applies to:

Oracle Commerce Platform - Version 10.1.1 and later
Oracle Commerce Guided Search / Oracle Commerce Experience Manager - Version 3.1.0 to 3.1.2 [Release 3.x]
Information in this document applies to any platform.

Goal

The Assembler used in an Endeca stand-alone instance or an ATG-integrated instance can request too many supplemental objects to be returned by the MDEX, which can cause large query response sizes and performance issues in the front-end web application.  

Endeca Assembler (part of Oracle Commerce Platform or ATG) makes the following types of queries to MDEX(dgraph) when a shopper is browsing a web page:

1. "Content" query:
This type of query is used to determine what content-items should be shown to the shopper based on their current navigation state.
This is always the first query, and should be made just *once* per page.

2. "Records" query:
These types of queries are used to determine what records should be displayed to the shopper.
Here the term records includes record shown in both record spotlights and result list.
This query usually follows the "content" query.
Assembler tries to optimize the number of records queries, but there can be more than one of these for each page.

Note: This article is specially related to "Records" query and not with "Content" query. 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms