Vertical scaling implementation

In a vertical scaling implementation you maximize the number of client connections supported on a single host.

The key features of this implementation are:

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)`

The Service Manager system consists of several servlet container processes running on one physical host

The implementation allows administrators to specify a system connection limit

The Service Manager system can manage a number of concurrent client connections up to the number of servlet container processes times the threadsperprocess value (For example, 6 servlet container processes supporting 50 threadsperprocess can support up to 300 client connections)

The implementation allows administrators to specify the communication ports the system uses

A dedicated load balancer process manages and routes client connections to available servlet container processes

Administrators can dynamically add and remove Service Manager instances from a virtual group

A vertical scaling implementation is typically used in small to medium environments where hardware system resources are limited. A vertical scaling implementation can support as many client connections as the Service Manager host has available system resources.

You can convert a vertical scaling implementation into a horizontal scaling implementations with the addition of virtual grouping parameters and one or more additional servlet container instances installed on separate physical hosts.

Note: There can be only one kmupdate process running at any time regardless of the number of hosts. Starting more than one kmupdate process causes unpredictable behavior on the search engine server.

Vertical scaling implementation diagram

The Vertical scaling implementation diagram is a reference diagram for implementers who are responsible for installing and configuring Service Manager. The guide shows the configuration settings and network connections required for a single server running multiple servlet containers implementation.

You can view and search this guide using Adobe® Reader, which you can download from the Adobe Web site.