Configuring BMC Remedy Distributed Server Option
Important
The Distributed Server Option (DSO) is available only for on-premises deployments.
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
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:
- Setting up DSO
- Enabling DSO on an AR System server
- Configuring a password for the DSO user
- Assigning an RPC program number to DSO
- Configuring remote AR System servers for DSO
- Configuring DSO for firewalls
- Specifying a DSO host name
- Configuring the RPC timeout setting
- DSO for load balancing
- AR System Administration - Server Information form - DSO tab
Comments
Log in or register to comment.