ar.cfg or ar.conf options C-D

The valid value for Cache-Mode is 0—(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.

The Development cache mode and Production cache mode behave in the same way. The AR System maintains a single copy of cache.
Do not change value for this setting. For this setting, the AR System assumes the value as per the production cache mode. This behavior is true, even if you try to change the setting directly through API.

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.

Specifies the time interval in milliseconds after which the CMDB refreshes its cache in the background.

Default value: 900000

If the value defined for this parameter is less than 60000 milliseconds (60 seconds), the default value is taken.

Frequency, in seconds, at which the BMC Helix CMDB cache is refreshed. The default value is 300 seconds (5 minutes). For more information about the cache refresh interval, see CMDB Engine configuration settings 

Specifies the time interval in milliseconds to start checking for the orphan data after CMDB server has started.

Default value: 900000

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

The value for this parameter should be greater than 60000 milliseconds (60 seconds), if it is not then the default value is taken.

Sets the limit for number of levels of recursion for CMDB graph query.

Specifies the name of the CMDB log file.

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

Defines the name of the component. AR System server uses this option to identify the active component in the database.

 Db-Case-Insensitive  ¹

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 AR System version 9.1 on Oracle, see the BMC Knowledge Base article  KA 000332707.

 Db-Functional-Index  ¹

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.

For more information, see the BMC Knowledge Base article KA 000332707 .

In the database (outside of the AR System server), you must manually convert any existing indexes to functional indexes.

For optimal performance when using database indexes for case-insensitive searches on Oracle, make sure 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).

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

Defines the name of the Database Server.

The Db-Host-Name parameter for all the servers in the server group should be the same. When you specify the Oracle-JDBC-URL parameter, the AR System server ignores this option. For more information, see Setting up an Oracle database.

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.

Db-Max-Text-Size  ²

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.

Defines the database port number.

When you specify the Oracle-JDBC-URL parameter, the AR System serverAR System server ignores this option. For more information, see Setting up an Oracle database.

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

Valid values:

• sqlserver
• oracle

(Microsoft SQL Server and Oracle) User name that AR System uses to access the underlying database. The default is ARAdmin.

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.

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

URL to the directory path for the default web server pointing to the AR System server.

Option that restricts time-consuming operations (such as reporting) during busy times, improving overall performance. The syntax is

• 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. For more information on the list of Client types, see Client-Type-IDs-for-API-programs.

Flag indicating whether Unicode servers can refuse requests from non-Unicode clients. 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 arcache utility is disabled for the AR System server.
• F—(Default) Cache utilities are enabled.

Full path name of the file to use if DSO server logging is on (See Debug-mode).

The 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:

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

DSOserver 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 Distributed-Server-Option-logging and Setting-log-files-options.)

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.

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

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.

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. If no value is specified, the default is 1000.

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.

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.

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.

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.

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. When this option is set to T, errors caused by valid problems might also be omitted from the log.
• F—(Default) Log ARERR 302 during distributed deletes except when the DSO-Error-Retry-Option is set to 2 (retry after every error). 

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

Password used to access the target AR System server through the DSO server. Use this format:DSO-Target-Password: serverName:encryptedPassword

Timeout (in seconds) that the DSO server applies during communication with the AR System server. Enter an integer between60 (1 minute) and 21600 (6 hours). If no value is specified, the system uses the default timeout (120 seconds).

Password for the local DSO server user.

 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.