Configuration settings N-R

Next-ID-Commit ²

(Component name: com.bmc.arsys.server)

Flag indicating whether to perform a new commit transaction when the system generates the next ID for a record in the database.

Valid values:

• T—Perform a new commit transaction. To increase efficiency and for debugging, use this value.
• F—(Default) Include the transaction to generate the next ID in the create entry transaction.

Next-ID-Block-Size replaced Next-ID-Commit, but Next-ID-Commit is available for backward compatibility.

System > General > Server Information > Configuration > Next Request ID Block Size.

(See Setting administrative options.)

Notification-Web-Path

(Component name: com.bmc.arsys.server)

System > General > Server Information > Advanced > Number of Preload Segments.

(See Setting performance and security options)

System > General > Server Information > Advanced > Number of Preload Threads.

(See Setting performance and security options.)

Num-selector-threads ²

(Component name: com.bmc.arsys.server)

Defines the number of threads that can be used to monitor all the live client socket connections for IO activity. When the thread detects any activity, it forwards the call to the appropriate queue.

Default value: 1 

System > General > Server Information > Ports and Queues > Number of Selector Threads.

(See Setting ports and RPC numbers.)

Oracle-Bulk-Fetch-Count ²

(Component name: com.bmc.arsys.server)

Oracle-Clob-Storage-In-Row

(Component name: com.bmc.arsys.server)

(Oracle databases only) Flag controlling Oracle CLOB storage.

Valid values:

• T—CLOBs are created "in row." In-row CLOBs can degrade CPU performance.
• F—(Default) CLOBs are created "out row." Out-row CLOBs can cause the database to grow rapidly.

No

Oracle-Search-On-Clob ²

(Component name: com.bmc.arsys.server)

Flag indicating whether CLOBs can be searched.

Valid values:

• T—(Default) Allow searches on CLOBs. When a search is performed, the qualification can include all the diary and character fields stored in the database as CLOB columns. Including these fields affects performance, and indexes cannot be used for this type of query.
• F—Searching on diary and character fields stored in the database as CLOB columns returns an error.

CLOBs can use the operator LIKE, but not =.

Oracle-SID ¹

(Component name: com.bmc.arsys.server)

Oracle-Service ¹

(Component name: com.bmc.arsys.server)

Oracle-Use-Bind-Variables-In-Case-Insensitive-DB

(Component name: com.bmc.arsys.server.shared)

Determines if select queries to the database should execute with variable binding if the Db-Case-Insensitive setting is enabled.

Valid values:
(Default) 0 = Never use a prepared statement (variable binding) for impacted select queries
1 = Do not use a prepared statement (variable binding) for the LIKE operator
2 = Always use a prepared statement (variable binding).

You must restart the AR System  after you modify the value of this setting.

Overlay-mode ²

(Component name: com.bmc.arsys.server)

Per-Thread-Logging

(Component name: com.bmc.arsys.server)

Flag indicating whether to create per-thread log files.

Valid values:

• T—Create per-thread log files.
• F—(Default) Do not create per-thread log files.

Peer-listener-port ¹

(Component name: com.bmc.arsys.server)

Defines the port number where all the cache instances from different servers communicate with each other.

Default value: 40001

System > General > Server Information > Ports and Queues > C ache Peer Listener Port.

(See Setting ports and RPC numbers.)

Defines the remote object port number where all ehcache instances from different servers communicate with each other.

Default value —40002

Plugin-ARDBC-Threads ²

Plugin-Log-File

(Component name: com.bmc.arsys.server)

Option that specifies the type of information printed to plug-in log files.

Valid values:

• 10000—No information (ARPLUGIN_OFF ).
• 1000—(Default) Only severe messages (ARPLUGIN_SEVERE ).
• 900—Severe and warning messages (ARPLUGIN_WARNING ).
• 800—Status, severe, and warning messages (ARPLUGIN_INFO ).
• 700—Configuration, status, severe, and warning messages (ARPLUGIN_CONFIG ).
• 600—Internal exceptions (ARPLUGIN_FINE ).
• 500—Trace logs that log tasks as they are executed (ARPLUGIN_FINER ).
• 400—Code-level information (ARPLUGIN_FINEST ).
• 100—All log information (ARPLUGIN_ALL ).

Plugin-Loopback-RPC-Socket ²

(Component name: com.bmc.arsys.server)

System > General > Server Information > Ports and Queues > Plugin Loopback RPC Program Number.

(See Setting ports and RPC numbers.)

Plugin-Password

(Component name: com.bmc.arsys.server)

Postgres-Index-Concurrently-Max-Retries

(Component name: com.bmc.arsys.server.shared)

This property is available only if the Enable-Non-Blocking-Index-Build property is set to True.

The maximum number of attempts to perform create or drop index operations on the  PostgreSQL database.

Default value — 3

Postgres-Index-Concurrently-Retry-Interval

(Component name: com.bmc.arsys.server.shared)

This property is available only if the Enable-Non-Blocking-Index-Build property is set to True.

The maximum time interval between two attempts of create or drop index operations on the  PostgreSQL database.

Default value — 5000 milliseconds

Postgres-Sort-Null-First

Preference-Server-Option

(Component name: com.bmc.arsys.server)

Option that specifies whether users must use centralized preferences.

Valid values:

• 1—Users can choose to use a preference server if one is available.
• 2—Users must use the specified preference server.
• 3—Users must use a preference server, but they cannot use this server as a preference server. If users choose a server that is not a preference server, a warning is returned.

Preferred-User-Locale

(Component name: com.bmc.arsys.server)

Sets the global locale for all users of the tenant. It takes precedence over user locale set by using My Preferences and browser locale.

When the global locale is not set, the user's locale from the My Preferences setting is applied, If none of the preferences are defined, then the browser locale is used for the user session.

If the user logs in to BMC Helix Innovation Studio by using multiple sessions and updates the locale by using the Preferred-User-Locale or My Preferences > Preferred Language setting, the locale is set only after the user logs out from all the active sessions. 

• Default—Browser locale
• English—en
• French—fr
• German—de
• Italian—it
• Chinese—zh_cn
• Korean—ko
• Portugese—pt_br
• Russian—ru
• Japanese—ja
• Spanish—es
• Dutch—nl
• Swedish—sv
• Danish—da
• Norwegian—no

Process-History-Level

(Component name: com.bmc.arsys.server)

Controls whether to enable or disable the activity history of a process instance.

If Process-History-Level is set to 0, the process start time and end time will be the same. For instances that are still active, the create date of the Process Context record is the start time and its end time will be null.

Valid values:

• 0—None
• 1—Enable at activity level
• 2—(Default) Enable at audit level

Process-Log-File

(Component name: com.bmc.arsys.server)

Full path name of the file to use if PROCESS logging is on.

Following is the default file where the log entries are created:

arprocess.log

Private-RPC-Socket

(Component name: com.bmc.arsys.server)

RPC program number that determines the type of queue to which requests are routed and the number of threads running on that queue.

System > General > Server Information > Ports and Queues > Server Queue.

(See Setting ports and RPC numbers.)

Private-RPC-Socket (for debug queue)

(Component name: com.bmc.arsys.server)

RE-Log-File-Location ²

(Component name: com.bmc.arsys.server)

System > General > Server Information > Configuration > Record Object Relationships.

(See Setting administrative options.)

Record-Server-Events

(Component name: com.bmc.arsys.server)

Server events to log in the Server Events form, which makes server-related changes available to workflow and API programs. Enter the following values, separated by semicolons, for the events to record.

• 1—Form
• 2—Field
• 3—Menu
• 4—Filter
• 5—Import
• 6—Active link
• 7—Escalation
• 8—View
• 9—Container
• 10—User
• 11—Group
• 12—Server setting
• 14—Archive
• 15—Server group actions

For example:Record-Server-Events: 4;8;9;12;14; For information about the Server Events form, viewing recorded server events, and using server events in workflow, see Capturing server events for workflow or API calls.

Register-With-Portmapper

(Component name: com.bmc.arsys.server)

System > General > Server Information > Ports and Queues >  Register with Portmapper.

(See Setting ports and RPC numbers.)

Registry-Admin-Password

(Component name: com.bmc.arsys.server)

Registry-Admin-User

(Component name: com.bmc.arsys.server)

Registry-Location

(Component name: com.bmc.arsys.server)

Remedy-App-Service-Password

(Component name: com.bmc.arsys.server) 

System > General > Server Information > Connection Settings > Application Service Password.

(See Specifying passwords and properties for connecting services to the server.)

Required-Field-Identifier

(Component name: com.bmc.arsys.server)

Character to add to the label of a field whose entry mode is Required. The default is an asterisk.

Required-Field-Identifier-Location

(Component name: com.bmc.arsys.server)

Position to add the character that identifies a Required field.

Valid values:

• 0—Add the character to the beginning of the field label.
• 1—(Default) Add the character to the end of the field label.

System > General > Server Information > Configuration > Required Field Identifier.

(See Setting administrative options.)

Rest-Authentication-Token-Timeout

(Component name: com.bmc.arsys.server.shared)

Restrict-Logging

Controls which type of logging restriction is enabled. The value of the Restrict-Logging parameter depends on the combination of logging restrictions that you select. Possible values of the restriction parameters are as follows:

• Users—1
• Client Type—2
• RPC Queues—8

You can have combinations of Users, Client Type, and RPC Queues restrictions. For example, if you select Users and Client Type restrictions, the value of the Restrict-Logging parameter is set to 9 (1+8).

The default value of Restrict-Logging parameter is 0. 
The Restrict-Logging parameter has an additional reserved value of 4.

Restrict-Log-Users

(Component name:com.bmc.arsys.server)

A list of semicolon-separated user names. Restricts the logging only for specified users.

For example, Allen;Mike

Restrict-Process-Name-Log

Represents the minimum time required to fetch results from a Row-level Security (RLS) query. The RLS query is logged in the AR System:RLS Autodiscovery form, if th e Subquery algorithm is not enabled on the forms where the RLS query runs.

Default value —5 seconds

Valid value —Integer value > 0

RMIRegistryPort

(Component name: com.bmc.arsys.flashboardServer)

Generates signatures based on the roles and user names.

Valid values:

• 0—(Default and recommended) Sends only one approval signature even if the user has multiple roles.
• 1—Generates duplicate signatures for the same user based on the user name and role.
• 2—Generates duplicate signatures for the same user based on the user name-role combination if the user has multiple roles.

This option sets the External Data Representation (XDR) for all clients connecting to the AR System Server. 

Use this option to frame data encoding and for transferring data from clients to the AR System Server.

This operation is performed at layer 6 of the OSI model and is negotiated on the initial connection of a client to the AR System Server.

If you are using any form in encryption, set the value to 450000 to avoid issues that may occur while transferring large files or records.

Default Value: (Not set/visible)

Forces API calls to use the private queue specified for the client type.

Syntax:

RPC-QUEUE-BY-CLIENT-TYPE: Client-Type Private RPC Queue

Example:

RPC-QUEUE-BY-CLIENT-TYPE: 0 390685

System > General > Server Information > Ports and Queues > Client Type to RPC Restriction Mapping.

(See Setting ports and RPC numbers.)

Allowlists all commands that are trusted and can be safely executed by using the Run Process action. The Run-Process-Command-WhiteList setting includes the following list of out-of-the-box commands:

"../artools/arexport.sh" | "./artools/arexport.bat" | "pdp.sh" | "./artools/pdp.bat" | "remoteaction/remoteaction.sh" | "remoteaction\remoteaction.bat" | "DMLDataImport.bat" | "DMLDataImport.sh" | "../AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.cmd" | "../AtriumCore/cmdb/utils/DashboardDataGenerator/rundashboardutil.sh" | "/opt/bmc/ARSystem/db/mkdir.sh"

Important:

• To update the commands in the list, contact BMC SaaS Operations. 

• To add a command to this setting, select the executable part of the command mentioned in the object along with double-quotes.

Controls the allowlisting of environment variables available to processes that run in a filter action. The environment variables in the allowlist are separated by a pipe character (|)

The default environment variables are as follows:

• "AC_BASE_FOLDER"
• "APP_HOME"
• "AR_BASE_FOLDER"
• "AR_SERVER_NAME"
• "BMC_AR_SYSTEM_HOME"
• "BMC_JAVA_HOME"
• "HOME"
• "HOSTNAME"
• "JAVA_HOME"
• "LANG"
• "PATH"

The hard-coded environment variables that you cannot use even if they are a part of allowlist are as follows:

• "AR_DB_NAME"
• "AR_DB_SERVER_NAME"
• "AR_SERVER_APP_SERVICE_PASSWORD"
• "AR_SERVER_DB_PORT"
• "AR_SERVER_DB_TYPE"
• "AR_SERVER_DB_USER_PASSWORD"
• "AR_SERVER_DB_USERNAME"
• "AR_SERVER_DSO_USER_PASSWORD"
•  "AR_SERVER_JAVA_OPTS"
• "AR_SERVER_MIDTIER_SERVICE_PASSWORD"
• "CARTE_SVR_JAVA_OPTS"
• "FTS_ELASTIC_HOST"
• "FTS_ELASTIC_SEARCH_PORT"
• "FTS_ELASTIC_SEARCH_SECURE"
• "FTS_ELASTIC_SEARCH_USER_PASSWORD"
• "FTS_ELASTIC_SEARCH_USERNAME"