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.
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. |
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 |
|
Example using Keep-Alive with .Net Web Services Studio
To use Keep-Alive with .Net Web Services Studio, perform the following actions.
- First set the following:
- set "AllowWriteStreamBuffering" to True
- set "BasicAuthUsername" to falcon
- set "KeepAlive" to True
- set "UserCookieContainer" to True
- Execute a RetrieveIncident action and search for the incident with the number IM1001.
- When you click Send, the "Set-Cookie" and "Connection" headers can be seen in the response window.
- Click Send again, only the "Connection" header can be seen in the response.
- In the sm.log, these two requests (one per send) will belong to one session, meaning they have the same Process ID (Thread ID) combination.
2052( 6096) 05/05/2008 15:30:31 RTE I Using "utalloc" memory manager 2052( 6096) 05/05/2008 15:30:31 RTE I Process sm 7.01.048 System: 13080 (0x784dfb00) on PC running Windows XP Professional (5.1 Build 2600) from server (127.0.0.1) 2052( 6096) 05/05/2008 15:30:31 RTE I Connected to SOAP client at 127.0.0.1 2052( 6096) 05/05/2008 15:30:31 RTE I Attaching to resources with key 0x784dfb00 2052( 6096) 05/05/2008 15:30:31 RTE I Info: SQL State: 01000-5701 Message: [Microsoft][SQL Native Client][SQL Server]Changed database context to 'sm701'. 2052( 6096) 05/05/2008 15:30:31 RTE I Info: SQL State: 01000-5703 Message: [Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english. 2052( 6096) 05/05/2008 15:30:31 RTE I sqmssqlExec info statement= SQL CONNECT 2052( 6096) 05/05/2008 15:30:31 RTE I Connection established to dbtype 'sqlserver' database 'sm701' user 'sm7' 2052( 6096) 05/05/2008 15:30:31 RTE I Connected to Data source 'sm701' SQL server 'server\SQLEXPRESS' version: 9.0.3042 Using database 'sm701' as user 'sm7' 2052( 6096) 05/05/2008 15:30:31 RTE I MS SQL Server collation 'Latin1_General_BIN', varchar codepage 1252, comparison 0: case sensitive, accent sensitive 2052( 6096) 05/05/2008 15:30:31 RTE I Thread 912DAAD51D1B0A53B251147F6665B7EE initialization done.