Implementing search interfaces

You implement search interfaces with Integrator ETL.

In Integrator ETL, you can use the WebClient component to send a request to Endeca Server using the Configuration Web Service. This request sends the RECSEARCH_CONFIG document to Endeca Server, thus creating a search interface. For information on how to configure a search interface using Integrator ETL, see the Oracle Endeca Information Discovery Integrator ETL User's Guide.

If you are not using Integrator ETL, you can create a request with the putConfigDocuments operation of the Configuration Web Service and send the RECSEARCH_CONFIG XML document to Endeca Server. For information, see Configuration Web Service operations.

Before implementing search interfaces, make sure that all the attributes that are going to be included in a search interface have already been enabled for record search. In addition, if the search interface will include a relevance ranking strategy, make sure that the relevance ranking strategy has been configured.

If you are implementing wildcard search in a search interface, search interfaces can contain a mixture of wildcard-enabled and non-wildcard-enabled members (although only the former will return wildcard-expanded results).

You implement a search interface via the RECSEARCH_CONFIG XML configuration document. The resulting search interface should look similar to this example of a search interface named AllFields that uses a relevance ranking strategy named All:

<RECSEARCH_CONFIG>
  <SEARCH_INTERFACE CROSS_FIELD_BOUNDARY="NEVER" 
      CROSS_FIELD_RELEVANCE_RANK="0" 
      DEFAULT_RELRANK_STRATEGY="All" NAME="AllFields">
    <MEMBER_NAME RELEVANCE_RANK="4">ProductType</MEMBER_NAME>
    <MEMBER_NAME RELEVANCE_RANK="3">ProductName</MEMBER_NAME>
    <MEMBER_NAME RELEVANCE_RANK="2">SalesRegion</MEMBER_NAME>
    <MEMBER_NAME RELEVANCE_RANK="1">Description</MEMBER_NAME>
  </SEARCH_INTERFACE>
</RECSEARCH_CONFIG>