A change request can be promoted in the system where it was created, the source system, and in a number of external target systems. Depending on the promotion administration perspective, promoting a change request can have up to three phases:
As a change request progresses from creation to application in one or more TIBCO Object Service Broker systems, it can take on various status codes. These codes could differ across the various systems where the change request is used. For more information on the meaning of these codes, refer to
Appendix C, Status Codes of Change Requests.
The Promotion system performs this validation step when you promote within either the target promotion administration or the remote promotion administration function sets. This step checks the validity of the disposition of objects in a change request. For more information on dispositions, refer to
Chapter 4, Target Promotions.
By default, the Promotion system takes a backup before applying change requests. A backup is essentially an image of object definitions and TIBCO Object Service Broker data involved in a change request. This image, taken before the actual promotion of a change request, can be used at a later time if you want to back out a promoted change request.
In a source system, change request numbers are assigned in ascending sequence, indicating creation sequence. The sequence of application, however, is not necessarily the same as the creation sequence. If there are potential interactions among change requests, the order of their application could be critical to their promotion as a set. Developers who create change requests and administrators who perform the promotions must coordinate and agree on the promotion sequence.