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.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
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.
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||
|A combination of search types||
- Configuring installation and setup options
- AutoPass licensing
- JRE support
- Server implementation options
- Lightweight Directory Access Protocol (LDAP)
- IPv6 overview
- Print options
- Regional settings
- Servlet implementation
- Startup and shutdown
- System information record
- Time zones
- UTF-8 (Unicode) support
Service Manager uses a servlet implementation to manage client connections to the server. The servlet implementation uses a pre-configured embedded Java servlet that does not require any additional installation or configuration of Java components. Administrators can manage the servlet implementation using the Service Manager configuration files and management procedures rather than Java interfaces.
A servlet implementation provides the following management features:
- The ability to specify the exact communications ports client connections use
- The ability to specify the maximum number of client connections Service Manager will accept
- Industry-standard resilience and scalability options
- Multithread processing capabilities
In a servlet implementation, administrators specify the communications ports the system uses in advance. The total number of communication ports required for a servlet implementation is based on the number of servlet container processes you want the Service Manager host to support. Each servlet container process manages a set number of client sessions as determined by the number of threads it contains.
Each servlet container process supports a set number of client connections over two communications ports, one for HTTP communications and one for HTTPS communications. Administrators set the number of client connections per process using the threading parameters. Two communications ports is sufficient for up to approximately 150 client connections (as determined by the Service Manager host's memory requirements).
A servlet implementation is ideal for administrators who want to do capacity planning and system resource management. The communications port and threading parameters allow administrators to control the resources that client connections consume. By specifying the communication ports and number of threads available for client connections, administrators can set a limit on the total number of client connections any one hardware resource supports. Setting connection limits prevent client connections from consuming more system resources than desired and allows administrators to set a server load threshold in advance. If a client attempts to connect to a Service Manager system that has reached its connection limit, the server refuses the connection and displays an error message that the server is unavailable.
Certain servlet implementations benefit from the native resilience and scalability features of grouping Java servlets. In a horizontal scaling implementation, administrators can create virtual groups where multiple Service Manager servers act as a single system. Each member in a virtual group communicates its connection availability and system resource usage to the other members of the group. Should a group member fail, the other group members are unaffected by the outage and the system can route any new client connection requests to another member in the virtual group. If the client connection routing process fails, the existing client connections are unaffected and an administrator can restart the client connection routing process.