Where a change request was created, where it is being managed, and where it is being applied dictate the type of promotion administration you perform. There are three perspectives or types of promotion administration:
Depending on the type of promotion administration being performed, you must also allow for other factors such as environment access rights, backup requirements, and external access permissions.
Accepting a newly submitted change request and managing it in the same TIBCO Object Service Broker system where it was created is known as source promotion administration.
Using one of two file-transfer methods, change requests can also be managed in TIBCO Object Service Broker systems other than the system where they were created. The first method, target promotion administration, consists of:
A developer creates change requests in a version of TIBCO Object Service Broker for other than the z/OS platform, and these changes must be applied in TIBCO Object Service Broker on the z/OS platform. Using source promotion administration functions in the version for other than z/OS, the change request information is written to external files. The files are then transferred to the z/OS platform and managed in that system using target promotion administration functions.
The second file-transfer method is a data communication connection between the source and target systems. Remote promotion administration is based on the TIBCO Object Service Broker distributed data facilities that use the data communications alternative. Except for its use of networking facilities, remote promotion administration offers functionality similar to source and target promotion administration.
