Overview of distributed change request tracking

Rational® Change Distributed is the distributed change request tracking package. A change request is a problem or issue that is entered and tracked through to completion by using Rational Change Distributed.
To work on change requests in a distributed environment, choose one of the following solutions.
  • Central CR Server.

    With central CR server, you have a single change request database and a Rational Change server. Change requests are submitted and maintained in this database. Developers working in separate engineering databases can create tasks associated with change requests in that central CR database. In this way, you do not need to replicate change requests across databases. All change request data is held in a single database.

  • Distributed change requests.

    The distributed change requests usage does not have a single change request database. Instead, change requests are replicated between development databases as required. Developers can create tasks associated to change requests and resolve the change requests in their local engineering database.

The advantages of central CR server are ease of use, and developers do not have to wait for control of a change request to be replicated before they can modify or work on the change request in their local database. The advantage of distributed change requests is that all of the data that a developer needs to work on is held locally. Keeping data local might make the data more resilient against network outages.

The following topics describe how to use distributed change requests. For information on central CR server, see the Rational Change information center.

Rational Change Distributed enhances change management functionality in the following ways.

You can configure Rational Change Distributed in the following ways.


Feedback