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 |
|
- System performance parameters
- Startup parameter: agstackl
- Startup parameter: arraysizelimit
- Parameter: attachmentsegmentsize
- Parameter: memorypollinterval
- Parameter: strongtypecheck
- Startup parameter: anubisPollInterval
- Startup parameter: cache_clean_interval
- Startup parameter: cache_locks
- Startup parameter: cache_slots
- Startup parameter: dao_sessiontimeout
- Startup parameter: dao_threadsperprocess
- Startup parameter: dashboard_export_path
- Startup parameter: dashboardquerycache_enable
- Startup parameter: dashboardquerycache_dbtime
- Startup parameter: dashboardquerycache_expire
- Startup parameter: dashboardonreplicatedb
- Special parameters: detectkeyed
- Startup parameter: enableAnubisMonitor
- Parameter: gcthreshold
- Startup parameter: KMSearchEngineTimeout
- Startup parameter: maxgroupsperview
- Startup parameter: maxhttpreqresponse
- Startup parameter: maxKeepAliveRequests
- Startup parameter: maxloginspercluster
- Startup parameter: maxmemoryperthread
- Startup parameter: maxmsgsharedmemory
- Startup parameter: maxpagesize
- Startup parameter: memdebug
- Startup parameter: memmanager
- Startup parameter: precision
- Startup parameter: recordlistcount
- Parameter: semaphoreWaitTime
- Startup parameter: shared_memory
- Startup parameter: shared_memory_address
- Startup parameter: shutipc
- Startup parameter: tmpdirectory
- Startup parameter: unlockdatabase
- Startup parameter: usealtsignalstack
- Startup parameter: usemembar
- Parameter: vj_record_limit
- Parameter: vj_record_warning
Startup parameter: enableAnubisMonitor
Startup parameters change the behavior of the Service Manager server. You can always set a startup parameter from the server's operating system command prompt.
Parameter
enableAnubisMonitor
Description
This parameter starts the anubis monitor to check the status of background scheduler threads. By default, this parameter is disabled.
This parameter should be used in conjunction with the anubisPollInterval parameter, which specifies the time interval (in seconds) at which the anubis monitor checks to see if any registered scheduler is alive (default: 15 seconds).
The following table describes different system behaviors based on the value of this parameter.
Value | Description |
---|---|
1 or empty | Enabled |
0 |
Disabled Note By default, this parameter is not specified and a value of "0" is used. |
Note The ThreadControllerId-background thread, which can be started no matter whether enableAnubisMonitor is enabled or not, has been modified to additionally include the anubis monitor functionality and thus eliminated the need for the anubis process. You are recommended to use the new anubis parameters instead of the old anubis process. If an anubis agent record and anubis schedule record, which were used to restart stopped background processes automatically, already exist in your system, before enabling enableAnubisMonitor you need to disable the original anubis RAD applications. To do this, follow these steps:
- Delete the existing anubis agent record.
- Type info on the Service Manager command line, and then click Search.
- Delete the anubis agent record.
- Delete the existing anubis schedule record.
- Type sch on the Service Manager command line, and then click Search.
- Delete the anubis schedule record.
Valid if set from
Server's operating system command prompt
Initialization file (sm.ini)
Requires restart of the Service Manager server?
Yes
Default value
0 (Disabled)
Possible values
0: Disabled
1 or empty: Enabled
Example usage
Command line: sm -httpPort:13080 -enableAnubisMonitor:1
Initialization file: enableAnubisMonitor:1
Related topics
System parameters
Enter a parameter in the sm.ini file
Enter a parameter in sm.cfg or the server’s OS command prompt
Create an anubis agent record
Create an anubis schedule record
Restart stopped background processes automatically
System performance parameters
Startup parameter: anubisPollInterval