The local Data Object Broker’s view of the network is contained in its resource management repository file, which is a VSAM Keyed Sequenced Data Set (KSDS) named Q1.Q2.RESOURCE. The resource management repository file is maintained using the Resource Management option of the Administration menu.
In a network that includes more than one Data Object Broker, it is not possible for a single file to describe the total configuration. The total TIBCO Object Service Broker network configuration can, in this case, be determined by looking at the resource files for all the individual Data Object Brokers.
To maintain the repository file, use the Resource Management option (option 3) of the Administration menu. The following illustration shows the initial RESOURCE MANAGEMENT screen for a Peer Server connection that uses default values. Refer to
Chapter 18, Monitoring and Controlling the TIBCO Object Service Broker Environment for information about the Administration menu and to
3. Resource Management for detailed information about using the Resource Management option.
If the schedule entry S6BDYNAMIC is not present in the Resource Management Repository File, a new entry is created there when the Data Object Broker is initialized.
These values may be modified using the Administration Menu, but the entry may not be deleted and is reserved for the exclusive use of dynamically created resources.
If the schedule S6BDYNAMIC satisfies the needs of any external connections to the Data Object Broker, only the PEER HRN and HIN entries need to be added to the Resource Management Repository File.
If the relevant permanent or dynamic resource entry exists, an external resource uses the existing entry when connecting to the Data Object Broker. If no entry exists, an entry matching the external resource’s requirements is created dynamically. This dynamically created resource entry will be deleted as follows:
To save a Data Object Broker’s resource repository file, use the S6BTLBRM (Resource Management Online Backup) utility. The utility writes out a copy of all resource detail and resource schedule entries to a sequential file, which can serve as a backup of the configuration.