This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

To view the latest version, select the version from the Product version menu.

ar.cfg or ar.conf options C-D

This table contains the options for the ar.cfg (ar.conf) file that begin with the letters C and D.

ar.cfg (ar.conf) file options (C-D)

Tips

  • Press F to view the table in full screen mode. Press Esc to exit full screen mode.
  • To easily search for a specific parameter in the below table, select the parameter from the Option list. Alternatively, type the name of the parameter in the Option text box.
    For example, to search for the Cache-Mode parameter, select it from the Option list, or type the parameter name in the Option text box.
  • To search for all parameters having a specific text string in the name, type the text string in the Option text box.
    For example, to search for all Debug parameters, type Debug in the Option 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 ARCreateEntry() in the description, type ARCreateEntry() in the Description text box.

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

The table is being loaded. Please wait for a bit ...

OptionDescriptionMaps to
Cache-Display-Properties 2 

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:

  • 0 — 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.)
  • 1 — No longer supported as a unique option. Defined the same as 3.
  • 2 — No longer supported as a unique option. Defined the same as 3.
  • 3 — (Default) Cache all form-display properties.
 
Cache-Mode 

Flag indicating whether a cache mode optimized for application development is on.
In this mode, user operations might be delayed when changes are made to forms and workflow.
Valid values:

  • 1 — Development cache mode is on.
  • 0 — (Default) Development cache mode is off, and the server is in production cache mode. 
    Note: Development cache mode is intended for a development server, 
    not
     a production server. In this mode, administrative operations cannot begin until
    in-progress user operations are completed. Subsequent user operations are blocked
    until the administrative operation is completed. Hence, the server often gives the false impression that it has stopped responding. (See Configuring a server's cache mode.)
The Development Cache Mode field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Cancel-Query-Option 2

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

  • 0 — Inactive
  • 1 — (Default) Active
 
Changed-By-Another-Check

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.
 
Client-Managed-Transaction-Timeout

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.

The Transaction Timeout (seconds) field in the Transaction Control area on the Advanced tab of the AR System Administration:
Server Information form. (See Setting performance and security options.)
Clustered-Index

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.
 
CMDB-Cache-Refresh-Interval 2Frequency, in seconds, at which the BMC Atrium CMDB cache is refreshed.
The default value is 300 seconds (5 minutes).
For more information about the cache refresh interval, see Setting the cache refresh interval.
 
Configure-Log4j1ndicates whether log4j package should be configured from the external properties file log4j.properties.
Copy-Cache-Logging 

Flag indicating whether the copy-cache logging is enabled. Valid values:

  • T — Copy cache logging is enabled.
  • F — Copy cache logging is disabled.

For more information, see Copy cache logging

Note: Copy-Cache-Logging is used for debugging purpose only.  

 
Create-Entry-DeadLock-Retries 2Number of times to retry the ARCreateEntry() function during deadlock situations. Value is an integer. 
Create-Entry-DeadLock-Retries-Delay 2Delay, in seconds, between each retry of a deadlocked ARCreateEntry() function. Value is an integer. 
Crossref-Blank-Password

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).
 
Currency-Ratio-Client-Refresh-Interval 2Number of minutes between each refresh of currency conversion ratios on the client. 
Db-Case-Insensitive 1

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 8.1 on Oracle, see the BMC Knowledge Base article KA406947.

 
Db-Character-Set 2

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.

 
Db-Connection-Retries 2

Number of times the BMC Remedy AR System server tries to reestablish a lost connection to the database.
The default is 100. The server retries the connection once every 30 seconds up to the specified number of times.
For example, when this option is set to 100, the server retries the connection once every 30 seconds for a duration of 25 minutes.

Note: The AR System server stops responding after 25 minutes (if the default is set to 100). You must manually restart the AR System server once the database is available.

 

Db-Functional-Index1     


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 vendorviewdisplay-only, and join forms.

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

  • The Oracle client is at least version 11.2.
  • 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.

 
Db-Host-Name1Defines the name of the Database Server.
Db-Max-Attach-Size2

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.

 
Db-Max-Text-Size  2(Oracle, Microsoft SQL Server, and Sybase) 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 and Sybase, the default is 2,147,483,647 bytes.
The maximum value for either database is 2,147,483,647 bytes.
 
Db-name 1For 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.
 
Db-password(DB2, Microsoft SQL Server, Oracle, and Sybase) 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.
 
Db-user 1(Microsoft SQL Server, Oracle, and Sybase) User name that AR System
uses to access the underlying database. The default is ARAdmin.
 
DB-Database-AliasDB database alias name for the AR System database. 
DB-Server-NameDB database server name. 
Dbhome-directory 1(SQL databases on UNIX only) Full path name of the home directory for the underlying database. 
Debug-GroupIdName of the group to which a user must belong to use logging options such as API,
database, and filter logging in BMC Remedy 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.
 
Debug-mode 

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 8 (value = 128 ) — Turns on arforkd logging in the default arforkd.log file.
    To specify a different file, use the arfork-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 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.
 
Default-Allowable-CurrenciesDefault allowable currency types for currency fields in clients. 
Default-Functional-CurrenciesDefault functional currency types for currency fields in clients. 
Default-Order-By 2

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.
 
Default-Web-Path

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

The Default Web Path field on the Advanced tab of the AR System Administration: Server Information form. (See Setting performance and security options.)
Delay-Recache-Time  

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

The Recache Delay field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-Admin-Ops

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.
The Disable Admin Operations field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-Alerts

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.
The Disable Alerts field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-Archive 

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

The Disable Archive field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-ARSignals 

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.
The Disable ARSignals field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-Audit-Only-Changed-Fields

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

The Disable Audit Only Changed Fields field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-Client-Operation  2

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.
    For more information on the list of Client types, see List of Client Type ID.

 
Disable-Escalations

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

The Disable Escalations field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Disable-New-RLS-Implementation

This parameter specifies the RLS implementation used. This parameter improves the performance of SQL queries for applying row level security.

Valid values:

  • T — Turns off New RLS implementation.
  • F — (Default) Turns on New RLS implementation.
AR System Configuration Generic UI form
Disable-Non-Unicode-Clients

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.
The Disable Escalations field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
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.
 
Display-General-Auth-Message2

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

 
Distrib-Log-FileFull path name of the file to use if DSO server logging is on (See Debug-mode). 
Distributed-RPC-Socket

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

 
Domain-Name 2New 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.
 
DSO-Cache-Check-Interval

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-Error-Retry-Option

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.
 
DSO-Host-Name 2Name 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.
 
DSO-Local-RPC-Socket

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

The DSO Local RPC Program Number field in the DSO Server area on the
Configuration tab of the AR System Administration: Server Information form.
(See Setting server passwords, RPC options, and plug-in timeouts.)
DSO-Log-Level

Level of logging for all DSO logs (ardist.logardist.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.)

 
DSO-Log-Max-Backup-Index 2Number 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.
 
DSO-Main-Thread-Polling-IntervalInterval 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).
 
DSO-Mark-Pending-Retry-Flag

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.
 
DSO-Max-Pending-Records-Per-QueryMaximum 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.
 
DSO-Merge-DupID-Overwrite 2

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.
 
DSO-Placeholder-ModeMode 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.
 
DSO-Polling-IntervalInterval (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.
 
DSO-Source-ServerThe 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.
Note: Use this entry to configure DSO for load balancing.
 
DSO-Supress-No-Such-Entry-For-Delete

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.
 
DSO-Target-Connection

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

The Target connection settings tables field in the DSO Server area on the
Configuration tab of the AR System Administration: Server Information form. (See Setting server passwords, RPC options, and plug-in timeouts.)
DSO-Target-PasswordPassword used to access the target BMC Remedy AR System server
through the DSO server. Use this format:
DSO-Target-Password: serverName:encryptedPassword
 
DSO-Timeout-NormalTimeout (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).
 
DSO-User-PasswordPassword 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.


This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments

  1. Rudolf Brenner

    Hi. Delay-Recache-Time: "The default value is 5 seconds." In Performance tuning checklists chapter "Tuning the AR System server" I can read: "Set the Delay-Recache-Time option... The recommended value is 300". I suggest to set the default value of an OOTB installation to 300 instead to 5 because 300 is the recommended value. In the meantime the documentation above could be like: "The default value is 5 seconds, the recommended value is 300, see Performance tuning checklists". Thanks.

    Feb 01, 2014 02:32
    1. Aparna Saxena

      Thank you for your comment, Rudolf!

      I've made the changes to the documentation.

      Thanks,

      Aparna

       

      Feb 04, 2014 05:18
  2. Bhupesh Gupta

    DB-Connection-Retries - what if the value is not there in CFG and is it applicable for 7.6.03?

    Aug 28, 2014 07:49
    1. Prachi Kalyani

      Hello Bhupesh,

      Thank you for your comment. I will verify this with the concerned SME and get back to you on this.

      Thanks,

      Prachi

      Aug 29, 2014 12:15
    1. Prachi Kalyani

      Hello Bhupesh,

      Thank you for your comment. The ar.cfg options are also applicable for BMC Remedy AR System version 7.6.03. If the value for any of the ar.cfg option is not set, then the default value for the option is considered.

      Thanks,

      Prachi

      Sep 09, 2014 12:28
  3. Lj Longwing

    The 'Delay-Recache-Time' specifically has a superscript of 2, which states that it CANNOT be set through the Server Information Preferences....but in the description of the option it states "Maps to: The Recache Delay field on the Configuration tab of the AR System Administration: Server Information form. (SeeSetting administrative options.)"

    Doesn't that conflict with itself....if it's available on the Configuration tab, that means it CAN be set, and shouldn't have the superscript 2 on the option name.

    Feb 16, 2015 10:25
    1. Prachi Kalyani

      Hello,

      Thank you for your comment. I have contacted the concerned SME for your query. I will get back to you soon.

      Thanks,

      Prachi

      Feb 17, 2015 04:06
    1. Prachi Kalyani

      Hello,

      Thank you for bringing this to our notice. I have updated the topic.

      Thanks,

      Prachi

      Feb 17, 2015 04:48
  4. Thomas Miskiewicz

    I'm missing Db-Host-Name in this list...

    Aug 28, 2017 06:03
  5. Thomas Miskiewicz

    I'm also missing the Configure-Log4j option

    Aug 28, 2017 06:08
    1. Anagha Deshpande

      Hello Thomas,

      Thank you for bringing this to our notice. I will confirm with the SME and will update the topic.

      Regards,

      Anagha 

      Aug 28, 2017 10:31
      1. Anagha Deshpande

        Hello Thomas,

        I have added the parameters.

        Regards,

        Anagha

        Sep 05, 2017 10:19
  6. Brad Taylor

    KA406947 mentioned in DB-Case-Insensitive does not exist. Perhaps it should be KA 000102992?

    Aug 23, 2018 10:35
    1. Anagha Deshpande

      Hello Brad,

      We are working on this. We will confirm soon.

      Regards,

      Anagha

      Aug 23, 2018 10:44
      1. Anagha Deshpande

        Hello Brad,

        Please refer to the latest documentation here.

        Regards,

        Anagha

        Sep 19, 2018 03:03
  7. Marek Ceizel

    DB-Connection-Retries: Number of times the BMC Remedy AR System server tries to reestablish a lost connection to the database. The default is 100. The server retries the connection once every 30 seconds up to the specified number of times. For example, when this option is set to 100, the server retries the connection once every 30 seconds for a duration of 25 minutes.

    Sorry but I don't get this. Shouldn't that be 50 minutes ? Just to be sure.

    Nov 07, 2019 06:08