CoreMedia Search Manual, Version 7.5.45-10
4.2. Configure the Content Feeder | 4.2.1. Required Configuration

Configuring the Content Server URL

The property repository.url has to be set to the IOR URL of the Content Server.

Example

repository.url=http://localhost:44441/coremedia/ior

Configuring the Search Engine Location

The Content Feeder needs the URL of the search engine. Configure the URL of Apache Solr in property feeder.solr.url. The URL has the following format

http://<host>:<port>/<solr-webapp>/<solr-core>

The Solr core is the index used by the Content Feeder. See Section 3.2, “Solr Home Directory” for a description of Solr cores and their configuration in Apache Solr.

Example

feeder.solr.url=http://localhost:8082/solr/studio

If the Apache Solr web application has been secured and needs HTTP Basic authentication, you must also configure the required user name and password in the properties feeder.solr.username and feeder.solr.password.

Configuring the Search Engine Collection

Configure the property feeder.solr.collection with the name of the CoreMedia Search Engine collection. The Content Feeder writes the collection name to the field collection in the Solr index.

Example

feeder.solr.collection=studio

Configuring the user account

The Content Feeder requires a user account to access the documents of the Content Server. During the initialization of the Content Server a dedicated user is created with the name and password feeder. For security reasons, change the password afterwards. The account requires at least read rights on the content to be indexed. A license of the service feeder is consumed by a running Content Feeder.

	Caution
	If you migrated from a release prior to CMS 2005, the Content Feeder fails to start when the CoreMedia Content Server starts, the first time because the user account does not exist. In that case, create the user account manually. Afterwards you can use the administration page to start the Content Feeder.