Updating centralized tenant configuration settings - Documentation for BMC Helix Platform 20.08
Ava Richardson Disable-Audit-Only-Changed-Fields
Flag indicating whether to audit all records, or to audit only those records whose field values have changed.
T—Audit all the records.
F—(Default) Audit only those records whose field values have changed.
Flag indicating whether full text searching is case sensitive or case insensitive. This setting affects all fields indexed for full text search and affects how the indexes are built. Therefore, any changes to this setting trigger an automatic re-index.
0— Full text search is case sensitive
1—(Default) Full text search is case insensitive
Flag indicating whether the server processes the pending indexing tasks.
T—Disable indexing. Pending indexing tasks are recorded for processing later when indexing is enabled.
F—(Default) Do not disable indexing.
T—Disable the full text search engine.
Note: The database search capability continues to work even after the full-text search engine is disabled.
F—(Default) Use the full text search engine.
T—(Default) Use FTS in workflow.
F—Do not use FTS in workflow.
Following is the default location where the files are created:
<tenantDirectory>/ftsconfiguration/collection
Following is the default location where the files are created:
<tenantDirectory>/ftsconfiguration/conf
Location of the directory where the full-text search index log files are stored.
Following is the default file where the log entries are created:
arftindx.log
Indicates the way the FTS server modifies qualifications from the client.
1—Ignore leading and force trailing wildcards.
2—Ignore leading wildcards.
3—Remove leading and trailing wildcards.
4—(Default) Leave query unchanged.
Space separated list of attachment file extensions which must be excluded from FTS indexing.
For example, if the value to this parameter is set to .xla, .xls, .xlsm, .xlsx, .xlt and if you have enabled FTS or MFS for the attachment field, all the attachments with these extensions are ignored while creating FTS index.
If there are other fields that have enabled FTS or MFS index, the entry still gets indexed.
If you change this option, you must restart the BMC Helix Platform server for the change to take effect.
Defines the relevancy weight for Title Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search capabilities in your application.
0 - 0.9—Reduces the relevancy weight of the Title Field.
1—No change to the relevancy weight.
1.1 - 2.0—Increases the relevancy weight of the Title Field.
(Default) 4.0
0 - 0.9—Reduces the relevancy weight of the Keywords field.
1—No change to the relevancy weight.
1.1 - 2.0—(Default) Increases the relevancy weight of the Keywords field.
Defines the relevancy weight for the Environment Field. This setting relates to the fields for which the application business analyst has defined the relevancy when Enabling full-text search capabilities in your application.
0 - 0.9—Reduces the relevancy weight of the Environment field.
1—(Default) No change to the relevancy weight.
1.1 - 2000—Increases the relevancy weight of the Environment field.
Articles (a, an, the), prepositions (in, on, from, front, beside), and so on.
Press Enter to add a new word in this list.
PC workstation laptop desktop computer
slow sluggish
bright shiny
Type a word followed by its synonyms separated by a space. Press Enter to add a new list of synonyms.
0—(Default) Re-indexing is not performed.
1—Starts re-indexing.
Following is the default file where the log entries are created:
arapi.log
Following is the default file where the log entries are created:
aresc.log
Full path name of the file to use if archiving is on.
Following is the default file where the log entries are created:
ararchive.log
Following is the default file where the log entries are created:
arfilter.log
Following is the default file where the log entries are created:
arsql.log
Following is the default file where the log entries are created:
arthread.log
Following is the default file where the log entries are created:
aruser.log
Following is the default file where the log entries are created:
arprocess.log
Following is the default file where the log entries are created:
arservice.log
T—(Default) Logged lines are written to disc.
F—Logged lines are buffered.
(Default) 0
1
T—Append new log information to the existing file.
F—(Default) Create a *.bak file.
1— (Default) Minimum number of backup log files allowed.
999—Maximum number of backup log files allowed.
0—(Default) Log records to a specific form.
1—Log records to a common log form.
Sets the global locale for all users of the tenant. It takes precedence over user locale set by using My Preferences and browser locale.
When the global locale is not set, the user's locale from the My Preferences setting is applied, If none of the preferences are defined, then the browser locale is used for the user session.
Note: If the user logs in to BMC Helix Innovation Studio by using multiple sessions and updates the locale by using the Preferred-User-Locale or My Preferences > Preferred Language setting, the locale is set only after the user logs out from all the active sessions.
Default—Browser locale
English—en
French—fr
German—de
Italian—it
Chinese—zh_cn
Korean—ko
Portugese—pt_br
Russian—ru
Japanese—ja
Spanish—es
Dutch—nl
Swedish—sv
Danish—da
Norwegian—no
Bitmask indicating the server logging modes. To activate one bit, set this option to its value. To activate two or more bits, add their values, and set this option to the total.
For example, to activate bits 1 and 3, set this option to 5 because bit 1 has a value of 1 and bit 3 has a value of 4. To deactivate a bit, subtract its value from the value of this option.
Unless otherwise specified in the following list, this option turns on logging for the arserverd process. Default log files are in the directory specified by the Server-directory option.
0—(Default) Nothing enabled
1—SQL
2—FLTR
4–-USER
16—API
1048576—PROCESS
1048598—All but SQL
1048599—Turn on all of the above components
Flag indicating whether log files display full SQL statements or not.
For more information, see Knowledge Base article ID 000024691.
T—The BMC Helix Platform server captures complete SQL statements into the log files without truncation.
F—(Default) BMC Helix Platform server captures only 4093 characters per line, including the header information.
VersionControl-Object-Modification-Log-Mode
Controls whether the object modification log is enabled or disabled. When the log is enabled, it records every change to BMC Helix Platform objects in your system.
0—(Default) Disabled
10—Enabled
Controls whether the BMC Helix Platform server writes a definition file each time an object is created or changed. This option is effective only when the object modification log is enabled.
0—(Default) Yes, a definition file is created.
10—No, a definition file is not created.