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 |
|
- Troubleshooting SOAP API
- Debugging
- Error messages
- Failure of the WSDL2JS utility
- Testing your WSDL with a SOAP UI
- Running Web Services on a dedicated port (servlet)
- Troubleshooting a Web service that is behind a closed firewall
- Max sessions exceeded in Web Services
- Troubleshooting HTTP socket connections
- Debugging SOAP errors
- Web Services client unable to connect
- Calling external web services with SSL fails
Max sessions exceeded in Web Services
If a Web Services request contains "connection: keep-alive" or it uses HTTP/1.1 without a connection header, the Service Manager server will keep the session alive for a predefined interval that is defined by setting the "webservices_sessiontimeout" parameter in the sm.ini file. If a Web Services client does not reuse the session for subsequent requests by providing valid headers, the Service Manager server creates a new session for each subsequent request and quickly run out of available sessions.
To avoid running out of available sessions, there are two options to consider:
Option A: Set the HTTP header "connection:closed" so that the Service Managerserver will not keep a Web Services session open after the current request is finished.
Option B: Utilize the Web Services session persistence by doing one of the following to reuse the existing Web Services session on theService Managerserver.
- Use connection: keep-alive. If the connection header is missing, it defaults to "keep-alive" for HTTP/1.1.
-
The Web Services client needs to supply a session cookie with the same user log-in information that created the session.
Note Even with Web Services session persistence, each SOAP API request is stateless, so that requests are handled independently between one another.
