Copyright © Cloud Software Group, Inc. All Rights Reserved

Promoting Change Requests

After completing the necessary preparations, you can promote change requests by applying them either immediately or as a batch job.

Managing Impact To Users

Before applying any change requests, you must consider how users who are currently logged in to the system are affected. For more information, refer to Chapter 1, Introduction to Administration of Promotions.

Applying Change Requests

Type in one of these line commands in the Managing Accepted Requests screen:

B	Submit a batch job to promote this change request. This results in a status of J (batch job submitted). For more information on this process, refer to Chapter 1, Introduction to Administration of Promotions.
I	Immediately promote the change request. The resulting status is C (completed). Refer to Chapter 1, Introduction to Administration of Promotions for more information on the promotion process.

Initiating Source Promotions from Rules

In addition to applying change requests interactively and in batch mode, you can also initiate promotions from your own TIBCO Object Service Broker rules. To initiate a promotion within the source system, invoke the rule APPLY_PROM(srclocn, change#). The two arguments are the source node name and the number of the accepted change request to be promoted.

Promotion Log

Whenever change requests are promoted, the Promotion system provides a log of its activities. These logs are kept only if the appropriate settings are set in the @PROM_CONSTANTS table. Review any warning and error messages associated with each promotion request. All messages are documented in TIBCO Object Service Broker Messages With Identifiers.

Saved promotion logs are also available via Query Promotion Information.

Copyright © Cloud Software Group, Inc. All Rights Reserved