Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Service Manager9.51

Administer > System configuration parameters > System performance parameters > Startup parameter: KMSearchEngineTimeout

Startup parameter: KMSearchEngineTimeout

Startup parameters change the behavior of the HPE Service Manager server. You can always set a startup parameter from the server's operating system command prompt.

Parameter

KMSearchEngineTimeout

Description

This parameter defines a timeout value in seconds for all Knowledge Management search server hosts (including indexing hosts, search hosts, and load balancer hosts). The default is 20 seconds, and the minimum is 10 seconds.

This parameter is used to prevent overloaded KM search servers from causing Service Manager to hang. When a search server host hangs (for example, because of 100% CPU usage), the Service Manager server tries to connect to the search server repeatedly until the timeout of the connection. The Service Manager server then returns an error. See the example scenarios in the following table.

Scenario Behavior

Scenario	Behavior
A search server hangs. From Knowledge Management > Configuration > Configure Search Servers, you select the server and click Verify Server.	The Service Manager server tries to connect to the search server until the timeout of the connection. A dialog box appears as if the search server is down or disconnected: "`Could not connect to Search Engine, please verify settings.`"
A knowledge base is assigned with a cluster of load balanced search servers, and one of the search slaves hangs. From Knowledge Management > Configuration > Knowledgebases, you select the knowledgebase and click Full Reindex.	The Service Manager server tries to connect to the slave search server until the timeout of the connection. A message appears as if the slave search server is down or disconnected: "`Slave server: <hostname or IP address> offline, skipping..`"
A master search server hangs. You attempt to search the knowledge bases.	The SM server tries to connect to the master search server until the timeout of the connection. Your search then fails, and a dialog box appears as if the search server is down or disconnected: "`Could not connect to Search Engine, please verify settings.`"

A search server hangs.

From Knowledge Management > Configuration > Configure Search Servers, you select the server and click Verify Server.

The Service Manager server tries to connect to the search server until the timeout of the connection. A dialog box appears as if the search server is down or disconnected: "Could not connect to Search Engine, please verify settings."

A knowledge base is assigned with a cluster of load balanced search servers, and one of the search slaves hangs.

From Knowledge Management > Configuration > Knowledgebases, you select the knowledgebase and click Full Reindex.

The Service Manager server tries to connect to the slave search server until the timeout of the connection. A message appears as if the slave search server is down or disconnected: "Slave server: <hostname or IP address> offline, skipping.."

A master search server hangs.

You attempt to search the knowledge bases.

The SM server tries to connect to the master search server until the timeout of the connection. Your search then fails, and a dialog box appears as if the search server is down or disconnected: "Could not connect to Search Engine, please verify settings."

Valid if set from

Server's operating system command prompt

Initialization file (sm.ini)

Requires restart of Service Manager server?

Yes

Default value

20 (seconds)

Possible values

No less than 10 seconds (if you specify a value less than 10, 10 is used.)

Example usage

Command line: sm -httpPort:13080 -KMSearchEngineTimeout:25

Initialization file: KMSearchEngineTimeout:25

Send Help Center feedback