Copyright © Cloud Software Group, Inc. All Rights Reserved

Keeping Source and Target Systems Consistent

Every TIBCO Object Service Broker Promotion source system has information in its own MetaStor on the presence or absence of objects in the target system. The Promotion system uses this knowledge of the target system when it marks the disposition of objects in a change request. Disposition refers to whether the object is designated for creation, replacement, or deletion in the target system.

Some intervention can cause this information in the source system to be inconsistent with the situation of objects in the target system. You can refresh the source system MetaStor by bringing in all the required information from the target system.

Aligning Disposition Mismatches

There are two methods to align disposition mismatches between systems in TIBCO Object Service Broker:

•

Local

•

Global

Local Method

This method is available during target and remote promotion administration. It affects only the objects in an individual change request, and aligns their disposition to that of the target system. It is activated by the R (Refresh Disp) line command, as discussed in Chapter 4, Target Promotions.

Global Method

The global method is more general and thorough, and affects all objects on the system. This method can be run only by a system administrator and only while no other users are logged in to the system. The procedure by platform is as follows:

z/OS Platform

1.	Allocate a sequential data set with the following characteristics in your target system:

−	RECORD FORMAT—VB

−	LRECL—2250 or larger

2.	Log in to the target TIBCO Object Service Broker system.

3.	Run the GEN_SYS_TBLS rule to refresh the list of objects on the target system.

Pass the GEN_SYS_TBLS rule two arguments:

−	A unique table name to be used as a temporary table. This table is deleted after GEN_SYS_TBLS is run.

−	The name of the data set allocated in step 1.

4.	Use one of the two following methods to ensure that the external file (allocated in 1 above) is accessible by the source TIBCO Object Service Broker system:

−	Copy the file across platforms.

−	Establish the availability via your data communication network if your facilities permit.

5.	Log in to the source TIBCO Object Service Broker system.

6.	Run the LOAD_SYS_TBLS rule and pass it the same data set name as defined in Step 1.

7.	Unaccept any change request whose validation during the apply process failed due to invalid object dispositions.

8.	Instruct application developers to resubmit those change requests to ensure that the refreshed object dispositions are used.

There is another method to correct change request validation failures. While on the target system, use the R line command (on the Manage Accepted Requests screen) to refresh the disposition to that of the target system. This action would replace steps 7 and 8. However, the promotions administrator should verify the cause of all disposition failures before taking this action.

Windows and Solaris Platforms

1.	Log in to the target TIBCO Object Service Broker system.

2.	Run the GEN_SYS_TBLS rule to refresh the list of objects on the target system.

Pass the GEN_SYS_TBLS rule two arguments:

−	A unique table name to be used as a temporary table. This table is deleted after GEN_SYS_TBLS is run.

−	The filename—the path is determined from your DSDIR session option.

3.	Log in to the source TIBCO Object Service Broker system.

4.	Run the LOAD_SYS_TBLS rule.

Pass it the same filename as defined in Step 3.

5.	Unaccept any change requests whose validation during the apply process failed due to invalid object dispositions.

6.	Instruct application developers to resubmit those change requests to ensure that the refreshed object dispositions are used.

There is another method to correct change request validation failures. While on the target system, use the R line command (on the Manage Accepted Requests screen) to refresh the disposition to that of the target system. This action would replace steps 5 and 6. However, the promotions administrator should verify the cause of all disposition failures before taking this action.

See Also

TIBCO Object Service Broker Parameters for information about the DSDIR parameter.

Copyright © Cloud Software Group, Inc. All Rights Reserved