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
Troubleshooting HTTP socket connections
The Service Manager server attempts to keep an HTTP socket connection open as long as possible, but the protocol requires that it must close if the server returns a SOAP fault. If there is no successful authentication, it must return a SOAP fault.
Redirected ports
To ensure the client has the correct hostname and port number, a SOAP client application can direct requests to the TCP port number used by the sm -httpPort instance, but must be able to recognize SOAP header values in the initial response:
- redirectServerHost
- redirectServerPort
The server returns these SOAP header values identifying the dynamically allocated TCP host and port number for the spawned process. During the client/server session, subsequent SOAP requests must be directed to the same hostname and port identified in the initial response.
TCP ECONNRESET messages
If a client/server connection using a spawned child thread terminates, the sm -httpPort child thread receives a TCP ECONNRESET message. The child thread responds to this by self-terminating to ensure that orphaned child thread does not collect on the server. However, poorly-designed client applications, or other third-party SOAP tools, that do not gracefully close a connection could cause the server process to see a TCP ECONNRESET message, and that also terminates the server thread.
