Enabling DSO on an AR System server
To enable DSO on a BMC Remedy AR System server, follow the given procedure:
- Add an AR Distributed Server license to the BMC Remedy AR System server.
 For information about licensing servers, see Licensing-overview.
- Uncomment the following DSO server entry in the armonitorconfiguration file: - The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. 
 By default, the armonitorconfiguration file is in this location:- (UNIX) /etc/arsystem/serverName/armonitor.conf
- (Windows) ARSystemServerInstallDir\Conf\armonitor.cfg
 
- Restart the BMC Remedy AR System server.
 The following items are now available in your system:- DSO settings on the Administration: Server Information form
- DSO editors in BMC Remedy 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 BMC Remedy AR System server:- Distributed Pending form — Lists pending distributed transfers, updates, returns, and deletes. See Viewing-items-in-the-pending-distributed-queue.
- Distributed Pending Errors form — Lists failed pending distributed operations. See Logging-failed-pending-items.
- 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-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. 
 
 
Related topics
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*
