Indexing object text in dual mode

Overview

Dual mode indexing transitions from Content Search Services to Elasticsearch by indexing content to both search engines simultaneously. Configuration involves setting up index areas for both engines and can ensure that newly ingested content is searchable in both engines during the migration period.

Use the Administration Console for Content Platform Engine to configure dual mode indexing at the domain and object store levels. After initial configuration, both Content Search Services and Elasticsearch automatically index new and modified documents in CBR-enabled classes.

Key configuration areas

Configuring dual mode indexing involves these main areas:

Content Search Services index areas

Content Search Services index areas must already be created and configured for the object store before you enable dual mode. These index areas continue to function during the migration period, ensuring uninterrupted search capabilities.

Elasticsearch cluster

An Elasticsearch or OpenSearch cluster must be added to the Content Platform Engine domain before you can create Elasticsearch index areas. The cluster connection defines how Content Platform Engine communicates with Elasticsearch, including connection endpoints, authentication, and SSL settings.

Elasticsearch index areas

Adding an Elasticsearch index area to an object store that already has Content Search Services index areas automatically enables dual mode indexing. The index area contains configuration settings for shards, replicas, and the maximum results window.

CBR-enabled classes

Content-based retrieval (CBR) must be enabled for each document class that you want to index. Classes that are already CBR-enabled for Content Search Services automatically participate in dual mode indexing. Only documents in CBR-enabled classes are added to both full-text indexes.

Language analyzers

Select one or more language analyzers for the Elasticsearch index area. Language analyzer selection affects how text is analyzed and indexed in Elasticsearch, improving search accuracy and relevance.

Indexing queue sweep

The Elasticsearch Indexing Queue Sweep processes documents and adds them to the Elasticsearch index. The sweep runs on a schedule and processes documents in batches. Configure the sweep schedule, batch size, and other parameters to optimize indexing performance for your workload.

Content migration

Content that existed before you enabled dual mode is not automatically migrated to Elasticsearch. Use a full text reindex job sweep to efficiently migrate large volumes of existing content to Elasticsearch while dual mode is active.

Configuration workflow

Follow this general workflow when you configure dual mode indexing:

1. Verify that Content Search Services index areas are created and configured for the object store
2. Add an Elasticsearch cluster to the Content Platform Engine domain
3. Configure Content Platform Engine to access the cluster (connection settings, authentication, SSL)
4. Create an Elasticsearch index area for the object store
5. Select one or more language analyzers for the Elasticsearch index area
6. Verify that CBR-enabled classes are configured correctly
7. Configure the Elasticsearch Indexing Queue Sweep schedule and parameters
8. Enable the sweep to process documents
9. Monitor indexing status to verify that the dual mode is working correctly
10. Use a full text reindex job sweep to migrate existing content to Elasticsearch

The topics in this section provide detailed procedures for each configuration area.

Transition considerations

After you verify that all content is indexed in Elasticsearch and that search functionality meets your requirements, you can plan to decommission Content Search Services and transition to Elasticsearch-only indexing. During the transition period, dual mode indexing validates Elasticsearch functionality without disrupting Content Search Services search capabilities.