How To Configure Webcenter Content for a Single Node Elasticsearch on Linux
(Doc ID 2696713.1)
Last updated on AUGUST 30, 2023
Applies to:Oracle WebCenter Content - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
Starting with Webcenter Content 184.108.40.206.0, Elasticsearch is now available to be used as the search index.
This KM will cover the steps to install Elasticsearch as a single node on a Linux system and configure the WCC to access it.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document
|Note: The steps have changed then what was previously written in this KM after the WCC Bundle Patch 01-07-2021 or higher have been applied.|
|WCC and Elasticsearch requirements|
|Webcenter Content 220.127.116.11.0 or higher.|
|Note: WCC now supports newer Elasticsearch 7.X versions such as 7.16.2 that addresses the log4j security issue.|
|The elasticsearch-rest-client-7.6.0.jar file|
|The four ways to configure ES for WCC|
|Set the Linux vm.max_map_count to be at least 262144|
|Install and configure Elasticsearch as a single node on the WCC system|
|Place the elasticsearch bundle|
|If not already present, place the rest client jar file in the Elasticsearch Component directory|
|Edit the WCC elasticsearch configuration file|
|Run the WCC elasticsearch configuration script|
|Setting the Elasticsearch data directory outside of the ES home directory|
|Running Elasticsearch on a different system|
|Configure the WCC to access Elasticsearch|
|If this is a newly created WCC and has been started but not yet logged into|
|If this is an existing WCC and is set for DATABASE.METADATA or OracleTextSearch|
|Indexing and Searching on Elasticsearch|
|By doing a collection rebuild in Repository Manager.|
|By migrating the previous index, OracleTextSearch or DATABASE.METADATA to Elasticsearch|
|Support for Elasticsearch|
|Note on creating new or migrating metadata fields|