Configuration settings N-R

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.

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

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 100. (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 does not malfunction because of this gap, and it should not be considered a defect.

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

(See Setting administrative options.)

Num-Preload-Schema-Segments

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

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

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

(See Setting performance and security options.)

Num-Preload-Threads

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

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.

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

(See Setting performance and security options.)

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

Oracle-Cursor-Sharing ²

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

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

With Remedy AR System, we recommend setting the Oracle parameter Oracle-Cursor-Sharing to EXACT for all 9.x versions if you are using case-sensitive database or case-insensitive database.

No

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

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.

Valid values:

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

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.

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

Number of threads dedicated to handling ARDBC requests from the BMC Remedy AR System server. You must specify a minimum number. Optionally, you can also specify a maximum number (the plug-in server increases the number of threads for a plug-in as needed up to the specified maximum). The syntax is

Plugin-ARDBC-Threads: <minimumNumberOfThreads [<maximumNumberOfThreads>]

Number of threads dedicated to handling AREA requests from the BMC Remedy AR System server. You must specify a minimum number. Optionally, you can also specify a maximum number (the plug-in server increases the number of threads for a plug-in as needed up to the specified maximum). The syntax is

Plugin-AREA-Threads:  <minimumNumberOfThreads> [<maximumNumberOfThreads>]

By default, 1 thread is initiated if this option is not specified.

Note: Plugin-AREA-Threads parameter is used by the C plugin server. This parameter is not used by Java plugin servers. For Java plugin server, you can change the number of threads by changing the value of the numCoreThreads tag in pluginsvr_config.xml file.

Number of threads dedicated to handling BMC Remedy AR System Filter API requests from the BMC Remedy AR System server. You must specify a minimum number. Optionally, you can also specify a maximum number (the plug-in server increases the number of threads for a plug-in as needed up to the specified maximum). The syntax is

Plugin-Filter-API-Threads:  <minimumNumberOfThreads> [maximumNumberOfThreads>]

By default, 1 thread is initiated if this option is not specified.

Note: Plugin-Filter-API-Threads parameter is used by the C plugin server. This parameter is not used by Java plugin servers. For Java plugin server, you can change the number of threads by changing the value of the numCoreThreads tag in pluginsvr_config.xml file.

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

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.

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

(See Setting ports and RPC numbers.)

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.

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)

Record-Object-Relationships

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

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.

Valid values:

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

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

(See Setting administrative options.)

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.

Register-With-Portmapper

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

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.

Valid values:

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

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

(See Setting ports and RPC numbers.)

Remedy-App-Service-Password

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

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

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

(See Setting server passwords, RPC options, and plug-in timeouts.)

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

RMIRegistryPort

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

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.

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

(See Setting ports and RPC numbers.)