Setting up DSO to synchronize data across multiple AR System servers
The information in this topic is applicable only for on-premises deployments.
() enables you to transfer requests between servers and to keep copies of a request synchronized across multiple servers, even if those servers are geographically dispersed. is available for Windows and UNIX platforms.
When to use
has many uses, including the following:
- Transferring requests to the location where they are processed
For example, suppose your company repairs office furniture. Desks are repaired in San Francisco, and chairs are repaired in Chicago. When a request for a chair repair is submitted to the San Francisco site, can automatically transfer the request to a server in Chicago. If the request needs the attention of a specialist, such as an upholsterer, can transfer the request to a different Chicago server that handles upholstery repairs. Transferring requests between regions in a customer support environment that operates 24 hours a day, 7 days a week
You can configure to forward open requests to another site at the end of each site's business day. For example, suppose your company has customer support centers in San Francisco, Paris, and Tokyo. DSO can forward open requests from San Francisco to Tokyo at the end of San Francisco's business day, from Tokyo to Paris at the end of Tokyo's business day, and so on. This helps alleviate employee down time and increases the speed at which requests are processed.- Creating a distributed knowledge base so that problem-solving information is accessible from any location
For example, you can create filters or escalations that instruct to forward requests closed on one server to all other servers in the environment. All servers then have access to the problem-solving information and solutions contained in the closed requests. - Archiving old requests
If you have a server dedicated to archiving, can send closed requests to the that server.
Before you begin
Get familiar with key concepts. See Manage-distributed-business-requests-by-using-Distributed-Server-Option.
Explore the use cases discussed in Distributed-operation-use-cases.
Process for setting up distributed operations
Step | Action | Reference |
|---|---|---|
1 | If you have not already done so, enable by configuring it for your distributed environment. | |
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: |
|
4 | Determine which distributed fields to add to the forms identified in step 2. Add distributed fields to the forms identified in step 2. | |
5 | Determine whether you will use distributed pools. | |
6 | Determine how to map the forms identified in step 2. | See Distributed-mapping. |
7 | Create the required distributed mappings. Unless otherwise noted, this step assumes that you are mapping between two servers. To maintain data integrity on more than two servers, see Chained-and-broadcast-distributed-transfers. | |
8 | Enable logical mappings. | |
9 | Create filters or escalations that define the conditions under which distributed operations occur. | |
10 | (Optional) Employ advanced functions. | |
11 | Monitor the pending distributed operations and resolve issues. |