Configuring Enterprise Search

Some of the framework's functions are built on SAP NetWeaver Enterprise Search. The prerequisite is that the enterprise search has been installed and configured in general. For more information, see http://help.sap.com/nwes and navigate to  SAP NetWeaver Enterprise Search 7.2  Configuration and Deployment Information  Configuration Guide  Configuring SAP NetWeaver Enterprise Search .

Besides, it’s the application’s responsibility to provide the appropriate search model and connectors to be triggered by the framework. In most cases, the existing search models and connectors can be reused. To do that, check if the following requirements are fulfilled.

1. Free-text search is supported.

   Check that free text search is supported by the model and the search makes business sense in the context of the geometry.

   If an attribute included in the free text search is flagged as “contains human readable text“”, then fine-grained text match will be enabled for that attribute.

2. The search result can identify business objects in the application.

   Other required attributes can only be populated when the business object is identified.

3. Ideally, geometry-relevant attributes, especially the filtering attributes, should be included in the search model.

   Depending on the business scenarios, real-time indexing may be necessary to have real time results, like in the following example, Controlling Real-Time Indexing, found at https://help.sap.com/saphelp_nwes73/helpdata/en/4a/2e6f041a161cece10000000a42189b/content.htm.

Different geo objects could have different search connectors or requests. Once the connector is ready, you can add it to your geo object definition.

In transaction SPRO, navigate to the Customizing activity Configure the Framework under  Cross-Application Components  Processes and Tools for Enterprise Applications  SAP Geographical Enablement Framework  and provide the connector ID in the geo object definition.

For more information, see the section on Geo Objects.

The default request is used if it’s not provided. The Maximum Record Count sets an upper limit on how many records will be returned during a search.

It’s good practice to test your search connector and request before applying them in Customizing. For that, ABAP report ESH_TEST_SEARCH can be used to see if your search behaves as expected.

In free text search, it’s generally expected that an exact match is applied. The fuzziness of a search can be controlled in the Set Parameters for Federated Search Customizing activity.

Other than the generic authorization checks like S_ESH_CONN, different enterprise search models could require different authorizations. Those authorizations are model-specific and not provided by the framework. If you aren't sure about the authorizations to use, you can bypass the check in the settings by going to  SAP NetWeaver  Search and Operational Analytics  Enterprise Search  Search Configuration  Set Parameters for Federated Search amd select Do not Check for Model Authorization.