Configuring Search
These topics describe configuring Contenta search functionality.
- Search overview
Before you can search, you must create an index. - Search workflow
Immediately after you install or upgrade Contenta and configure AppData, all object data in the database is indexed in Solr (if this is a new install there will not be any Contenta objects to index). - Content and Property Sheet Data in XML
We have included limited XML indexing and search capabilities in the installed collection named Contenta_home\tools\solr\example\solr\collectionSDL_Contenta_Sample. - Configuration Settings
There are certain AppData settings and registry settings used by the Crawler and Contenta to export the correct Contenta objects, and index them in the correct Solr collection. - Foreign language support
During indexing, Apache Tika attempts to determine the language of each Contenta object’s content when the language is not specified in an object’s property sheet Language ISO Code or the AppData value, LANGUAGE_CODE. - Stop Words list
Stop words are words are words to be ignored in content during search. A set of stop word files is installed with Solr in thecollectionSDL_Contenta_Sample/conf/langdirectory. Stop words are supported in many foreign languages. - Supported File Formats
Textual content will be extracted from non-structured files using Apache Tika. - Customizing Search
Your Contenta custom property data fields will automatically be indexed to Solr. - Starting and stopping search services
As an Administrator you may have to stop, and then restart search when there is a systemwide failure or when software updates need to be installed. - Activity and error monitoring
Activity monitoring, including error logging is controlled by settingCONTENTA CRAWLER/CRAWLER_DEBUG_LEVELto one of the values below. The default iswarn. - Adding a Solr Collection
If you do not want to use the default collection name,"collectionSDL_Contenta_Sample",you will need to add a new Solr collection. - Adding a Contenta Configuration to the Solr Collection
A Solr Collection may contain one, many, or all Configurations from a given database. All configurations will be indexed by default. This is controlled by the AppData key,all_Configs, which is located under the collection key (“F18_Avionics_DB” in this example). If you do not want to index all of your configurations, you should add one or more Contenta configuration to a Solr collection. - Deleting a Solr Collection
When you "drop a database", you will need to delete its Solr Collection, if there is one. If all you want to do is delete a Solr Collection, skip steps 2 and 3. - Enabling Indexing for your database
After you are satisfied that your AppData and registry settings are properly configured, verify the following to enable indexing: - Solr Security
Perform these steps if your corporate policy requires you to run Solr within an HTTPS environment. - Troubleshooting
Use the Crawler log to help with troubleshooting.