You can download the latest version of Elasticsearch from elastic.co/downloads/elasticsearch.

To run Elasticsearch, open a console, and run the following command:

cd elasticsearch-<version>
./bin/elasticsearch

If you’re running Elasticsearch on Windows, simply run:

bin\elasticsearch.bat

You can easily test if the Elasticsearch engine is reached by trying to access http://localhost:9200/?pretty or by opening a new terminal window and running the following:

curl 'http://localhost:9200/?pretty'

You should then get:

You now have an Elasticsearch node up and running.

You also have the possibility to enable debug mode.

When it is enabled, a toolbox will be displayed on the frontend with the below information:

• Infinite scroll?: have the products been loaded via the infinite scroll?
• Cache?: the module offers a cache for the current page. If the request is cached, the server will not be called and the response will be faster
  Yes = the result comes from the cache.
  No = the result doesn't come from the cache.
  The cache is reset when the page is reloaded.
• Elasticsearch?: it is the contrary of "cache?". Are the results coming from the Elasticsearch server or not?
  Yes = the request has been sent to the Elasticsearch server and the results are coming from Elasticsearch.
  No = the results were cached.
• PHP time: it is the execution time of the PHP code (including requests to the Elasticsearch server).
• Request time: it is the total execution time of the Ajax request to retrieve the products (including "PHP Time").
• Rendering Time: it is the time needed to render the products on the page ("Request Time" not included).
• Total time: it is the time required for the Ajax request and the rendering of the products.
• Enable Template Hints: to display the templates used for rendering the page by the module.
• Show last request data: to show the results of the last query (Elasticsearch or cached). It contains an explanation of why and how some products score higher than others.

Once the extension is enabled, define the URLs settings.

• Enable attribute codes in the generated URLs
  

  If enabled, attribute codes will be added as keys in the generated URLs for the filters.

  enabled: http://www.website.com/men/tops-men/color/blue/size/l-xs.htmldisabled: http://www.website.com/men/tops-men/blue/l-xs.html

   Note that the category, rating, and price filters cannot be interpreted when the option is disabled and that using identical values for distinct attributes may provide inconsistent results.
  
• Attribute Identifier
  Choose the identifier to use in the URLs generated for the filters between Code or Label. 
  Code: https://www.website.com/gear/bags/features_bags/70.htmlLabel: https://www.website.com/gear/bags/features/70.html
  Note that the label must be unique otherwise it can create conflicts
• URL format
  You can define the URL format on Native or Mageworx. 
  
  Native: https://www.website.com/women/tops-women//pattern/checked-solid-striped/style_general/jacket.htmlMageworx: https://www.website.com/women/tops-women/{{PARAMETER}}/pattern:checked-solid-striped/style_general:jacket.html
  When using the Mageworx model, {{PARAMETER}} will be replaced with the value of the Mageworx format: filters parameter field.filters
  
  Contact us if you need another format.
  

Configure the display settings. Advanced Layered Navigation offers you two methods of rendering for the product listing pages: 

• Full Elasticsearch template engine
  When enabled, the product listing will be displayed faster than when using the native Magento template engine. However, it may require some customizations to be fully compatible with your custom theme.
• Magento native template engine
  The Magento native template engine is used to load the listing of the products.
  Rendering is fully compatible with custom themes.

You can first choose to Hide filters with only one value. 

You also have the possibility to refresh the filters according to those that are already selected.

When that option is enabled, you can define how the unavailable filters are displayed: 

• Disabled
  The values with no product matching will be displayed but won't be available for selection.
• Hidden
  The values with no product matching will be hidden.

Finally, you will have to choose the filters options sorting method between:

• Native: The values will be sorted according to the configuration of the attribute.
• Alphabetical: The values will be sorted according to alphabetical order.
• Count: The values will be sorted according to the number of results for each option.

Choose if you want to enable or disable Breadcrumbs.

If Breadcrumbs are enabled, the path of the filters used to get the current product listing will be displayed.

When Breadcrumbs are disabled, each selected filter will be displayed as below:

If Breadcrumbs are disabled, you'll have the possibility to merge selected values for the same attribute. 

If enabled, it displays input boxes below the slider to allow customers to filter products by typing any price value.

The Advanced Layered Navigation extension allows you to add layers in your Category and Search Results pages. You can:

• Enable top layer
• Enable left column layer
• Enable right column layer
  
• The mobile layer is enabled by default:
  
  

For each layer, you can:

1. Add as many attributes as you want by clicking on the + icon.  
2. Use drag and drop to define the order of each filter.
3. Choose the filterable attribute.
4. Define if filters are Closed by default or not.
5. Show results count for each attribute or not.
   
   
6. Show More/Less option for each attribute.
   
   
7. When the Show More/Less option is enabled, you can configure the number of values to display.
8. Filter the options (Input filter: not available for categories, price, reviews, swatch)
   
   
9. Update Browser URL so that the browser URL can be updated according to the selected filters' options.
   For example: In the Fitness equipment category, a user selects the red and blue options of the color filter, the URL will be:
   http://www.yourstore/fitness-equipment/color/red-blue 
   Each filters' option will be combined. For example, if you select Update Browser URL for the color and the size, you could get:
   http://www.yourstore/fitness-equipment/color/red-blue/size/s
   These URLs can allow users to access the page with the filters already selected.
10. Define the attribute on No Index, No follow in order to avoid indexing pages that are not relevant. 
    No Index, No follow is not linked to Update browser URL. If the option is enabled, no link is generated for the filters' options and the search engines won't be able to follow the link with the selected options.
11. Delete the attribute from the filters.

For each layer, you have the possibility to enable floating layers. If enabled, the left/right layers block will scroll with the page content.

You can quickly apply the same layers' configuration to your category by duplicating the configuration from another category. 

This will apply the same configuration to the category you're editing. 

You also have the possibility to apply the current layers' configuration to all sub-categories.

The layers' configuration of the subcategories will be replaced by the layers' configuration of the category you're editing.

Advanced Layered Navigation allows you to configure each category page with specific layered navigation.

For that, go to a category page from: 
CatalogCategories

From the category page, you can go to the Advanced Layered Navigation section. 

You have the possibility to switch the Use Store Config option to No and to enable Top / Left / Right / Mobile layers. 

You can now add the layers you want for that category. 

A log file is created for the frontend requests:
var/log/Wyomind_ElasticsearchCore_Frontend_Requests.log

A log file is created for the reindexation process:
var/log/Wyomind_ElasticsearchCore_Indexation.log

A log file is created for the Elasticsearch client calls:
var/log/Wyomind_ElasticsearchCore_Client.log

A log file is created for the Elasticsearch Server status:
var/log/Wyomind_ElasticsearchCore_Server_Status.log

When the Elasticsearch Server status log is enabled, you can enable and define your own configuration for the backend notification subject and content.

Note that you have the possibility to use variables in the notification content:

• {{store_id}}
  Store ID
• {{code}}
  Store code
• {{name}}
  Store name
• {{server_version}}
  Elasticsearch Server version
• {{servers}}
  Servers

When the Elasticsearch Server status log is enabled, you can enable and define your own configuration for the email notification.

Note that you have the possibility to use variables in the email content: 

• {{store_id}}
  Store ID
• {{message}}
  Returned message
• {{server_status}}
  Elasticsearch Server status
• {{server_version}}
  Elasticsearch Server version

Here will be displayed the version of the Elasticsearch server that you have installed.
6.3.2

The servers must be written as host:port and separated with a comma.
Follow this pattern for full available parameters.
Check that your servers are correctly configured by clicking on TEST servers.

This is only used for https connection. You can set that option to No if you don't have a valid SSL certificate.

Number of seconds after a timeout occurs for every request.
5 seconds

This is used to prefix index names in order to avoid potential collisions. 
demo_m2_

Having more shards enhances the indexing performance and allows to distribute a big index across machines and having more replicas enhances the search performance and improves the cluster availability.

This is where you can define the analysis settings.

Reindex in a temporary index and switch to it once finished. Especially useful for large product catalogs.

In some cases, you might need to reindex indexes automatically as it can take a lot of time. Then you can choose to automatically run indexers via a cron task when they are invalidated.

A notification is displayed in the header of Magento when indexes are invalidated.

If you disable this option, see how to run your indexes manually.

By default, it is set to AND. You may have fewer results with the AND operator but they’ll be more relevant.
"digital camera" is translated to "digital AND camera" or "digital OR camera"

This enables product weight modifier. It is only available for search results.

By enabling this option, when a product (configurable or bundle) is found from the data of a child product, then the parent product images will be used instead of the child product images.

Enable this option to return the products available for purchase before the products not available.

You can enable Category Search so that they can be indexed in Elasticsearch.

If you do, you need to select and configure the category attributes that are searchable.
Description
Name
Page Title
URL Key

You can enable the search among your CMS pages to be indexed in Elasticsearch.

You just need to select and configure the searchable attributes. 
Content, Content Heading, Identifier, Title

You also have the possibility to exclude some pages that may not be relevant from the search results. 
404 Not Found, Enable Cookies, Privacy Policy

When the Product Search is enabled, the products are indexed in Elasticsearch.

You can define the image size in pixels. 
50px

Then, select and configure the attributes that are searchable.
Product Name
SKU
Color
Description
Gender
Manufacturer

Choose the image you want to display when categories and search pages are loading. It can be:

• jpg
• jpeg
• gif
• png
  

Used for the main elements.

Generally used for highlighting search terms in the search results.

Generally used as the products listing background.

Generally used as the secondary entities listing and layers background.

Dark overlay behind the autocomplete popup.

Blurred background behind the autocomplete popup.

Smoothly show/hide the autocomplete popup.

If enabled, you can define the duration of the transition in seconds. 
0.2

There are 3 types of index:

• category
• cms
• products

In the Description column, when clicking on More information, you can see:

• demo_m2_default_category
  It is the name of the index at the Elasticsearch server level under the below format:
  the prefix + the storeview code + the index type
• 36 documents
  It means that 36 categories are indexed.
• 14,77 kB
  It is the size of the index on the disk.
• View Mapping
  When clicking on View Mapping, a popup should open and display the mapping data. 
  

The last time the index has been run will be recorded in the Last Update column. 

The last action state will be recorded in this column. You can also see the number of entities that were indexed by hovering the mouse over the status.

When running an index, a progress bar will display its status and some information about the indexing process.

From the Status column, you can see if the indexes are valid of invalidated. 

From the Action column, you can choose to:

• Flush the index: this will empty, reset the index.
• Run the index: this will fully reindex the entities.
• Run via cron: this will trigger the cron task to run the selected index.

To update the Elasticsearch server version with the right, you can use the below command line:

bin/magento wyomind:elasticsearchcore:update:server:version​

To update the configuration file which is used on the frontend to avoid loading the full Magento Core, you can use the below command line:

bin/magento wyomind:elasticsearchcore:update:config

To reindex your data, you can use the below command line:

bin/magento wyomind:elasticsearchcore:indexer:reindex [options]

Options:

• -s storecode or --store storecode
  The code of the store view for which to re-index data.
  
  Note that this parameter is unique, you can’t add many store codes.

  To reindex all types for the store view which code is “storefr”:

  bin/magento wyomind:elasticsearchcore:indexer:reindex -s storefr

  or

  bin/magento wyomind:elasticsearchcore:indexer:reindex --store storefr

• -i type or --index type
  A space-separated list of index types: cms, category, and product
  
  

  To reindex products only:

  bin/magento wyomind:elasticsearchcore:indexer:reindex -i product

  or

  bin/magento wyomind:elasticsearchcore:indexer:reindex --index product

  You can also reindex your brands when using the Shop by Brand extension. 
• -p ID or --product ID
  The ID of the product to reindex. 
  
  Note that this parameter is unique, you can’t add many products.
  To reindex product with ID 2:
  

  bin/magento wyomind:elasticsearchcore:indexer:reindex -i product -p 2

  or 

  bin/magento wyomind:elasticsearchcore:indexer:reindex --index product --product 2

More examples:

To reindex all index types for all store views and products:

bin/magento wyomind:elasticsearchcore:indexer:reindex

To reindex categories for the store view which code is “storefr”:

bin/magento wyomind:elasticsearchcore:indexer:reindex -s storefr -i category

To reindex categories and CMS pages:

bin/magento wyomind:elasticsearchcore:indexer:reindex -i category cms

When running an index, a progress bar will display its status and some information about the indexing process.

To boost your products in the search results, you can give them a weight. For this, go in:
CatalogProducts

There, edit a product you want to showcase.

In the Wyomind Elasticsearch Core tab, you can define the weight from 1 to 10. 

You have the possibility to ignore products in the indexation process. For this, go in:
CatalogProducts

There, edit a product you want to ignore.

In the Wyomind Elasticsearch Core tab, you can switch the Ignore the product for indexation option to Yes. 

You can create new groups of synonyms from:
MarketingSeo & SearchSearch Synonyms

For example, if you create the list of synonyms:
shoes,footwear

This means that when searching for "orange shoes", the extension will search:
orange shoes
orange footwear

If other synonyms are defined such as:
red,orange,yellow

In that case, the extension will search:
red shoes
red footwear
orange shoes
orange footwear
yellow shoes
yellow footwear

All the corresponding products will then be displayed in the same list.