Solr Configuration

Select the appropriate subsystem.

Type a name for the Solr Configuraiton.

Type a description for Solr Configuration.

When you index data to more than one solr instance, you need to define seperate names for the destination. These are logical names, but refer to Installation properties where you define index- and search URLs to the instances. If you define a new search name, Installation properties will be populated by dummy data.

Select a language if you have a single language environment and the index should only handle that specific language. Set the value to blank if you want to index the values in all languages defined in iKnowBase.

A custom function is used to execute your own built-in function to add / remove content before it is sent to the indexer service. (e.g. You want to create a Solr field for sorting where you select an attribute value if it exists, else you use the document timestamp).
The function is executed after the document data is populated. The signature is defined in the Database funtion-section. To add an extra field for indexing, it must be added to the object type ct_solr_rows like this:

p_solr_data.EXTEND;
    p_solr_data (p_solr_data.COUNT) :=
	ot_solr_row (
		'<a name>',
		'<type>',  -- Value can be VALUE_CHAR/DATE/NUMBER/XML/BLOB
		<char-value>,
		<number-value>,
		<date-value>,
		<xml-value>,
		<blob-value>,
		<mimetype>);

Defines maximum size of a binary file to be indexed. Very large files can be time consuming to index and should be avoided.

Defines where and how the link should be generated when indexed. Default values is retrieved from domain preferences, but can be overridden here.

Defines the seperator used when building path elements from dimensions.

You can choose between two types of attributes:

• Document properties: Values from the document itself. The required attributes are already selected when you create a new configuation.
• Attributes: Regular attributes tagged on the document.

Delete the parameter by clicking the icon. Mandatory attributes are not possible to delete.

Name of the attribute / property.

Document means it’s a document property, Attribute means its a regular attribute on the document.

Display the datatype.

First part of the name used for the attribute in Solr. For attribute values the full name is generated when you select how to store/index/search the value in Solr. Some document properties are locked and will be named by the same value as the prefix.

The full name in Solr for the attribute.

Select (if available) if you want the value to be searchable.

Select (if available) if you want the value to be indexed.

Select (if available) if you want the value to be stored.

Select (if available) if you want to index and store the Ident of the value. The Solr name will be <prefix>__ident.

Select (if available) if you want to index and store the GUID of the value. The Solr name will be <prefix>__guid.

Select (if available) if you want to store the path of the value. The Solr name will be <prefix>__path.

A custom function is used to execute your own built-in function to add / remove content before it is sent to the indexer service.
The signature is defined in the Database funtion-section. This function is called if the attribute exists.

Displays all selected attributes and how many times they are used by documents. This might indicate if the attribute is a useful indexed attribute. The only available operation you can do is to delete the attribute from the configuration.

Displays all attributes not in the configuration and how many times they are used by documents. This might indicate if the attribute is a useful indexed attribute. The only available operation you can do is to add the attribute to the configuration.

Displays all used file formats in iKnowBase. You can decide if files with this format should be indexed or not.

Displays all events using the current configuration. You can easily reindex all documents for all events using the configuration, or delete all documents from solr by checking the boxes and then press the desired button.

The SOLR changelog might have entries originally created by a event or a solr configuration.
If the event definition / solr configuration is deleted or changed, the changelog can ‘come out of sync’. Use cleanup to remove entries without a correct event or solr configuration. The option is only available if such misconfiguration exists.