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 |
|
The IDs of the dimension values to be used for a navigation
query, or
|
Java:
.NET:
|
Record search |
|
The specifier (string-based ID) of the record to be returned. |
Java:
.NET:
|
Dimension search |
|
The dimension search terms. |
Java:
.NET:
|
Aggregated record search |
|
|
Java:
.NET:
|
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.