Configuring Content Search

You can use the Admin Console to select and configure your search service, rebuild the content search index, and monitor the status of your search services.

For more on selecting a Search service, see Selecting a Search service. Support for searching internal content relies on multiple technologies, including the open source Lucene library.

In addition to content written and published with the community's editor, the search feature also searches the following file types: .html, .rtf, .txt, .pdf, .ppt, .pptx, .doc, .docx, .xls, .xlsx, .odt, .ods and .odp (OpenOffice formats). The application will also search the contents of a .zip file.

Fastpath: Admin Console: System > Settings > Search > Content Search

Index Tasks

Rebuild Index
Having the application regularly update the search indexes is very handy, but rebuilding an index (via the Index Tasks tab) can be very time-consuming. You should only manually rebuild if the search index becomes corrupted or you find you're missing large amounts of content in search results. Please see these detailed instructions when manually rebuilding the search index. The rebuild processing will happen on the web app node you are accessing when you initiate the rebuild. This node sends the data to the external search service you have configured.
Check status of content in index
You can check the status of a piece of content in the Search index by entering the URl for that item in the Content URL field and clicking Retrieve modification dates. If the date is old, you can click Update in index to get the latest version in the index.


For Jive 6.0.1 and higher, Synonyms improve searches for content by enabling you to search for matching words when another word in the list is used. For example, if you realize that people will search using slang common to your industry, you could add synonyms that associate a commonly used term with slang alternatives. A Jive-specific example could be "conversation,discussion,question".

Synonyms are language-specific and should be enabled per language if you have multiple languages enabled. New synonyms work only on new content. If you want new synonyms to work on existing content, a Search Index Rebuild is necessary. For more on this see Search Index Rebuilding.

To use synonyms:

  1. Type in a comma-separated list of synonyms.
  2. Click Add Synonyms.

Search Service Status

You can use the Search service status to track the successes and failures of calls to the different services for search. The following list describes the available services:
Activity Ingress
Jive uses this service to send activity data to the search system. Search uses this service to receive everything that has been indexed. For example, content creation, updates to content, user creation, user updates, place creation, updates to places, likes and comments all get posted to the activity ingress and get indexed. Failures to this service mean that events will queue up on the web app node waiting to be pushed into search.
Jive uses this service to execute search queries. The Query service enables Jive to access the content that has been indexed. For example, Jive uses this service when you use spotlight search on the Search page, when you select content under the "Show more like this" heading, when you use the user picker, and when you use most fields that auto-suggest searches as you type. Failures to this service means searches will fail.
Tenancy and Directory
These services always use the same host and port. If they use localhost, they are referring to the host and port that you configured for On-Premise search. This service is the entry point into search and tells Jive where to go for all the other services, and it assigns a tenant ID to the Jive instance so it can be uniquely identified by all search services.
Failures to these services mean search is not working. If you are using On-Premise search, make sure the Search node is up and running, and that you can telnet from the Web App node to the On-Premise Search node at the configured port. If you are using Cloud search, make sure your firewall is setup properly. If your firewall has been setup properly, then gather your logs and contact Support. For more on ports, see List of Required Ports and Domains.

Search Service Configuration

Use these settings to connect to your Search service from your web application nodes. You have the option of either connecting to Jive's Cloud Search service or installing and connecting to an On-Premise Search service.

Setting Options Description
On-Premise Search    
  On-Premise Search Service Host Enter the host name that Jive can use to connect to the Search service. For On-Premise Search, this is the host name for the node where you installed Search. Default is localhost. Refer to system requirements for information on Search node size.
  On-Premise Search Service Port Enter the tcp port that Jive can use to connect to the Search service. Default is 30000.
Cloud Search    
  Search Endpoint For Cloud Search, select the public cloud search end point in your area. For connection information, see Connecting to Jive-Hosted Services.