Documentation Center

Search overview

Before you can search, you must create an index.

Contenta and Contenta S1000D use Solr to index data stored as content or property sheet metadata in objects used across one or more Contenta configurations. By default, all objects in all Contenta configurations will be indexed by the Crawler; however, you can restrict indexing to specific Contenta configurations and object types. Whenever users modify object content, object names, object property sheet metadata, and the object hierarchy, the Crawler will export the affected Contenta objects to a Solr collection, where these changes will be indexed.

A Solr instance is a Web App that runs within the Jetty Web Server, which are both installed with a Contenta installation or upgrade. There is a one-to-one relationship between a Contenta database and a Solr collection; therefore, each Contenta database must be configured to use its own Solr collection. One Solr instance can contain multiple collections, and one Crawler can index these same multiple collections. Multiple Crawlers can be run, but each must run on its own computer. If there are multiple Contenta databases that must be indexed, and they reside in multiple Oracle or SQL Server instances, there must be one Crawler running for each instance. Database instances are usually distinguished by different Oracle SIDs or SQL Server identifiers.

Solr is a Java application (32- or 64-bit) that runs as a standalone, full-text search server within a Jetty servlet container. It is scalable and customizable (see Customizing Search) and can use either the HTTP or HTTPS protocol.

Search is comprised of the following services on Windows or daemons on Linux:

  • XyEnterprise Solr Server
  • XyEnterprise Contenta Server
  • XyEnterprise Search Crawler

See Starting and Stopping Search Services for more information on services.

The Solr index facilitates searching for objects containing data that meets the specified search criteria, such as in object content or object property data. Before the Solr index can be searched, it must be populated with Contenta data. The process of indexing Contenta data in Solr starts when all three search services are started, and when AppData and registry settings are properly configured. Therefore, the Crawler and Portal services, in effect, copy the existing data from Contenta objects to the Solr index. The Solr index is continuously kept current whenever users modify object content, object names, object property sheet metadata, and the object hierarchy.

You specify search criteria in Contenta Web or Contenta Explorer. In Contenta Web, you enter search terms, phrases, or saved queries using a GUI that visually aids you in developing search criteria. Also available in Contenta Web is a power search window from which you can enter search criteria complemented with Solr query syntax. Contenta Explorer contains a type-in field (click Tools > Search or click the binocular icon) from which you enter a search term or phrase. Search results are categorized and ranked.

See the following publications for information on conducting search queries:

  • SDL Contenta Web User Guide
  • SDL Contenta Explorer User Guide

Indexing is performed automatically whenever a Contenta object is added, deleted, or modified, and whenever an object management activity takes place, such as renaming, moving or posting (from a project) an object (see Workflow).

Solr supports foreign languages (see Supported Languages), and multiple content formats (see Supported File Formats), both structured and unstructured.

Solr includes support for foreign languages (see Supported Languages), and support for multiple content formats (see Supported File Formats), both structured and unstructured.