Setting up distributed operations

To set up distributed operations, follow this process:

1. Activate DSO and configure it for your distributed environment.
    See Configuring-BMC-Remedy-Distributed-Server-Option.
2. Determine which forms you will transfer data from and which forms you will transfer data to.
3. Determine the amount of control you need over the transferred data:
   • Should one server own master copies of transferred requests, or should all copies be independent?
      See Types of distributed transfers.
   • How often should requests be updated on a server?
      See  the definition for "When to Update" in Creating-distributed-mappings.
   • How should duplicate request IDs be handled?
      See Managing-request-IDs-in-distributed-environments.
   • Will you need to override distributed mapping settings on a per-request basis?
      See Overriding mapping settings on a per-request basis.
4. Determine which distributed fields to add to the forms identified in step 2.
    See Distributed-fields.
5. Add distributed fields to the forms identified in step 2.
    See Adding distributed fields to forms.
6. Determine whether you will use distributed pools.
    See Distributed-pools.
7. (Optional) Create distributed pools according to your analysis in step 3.
    See Enabling-distributed-pools.
8. Determine how to map the forms identified in step 2.
    See Distributed-mapping.

9. Create the required distributed mappings.
    See Creating-distributed-mappings. 

   Warning

   Note

   Unless otherwise noted, this section assumes that you are mapping between two servers. To maintain data integrity on more than two servers, see Chained-and-broadcast-distributed-transfers.

10. Create filters or escalations that define the conditions under which distributed operations occur.
     See Creating-workflow-to-perform-DSO-operations.
11. (Optional) Employ some of these advanced functions:
    • Setting-up-chained-distributed-transfers
    • Setting-up-broadcast-distributed-transfers