ar.cfg or ar.conf options C-D

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.)

The valid value for Cache-Mode is,

0 — (Default)

Note: You should always set the value for Cache-Mode to 0.  

The Development Cache Mode field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)

Note: You should not change the default value for the Development Cache Mode checkbox.

Flag indicating whether the cancel query functionality in a browser is enabled. Valid values:

• 0 — Inactive
• 1 — (Default) Active

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.

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 an error on the next operation that uses the transaction handle.

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 BMC Remedy AR System server.

Specifies the time interval in milliseconds after which the CMDB refreshes its cache in the background.
Default value: 900000
Note: If the value defined for this parameter is less than 60000 milliseconds (60 seconds), the default value is taken.

Specifies the time interval in milliseconds after which the data will be treated as orphaned and the memory can be reclaimed by server.
Default value: 3600000
Note: The value for this parameter should be greater than 60000 milliseconds (60 seconds), if it is not then the default value is taken.

Specifies the time interval in milliseconds to start checking for the orphan data after CMDB server has started.
Default value: 900000
Note: The value for this parameter should be greater than 60000 milliseconds (60 seconds), if it is not then the default value is taken.

Specifies the time interval in milliseconds at which the CMDB server should perform the orphan data checks. To disable this parameter set a value to minus -. For example, -1.
Default value: 300000
Note: The value for this parameter should be greater than 60000 milliseconds (60 seconds), if it is not then the default value is taken.

Specifies the number of backup CMDB log files to be maintained.
Default value: 10

Number of times to retry the ARCreateEntry() function during deadlock situations. Value is an integer.

Default value - 3 (3 retries)

Delay, in seconds, between each retry of a deadlocked ARCreateEntry() function. Value is an integer.

Default value - 0 (Retries happen immediately, without a delay)

Flag indicating how the system responds when a user's logon name is 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).

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. For more information, see Db-Functional-Index.

• F (the default) — Performs case-sensitive queries.

To learn how to enable case-insensitive search for fixed-length text fields in BMC Remedy AR System version 9.x on Oracle, see the BMC Knowledge Base article KA406947.

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

Note: The installer sets this option's value.

Option to change the AR System server's default behavior for index creation. 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. BMC provides an unsupportedOracleFunctionalIndexHelper.bat utility to manage these existing indexes and to convert them from regular to functional indexes. You can find this unsupported utility in the ARServerInstallDirectory\Arserver\api\lib folder.
Due to known issue with Oracle, set cursor sharing to EXACT so that the query optimizer can use functional indexes for LIKE queries. For help, see your database administrator. 

Note: While running the OracleFunctionalIndexHelper.bat utility for existing forms, you might see the following error: 
Error message ERROR (552): The SQL database operation failed.; ORA-00942: table or view does not exist. 
This occurs because indexes are not applicable on vendor, view, display-only, and join forms.

For optimal performance when using database indexes for case-insensitive searches on Oracle, ensure that:

• The database administrator sets cursor sharing to EXACT for the functional indexes that Oracle Optimizer will use (otherwise, performance can be severely degraded due to full table scans).

Note: Depending on the volume of data, creating functional indexes may take a long time.

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.

Note: To limit the size of compressed attachments that can be sent to the database server from AR System server, see AR-Max-Attach-Size.

Defines the type of database the AR System server is connecting to.

Valid values:

• sqlserver

• oracle

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 theEscalation-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-Fileoption.
• 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 theServer-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 11 (value = 1024) — Turns on logging for archiving operation in the default ararchive.log file. To specify a different file, use the Archive-Log-File option.
• Bit 16 (value = 32768 ) — Turns on DSO server logging in the default ardist.log file. To specify a different file, use theDistrib-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 thePlugin-Log-File option.

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.

URL to the directory path for the default web server pointing to the BMC Remedy AR System 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.

The default value is 5 seconds. The recommended value is 300 (5 minutes).

Flag indicating whether administrative operations are allowed on the server. Valid values:

• F — (Default) Disabled
• T — Enabled 
  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.

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.

Switch that disables (T ) or enables (F ) the archive when the server starts.

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 changes to user, licensing, and computed group information are 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 arsignal.exe or arsignal. See Configuring the server group signaling option.)

Flag indicating whether to audit all records (T ), or to audit only those records whose field values have changed (F, the default).

Flag indicating whether escalations are allowed on the server. Valid values: T and F (default). If the Server Group Member 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.)

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.

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.

Flag that indicates whether the dispatcher logging is enabled. Valid value is location to the log file.

To add the parameter, perform the following steps:

1. In a browser, open the BMC Remedy AR System Administration Console, and click System > General > Centralized Configuration.
2. In the AR System Configuration Generic UI form, from the Component Name list,
   select com.bmc.arsys.server > <servername>.
3. Click Add.
4. Enter the name of the setting that you want to add and its value.
   For example, Dispatch-Log-File and the location to the log file.
5. Click Apply and Close.
6. To invoke this setting, restart arserver.
   The armonitor restarts the dispatcher logging and locates the log file on the specified location.
   Or you can kill the Dispatcher process and the armonitor automatically restarts it with logging enabled.
   (Linux/Unix) Terminate the arsvcdsp process.
   (Windows) Terminate the arsvcdsp.exe process.

Flag indicating whether to display a message when user authentication fails. Valid values:

• T— (Default) A generic message is displayed for user name and password errors:
  • ARERR 623 Authentication failed
  • ARERR9388Authentication failed
• F— Each authentication error displays a different message:
  • ARERR 624 User account locked out due to too many bad password attempts
  • ARERR9381No such user is registered with this server
  • ARERR9382Invalid password or authentication string for existing user

This parameter can be used in conjunction with Max-Password-Attempts. (See ar.cfg or ar.conf options E-M.)

The BMC Remedy AR System server to use for the DSO server. By default, the DSO server runs in queues like any other user.

Obsolete. (See Assigning an RPC program number to DSO.)

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).

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.

RPC program number that DSO uses. This setting is optional.

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.

(See BMC Remedy Distributed Server Option logging and Setting log files options.)

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). 
  
  Note: Regardless of this option's value, the pending item is retried based on its retry configuration.

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.

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). 
  
  Note: When this option is set to T, errors caused by valid problems might also be omitted from the log.

Information for the target BMC Remedy AR System server. Use this format:DSO-Target-Connection:serverName:RPCNumber portNumber