Configuring DSO for a server group
The BMC Remedy Distributed Server Option (DSO) is used to build large-scale, distributed environments that behave like a single virtual system. DSO enables an organization to share common information among geographically distributed servers and to keep that information consistent. DSO 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.
In a BMC Remedy AR System environment with load balancing or multiple servers, a DSO server process runs on each server, but only one process actively distributes data. The configuration needed to support DSO fail-over is limited to modification of the distributed mappings to indicate that any server in the server group can act as the source server.
To configure DSO for load balancing, you must configure multiple servers to use a single database (in addition to configuring the hardware load balancer). To do this, a server group is used. In a server group, you can use DSO to provide automatic fail-over capability for transfer operations typically restricted to one server. You do this by creating a distributed mapping and then specifying that transfers can be initiated from any server in the group. See Creating distributed mappings.
For example, as illustrated in the following figure, you can transfer copies of a request to other servers and ensure that any changes made to the copies are also made to the original request. The way that you define the processes for transferring information is similar to the way that you define business processes for an application. First, managers at each site must agree on what information to transfer from one application to another, what conditions drive transfers, and which sites control the ability to update a record. An administrator at each site then uses DSO to implement these decisions.
Distributed AR System servers in a server group using DSO
To configure DSO for a server group
To configure DSO in a server group environment, you must specify a server group name. Log on to the primary server, and perform the following steps:
- In a browser or BMC Remedy User, open AR System Administration Console, and click System > General > Server Information.
- On the Advanced tab, enter the server group name in the Server Group Name field.
- Click OK to apply the changes.
- In BMC Remedy Developer Studio, double-click Distributed Mappings in the AR System Navigator object tree.
- On the Basic panel of each distributed mapping, select the Allow Any Server in Server Group check box.
This setting indicates to the servers in the group that regardless of the source (From) server name specified in the mapping, any server in the group is qualified to be the source server. In the event of a fail-over where the distributed operation moves from one server to another, the data continues to be processed.