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
Web Services client unable to connect
The most common error occurs when your Web Services client application fails to obtain a response, or you receive this error message:
Server Error in <name> Application
The underlying connection was closed: Unable to connect to the remote server
The Web Services client may be directing SOAP requests to the wrong host or to the wrong TCP port number. Service Manager generates WSDL files that contain the hostname and TCP port number for the Service Manager server instance receiving the request. The Web Services client application may use the hostname and port number used during application development, but the production hostname and port might be different each time the application runs if they are dynamically allocated.
If the server instance generating the WSDL is different from the hostname or port number receiving the client application requests, the client/server connection will fail. Follow these rules to ensure successful client/server SOAP communication.
- Ensure that your Web Services request is not running against a common port with heavy server traffic. Otherwise, tracking request and response messages will be difficult.
-
Type the following at the command line to generate debug logs:
sm -httpPort:unique portnumber -sslConnector:0 -debughttp:1 -log:../logs/debug.log
where
-httpPortidentifies a dedicated port for Web Service client connections-logdefines a path to store the logs for this connection.Note It is easier to troubleshoot errors if each SOAP client application connects to its own TCP port number.
- Examine the HTTP.LOG file for response messages. You can use this information to determine where a Web Service client connection failure occurs.
