Enabling DSO on an AR System server
The information in this topic is applicable only for on-premises deployments.
- Add an AR Distributed Server license to the AR System server.
For information about licensing servers, see Licensing-overview. Uncomment the following Distributed Server Option entry in the armonitor configuration file:
The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.
By default, the armonitorconfiguration file is in this location:- (UNIX) /etc/arsystem/serverName/armonitor.conf
- (Windows) ARSystemServerInstallDir\Conf\armonitor.cfg
- Restart the AR System server.
The following items are now available in your system:- DSO settings on the Administration: Server Information form
- DSO editors in Developer Studio:
- Distributed Mapping editor—Used to create and maintain distributed mappings. See Distributed-mapping.
- Distributed Pool editor—Used to create and maintain distributed pools. See Distributed-pools.
- DSO forms on the AR System server:
- Distributed Pending form—Lists pending distributed transfers, updates, returns, and deletes. See Monitoring-and-managing-pending-distributed-operations.
- Distributed Pending Errors form—Lists failed pending distributed operations. See Monitoring-and-managing-pending-distributed-operations.
- Distributed Mapping form—Used to store definitions of distributed mappings. Normally, you do not need to access this form.
- Distributed Logical Mapping form—Used to create and store the definitions of logical and physical names. See Creating-and-modifying-logical-mappings.
Distributed Pool form— Used to store definitions of distributed pools. Normally, you do not need to access this form.
You can transfer entries in the Distributed Mapping and Distributed Pool forms to their counterparts on remote servers. See Setting-up-broadcast-distributed-transfers.
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*