This documentation supports the 9.0 version of Remedy Action Request System.

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

Configuration settings N-R

The centralized configuration forms store configuration settings as name value pairs in the following format:

<Setting Name>: <Setting Value>

Each setting represents a particular configuration option. The associated value represents the current setting for the option. All numeric values are in a base 10 system. Default behavior occurs either when an option is set to the default value or when the option is not in the centralized form.

You can modify the settings using the AR System Configuration Generic UI form. The settings are case- and space-sensitive. See Updating configuration settings by using the AR System Configuration Generic UI form.

The following table lists the options available for centralized configuration.   

Tip

  • If you cannot view all the columns, click the icon on the top-right corner of the page to open it in full screen mode. Alternatively, use the scroll bar at the bottom of the table.
  • 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 Next-ID-Block-Size parameter, select it from the Option list, or type the parameter name 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 Configuration in the description, type Configuration in the Description text box.

Configuration options (N-R)

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

OptionDescriptionServer group configurationMaps to
Next-ID-Commit 2

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

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

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

No 
Next-ID-Block-Size

Option that allocates next IDs in blocks instead of one at a time. Allocating in blocks increases performance during create operations. Values are any positive number up to 1000. The default value is 25. (A value of 1 disables the feature.) You can also disable it by removing it from the configuration file. You do not need to restart the server for the change to take effect.
This setting is always disabled on the Distributed Pending form so that DSO can operate correctly.

Warning: The use of this option might result in unpredictably large Next-ID sequence gaps. The likelihood of this occurring increases with the use of multiple servers that share a database. The BMC Remedy AR System server will not malfunction because of this gap, and it should not be considered a defect.

NoThe Next Request ID Block Size field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Notification-Web-PathBase URL that appears in email notifications. If this option is not used, the Default-Web-Path option is used. (Notification-Web-Path is available because the Default-Web-Path is specified for other applications such as Flashboards, and it might be different from the mid tier web path for opening requests in a notification.)No 
Num-Preload-Schema-Segments

Total number of preload segments loaded by the preload threads when preload threads are configured. See Setting the Preload Tables Configuration option.

NoThe Number of Preload Segments field on the  Advanced tab of the AR System Administration: Server Information form. (See Setting performance and security options.)
Num-Preload-Threads

Number of preload threads to use when preload threads are configured. A value of 0 indicates that preload threads are not used. The maximum value is 30 or twice the number of preload segments, whichever is lower. See Setting the Preload Tables Configuration option.

NoThe Number of Preload Threads field on the  Advanced tab of the AR System Administration: Server Information form. (See Setting performance and security options.)
Oracle-Bulk-Fetch-Count 2Number of data rows simultaneously fetched from the result set when an Oracle database is queried. The minimum is 1, the maximum is 100, and the default is 50. The higher the value, the more memory is used during data retrieval.No 
Oracle-Clob-Storage-In-Row

(Oracle databases only) Flag controlling Oracle CLOB storage. Values are

  • 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-Cursor-Sharing 2

Database setting that matches the setting in the Oracle initialization file (initARS.ora if the BMC Remedy AR System database SID is ARS). Values are

  • FORCE — Use this value if the initARS.ora file includes the following line: CURSOR_SHARING=FORCE. It is  recommended that you set the initARS.ora setting to EXACT and set Oracle-Cursor-Sharing to EXACT
  • SIMILAR — Deprecated.
  • EXACT — Use this recommended value as BMC Remedy AR System uses the SQL bind variables when interacting with Oracle database server   

    Default value: EXACT  (For AR System 9.0 SP1 and later)

No 
Oracle-Search-On-Clob 2

Flag indicating whether CLOBs can be searched. Values are

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

No 
Oracle-SID  1(Oracle databases only) System ID for the underlying database.No 
Oracle-Two-Task 1(Oracle databases only) Two-task environment setting for the underlying database.No 
Overlay-mode 2

Specifies the default overlay group for the server. Clients that use the default overlay group (all clients other than Developer Studio) will retrieve and use objects from the default group.

  • 0 — Clients will only retrieve and operate on origin objects. Custom objects and overlays of origin objects will not be visible to clients, and the server will execute only origin filters and escalations. In this mode, customizations are ignored.
  • 1 — Clients will retrieve non-overlaid origin objects, overlays, and custom objects. All customizations will be visible, and the server will execute non-overlaid escalations, overlays of escalations, and custom escalations.

See Ignoring overlay and custom objects at runtime.

No 
Per-Thread-Logging

Flag indicating whether to create per-thread log files. Values are

  • T — Create per-thread log files.
  • F — (Default) Do not create per-thread log files.
No 
Plugin 2File name of one or more plug-ins that the plug-in server loads. The file name of the DLL or shared object is provided. The file name might be an absolute file name or might be relative to the BMC Remedy AR System installation directory. Add as many entries for this option to the server configuration file as needed, but specify only one file name in each option.No 
Plugin-Log-FileFull path name of the file to use if plug-in logging is on (see Debug-mode).No 
Plugin-Log-Level

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

  • 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 ).
No 
Plugin-Loopback-RPC-Socket 2

RPC socket number for the private server queue to which loopback plug-in API calls should be directed. Values are in the following ranges:

  • 390621-390634    
  • 390636-390669    
  • 390680-390694    

Loopback plug-ins (such as the Report Creator plug-in) that call back into BMC Remedy AR System use this number to determine the queue to request. By default, plug-in API calls are directed to a queue that corresponds to the call type. To be effective, the server must be configured to have a designated private queue for this option.

NoThe Plugin Loopback RPC Program Number field on the Ports and Queues tab of the AR System Administration: Server Information form.
Plugin-PasswordPlug-in password. If this option is specified, the plug-in server accepts connections only from BMC Remedy AR System servers whose Server-Plugin-Target-Password option is set to the same password. If this option is not specified, the plug-in server accepts connections from BMC Remedy AR System servers that are not configured to use a plug-in password.No 
Plugin-Port 2The port number on which the plug-in server waits for incoming requests.No 
Preference-Server-Option

Option that specifies whether users must use centralized preferences. Values are

  • 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.
NoThe Preference Server Option field on the  Advanced tab of the AR System Administration: Server Information form. (See Setting performance and security options.)
Private-RPC-Socket

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

NoThe Server Queue field on the Ports and Queues tab of the AR System Administration: Server Information form. (See Setting ports and RPC numbers.)
Private-RPC-Socket (for debug queue)Option that designates debug queues. A debug queue is a type of private queue used by the BMC Remedy AR System Workflow Debugger. To make any private queue a debug queue, use this syntax:Private-RPC-Socket: rpcNumber Debug For example: Private-RPC-Socket: 390666 Debug Alternatively, you can make a private queue a debug queue by selecting its Debug check box in the list of queues in the Ports and Queues tab of the Administration Console.No 
RE-Log-File-Location 2Location of the Reconciliation Engine log file.No 
Record-Object-Relationships

Flag indicating whether the BMC Remedy AR System server records the relationships between workflow objects.

Note: If using a server group, all servers within the same server group must have the same setting for this option. If they do not, the servers in the group inconsistently populate and un-populate the object relationship database should they be the highest ranked server for the Administration operation when they are restarted. Only the highest ranked server for the Administration operation in the server group will perform the required object relationship actions when restarted.

Values are

  • T — The server creates entries in a database table to track the relationships between many types of workflow objects.

When you set this option to T and restart the server, it records the relationships of all server objects before it accepts connections from clients. Therefore, the first time you restart the server after selecting this option, you cannot connect to the server with any clent for a period of time, depending on how many objects are defined on the server. With a large number of objects, such as with an ITSM application installed, this could take as long as an hour depending on the performance of the database. (Subsequent server startups are not affected by this setting.) When you can connect, the recording of object relationship data is complete.

  • F — (Default) The server does not record relationships.

When you set this option to F or remove it and restart the server, all the recorded relationships are removed from the database. You must restart the BMC Remedy AR System server before a change to this option takes effect.

Note: BMC recommends that you set this option by using the Record Object Relationships option on the Configuration tab of the BMC Remedy AR System Administration: Server Information form instead of setting it manually in the configuration file. See Viewing and sorting related objects.

NoThe Record Object Relationships field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Record-Server-Events

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 Understanding the Server Events form.

No 
Register-With-Portmapper

Flag that prevents the BMC Remedy AR System server from registering with a portmapper. Use this feature in conjunction with setting specific ports to enable you to run servers on computers that do not have a portmapper. Values are

  • T — (Default) Register with portmapper.
  • F — Do not register with portmapper.

No more than one server should try to register with AR System Portmapper in an environment with multiple servers on one computer.

NoThe Register with Portmapper field on the Configuration tab of the AR System Administration: Server Information form. (See Setting ports and RPC numbers.)
Registry-Admin-PasswordPassword of the BMC Atrium Web Services Registry admin user. Used by workflow for the BMC Remedy AR System Web Services Registry form.No 
Registry-Admin-UserUser name of the BMC Atrium Web Services Registry admin user. Used by workflow for the BMC Remedy AR System Web Services Registry form.No 
Registry-LocationURL of the BMC Atrium Web Services Registry. Used by workflow for the BMC Remedy AR System Web Services Registry form.No 
Remedy-App-Service-Password

Encrypted password that AR System application services such as Approval Server use to access the BMC Remedy AR System server.

NoThe Application Service Password field on the Connection Settings tab of the AR System Administration: Server Information form. (See Setting server passwords, RPC options, and plug-in timeouts.)
Required-Field-Identifier

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

NoThe Required Field Identifier field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)
Required-Field-Identifier-Location

Position to add the character that identifies a Required field. Values are

  • 0 — Add the character to the beginning of the field label.
  • 1 — (Default) Add the character to the end of the field label.
NoThe Required Field Identifier field on the Configuration tab of the AR System Administration: Server Information form. (See Setting administrative options.)

(Starting from Service Pack 1) RPC-QUEUE-BY-CLIENT-TYPE

This option specifies a private queue for a Client type. The option forces the API calls made by the Client Types to use this private queue. The syntax is: RPC-QUEUE-BY-CLIENT-TYPE: Client-Type Private RPC Queue.

For example: RPC-QUEUE-BY-CLIENT-TYPE: 0 390685.

Yes

The Client Type to RPC Restriction Mapping field on the Ports and Queues tab of the AR System Administration: Server Information form. (See Setting ports and RPC numbers.)

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.


Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Jaime Mayol

    Hello Team as per the defect: SW00525637 the parameter RPC-Non-Blocking-IO is no longer applicable since we use the Java code in the AR Server. Please check the defect's details as it states that the docs in 9.x should have been updated.


    Thanks in advance.

    Jaime


    Nov 21, 2017 02:08