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
Special considerations for using Keep-Alive with Service Manager
A Service Manager user session starts when the Service Manager server receives the first request from a SOAP client and ends when the SOAP client closes the HTTP connection. The user login process is performed in the first SOAP client request and the user logout process is performed when the SOAP client ends this Service Manager session. A SOAP client can reduce the login and logout overhead by enabling HTTP persistent connections, also called HTTP keep-alive. If you want to use HTTP 1.1 Keep-Alive connections with a SOAP API client, the SOAP API client must support cookies. When Service Manager responds to the first POST request from the SOAP API client, it includes a Set Cookie header that conveys the servlet container sessionid to the client.
- Configure the SOAP stack with which the SOAP API client is written to support cookies. Axis and .NET can both be configured to do this.
- If the SOAP toolkit supports HTTP 1.1 Keep-Alive but not cookies, you can arrange for the application to echo back the JSESSIONID value in a Cookie header by adding code to the client application to manually create the HTTP header on the second and subsequent requests
Note
- In HTTP/1.1, persistent connections are the default behavior of any connection.
- If you use HTTP 1.0 you have to manually set the HTTP header “connection” to keep-alive.
- A SOAP client ends a Service Manager session by sending a request with the HTTP header “connection” set to “close”. If a close request is never received by the Service Manager server then this session is terminated by the Service Manager server when the webservices_sessiontimeout time is reached.
