Building a basic query with the UrlENEQuery class

In order to create an MDEX Engine query based on a client browser request, the request URL must contain MDEX Engine-specific query parameters. While the number of parameters that the UrlENEQuery class can interpret is large, only a few of these parameters are required for the four basic queries.

The parameters that the UrlENEQuery class needs for the four basic queries are listed in this table:

Note

Controller.jsp or Controller.aspx in the examples below refer to the point of entry into the UI reference implementation.

Basic query type

URL param

Parameter definition

URL query string example

Navigation

N

The IDs of the dimension values to be used for a navigation query, or N=0 for the root navigation request.

Java: controller.jsp?N=0 controller.jsp?N=123+456

.NET: controller.aspx?N=0 controller.aspx?N=123+456

Record search

R

The specifier (string-based ID) of the record to be returned.

Java: controller.jsp?R=12345

.NET: controller.aspx?R=12345

Dimension search

D

The dimension search terms.

Java: controller.jsp?D=red+wine

.NET: controller.aspx?D=red+wine

Aggregated record search

A,An ,Au

A: The specifier (string-based ID) of the aggregated Oracle Commerce record to be returned.

An: The navigation descriptors that describe the record set from which the aggregated record is created.

Au: The rollup key used to create the aggregated record.

Java: controller.jsp?A=123&An=456+789&Au=Name

.NET: controller.aspx?A=123& An=456+789&Au=Name

You can combine the four basic queries in one URL, with the restriction that each type of query can appear only once per URL. Each basic query, however, has no impact on the other queries. Combining queries in the URL is used exclusively for performance improvement because it reduces the number of independent queries that are queued up waiting for the MDEX Engine.

Copyright © Legal Notices