Important for non-English deployments:
Enabling multilingual support for Search is a mandatory post-installation step that needs to be performed before you start your IBM
Connections Search server for the first time. Without multiple dictionary support, for languages other than English, Search will only return results where there is an exact match between the search term and content term. Enabling multiple dictionaries ensures better quality search results when your user base is multilingual. For more information about enabling multilingual support, see Configuring dictionaries for Search
By default, the IBM
Connections user interface is displayed in the language identified in the locale settings of the web browser being used. You can set it up to allow users to explicitly choose the language in which the product is displayed. For more information, see Enabling users to set a language preference
You can also perform optional post-installation configuration tasks relating to indexing, such as configuring J2C authentication for Search or changing the location of the Search index.
Enabling indexing resumptionParent topic: Administering Search
Enabling users to set a language preference
You can add a configuration setting to the search-config.xml
file to specify that interrupted or failed indexing tasks are automatically resumed.
Configuring dictionaries for Search
The Search application provides globalization support by using different dictionaries for different languages. Each dictionary file must be enabled in the Search configuration file before indexing. By default, only the English language dictionary is enabled during installation.
Changing the location of the Search index
By default, the Search index is stored in the search/index
subdirectory of the IBM
Connections data directory defined at install time, for example, on Linux
. This location can be changed by editing the IBM WebSphere
® Application Server variable, SEARCH_INDEX_DIR.
Configuring J2C authentication for Search
When you install IBM
Connections, the installation wizard automatically configures authentication and authorization for each application. Crawling content for indexing occurs over an internal REST API interface, and the credentials used are retrieved from the connectionsAdmin J2C authentication alias that is configured during installation. The user ID from the credentials is also added to the search-admin Java EE role for each application. If you want to further secure the IBM
Connections environment, you can override this authentication alias on an application-by-application basis.
Search and globalization
You can configure globalization settings to enable users to perform accent-insensitive searches, ignore punctuation in search terms, and perform a one-to-two mapping in search terms. Search globalization settings are disabled by default.