Configuring the Distributed Server Option service for BMC Helix ITSM
As an administrator, you can implement the Distributed Server Option (DSO) with the following applications in the BMC Helix ITSM:
- BMC Helix ITSM: Asset Management
- BMC Helix ITSM: Change Management
- BMC Helix ITSM: Service Desk (Incident Management and Problem Management)
The applications run in conjunction with the AR System server and share a common database. All applications use data from the BMC Helix CMDB application. Making the configuration changes described in this section helps your forms transition smoothly to a new distributed environment.
DSO implementation examples
The following points provide a few examples of how BMC customers have implemented DSO with BMC Helix ITSM applications:
- Transfer data for a set of forms to the target server without transferring other, unrelated, data (for example, transferring only incident (help desk) and related forms).
- Create staging forms on both the source and target servers and create a DSO workflow to transfer data between the staging forms. Create an additional custom workflow to transfer the data from the staging forms to the other required forms.
- Transfer data of a complete application to the target servers for scenarios such as data replication, archiving, or reporting.
Before you begin
Before performing the procedures, you should be familiar with distributed server operations. For information about DSO, see Configuring DSO for a server group.
Configuring and implementing DSO
For configuring and implementing DSO, perform the following tasks:
Task | Reference |
---|---|
To make sure that the servers create records with unique IDs | |
Running-the-Prefix-Manager for hub and spoke environment | |
To configure your DSO environment for data transfer and deletion | |
To synchronize the foundation data on your target server |