ex) http://165.xxx.yyy.zzz:17000/graph?node=0&format=xml&group=1
아래는 각각의 파라미터가 무엇을 의미하는지 알 수 있는 표다.
Administrator's Guide > The MDEX Engine Request Log
URL parameter mapping
This section provides a mapping between the URL that is sent from the application to the Endeca Presentation API, and the URL that is sent from the API to the MDEX Engine. As described in the Endeca Developer's Guide, there is not a one-to-one correlation between these two URLs. The Presentation API transforms the URL it receives from the application into a MDEX Engine-specific URL before sending it to the engine.
You can use the information in the remainder of this section to translate the MDEX Engine request log file, which tells you exactly which URLs the MDEX Engine has processed. By extension, these are the URLs that the Presentation API has sent to the MDEX Engine. If the API has sent an incorrect URL to the MDEX Engine, it is a good indication that the API received an incorrect URL from the Web application in the first place.
Use the table below to map the parameters as follows: The left column is the mapping between the Presentation API and the ENE parameter. The far right column is the mapping between the Web application and the Presentation API parameter.
Note: For a complete description of the ENE URL query parameters, see the Endeca Developer's Guide.
Example mappings
Here are some sample mappings.
Web Application to API API to MDEX Engine/controller.jsp?N=0
/graph?node=0
/controller.jsp?N=0&Ntk=DESC&
Ntt=merlot/graph?node=0+attrs=DESC+merlot
Mapping parameters
The ENE parameters in bold are the primary parameters, while those in non-bold are secondary parameters.
© 2007 Endeca Technologies, Inc.
Endeca confidential
Endeca Web Site
Feedback
'Dev > endeca' 카테고리의 다른 글
HttpServletRequest 메소드 정리 (0) | 2009.02.13 |
---|---|
jspref에서 merchandising rule 보이게 하기 (310) | 2009.02.10 |
obtain lock (0) | 2008.12.17 |
dimension url 가져오기 (0) | 2008.12.16 |
property,dimension 관련파일 (0) | 2008.12.14 |