Search Manual / Version 2406.1
Table Of ContentsThe CoreMedia Search Engine adds full-text search capabilities to the CoreMedia CMS. You can use it to quickly find content of a CoreMedia Content Server, content beans of a CoreMedia CAE and social data such as users and comments of CoreMedia Elastic Social. It is possible to search for text in binary data of many supported formats.
You can search for content in Studio. You can also integrate search functionality into your website and custom applications.
The CoreMedia Search Engine is based on Apache Solr and comes with some CoreMedia specific extensions for content processing. It maintains indices and provides full-text search capabilities. Chapter 3, Search Engine describes the Search Engine in more detail.
The CoreMedia CMS is delivered with different Feeder applications, which send data to the Search Engine.
The Content Feeder sends content to the Search Engine for indexing. This makes it possible to search for content in the Studio and custom content applications.
Chapter 4, Searching for Content describes concepts, configuration and operation of the required components in detail.
Content applications often require search functionality not only for content items but for content beans of a CoreMedia CAE. The CoreMedia CAE Feeder makes content beans searchable by sending their data to the Search Engine.
Chapter 5, Searching for CAE Content Beans describes concepts, configuration, operation and developing for the CAE Feeder in detail.
Elastic Social worker applications send social data such as created comments and users to the Search Engine. Worker applications are Elastic Social applications configured with property
taskqueues.worker-node=true.The Elastic Social Plugin for CoreMedia Studio allows searching for comments and users.
See the Elastic Social Manual for more information.
A Search Engine index contains index documents. Each of these index documents carries a unique String identifier and multiple fields with values. Applications can search for index documents that match a given query, for example index documents that contain a specific word in one field. Index document fields and field types can be configured in the index schema as required by the application.
When using the Content Feeder, an index document represents a CoreMedia content. When using the CAE Feeder, an index document represents a content bean. With Elastic Social, an index document represents a comment or a user.
Multiple Content Feeder applications, CAE Feeder applications and Elastic Social tenants can use the same Search Engine but require separate indices. An index is a group of index documents for a specific application and with similar structure. Search requests use a specific index to retrieve results for the specific application. Each index can use different fields for its index documents as configured in the index schema.
