Error: Invalid spaceKey on retrieving a related space config.

Configuring BMC Remedy Distributed Server Option

This section explains how to configure BMC Remedy AR System servers for a distributed environment.

For information about BMC Remedy AR System server management, see the Administering and Troubleshooting sections.

A BMC Remedy AR System server can be associated with only one Distributed Server Option (DSO) server (ardsoj versionNumber _buildNumber.jar on Windows or UNIX). To the DSO server, that BMC Remedy AR System server is the local or source BMC Remedy AR System server. All other servers, whether they reside on the same host as the DSO server or on a different host, are considered remote servers.

Each DSO server can transfer data from a form on its local server to

  • Another form on its local server
  • A form on a remote server

Note

Starting from BMC Remedy AR System 9.1, on initialization, the BMC Remedy DSO reads the configuration settings from the centralized configuration form. BMC Remedy DSO does not read the initialization configurations from the ar.cfg file. However ar.cfg file is used only for the parameters (like Server-Name, Server-Connect-Name) required for BMC Remedy AR System server connection.

For more information on BMC Remedy DSO centralized configuration settings, see Configuration settings C-D.

The following topics are covered in this section:

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

Comments

  1. David Still

    Typo:


    BMC Remedy DSO does not reads the initialization configurations from the ar.cfg file. However ar.cfg file is used only for the parameters (like Server-Name, Server-Connect-Name) required for BMC Remedy AR System server connection.


    This should be 'read'

    Apr 24, 2018 12:31