Configuration settings C-D

The centralized configuration forms store the configuration settings. All the numeric values for the settings are in base 10 system. You can modify the settings by using the AR System Configuration Generic UI form. The settings are case- and space-sensitive. See Updating configuration settings by using the AR System Configuration Generic UI form.

Best practice

We recommend that you use the AR System Configuration Generic UI form to modify the configuration settings. Do not use the ar.cfg file to modify the configuration settings on the AR System Configuration Generic UI form.

The following table lists the settings available for centralized configuration.

Tips

If you cannot view all the columns, view the page in full screen mode. Alternatively, use the scroll bar at the bottom of the table.
Press F11 to view the table in full screen mode. Press F11 to exit full screen mode.
To easily search for a specific parameter in the table, select the parameter from the Setting list. Alternatively, type the name of the parameter in the Setting text box.
For example, to search for the Next-ID-Block-Size parameter, select it from the Setting list, or type the parameter name in the Setting text box.
To search for the parameters which have a specific text string in the description, type the string in the Description text box.
For example, to search for the parameters which have Configuration in the description, type Configuration in the Description text box.

Configuration settings (C-D)

Oops, it seems that you need to place a table or a macro generating a table within the Table Filter macro.

Setting	Description	Sever group configuration	Maps to
Cache-Display-Properties ² (Component name: com.bmc.arsys.server)	The way that the server caches form display properties. The form display property is the background image of the form view and the display property of each form field. Valid values: T—(Default) Cache all form-display properties. F—Cache only server-display properties. (This can negatively impact the performance of the server if a form is changed, but it reduces the amount of memory used in the server cache.)	No	AR System Configuration Generic UI form
Cache-Mode	The valid value for Cache-Mode is 0 (the default). In this mode administrative operations cause the server to create an administrative copy of its cache so that other users can continue using the shared cache while administrative operations are performed. In AR System 9.x and later, the Development cache mode and Production cache mode behave in the same way. The AR System server maintains a single copy of cache. Do not change value for this setting. For this setting, the AR System server assumes the value as per the production cache mode. This behavior is true, even if you try to change the setting directly through API.	No	AR System Administration Console > System > General > Server Information > Configuration > Development Cache Mode. (See Setting administrative options.)
Cancel-Query-Option ² (Component name: com.bmc.arsys.server)	Flag indicating whether the cancel query functionality in a browser is enabled. Valid values: 0—Inactive 1—(Default) Active	No	AR System Configuration Generic UI form.
Changed-By-Another-Check (Component name: com.bmc.arsys.server)	Flag indicating whether the system checks whether another user changed an entry after you retrieved the entry. If you try to save modifications to an entry, you receive a warning and must confirm the save. Valid values: T—(Default) Perform the check and issue a warning. F—Do not perform the check.	No	AR System Configuration Generic UI form
Clamav-Max-File-Size-KB (Component name: com.bmc.arsys.server)	The maximum file size that is scanned by the ClamAV antivirus. We recommend setting the file size to less than 25 MB. Default value — 25600 KB	Yes	AR System Configuration Generic UI form
Clamav-Service-Hostname (Component name: com.bmc.arsys.server)	Host name of the ClamAV service. Default value — clamav	Yes	AR System Configuration Generic UI form
Clamav-Service-Port (Component name: com.bmc.arsys.server)	Port where the ClamAV service is running. Default value — 3310	Yes	AR System Configuration Generic UI form
Clamav-Socket-Timeout (Component name: com.bmc.arsys.server)	The socket timeout value for TCP connection to the ClamAV antivirus. Default value — 20000 milliseconds	Yes	AR System Configuration Generic UI form
Classification-Service-Provider (Component name: com.bmc.arsys.server)	Enables you to define the classification service provider that should be used for the cognitive classification service. WATSON—(Default) Enables auto-classification by using the IBM Watson Assistant service. NATIVE—Enables auto-classification by using the BMC Native (Google) classification service.	No	AR System Configuration Generic UI form
Client-Managed-Transaction-Timeout (Component name: com.bmc.arsys.server)	Maximum time (in seconds) to hold a transaction before a timeout occurs. The default is 60 seconds, and there is no maximum. If a timeout occurs, the server automatically rolls the transaction back, and the client receives anerroron the next operation that uses the transaction handle.	No	AR System Administration Console > System > General > Server Information > Advanced > Transaction Control section > Transaction Timeout (seconds). (See Setting performance and security options.)
Clustered-Index (Component name: com.bmc.arsys.server)	Flag indicating whether indexes for the database are clustered. Valid values: T—(Default) Use a clustered index. F—Do not use a clustered index. You must set this option before you start the AR System server .	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.level² (Component name: com.bmc.arsys.emaildaemon)	Specifies the log level for email engine based on which the logs are generated in the email.log file Valid values: Off Severe (Default) Warning Info Config Fine Finer Finest Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. ARSystemHandler.level ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the log level for Email Engine based on which the logs are saved in the AR System Email Error Logs form Valid values: Off (Default) Severe Warning Info Config Fine Finer Finest Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.EnableWatcherThread (Component name: com.bmc.arsys.emaildaemon)	If this setting is set to `true`, the Email Engine watches the process of outgoing emails. If an email message is not processed for the time interval configured, the Email Engine automatically restarts. Valid values: True (Default) False	Yes	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.logfileName (Component name: com.bmc.arsys.emaildaemon)	Enables users to specify the log file path Once the user specifies a file path, email engine logs that user defined file only when it connects to AR System server . if any error occurred before connecting to Centralized configuration form then logs will be stored into default log file path. Default value: emailEngineInstallDir/AREmail/Logs/email.log	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.logfilesize (Component name: com.bmc.arsys.emaildaemon)	Specifies the maximum size of the log file in bytes If the file size exceeds this limit, a new file is created. Default value: Unlimited	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. AdditionalMailHeaders ² (Component name: com.bmc.arsys.emaildaemon)	Specifies additional email headers. Separate the additional email headers with commas. See Adding extra custom headers to outgoing SMTP emails. Default value: X-Loop-Detect Related functionality: Outgoing Related protocol: SMTP	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.ARDATE ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the date and time format that the Email Engine uses for parsing date and time strings given in the incoming mails. MMMMM dd, yyyy HH:mm:ss z is equivalent to December 21, 2009 12:08:56 PDT. Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.ARDATEONLY ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the date format that Email Engine uses for parsing date strings given in incoming mails. MMMMM dd, yyyy is equivalent to December 21, 2009. Default value: X-Loop-Detect Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. ARTIMEONLY ² (Component name: com.bmc.arsys.emaildaemon)	This setting lets you specify the time format used by Email Engine for parsing time strings given in incoming mails. HH:mm:ss z is equivalent to 12:08:56 PDT. Default value: X-Loop-Detect Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. ContentTypeWithCharset ² (Component name: com.bmc.arsys.emaildaemon)	This setting indicates whether to send the charset property in the Content-Type header of an outgoing message. If you do not want the charset string to be present in the Content-Type header, set this property to False. Valid values: True (Default) False Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. ChunkSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of entries to return when the Email Engine makes a call to the AR System server. Default value: 100 The maximum value is also 100. Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. CommaValidAddressSeparator ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether you can use a comma as a separator when entering multiple addresses in the To and CC fields. If user names in the mail server contain commas, set this property to false (usually needed only when using the MAPI protocol). For example, if names are stored on the mail server as: Smith, John and Cho, Rick You would need to use semicolons to separate the addresses: Smith, John; Cho, Rick Valid values: True (Default) False Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. Exchange-Wait-Time ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the amount of time in milliseconds for which the Email Engine waits before processing the nextincomingmessage,when there are more messages residing on the Exchange Server. Default value: 1 Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. FetchUserGroupInfoOnDemand ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to fetch the user and group information about demand as opposed to loading all users and groups at startup. If there are many users or groups, you might want to set this property to true to reduce the startup time for email. Valid values: True False (Default) Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. getReplyToWithFromAddress ² (Component name: com.bmc.arsys.emaildaemon)	Determines whether the outgoing message header should contain the Reply To field and what its value should be.getReplyToWithFromAddress is not used by default. If you want the Email Engine to use this property, you must add it to EmailDaemon.properties and set its value to true. If you add the property but do not specify a value, it is considered as false. The effect of using this property is as follows: If no values are provided in the Reply To Address field of the outgoing mailbox configuration form and the Reply To field of the messages form, and the value of this property is: false (or not provided)—The Reply To field is not included in the outgoing message header. true—The Reply To field is included in the outgoing message header, and its value is the address in the From field of the messages form. If the Reply To Address field of the outgoing mailbox configuration form or the Reply To field of the messages form contains a value, the message header will contain theReply To headervalueas set in the message, regardlessofvalue of this property. Valid values: True (Default) False Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.IMAPTimeout (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to wait before cancellinganattempt to connect to the mail server and generating an error. In caseofan IMAP timeout, the email engine waits for the timeout interval and then marks the queued message as erroneous. IMAPTimeout is not used by default. If you want the Email Engine to use this property, you must add it to EmailDaemon.properties and set its value to true. Valid values: True False (Default) Related functionality: Incoming Related protocol: IMAP	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.IMAPTimeoutPeriod (Component name: com.bmc.arsys.emaildaemon)	Specifies the duration in numberofseconds to wait before cancellinganattempt to connect to the mail server and generating an error. In caseofan IMAP timeout, the email engine waits for this interval and then marks the queued message as an erroneous. IMAPTimeoutPeriod is not used by default. If you want the email engine to use this property, you must add it to EmailDaemon.properties and set its value to any positive integer. Related functionality: Incoming Related protocol: IMAP	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. IncomingConnectionRecycleSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the default number of email messages the Email Engine receives before the connection is closed and reopened. In the 5.1 and 5.1.1 releases of the Email Engine , the connection with the mail server was closed only after reading all incoming messages. Consequently, if the Email Engine crashed or hung before the connection was closed, it was possible that messages marked for deletion would not be deleted from the mail server. This property helps you avoid that situation. Default value: 100 Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. IncomingMessagesQueueSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the message queue size (number of emails). The Receiver module writes messages to the queue, and the Execution module reads messages from this queue to parse and execute. The Receiver module still writes messages to the server in AR System EmailMessagesform, but the Execution module reads the message from the message queue instead of from the server. This reduces the traffic to the AR System server and improves the performance. Default value: 100 Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. instructionCacheSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of instructions to be stored in the cache, which is used to improve performance. If the value of this property is set to 15, the cache already contains 15 instructions, and another instruction is to be added, then the oldest instruction is removed to accommodate the newest one. If any changes are made to the BMC Remedy AR System Email Instructions form, the instruction cache is flushed based on the setting of the serverName .Interval property. Default value: 20 Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.Mailboxes ² (Component name: com.bmc.arsys.emaildaemon)	If you run multiple instances of the Email Engine on a single server, this property specifies which mailboxes should the Email Engine process. The value of this property should contain comma-separated mailbox names; the Email Engine only processes these mailboxes. If you do not specify a value, the Email Engine processes all of the mailboxes configured for the server. Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. MailboxPollingUnitIsMinutes ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether the polling interval is to be considered in minutes (as configured in AR System Email Mailbox Configuration form) or seconds. The email engine interprets the value of this property as follows: true—Consider the polling interval in minutes. false—Consider the polling interval in seconds. Whatever measure of unit you select applies to all configured mailboxes that are enabled. Valid values: True (Default) False Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. MaxAttachSize and com.bmc.arsys. emaildaemon.MaxAttachSizeFileExtensions ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the attachment types that you want to permit in an email message and the maximum size of each attachment. MaxAttachSize specifies the maximum size limit for attachments, whereas MaxAttachSizeFileExtensions specifies the file types by using comma-separated extensions. These properties must be used together to impose limits on email attachments of specific file types. For example, to set the maximum size of .doc, .pdf, and .xls attachments to 1000000 bytes (1 MB), use the following syntax: com.bmc.arsys.emaildaemon.MaxAttachSize=1000000 com.bmc.arsys.emaildaemon. MaxAttachSizeFileExtensions=doc,pdf,xls The size limit is not imposed on files whose extensions are not specified by using MaxAttachSizeFileExtensions. Email messages with attachments that exceed this limit are logged to the AR System Email Error Logs form. Optionally, you cancreateworkflow for this form to process such messages separately. Valid values: True False (Default) Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. MBOXFromLineWith-At-The-Rate-Sign ² (Component name: com.bmc.arsys.emaildaemon)	The email engine interprets the value of this property as follows: true— Email Engine fetches only those messages that contain the @ sign in the "from line" (from address). false— Email Engine fetches all the messages. Valid values: True False (Default) Related functionality: Incoming and Outgoing Related protocol: MBOX	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.Monitor ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the interval in minutes between checks to see if all the threads are functioning properly. If the monitoring system detects that a thread has failed, it restarts the thread. Default value: 30 minutes Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. NumberOfSenderThreads ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of sender threads that the email daemon uses for each outgoing mailbox. The optimum number of threads depends on many factors including the number of mailboxes, the hardware configuration, and so on. Valid values: 1 through 20 Default value: 4 Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
*com.bmc.arsys.emaildaemon.<servername>.Interval*	Specifies the interval (in minutes) at which the mailbox configuration is updated. Default value: 30	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.POP3Timeout (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to wait before cancellinganattempt to connect to the mail server and generating an error. In caseofan POP3timeout,the email engine waits for the timeout interval and then marks the queued message as erroneous. POP3Timeout is not used by default. If you want the email engine to use this property, you must add it to EmailDaemon.properties and set its value to true. When you set POP3Timeout to true, the POP3TimeoutPeriod property is used. Valid values: True False (Default) Related functionality: Incoming Related protocol: POP3	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.POP3TimeoutPeriod (Component name: com.bmc.arsys.emaildaemon)	Specifies the duration in number of seconds to wait before cancelling an attempt to connect to the mail server and generating an error. In case of an POP3timeout,the email engine waits for this interval and then marks the queued message as an erroneous. POP3TimeoutPeriod is not used by default. If you want the Email Engine to use this property, you must add it to EmailDaemon.properties and set its value to any positive integer. Related functionality: Incoming Related protocol: POP3	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. SaveSentItem ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to retain messages in the Email Messages form after sending. To delete sent messages from the Email Messages form, set this property to False. Valid values: True (Default) False Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. securityCacheSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of security keys to be stored in the cache. If the value of this property is set to 15, the cache already contains 15 security keys, and another key is to be added, then the oldest key is removed to accommodate the newest one. If any changes are made to the BMC Remedy AR System Email Security form, the security cache is flushed based on the setting of the serverName .Interval property. Default value: 20 Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. SendEmailSetSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of outgoing emails to query at a time. Default value: 100 Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. SMTPTimeout ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to wait before cancellinganattempt to connect to the mail server and generating an error. In caseofan SMTP timeout, the email engine waits for the timeout interval and then marks the queued message as erroneous.SMTPTimeout is not used by default. If you want the email engine to use this property, you must add it to EmailDaemon.properties and set its value to true. If you add the property but do not specify a value, it is considered as false. Valid values: True False (Default) Related functionality: Outgoing Related protocol: SMTP	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. SMTPTimeoutPeriod ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the duration in numberofseconds to wait before cancellinganattempt to connect to the mail server and generating an error. In caseofan SMTP timeout, the Email Engine waits for this interval and then marks the queued message as an erroneous. SMTPTimeoutPeriod is not used by default. If you want the Email Engine to use this property, you must add it to EmailDaemon.properties and set its value to any positive integer (upper limit depends on the platform). If you add the property but do not specify a value, it is considered as half the polling interval that is set for outgoing mailboxes. SMTPTimeoutPeriod is dependent on SMTPTimeout ; it works only when SMTPTimeout is set to true. Related functionality: Outgoing Related protocol: SMTP	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.SortMessages ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to process messages with a higher priority setting first. Valid values: True False (Default) Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.StoreInstructions ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to store instructions and instruction parameters in the AR System server . If set to true, the Email Engine retains data in the Email Instructions and Instruction Parameters forms for troubleshooting. Then, you must delete this data explicitly. The Execution module in the Email Engine handles both the parsing and execution of messages. There will be one message queue created for each Incoming mailbox. By default, instructions are not stored in the server. Valid values: True False (Default) Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. SynchronizedLoggingMode ² (Component name: com.bmc.arsys.emaildaemon)	This property is not available by default. Valid values: True—The synchronized logging mode is used. False (Default)— The bulk API logging mode is used. The Email Engine 's performance might degrade when synchronized loggingisenabled, because all the Email Engine threads are suspended while processing the synchronized logs. Synchronized logging continues to occur periodically, and control is restored to the threads only after the logging is over. Related functionality: Incoming and Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. templateCacheSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of email templates to be stored in the cache to improve the performance. If the value of this property is set to 15, the cache already contains 15 templates, and another template is to be added, then the oldest template is removed to accommodate the newest one. If any changes are made to the BMC Remedy AR System Email Templates form, the templates cache is flushed based on the setting of the serverName .Interval property. Default value: 20 Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. URLWithHrefTag ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether an <a href> tag is placed around a URL in an HTML message. If the setting is true, the <a href> tag is used. If the setting is false, the URL is not enclosed in an <a href> tag. Valid values: True (Default) False Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. UseNameIfNoEmailAddress ² (Component name: com.bmc.arsys.emaildaemon)	Specifies whether to retain display names that do not have email addresses associated with them in the To, CC, or BCC fields. If the setting is true, the display names are not removed from the To, CC, or BCC fields. If the setting is false, the display names are removed from the To, CC, or BCC fields. The Email Engine checks for email addresses associated with display names only on the User form and not on the Exchange server. Valid values: True (Default) False Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. UserChunkSize ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the number of users (records from the User form) to retrieve from the AR System server at one time. This setting can be used to tune the Email Engine 's performance. Default value: 5000 Related functionality: Outgoing Related protocol: All Supported	No	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon.WatcherThreadInterval (Component name: com.bmc.arsys.emaildaemon)	When the email watcher thread is enabled, this parameter defines the interval to check the status of outgoing email messages. Default value: 300 seconds	Yes	AR System Configuration Generic UI form
com.bmc.arsys.emaildaemon. AdminAddresses ² (Component name: com.bmc.arsys.emaildaemon)	Specifies the email address of the administrator. If a database transaction fails while storing an incoming message, the Email Engine forwards the original mail to this email address, so that it is retained. An example of a transaction failure could be when the database is full and cannot save anymore incoming email messages. You can specify multiple addresses separated by commas. This property can be used only when the Email Engine does not capture the error out incoming email messages in the BMC Remedy AR System Email Error Messages Form. Default value: Default value is set to the administrator address specified during installation. Related functionality: Incoming Related protocol: All Supported	No	AR System Configuration Generic UI form
Common-Logging-Root-Path (Component name: com.bmc.arsys.server)	This parameter allows you to change the default location for storing the log files. If this value is not set then the logs are stored in the location set by Server directory. Also, the BMC Remedy AR System Maintenance Utility uses this setting to include files when you use the Log Zipper feature. Default value: NULL This parameter is applicable for the following components: API Log Escalation Log Filter Log SQL Log Thread Log User Log Alert Log Full Text index Log Server Group Log Archive Log DSO Log Plug-in Log Approval Log Assignment Engine Log JAVA Plugin Log Email Engine Log CMDB Engine Log CMDB Service Log Flashboards Log When the Common-Logging-Root-Path parameter is set for AR System server and only the C Plug-in log is enabled, the C Plug-in log is not created because the directory is not created with the C Plug-in log. Therefore, we recommend that you first enable any other log such as API log or SQL log, and then enable the C Plug-in log.	Yes	Centralize Configuration
ConfigFileCheckInterval (Component name: com.bmc.arsys.flashboardServer)	Interval (in seconds) after which the Flashboards server checks for the changes to the server.conf file. Default value: 60 seconds	No	AR System Administration Console > System > General > Flashboard Server Configuration > Config File Check Interval. (See Configuring the Flashboard server settings at a global level.)
Configuration-Name ² (Component name: com.bmc.arsys.server)	Name of the component. AR System server uses this option to identify the active component in the database.	No	AR System Configuration Generic UI form
Create-Entry-DeadLock-Retries ² (Component name: com.bmc.arsys.server)	Number of times to retry the ARCreateEntry() function during deadlock situations. Value is an integer.	No	AR System Configuration Generic UI form
Create-Entry-DeadLock-Retries-Delay ² (Component name: com.bmc.arsys.server)	Delay, in seconds, between each retry of a deadlocked ARCreateEntry() function. Value is an integer.	No	AR System Configuration Generic UI form
Create-Workflow-Placeholders (Component name: com.bmc.arsys.server)	If the place holder forms are missing, this setting determines whether to create a place holder form while importing the shared workflow. Valid values: T—If the form is missing, create the place holder form while importing shared workflow. F—Do not create place holder form while importing shared workflow.	No	AR System Configuration Generic UI form
Crossref-Blank-Password (Component name: com.bmc.arsys.server)	Flag indicating how the system responds when auser'slogonnameis not assigned a password in the User form. Valid values: T—The system tries to validate the password in the Windows server domain (or through the External Authentication API if external authentication is on) or against the UNIX server /etc/passwd file. F—(Default) Blank passwords are not cross-referenced. This option enables you to manage group membership and other support information with AR System while managing passwords with the /etc/passwd file (UNIX) or the server domain security model (Windows).	No	AR System Configuration Generic UI form
Currency-Ratio-Client-Refresh-Interval ² (Component name: com.bmc.arsys.server)	Number of minutes between each refresh of currency conversion ratios on the client.	No	AR System Configuration Generic UI form
Do-customdb-function-validation (Component name: com.bmc.arsys.server.shared)	Flag indicating whether to skip validating custom database functions to be run in BMC Helix ITSM: Smart Reporting . When you set this flag to false, the validation of number of arguments and their respective data types of a custom database function is skipped. Valid Values: T—(Default): Select to validate custom database functions, including validation of the number of arguments and their respective data types. F—Select to skip validation of the number of arguments and their respective data types of a custom database function.	Yes	AR System Administration Console > System > General > Centralized Configuration
D2P-Rollback-Timeout-Interval	Flag indicating timeout for rolling back a deployment package. Default value—48 hours Valid values—48 to 168 hours	Yes
Db-Case-Insensitive ² (Component name: com.bmc.arsys.server)	Flag indicating whether to perform case-insensitive queries on Run If qualifications for active links, filters, and escalations. (For Oracle databases, ensure that this option matches the behavior of your Oracle database so that all queries are consistent.) Valid values: T—Performs case-insensitive search. Setting this parameter in the ar.cfg (ar.conf) file causes special session parameters (NLS_SORT and NLS_COMP) to be set to support case-insensitive searches and invalidate existing database indexes. By default, the AR System server creates regular indexes when you add an index to a form. To support case-insensitive searches on Oracle databases, functional indexes are required instead of regular indexes. To change the AR System server 's default behavior for index creation, set the Db-Functional-Index parameter to T. Then, when a new index is added to a form, the AR System server creates a functional index for the form. This parameter helps to avoid performance degradation that can result from not using database indexes. The Db-Functional-Index parameter is ignored if Db-Case-Insensitive is set to F or if it is absent from the ar.cfg file. The Db-Case-Insensitive and Db-Functional-Index parameters handle new indexes. In the database (outside of the AR System server ), you must manually convert any existing indexes to functional indexes. With AR System , we recommend setting the Oracle-Cursor-Sharing parameter to EXACT if you are using case-insensitive database. F (the default)—Performs case-sensitive queries. For optimal performance when using database indexes for case-insensitive searches on Oracle, make sure that the database administrator sets cursor sharing to EXACT. Depending on the volume of data, creating functional indexes may take a long time.	No	AR System Configuration Generic UI form
Db-Character-Set ² (Component name: com.bmc.arsys.server)	Option that initializes an internal variable that the server uses for various purposes, such as informing the ARGetServerInfo function's AR_SERVER_INFO_DB_CHAR_SET server option request or adjusting the database short column size so that the number of characters in a datum does not exceed the number of bytes in the database field. Valid values: Unicode (UTF-16)—UTF-16 UCS-2 Unicode (UTF-8)—UTF-8 The installer sets this option's value.	No	AR System Configuration Generic UI form
Db-Connection-Retries ² (Component name: com.bmc.arsys.server)	Number of times the AR System server tries to reestablish a lost connection to the database. The default is 100. The server retries the connection once every 15 seconds up to the specified number of times. For example, when this option is set to 100, the server retries the connection once every 15 seconds for a duration of 25 minutes.	No	AR System Configuration Generic UI form
Db-Custom-Conn-Props (Component name: com.bmc.arsys.server)	Use this optional property to set the custom connection properties on a database connection. This property is database-specific. For example, Cipher suites, trustStore. Format Db-Custom-Conn-Props: key1=value1;key2=value2 Example Db-Custom-Conn-Props: encrypt=true;trustServerCertificate=true When you specify the `Oracle-JDBC-URL` parameter, the AR System server ignores this option.	No	AR System Configuration Generic UI form
Db-Host-Name ² (Component name: com.bmc.arsys.server)	Logical server name of the underlying database.	No	AR System Configuration Generic UI form
Db-Max-Attach-Size ² (Component name: com.bmc.arsys.server)	Maximum size (in bytes) of compressed attachments that the AR System server can retrieve from Oracle databases. The default value is 2 GB. This value is limited by your server operating system and configuration. To limit the size of compressed attachments that can be sent to the database server from AR System server , see AR-Max-Attach-Size.	No	AR System Configuration Generic UI form
Db-Max-Text-Size ² (Component name: com.bmc.arsys.server)	(Oracle, Microsoft SQL Server) Maximum size for long character text data in databases. For Oracle databases, this value is also used for memory allocation during the processing of long text data; therefore, use it conservatively. The default for an Oracle database is 4,194,308 bytes. For SQL Server, the default is 2,147,483,647 bytes. The maximum value for either database is 2,147,483,647 bytes.	No	AR System Configuration Generic UI form
Db-name ² (Component name: com.bmc.arsys.server)	For Oracle, the name of the tablespace that the AR System server uses. For all other supported databases, the name of the underlying SQL database. The default value is ARSystem.	No	AR System Configuration Generic UI form
Db-password (Component name: com.bmc.arsys.server)	(Microsoft SQL Server, Oracle) Database password associated with the ARSystem database and table space. The password can be modified by using the ARSetServerInfo function and is stored in encrypted form. If you change the password manually, specify this option by using clear text, and change the password by using the AR System Administration: Server Information form to encrypt it.	No	AR System Configuration Generic UI form
Db-Server-Port ² (Component name: com.bmc.arsys.server)	Defines the database port number.	No	AR System Configuration Generic UI form
Db-Type ² (Component name: com.bmc.arsys.server)	The type of database the AR System server is connecting to. Valid values: sqlserver oracle postgresql	No	AR System Configuration Generic UI form
Db-user ² (Component name: com.bmc.arsys.server)	(Microsoft SQL Server, Oracle) User namethatAR System uses to access the underlying database. The default is ARAdmin.	No	AR System Configuration Generic UI form
Debug-GroupId (Component name: com.bmc.arsys.server)	Name of the group to which a user must belong to use logging options such as API, database, and filter logging in AR System clients. Logging options are disabled for users who are not members of the specified group. The group name can be Public, Administrator,Sub Administrator, or Browser. You can also set this option in the Client-Side Logging Group field on the Log Files tab.	No	AR System Configuration Generic UI form
Debug-mode (Component name: com.bmc.arsys.server)	Bitmask indicating the server logging modes. To activate one bit, set this option to its value (see the following list). 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. Bit 1 (value = 1 )—(SQL databases only) Turns on SQL logging in the default arsql.log file. To specify a different file, use the SQL-Log-File option. Bit 2 (value = 2 )—Turns on filter logging in the default arfilter.log file. To specify a different file, use the Filter-Log-File option. Bit 3 (value = 4 )—Turns on user logging in the default aruser.log file. To specify a different file, use the User-Log-File option. Bit 4 (value = 8 )—Turns on escalation logging in the default arescl.log file. To specify a different file, use the Escalation-Log-File option. Bit 5 (value = 16 )—Turns on API logging in the default arapi.log file. To specify a different file, use the API-Log-File option. Bit 6 (value = 32 )—Turns on thread logging in the default arthread.log file. To specify a different file, use the Thread-Log-File option. Bit 7 (value = 64 )—Turns on alert logging in the default aralert.log file. To specify a different file, use the Alert-Log-File option. Bit 9 (value = 256 )—Turns on server group logging in the default arsrvgrp.log file. To specify a different file, use the Server-Group-Log-File option. Bit 10 (value = 512 )—Turns on logging for full text indexing in the default arftindx.log file. To specify a different file, use the Full-Text-Indexer-Log-File option. Bit 16 (value = 32768 )—Turns on DSO server logging in the default ardist.log file. To specify a different file, use the Distrib-Log-File option. Bit 17 (value = 65536 )—Turns on Approval Server logging. To specify the location for the arapprov.log file, use the Approval Menu > Server Settings > AP: Admin-Server Settings form. Bit 18 (value = 131072 )—Turns on plug-in logging in the default arplugin.log file. To specify a different file, use the Plugin-Log-File option.	No	AR System Configuration Generic UI form
Default-Allowable-Currencies (Component name: com.bmc.arsys.server)	Default allowable currency types for currency fields in clients.	No	AR System Configuration Generic UI form
Default-Functional-Currencies (Component name: com.bmc.arsys.server)	Default functional currency types for currency fields in clients.	No	AR System Configuration Generic UI form
Default-messaging-port (Component name: com.bmc.arsys.server)	Specifies port for JMS (Java Messaging Service) used by Java server for asynchronous communication within server or server group. Default value: 61617	No	System > General > Server Information > Ports and Queues > Message Broker Port. (See .Setting ports and RPC numbers v21.3.)
Default-Order-By ² (Component name: com.bmc.arsys.server)	Flag indicating whether to apply the default sort order to search results. Valid values: T—(Default) Use the default sort order, which is to sort by request ID. F—No default sort order exists, and no order by clause is added to the command if a sort order is not specified.	No	AR System Configuration Generic UI form
Default-Web-Path (Component name: com.bmc.arsys.server)	URL to the directory path for the default web server pointing to the AR System server .	No	AR System Administration Console > System > General > Server Information > Advanced > Default Web Path. (See Setting performance and security options)
Display-Filter (Component name: com.bmc.arsys.server)	Allows display of attachments in a browser. Valid values: 0— No filter. 1—Allow users to view the attached files that have the extensions specified in Display-Ext-List setting. 2—(Default) Disallow users to view attached files that have extensions specified in Display-Ext-List setting.	No	AR System Configuration Generic UI form
Display-Ext-List (Component name: com.bmc.arsys.server)	A list of comma separated attachment extensions that you want to allow to be displayed.	No	AR System Configuration Generic UI form
DisplayTabsInTicketPreview (Component name: arsystem.bmc.arsys.itsm)	This configuration parameter controls if the Activity and Resource tabs are displayed when you a preview a ticket in Smart IT PWA screens. If you set this configuration parameter to T, the Activity and Resource tabs are displayed during ticket preview. If you set this configuration parameter to F, the Activity and Resource tabs are not displayed when you preview a ticket. Default value: T	No	AR System Configuration Generic UI form
Delay-Recache-Time ² (Component name: com.bmc.arsys.server)	Number of seconds before the latest cache is made available to all threads. Valid values: 0 to 3600 seconds. If this option is set to 0, every API call gets the latest cache (that is, the cache is copied for every administrator call). Setting the option to 0 causes slower performance for cache operations. Default value: 5 seconds	No	AR System Administration Console > System > General > Server Information > Configuration > Recache Delay. (See Setting administrative options.)
Dev-Studio-Development-Mode (Component name: com.bmc.arsys.server)	Indicates whether you can use Developer Studio in the Best Practice Mode, Base Mode or both. Valid values: 1—Allows you to work in the Base Mode 2—(Default) Allows you to work in the Best Practice mode 3—Enable both the modes	No	AR System Configuration Generic UI form
Direct-SQL-In-Parent-Transaction	Indicates whether Direct SQL actions can run directly in the parent transaction or a new transaction. Default—True
Direct-SQL-In-Parent-Transaction-Exclusion	Overrides the Direct-SQL-In-Parent-Transaction setting to run Direct SQL actions in a new transaction.
Disable-Admin-Ops (Component name: com.bmc.arsys.server)	Flag indicating whether administrative operations are allowed on the server. Valid values: F—Enabled (Default) T—Disabled If the Server Groups check box is selected, this option is ignored. Server groups can be configured in the AR System server Group Operation Ranking form to make sure that only one server performs the operation. See Configuring server groups.	No	AR System Administration Console > System > General > Server Information > Configuration > Disable Admin Operations. (See Setting administrative options.)
Disable-Admin-Ops-Global (Component name: com.bmc.arsys.server)	Flag indicating whether administrative operations are allowed on all the servers. Valid values: F—Enabled (Default) T—Disabled In a server group environment: This configuration setting is shared among all the servers. If you set this parameter on any of the servers, it will be applicable for all the servers. For non-server group environment, this parameter is same as Disable-Admin-Ops. If you configure this parameter, Disable-Admin-Ops is automatically updated with the same value. You can set the parameter value from the AR System Administration Console using the following steps: Open AR System administration console. Click System > General > Centralized Configuration. Select com.bmc.arsys.server.shared > . The list of already added shared parameters appears. Add new parameter with name Disable-Admin-Ops-Global* and set the value as F or T to enable or disable admin operations. You can also update the parameter usingthesesteps, if it already exists.	Yes	AR System Configuration Generic UI form
Disable-Alerts (Component name: com.bmc.arsys.server)	Flag indicating whether alerts are sent when alert events are created. Valid values: T—No threads are started in the alert queue, and no alerts are sent. F—(Default) Alerts are enabled. Changes to this setting do not take effect until the server is restarted.	No	AR System Administration Console > System > General > Server Information > Configuration > Disable Alerts. (See Setting administrative options.)
Disable-Archive ² (Component name: com.bmc.arsys.server)	Switch that disables (T ) or enables (F ) the archive when the server starts. If the Server Groups check box is selected, this option is ignored. Server groups can be configured in the BMC Remedy AR System Server Group Operation Ranking form to make sure that only one server performs the operation. See Configuring server groups.	No	AR System Administration Console > System > General > Server Information > Configuration > Disable Archive. (See Setting administrative options.)
Disable-Archive-Global (Component name: com.bmc.arsys.server)	Switch that disables (T ) or enables (F - default) the archive when the server starts. In a server group environment: This configuration setting is shared among all the servers. If you set this parameter on any of the servers, it will be applicable for all the servers. For non-server group environment, this parameter is same as Disable-Archive. If you configure this parameter, Disable-Archive is automatically updated with the same value. You can set the parameter value from the AR System Administration Console using the following steps: Open AR System administration console. Click System > General > Centralized Configuration. Select com.bmc.arsys.server.shared > . The list of already added shared parameters appears. Add the parameter with name Disable-Archive-Global* and set the value as F or T to enable or disable archive operations. You can also update the parameter using these steps, if it already exists.	Yes	AR System Configuration Generic UI form
Disable-ARSignals ² (Component name: com.bmc.arsys.server)	Flag indicating whether automatic signals triggered by changes to the following data on a server group's administrative server are disabled: Archive definitions Escalation definitions Group information from the database The signals can be generated by arsignald or the database. Signals triggered by changestouser, licensing,andcomputed groupinformationare not disabled. Valid values: T—The specified signals are disabled. F—(Default) Automatic signaling remains in effect for all object definition changes. To send the disabled signals manually, use the arsignal program (see 2023-10-12_09-06-46_.arsignal.exe or arsignal v21.02). See Signaling mechanism in a server group.	No	AR System Administration Console > System > General > Server Information > Configuration > Disable ARSignals.(See Setting administrative options.)
Disable-Audit-Only-Changed-Fields (Component name: com.bmc.arsys.server)	Flag indicating whether to audit all records (T ), or to audit only those records whose field values have changed (F, the default).	No	AR System Administration Console > System > General > Server Information > Configuration > Disable Audit Only Changed Fields. (See Setting administrative options.)
Disable-Client-Operation ² (Component name: com.bmc.arsys.server)	Option that restricts time-consuming operations (such as reporting) during busy times, improving overall performance. The syntax is `Disable-Client-Operation: <tagNumberToDisable> [[<startTime>]-[<stopTime>]] [<groupIDList>]` The tag number identifies the client whose operations are restricted. It is defined in the ar.h file. See the list at the end of this description. (Optional) To specify start and stop times for the restriction, enter them in 24-hour format (hh:mm ). The times are include times. For example, 00:00-13:59 disables the operations from midnight until 1:59 P.M. If you do not specify a start or stop time, the syntax looks like this: Disable-Client-Operation: 2 18:00- 10 To disable operations from midnight until 6:00 A.M., enter this: Disable-Client-Operation: 2 -6:00 10 If no start and stop times are specified, the operations are disabled all the time. (Optional) The groupIDList is a list of groups whose users can run the operations during the specified time period. For example, you can allow only the administrator to run reports during busy hours. Enter none, one, or multiple group IDs delimited by spaces. For example, to exempt group 10, enter this: Disable-Client-Operation: 1 13:00-17:59 10 If no groups are specified, all users are barred from running the operations during the specified time period. You can enter multiple Disable-Client-Operation lines. Following are the Disable-Client-Operation tag numbers: 1—AR System clients prior to the 5.0 version 2—BMC Remedy Administrator (pre-7.5.00) 4—BMC Remedy Import (pre-7.5.00) 5— Distributed Server Option 6—AR System ODBC Important: ODBC drivers are not supported in SaaS environments. For on-premises deployments, we do not recommend using ODBC drivers. 7— Approval Server 8 ---AR System web server (waserver) 9—Mid tier (version 5.0 and later) 10—Palm Pilot 11— Flashboards 12— Flashboards Mid Tier 13—Enterprise integration 14—arreload 15—arcache 16—ardist 17—runmacro 18—armaild, armailex (pre-5.1) 20—Report creator plug-in 36— Developer Studio 4000—Driver (sample program) 4001—Distributor of application 4002—arhelp 4003—arjanitor 4004—armenu 4005—arstruct 4006—artext 4007—arsqled 4008—archgsel	No	AR System Configuration Generic UI form
Disable-Escalations (Component name: com.bmc.arsys.server)	Switch that disables (T ) or enables (F - default) the escalations when the server starts. If the Server Group Member check box is selected, this option is ignored. Server groups can be configured in the AR System server Group Operation Ranking form to make sure that only one server performs the operation. See Configuring server groups.	No	AR System Administration Console > System > General > Server Information > Configuration > Disable Escalations. (See Setting administrative options.)
Disable-Escalations-Global	Switch that disables (T ) or enables (F - default) the escalations when the server starts. In a server group environment: This configuration setting is shared among all the servers. If you set this parameter on any of the servers, it will be applicable for all the servers. For non-server group environment, this parameter is same as Disable-Escalations. If you configure this parameter, Disable-Escalations is automatically updated with the same value. You can set the parameter value from the AR System Administration Console using the following steps: Open AR System administration console. Click System > General > Centralized Configuration. Select com.bmc.arsys.server.shared > . The list of already added shared parameters appears. Add new parameter with name Disable-Escalations-Global* and set the value as F or T to enable or disable escalations. You can also update the parameter using these steps, if it already exists.	Yes	AR System Configuration Generic UI form
Disable-Hierarchical-Groups	This parameter controls whether the hierarchical group computation is performed or not. For more information see, Controlling access to requests for hierarchical groups. Valid values: T—Stops populating Parent for the Hierarchical groups. F—(Default) Populates Parent for the Hierarchical groups.	Yes	AR System Configuration Generic UI form
Disable-Manage-Process-Operation (Component name: com.bmc.arsys.server)	Prevents performing start, stop, restart process by using the Manage Process tab of the Remedy Management console. This helps prevent any inadvertent restarts of processes. Valid values are True and False (default).	No	AR System Configuration Generic UI form
Disable-New-RLS-Implementation	This parameter improves the performance of SQL queries for applying row level security. Valid values: T —(Default) Turns off New RLS implementation. F—Turns on New RLS implementation. Disable-New-RLS-Implementation has impact only on the rls query. If true, the query is made using or and when false, the query uses regex for dynamic group permissions.	Yes	AR System Configuration Generic UI form
Disable-Non-Unicode-Clients (Component name: com.bmc.arsys.server)	Flag indicating whether Unicode servers can refuse requests from non-Unicode clients (for example, not Mid Tier 7.0.00). This option does not affect non-Unicode servers. Valid values: T—Unicode servers refuse requests from non-Unicode clients. F—(Default) Unicode and non-Unicode clients can contact Unicode servers.	No	AR System Administration Console > System > General > Server Information > Configuration > Disallow Non. (See Setting administrative options.)
Disable-Notifications (Component name: com.bmc.arsys.server.shared)	The flag that you can use to indicate whether you have enabled or disabled all notifications that go out of the AR System server . Valid values: T —All notifications that go out of the AR System server are disabled. F —(Default) All notifications that go out of the AR System server are enabled.	Yes	AR System Configuration Generic UI form
Disable-Process-Timer-Task-Execution (Component name: com.bmc.arsys.server.shared)	This parameter allows users to disable the process timer during migrations. Valid values: T—The process timer is disabled. F—(Default) The process timer is enabled.	Yes	AR System Configuration Generic UI form
Disable-User-Cache-Utilities	Flag that prevents unauthorized users from using User Cache commands. Valid values: T—The arreload and arcache utilities are disabled for the AR System server . F—(Default) Cache utilities are enabled.	No
Dispatch-Log-File	Flag that indicates whether the dispatcher logging is enabled. Valid values: T—The dispatcher logging is enabled. When you enable the dispatcher logging, specify thelogfilename that you want to use. F—(Default) The dispatcher logging is disabled.	No	AR System Configuration Generic UI form
Display-General-Auth-Message ²	Flag indicating whether to display a message when user authentication fails. Valid values: T— (Default) A generic message is displayedforuser name and password errors: `ARERR 623 Authentication failed` `ARERR` `9388` `Authentication failed` F— Each authentication error displays a different message: `ARERR 624 User account locked out due to too many bad password attempts` `ARERR` `9381` `No such user is registered with this server` `ARERR` `9382` `Invalid password or authentication string for existing user` This parameter can be used in conjunction with Max-Password-Attempts. See Configuration settings E-M.	No	AR System Configuration Generic UI form
Distrib-Log-File	Full path name of the file to use if DSO server logging is on (see Debug-mode).	No	AR System Configuration Generic UI form
Domain-Name ²	New domain name portion of the fully qualified server name. By default, a server determines the domain name from the network interface. In rare cases, this method does not produce the desired result because of unexpected network card configurations. In those cases, you can use this option to override the domain name derived from the network interface.	No	AR System Configuration Generic UI form
DSO-Cache-Check-Interval (Component name: com.bmc.arsys.server)	Number of seconds between occurrences of these operations: DSO checks for changes to the source and target forms. Updates of cached DSO mapping information. By default, this option is set to 1800 seconds (30 minutes). The maximum value is 43200 seconds (12 hours).	No	AR System Administration Console > System > General > Server Information > DSO > Cache Check Interval. (See Configuring DSO by using the Server Information form)
DSO-Error-Retry-Option (Component name: com.bmc.arsys.server)	DSO server retry behavior after an error: 0—(Default) Retry after standard connection and transmission errors. 1—Never retry after any error. 2—Retry after every error. 3—Retry after standard connection and transmission errors and after database errors.	No	AR System Administration Console > System > General > Server Information > DSO > Error Retry Option. (See Configuring DSO by using the Server Information form.)
DSO-Host-Name ² (Component name: com.bmc.arsys.server)	Name to use for the From (source) server in distributed mappings. This setting enables you to use an alias for the From server in distributed operations.	No	AR System Configuration Generic UI form
DSO-Local-RPC-Socket (Component name: com.bmc.arsys.server)	RPC program number that DSO uses. This setting is optional.	No	AR System Administration Console > System > General > Server Information > DSO > DSO Local RPC Program Number. (See Specifying passwords and properties for connecting services to the server.)
DSO-Log-Level (Component name: com.bmc.arsys.server)	Level of logging for all DSO logs (ardist.log, ardist.log.default, ardist. poolName .log, and ardist.log. poolName ): 0—Logs only errors. Includes contextual information. 1—Logs errors and warnings. Includes contextual information. 2—Logs errors, warnings, and other information to provide a step-by-step record of DSO activities.	No	AR System Configuration Generic UI form
DSO-Log-Max-Backup-Index ² (Component name: com.bmc.arsys.server)	Number of indexed backup files saved for each DSO Java log file. If you do not specify a value for this option, 5 indexed backups are saved for each DSO Java log file.	No	AR System Configuration Generic UI form
DSO-Main-Thread-Polling-Interval (Component name: com.bmc.arsys.server)	Interval at which the DSO server queries the distributed pending queue for pending distributed items. Enter any integer from 0 (no polling) to 3600 seconds (1 hour).	No	AR System Administration Console > System > General > Server Information > DSO > Polling Interval. Configuring DSO by using the Server Information form
DSO-Mark-Pending-Retry-Flag (Component name: com.bmc.arsys.server)	Flag indicating whether to set the status of items in the DSO distributed pending queue to Retry after an attempt to perform the associated operation fails. (Failure must be due to a recoverable error. Items that fail because of nonrecoverable errors are removed from the queue.) Valid values: T—(Default) Does not set the status to Retry. Instead, the status remains set to New. Depending on the number of pending items that the DSO server processes, this setting might improve the server's performance. F—Sets the status to Retry. Use this to differentiate items in the queue that have never been processed (status = New) from items that were processed but failed because of recoverable errors (status = Retry). Regardless of this option's value, the pending item is retried based on its retry configuration.	No	AR System Administration Console > System > General > Server Information > DSO > Mark Pending Retry. Configuring DSO by using the Server Information form
DSO-Max-Pending-Records-Per-Query (Component name: com.bmc.arsys.server)	Maximum number of records in the Distributed Pending form that DSO reads in a single database query. Minimum value is 1. Maximum value is unlimited. Default: 1000	No	AR System Administration Console > System > General > Server Information > DSO > Max Pending Records Per Query. Configuring DSO by using the Server Information form
DSO-Merge-DupID-Overwrite ² (Component name: com.bmc.arsys.server)	The way the DSO server behaves when it finds a duplicate request ID on the target server. Valid values: T—Updates mapped fields and sets unmapped fields to NULL. F—(Default) Updates only the mapped fields on the target request.	No	AR System Configuration Generic UI form
DSO-Placeholder-Mode (Component name: com.bmc.arsys.server)	Mode that disables the DSO server installed on the same host as the AR System server . Use this when setting up a DSO server outside a firewall to support an AR System server running behind a firewall.	No	AR System Administration Console > Server Information form > DSO tab > Placeholder Mode. Configuring DSO by using the Server Information form
DSO-Polling-Interval (Component name: com.bmc.arsys.server)	Interval (in seconds) at which the DSO server checks the distributed pending queue for pending distributed items. This is used as a backup when no signals are received from workflow. The value can be any integer between 15 and 7200. By default, the backup polling interval is disabled.	No	AR System Administration Console > System > General > Server Information > DSO > Polling Interval. Configuring DSO by using the Server Information form
DSO-Source-Server (Component name: com.bmc.arsys.server)	The AR System server for a DSO server to support when that AR System server is different from the one installed with the DSO server. Use this when setting up a DSO server outside a firewall to support an AR System server running behind a firewall. Use this entry to configure DSO for load balancing.	No	AR System Administration Console > System > General > Server Information > DSO > Source Server. Configuring DSO by using the Server Information form
DSO-Supress-No-Such-Entry-For-Delete (Component name: com.bmc.arsys.server)	Flag indicating whether to log AR System server error 302 (entry does not exist in database) in the arerror.log file when performing distributed delete operations. Valid values: T—Do not log ARERR 302 during distributed deletes. F—(Default) Log ARERR 302 during distributed deletes except when the DSO-Error-Retry-Option is set to 2 (retry after every error). When this option is set to T, errors caused by valid problems might also be omitted from the log.	No	AR System Administration Console > System > General > Server Information > DSO > Suppress No Such Entry Error for Distributed Delete. Configuring DSO by using the Server Information form
DSO-Target-Connection (Component name: com.bmc.arsys.server)	Information for the target AR System server . Use this format:DSO-Target-Connection: serverName:RPCNumber portNumber	No	AR System Administration Console > System > General > Server Information > Connection Settings > DSO Server > Target connection settings tables. (See Specifying passwords and properties for connecting services to the server.)
DSO-Target-Password (Component name: com.bmc.arsys.server)	Password used to access the target AR System server through the DSO server. Use this format:DSO-Target-Password: serverName:encryptedPassword	No	AR System Configuration Generic UI form
DSO-Timeout-Normal (Component name: com.bmc.arsys.server)	Timeout (in seconds) that the DSO server applies during communication with the AR System server . Enter an integer between 60 (1 minute) and 21600 (6 hours). If no value is specified, the system uses the default timeout (120 seconds).	No	AR System Configuration Generic UI form
DSO-User-Password (Component name: com.bmc.arsys.server)	Password for the local DSO server user.	No	AR System Configuration Generic UI form

^{1. Options you can view (but not set) using the AR System Administration: Server Information form.}

^{2. Options you cannot set or view using the AR System Administration: Server Information form.}

Configuration settings C-D

Comments