Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Words and Phrases
| 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. |
Using Boolean Operators
| Search for | Operator | Example |
|---|---|---|
|
Two or more words in the same topic |
|
|
| Either word in a topic |
|
|
| Topics that do not contain a specific word or phrase |
|
|
| Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
| A combination of search types | ( ) parentheses |
|
Servlet implementation processes
All Service Manager servlet implementations use multithreaded processes. To control the client connections to these threads, you can configure the Service Manager server to start one of two types of processes:
- One or more servlet container processes that accept direct HTTP and HTTPS client connections
- One load balancer process to be the master thread controller for all servlet container processes in a virtual group
A servlet container process is a Service Manager sm.exe process that includes a multithreaded Java servlet container. Each servlet container process manages a pool of child threads dedicated to handling Service Manager client transactions. The Servlet container process listens for incoming client connection requests on a predetermined HTTP port and routes the requests to an available thread in the process. The thread then binds to the HTTP or HTTPS port of the parent servlet container process for the duration of the client connection. The total number of threads available determine the total number of client connections the servlet container process can manage. Each active thread in the servlet container process holds system locks and communicates this information to other servlet container processes in the same virtual group.
A load balancer process is an Service Manager sm.exe process dedicated to routing incoming client requests to servlet container processes in vertical and horizontal scaling implementations. In either scaling implementation the virtual group only requires one load balancer process. The Load balancer process does not have any child threads of its own, nor does it maintain any system locks or hold system resources. The load balancer listens for incoming client connection requests on a predetermined HTTP port and routes them to an available servlet container. The available servlet container may be on the same physical system or on another system in the same virtual group depending on the implementation.
| Property | Servlet container process | Load balancer process |
|---|---|---|
| Routes client connections to servlet container processes? | No | Yes |
| Routes client connections to threads? | Yes | No |
| Creates child threads? | Yes | No |
| Accepts client connections? | Yes | No |
| Uses an HTTP port? | Yes | Yes |
| Uses an HTTPS port? | Yes (optional) | No |
Related topics
Managing multiple servlet container processes
Servlet implementation options
Quiesce all servlet container processes in a servlet implementation
Quiesce all servlet container processes on a host
Shut down all servlet container processes in a servlet implementation
