This documentation supports the 21.05 version of Action Request System.
To view an earlier version, select the version from the Product version menu.

Configuring DSO by using the Server Information form

The information in this topic is applicable only for on-premises deployments.

Many of the DSO server configuration tasks are performed in the DSO tab in the AR System Administration: Server Information form.

Best Practice

BMC recommends using the AR System Management Console to manage the DSO options. For more information, see Setting global-level and local-level configurations for a server group.

Important

The AR System Administration: Server Information form shows the local level value of the configuration. If a local value does not exist, the form displays the global level configuration. If you modify the value on this form, the local level configuration value is modified.

For example, if a configuration shows global level value and you modify the value by using this form, the local level value gets created for the configuration.

The fields in the DSO tab are described in the following table: 

FieldDescription
Source Server

Specifies the 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 the firewall. The corresponding AR System server configuration file entry is DSO-Source-Server. See Configuring DSO for firewalls.

Polling Interval

Specifies the interval 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). The corresponding AR System server configuration file entry is DSO-Main-Thread-Polling-Interval. When a polling interval is specified, the DSO server does not receive real-time signals from workflow.

Backup Polling Interval

Specifies the interval (in seconds) at which the DSO server checks the distributed pending queue for pending distributed items.

This is used only as a backup in case an issue causes the DSO server to receive no signals from workflow. Unless an issue occurs, the DSO server continues receiving real-time signals from workflow when this option is enabled. The server does not become a polling server. The value can be any integer between 15 and 7200. By default, the backup polling interval is disabled. The corresponding AR System server configuration file entry is DSO-Polling-Interval.

API Timeout Normal

Specifies the timeout (in seconds) that the DSO server applies during communication with the AR System server .

Enter an integer between 60 (1 minute) and 21600 (6 hours). If you enter a value out of range, the closest in-range value is used. If you do not enter a value, the system uses the default timeout (120 seconds). The corresponding AR System configuration file entry is DSO-Timeout-Normal. See Configuring the RPC timeout setting.

Cache Check Interval

Specifies the number of seconds between occurrences of these operations:

  • Checks by DSO 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). The corresponding AR System server configuration file entry is DSO-Cache-Check-Interval. See Setting the distributed mapping cache refresh interval.

Error Retry Option

Specifies how the DSO server responds to errors.

Valid values are:

  • 0 (default)Retry after standard connection and transmission errors.
  • 1Never retry after any error.
  • 2Retry after every error.
  • 3Retry after standard connection and transmission errors and after database errors.

The corresponding AR System server configuration file entry is DSO-Error-Retry-Option.

Max Pending Records Per Query

Specifies the maximum number of records in the Distributed Pending form that DSO reads in a single database query.

Valid values are:

  • Minimum number1
  • Maximum numberUnlimited

If no value is specified, the default is 1000. The corresponding AR System server configuration file entry is DSO-Max-Pending-Records-Per-Query

 Mark Pending Retry

Specifies whether to set the status of items in the DSO distributed pending queue to Retry after an attempt to perform the associated operation fails.

(The failure must be due to a recoverable error. Items that fail due to nonrecoverable errors are removed from the queue.) Valid values are

  • 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 due to recoverable errors (status = Retry).

The corresponding AR System server configuration file entry is DSO-Mark-Pending-Retry-Flag.

Regardless of this option's value, the pending item is still retried based on its retry configuration (see Monitoring and managing pending distributed operations).

Placeholder Mode

When selected, disables the DSO server that was 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. The corresponding AR System server configuration file entry is DSO-Placeholder-Mode. See Configuring DSO for firewalls.

Log Errorsto DSO Pending Errors Form

Specifies whether to log failed pending distributed operations to the Distributed Pending Errors form.

The corresponding AR System server configuration file entry is Log-DSO-Errors-To-Form. To learn how errors affect pending items, see Monitoring and managing pending distributed operations.

Suppress No Such Entry Error for Distributed Delete

Specifies whether to log AR System server error 302 (entry does not exist in database) in the arerror.log file when performing distributed delete operations.

  • When this option is selected, ARERR 302 is never logged during distributed deletes.
  • (Default) When this option is not selected, ARERR 302 is always logged during distributed deletes except when the Error Retry Option is set to 2 (retry after every error).

The corresponding AR System server configuration file entry is DSO-Supress-No-Such-Entry-For-Delete. See Logging the ARERR 302 error during distributed deletes.

When this option is selected, errors caused by valid problems might also be omitted from the log.


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

Comments