ar.cfg or ar.conf options E-M

Obsolete in version 5.1.0 and later.

Flag indicating whether log files display complete lines into log files or not. Values are:

• T — AR System server logs complete lines into log files without truncation.
• F — (Default) AR System server logs only 4093 characters per line, including the header information.

For more information, see BMC Knowledge Base article KA308638.

Integer indicating the encryption algorithm of the data key. Use the following values.

Standard Security

• 1 — 56-bit DES using CBC mode (default)

Performance Security

• 2 — 128-bit RC4 key (default)
• 6 — 128-bit AES CBC key (FIPS noncompliant)
• 8 — 128-bit AES CBC key (FIPS compliant)

Premium Security

• 3 — 2048-bit RC4 key (default)
• 7 — 256-bit AES CBC key (FIPS noncompliant)
• 9 — 256-bit AES CBC key (FIPS compliant)

For more information, see the Encryption Security section.

Integer indicating the encryption algorithm of the public key. Values are

• 4 — 512-bit RSA key (default for Standard Security)
• 5 — 1024-bit RSA key (default for Performance Security)
• 6 — 2048-bit RSA key (default for Premium Security)

For more information, see the Encryption Security section.

Integer indicating whether encryption is on or off. Values are

• 0 — (Default) Optional: Clients with and without encryption installed can communicate with the server. Network traffic is encrypted only if the client supports the server encryption configuration. Otherwise, network traffic is exchanged in plain text.
• 1 — Required: Only clients with encryption installed can communicate with the server. The encryption level installed on the client (standard, performance, or premium) must be compatible with the encryption algorithms used by the server.
• 2 — Disabled: Whether encryption is installed on a client or not, communication with the server is not encrypted. Network traffic is exchanged in plain text.

For more information, see the Encryption Security section.

Size of the hash table that holds the encrypted session information. The default is 509; there is no maximum.

Integer value controlling the diagnostic output when the server crashes. Values are

• 0 — AR_EXCEPTION_DIAG_ALL ; includes all diagnostic output when an exception occurs.
• 1 — AR_EXCEPTION_EXCLUDE_STACK ; excludes the stack trace in the diagnostic output when an exception occurs.

Flag used by AR System during external authentication. Values are

• 0 — (Default) Users are authenticated when a match exists between every LDAP group to which a user belongs and a corresponding group in AR System.
• 1 — Users are authenticated when any single LDAP group to which a user belongs matches a group in BMC Remedy AR System. Excess LDAP groups are ignored.

This option can be used with the External-Authentication-Group-Mapping option.

Bit mask that specifies the return data capabilities for the current AREA plug-in. This option does not control the AREA plug-in; it merely describes the behavior of the plug-in, enabling server optimization. Values are

• 0 — (Default) The server tries to retrieve this information from AREA.
• Bit 1 (value = 1 ) — No email address is provided.
• Bit 2 (value = 2 ) — No notify mechanism is provided.
• Bit 3 (value = 4 ) — No group identifiers are provided.
• 7--The server potentially can reduce the number of AREA related calls during notification processing.
• Bit 4 (value = 8 ) — No license information is provided.
• Bit 5 (value = 16 ) — No notification user validation should occur. This enables the server to avoid using AREA for notification user validation and information retrieval. Use this setting for sites using a form of AREA that applies user names as email addresses and where accessing an authentication database provides no benefit.

Maximum number of recursion levels allowed for an operation. The data modification performed by an AR_FILTER_ACTION_FIELDP filter action might trigger a second set, or level, of filters, one of which might trigger a third level of filters and so on. This option limits the number of times such recursion can happen, preventing the server crash that would occur if the recursion continued indefinitely. The default value is 25.

Maximum number of filters that the server executes for a given operation. The default value is 10000.

Flag indicating whether logged lines are buffered or written directly to disc. Values are:

• T — (Default) Logged lines are written to disc.
• F — Logged lines are buffered.

Flag indicating whether full text searching is case sensitive or case insensitive. This setting affects all fields indexed for full text search and affects how the indexes are built. Therefore, changes to this setting trigger an automatic re-index. Values are

• 0 — Full text search is case sensitive
• 1 — (Default) Full text search is case insensitive

Location in the file system where search engine index files are stored.

Location in the file system where search engine configuration files are stored.

Note: If you change the directory in this option, update the pluginsvr_config.xml file with the correct directory path. This file is in ARSystemInstallDir\pluginsvr\fts.

Flag indicating whether the server processes pending indexing tasks. Values are

• T — Disable indexing. Pending indexing tasks are recorded for processing later when indexing is enabled.
• F — (Default) Do not disable indexing.

Flag indicating whether the server uses the full text search engine for searching. Values are

• T — Disable the full text search engine. The server uses the search capability of the underlying database whether or not a user has a full text license.
• F — (Default) Use the full text search engine.

Full-Text-Index-Commit-Interval

(This option is added in Patch 1 for version 9.0.00)

Time, in milliseconds, used by the FTS Lucene index commit thread to decide the interval after which an index for an entry is committed in Lucene collections folder.

Default value is 60000 milliseconds (or 1 minute).

For example, consider Lucene commit thread runs at 10:45:23 AM. If the first entry is created at 10:45:24 AM, the second entry is created at 10:45:45 AM and the third entry is created at 10:46:21 AM. Then all the three entries are committed to Lucene collections folder at 10:45:23 AM; that is 1 minute after the last entry is created.

Note: If the value of the Full-Text-Index-Commit-Interval is set to less than 2000 milliseconds (or 2 seconds), then the default value is set to 2000 milliseconds (or 2 seconds).

Full-Text-Index-Scheduler-Interval 

(Starting from BMC Remedy AR System 9.0 Service Pack 1)

Default value: 120000 milliseconds (120 seconds)

If the Full-Text-Index-Scheduler-Interval is set to a value less than 60000 milliseconds (1 minute), the Full-Text-Index-Scheduler-Interval is reverted to a default value of 60000 milliseconds.

Number of minutes that the server waits between periodic attempts to index entries that failed to index for an unexpected reason in a prior attempt. The default value is 60 minutes.

The way the server modifies qualifications from the client. Values are

• 0 — Force leading and trailing wildcards.
• 1 — Ignore leading and force trailing wildcards.
• 2 — Ignore leading wildcards.
• 3 — Remove leading and trailing wildcards.
• 4 — (Default) Leave query unchanged.

The maximum number of search results returned from the search engine. The default value is 10,000. To limit the number of search results (because of constraints on the computer where the search engine is running), reduce the threshold. If you change this option, you must restart the BMC Remedy AR System server for the change to take effect.

During the processing of search results, the server combines results from subqueries to arrive at the final result set. If the number of rows created during processing exceeds this value, the server returns an error message indicating the search is too complex. The default value is 1,000,000.

While processing search results, the server creates a temporary table if the number of FTS matches reaches this value. If the number of FTS matches is under this value, the server uses the SQL IN operator for a query on an existing table. The default value is 200.

(Server groups only) Number of seconds before a signal is sent to the server that owns the full text indexing operation (if no signal is pending). When a server is not the owner of the full text indexing operation and generates indexing work, that server signals the server that is the owner of indexing. To reduce the frequency of signals sent, the signaling is conducted on a delayed basis. When indexing is generated, the server checks whether a signal is pending. If a signal is pending, the server does not need to take any action. If a signal is not pending, the server creates a pending signal to be sent in the specified amount of time. If the full text signal delay configuration value is changed, the duration of any pending delay interval does not change. The change takes effect the next time a delay interval is started. The default number of seconds for Full-Text-Indexer-Signal-Delay is 10 seconds. The minimum is 1 second; there is no maximum.

Flag indicating where to format the GetListEntry date. This option is used mainly for backward compatibility purposes. Values are

• T — Format date on server.
• F — (Default) Format date on client.

Flag indicating whether guest users receive a restricted read license when they log in to BMC Remedy AR System. Values are

• T
• F

If this option is not specified, guest users receive a read license.

Path to the systemwide default home page. This home page is used only if

• The current server is designated as the server for the home page in the BMC Remedy AR System User Preference form.

Or

• The current server is designated as the home page server on the General Settings page in Mid Tier Configuration Tool (See Configuring the General Settings page.)

And

• No home page is specified in the BMC Remedy AR System User Preference form.

Note: If the home page is deleted, this option is cleared, and the default home page must be reentered.

Number of shared, linked lists that hold all user-related information. This number must be a power of 2. The default setting is 128. The minimum number is 2. There is no maximum.

Note: BMC Remedy AR System does not verify that this number is a power of 2. If the number is not a power of 2, the AR System server might behave in unexpected ways.

Time, in minutes, that the AR System server waits before removing inactive user instances from its internal memory cache. Use this option in an LDAP environment to reduce the frequency of checks against an outside authenticator (if a user's record is in server memory, the server does not need to check the user's password outside the system). The default is 2 hours (120 minutes), and the minimum is 30 minutes.

Note: This value must be greater than or equal to the value of the Floating License Timeout on the AR System Administration: Server Information form's Timeouts tab (by default, 2 hours). If you specify a value that is less than the Floating License Timeout, you will not receive an error. Inactive user instances, however, will not be removed in less than the time specified by the Floating License Timeout. If you do not set this option, the persistence of inactive user instances is controlled by the Floating License Timeout.

Defines the JMX port number that enables administrators to connect to JVM by using Java Messaging Extensions (JMX).

Default value: 61500

Allows you to monitor large memory allocations

Default value 1000000

The installed language packs. Some sample values are

• de — German
• en — English
• es — Spanish
• fr — French
• it — Italian
• ja — Japanese
• ko — Korean
• pt_br — Brazilian Portuguese
• ru — Russian
• zh_cn — Simplified Chinese

A semicolon-separated list of message numbers used to modify the server's default caching behavior for localized system messages.

To cache all localized system messages the first time they are retrieved from the AR System Message Catalog form (the default), do not use this option in the configuration file.

To not cache any localized system messages, use this option without any message numbers, for example:

Localized-Messages-To-Cache:

To restrict the caching of localized system messages to a specific subset of message numbers, use this option with a semicolon-separated list of message numbers, for example:

Localized-Messages-To-Cache: 66;72;302;314

Flag indicating whether the server is running in localized support mode. Values are

• T — Run in localized support mode, and use localized messages if available.
• F — (Default) The server does not search for or use localized strings.

Flag indicating whether to log failed pending distributed operations to the Distributed Pending Errors form. Values are

• T — Log errors to the form.
• F — Do not log errors to the form.

Flag indicating whether to include a list of source entry field/value pairs for errors and warnings in the DSO log files when the DSO log level is set to Error or Warning. Values are

• T — Include the list.
• F — Do not include the list.

Flag indicating whether to create a separate *.bak file or to append to the existing log file. Values are

• T — Append new log information to the existing file.
• F — (Default) Create a *.bak file.

Bitmask indicating the type of information to log in the common log form (AR System Log:ALL). To activate one bit, set this option to its value (values are listed under the Debug-mode option). 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. This option does not apply to the following bits because information about their corresponding applications is not logged to a form:

• Bit 8 (value = 128 ) for ARFORK.
• Bit 16 (value = 32768 ) for the DSO server.
• Bit 17 (value = 65536 ) for Approval Server.
• Bit 18 (value = 131072 ) for the plug-in server.

Bitmask indicating the information to log in predefined forms (for example, AR System Log: API and AR System Log: Filter). To activate one bit, set this option to its value (values are listed under theDebug-mode option). 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. This option does not apply to the following bits because no log form is created for their corresponding applications:

• Bit 8 (value = 128 ) for ARFORK.
• Bit 16 (value = 32768 ) for the DSO server.
• Bit 17 (value = 65536 ) for Approval Server.
• Bit 18 (value = 131072 ) for the plug-in server.

IP address mappings that enable alerts to work through firewalls when Network Address Translation (NAT) is on. You must set up a mapping for each client computer that has access through the firewall where the client IP address is translated from an internal address to a valid external address. In addition, a mapping is required for the AR System server IP address if the host where the server resides is also translated. Here is a multiple line example:

Map-IP-Address: 123.45.67.89 10.5.119.83
Map-IP-Address: 123.45.55.90 10.26.55.65

Maximum number of requests returned by a search. Because users can also specify the maximum number of requests returned through Search Preferences in the BMC Remedy AR System User Preference form, the actual maximum is the lower of these values. The default value is no server-defined maximum.

BMC recommends always setting a value for this parameter as unqualified searches can yield enormous results resulting in unpredictable system behavior.

Maximum number of consecutive bad password retries a user can make. If this option is set to 3, the user has 3 chances to log in. If all 3 attempts have bad passwords, the user account is markedINVALID. Values are 0 (which turns this feature off) and all positive integers.

This parameter can be used in conjunction with Display-General-Auth-Message. (See ar.cfg or ar.conf options C-D. See also the description for error 624.)

For forms that contain hierarchical data, such as manager and employee relationships, the maximum number of levels in the hierarchy that a recursive query retrieves. Values are any integer greater than 0. The default is 25. (See ARGetListEntryWithMultiSchemaFields.)

Maximum number of temporary tables that can exist on an AR System server for a single vendor form. The ARGetListEntryWithMultiSchemaFields function stores data from vendor data sources in these tables. By default, only one temporary table can exist for each vendor form. This setting applies to all vendor forms on the server. It is overridden by the value of an individual vendor form's Maximum Vendor Temp Tables property. Enter any integer greater than 0. (See ARGetListEntryWithMultiSchemaFields.)

Allows you to create maximum eight backup log files. Each log file will be of the size defined in the Max-Log-File-Size parameter.

Default value:8

Allows you to set the size of backup file.

Default value: 134217728  

Password that administrators use to access the mid tier.

Oldest API version with which the server communicates. The default value is 0, which means that the server communicates with all API versions. If the client's API version is less than the specified value, the server refuses to talk with the client, and the client receives a decode error. (A AR System client is any program that accesses the AR System server through API calls, for example, BMC Remedy Developer Studio, plug-ins loaded by the plug-in server, and so on.)

Flag indicating whether other AR System servers can run on this server's host computer. Values are

• T — (Default) Other servers can run on this server's host computer.
• F — Other servers cannot run on this server's host computer.

To run multiple servers on the same host computer, this option must be set to T in the configuration file of each server.

Note: To add a 7.5.00 or later AR System server to an environment in which a 7.1.00 or earlier AR System server is already installed, you must first change the value of this option from F toT. Otherwise, the 7.5.00 or later server installation will fail.

Flag indicating whether multiple assignee groups can be stored in row-level security field ID 112. This enables users from multiple groups to access the same request. In the past, only one group could be stored in Field 112. Values are

• T — (Default) Allow multiple groups in field ID 112.
• F — Do not allow multiple groups in field ID 112.

is-ZDT

(Starting from BMC Remedy AR System 9.0 Service Pack 1)

You need to add this parameter to perform zero downtime upgrade of the platform components.

• T — Allows zero downtime upgrade.