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
Debugging SOAP errors
The best practice for troubleshooting SOAP errors is to start a new client connection process with a dedicated log file associated with it. Opening a new client connection process allows you to isolate any faulty client traffic from your regular client traffic.
- To set up your system to debug SOAP traffic, do one of the following:
- Start HTTP debugging for the entire system. Type the following command on a single line in the sm.ini file and then save the file.
debughttp:1
Debug parameters in the sm.ini file affect all Service Manager processes and the log files record all send/receive messages. This method is not recommended for a busy server however, since you have to restart the server for the debugging parameter to take effect. - Start a separate client connection process to troubleshoot your SOAP errors. Type the following command in the operating system command line:
sm -httpPort:unique portnumber -sslConnector:0 -debughttp:1
-log:../logs/debug.log
where
-httpPort identifies a port where Web Services clients can connect
-log defines a path to store the logs for this process
Normally, all client connection processes for a particular Service Manager installation use the parameter values listed in the sm.ini file. This means that all client connections share the same log file specified in the sm.ini file. By starting a new client connection process with a different log parameter value, you can isolate the logs for a particular group of clients. Choose a port number that is not likely to be used by any other process.
- Recreate the error.
- Review the http.log, sm.log and log files from the Web Services consumer or publisher that Service Manager is communicating with and server, and client log files for information about the SOAP error. The HTTP log is in the server's RUN folder. The server logs are in the path you specified with the log parameter. The client logs are located in the following paths:
- For a Web Services client, see your Web Services client log
- For a Web client, see the log filed specified in the log.properties file on the web tier system
- For a Windows client, see the .log on the Windows client system
