Configuring Distributed Server Option


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

You can associate an AR System server with only one Distributed Server Option (DSO) server (ardsoj versionNumber _buildNumber.jar on Windows or UNIX). The associated AR System is the local or source AR Systemto the DSOserver. All other servers, whether they reside on the same host as the DSOserver 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

To set up distributed operations

Perform the steps in the following table to set up distributed operations.

Step

Action

Reference

1

Add a DSO license in the AR System server.

2

Configure a password for the DSOuser.

3

Determine whether you will use RPC program numbers. 

4

Enable the communication between the local DSO server and the remote AR System servers. 

5

Configure DSO for firewalls.

6

Determine whether you want to specify a DSO host name. 

7

Determine whether you want to specify the RPC timeout setting.

8

Determine whether you will need DSO for load balancing. 

 On initialization, the DSO reads the configuration settings from the centralized configuration form. 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 AR System server connection.

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

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*