Universal Search Connector

Here you can find an overview of the universal search connector in Emporix, along with its features and benefits.

Looking for tutorials? Check out the Search Configuration.

Purpose

With the Emporix universal search connector, it is possible to gather all events happening in the system and set up automated actions that will ensue in relation to those events. Every time an object is created, updated, or deleted, the events are being indexed and sent to the Webhook Service. The webhook events are further sent out to the Svix application, which in turn updates the search engine database of your choice. The actions, as configured in Svix, can be executed in various third-party applications, as the solution is universal and widely applicable.

Features

FeatureDescription
Universal search engine integration solutionThis feature is designed to be universal in order to fit your business' needs. You can use various search engines, such as Algolia, clerk.io, constructor.io, and others.
Product-related eventsAll product-related events, such as price updates, product deletions, and others, trigger the indexing service that sends events to Svix.
Management Dashboard navigationThe configuration and management of the indexing feature is handled through the Emporix Management Dashboard.
Webhooks integrationThanks to the integration with the Webhook Service, the product-related events are automatically sent out to other integrated third party applications.
Event GatewayIn the Svix application, the event gateway serves as an intermediary between Emporix services and search engines.

Overview

The indexing process consists of the following sequence of events:

  1. When a product-related event takes place, it is processed by CE.
  2. The event is consumed by a messaging system and undergoes indexing.
  3. An indexing message is sent to the Webhook Service.

The indexing messages are sent in an asynchronous way. The indexing service searches for changes every two minutes to gather all related events and send them in one collective message, for example when you update the price, availability, and delivery methods of a particular product. This may result in a delay in message delivery.

  1. The Webhook Service forwards the message to the Svix Event Gateway.
  2. The Event Gateway passes the event to your pre-configured endpoint for this particular event, and updates the search engine database of your choice.

For example, if a price is updated in the Emporix environment, an indexed message is sent to the Webhook Service. In Management Dashboard, if you enabled actions for index item updates and/or deletions, the events are passed further to the Svix Event Gateway. If an endpoint for the update/delete actions was configured in Svix, all relevant actions are executed in the third-party search engines that your system is integrated with.