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 |
|
- Consuming a Service Manager Web Service
- Dynamic and static Web Services clients
- Updating Service Manager tables
- Requirements for developing custom Web Services clients
- Checklist: Creating a custom Web Services client
- Sample Web Services client for sc62server PWS URL
- Command line arguments for the .NET sample application
- Command line arguments for the Axis sample application
- Using query syntax
- Retrieving data from Service Manager
- Example: Retreiving data from Service Manager via a Web Service
- Retrieving data from Service Manager using Pagination
- Retrieve data from Service Manager for Optimistic Locking
- Web Services examples in the RUN directory
- Special considerations for using Keep-Alive with Service Manager
- Use SSL to consume Service Manager Web Services
- Attachment handling
Attachment handling
What do the following error messages mean?
Error Message: Warning: incoming add attachment request 1 has no href attribute
Error: unable to match incoming add attachment request 1 with no href attribute to an attachment part
They indicate that the <attachment> elements in the XML in the SOAP requests do not have a href or contentId attribute value. The same value is supposed to be in the MIME message part as the Content-ID: value. In SOAP with attachments, we need a correlation between the XML element/attributes that describe the attachment, and the actual binary or base64 attachment content which is in a MIME message. This correlation is typically a unique ID specified in an href or Content-ID attribute.
The Service Manager server deliberately allows requests that omit the href or contentId and attempts to match up the XML and the attachment parts.
We report the missing href or contentId value with a message in the sm.log file, as follows:
Warning: incoming add attachment request 1 has no href attribute
The server first tries to get an href or contentId value out of the XML; if it succeeds, it finds the associated MIME attachment by looking for a MIME message part whose id has the same value. If there is no href or Content-ID, the server tries to match up the <attachment> element with a particular attachment part. This assumes that there is a one-to-one correspondence between <attachment> elements and attachment parts and uses the index of the DOM node of the <attachment> element as an index into the array of binary attachment parts.
This strategy does not work when there are miscellaneous white-space nodes in the DOM document, because the index number of the DOM node for the <attachment> element is greater than it would otherwise be.
