Documentation

Search Experiences

Available Liferay DXP 7.4 Update 5+; 7.3 Update 6+

Liferay Enterprise Search (LES) Subscribers

The Liferay Enterprise Search Experiences app includes a suite of features granting fine-grained control over the end user’s search experience. As the search administrator you can use Search Experiences for search customizations varying in complexity:

  • Make minor tweaks to Liferay’s default search page behavior

  • Override the search page behavior completely

  • Configure context-aware search results based on attributes of the search user

Getting Liferay Search Experiences

Liferay Search Experiences is available to Liferay DXP customers with a Liferay Enterprise Search subscription in Liferay DXP 7.3, and bundled with Liferay DXP in Liferay 7.4. Check the LES Compatibility Matrix for details:

Version Availability

Installation Method

Fix Delivery Method

DXP 7.4 Update 5+

Bundled and Activated

DXP Updates

DXP 7.3 Update 6+

Downloaded and Installed (steps below)

App Releases

In Liferay DXP 7.3, Search Experiences is available as an add-on application to LES subscribers:

  1. Download the app from the Customer Portal.

  2. Install the application into Liferay DXP

    • If running a Liferay bundle, copy the LPKG into the [Liferay Home]/deploy folder. If Liferay isn’t running you can copy it directly to [Liferay Home]/osgi/marketplace before starting Liferay.

    • If running a Liferay Docker container, install the LPKG in one of the supported ways.

Search Experiences REST API

The Search Experiences applications publish and consume REST API endpoints (under the path search-experiences-rest) to remain consistent with Liferay’s other native applications.

Warning

It is not advisable for third party code to consume the Search Experiences APIs as they are volatile: this includes the /search endpoint which is only intended to be used by the Blueprints preview feature. Schema changes are expected to happen as the features evolve, and Liferay will not support custom code that uses the Search Experiences APIs. This decision may change in the future as the APIs become more stable.