![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
This section describes switch processing, and also lists the commands used to manage multiple Data Object Brokers and Message Switches.The following describes the processing that occurs when an operator initiates a switch from the primary Data Object Broker to a secondary Data Object Broker.
3. Once the checkpoint is complete, the primary Data Object Broker takes a systems-wide enqueue to stop any further changes to the Data Object Broker XCF Group. A target secondary Data Object Broker is chosen if the operator specified ANY on the switch command; otherwise, the specified secondary Data Object Broker will become the target Data Object Broker.
5. The secondary Data Object Broker performs a standard initialization. It will attempt to obtain the systems-wide enqueue currently held by the primary Data Object Broker, and will enter a wait until it becomes available.
6. All MSW address spaces drain message traffic to the current primary Data Object Broker. Messages currently active in the primary will be allowed to complete their processing, but new messages and session connections are queued in the MSW address space until the switch is complete.
7. Any transactions that are currently held by the Data Object Broker for locks are terminated with a LOCKFAIL condition.
8. Once all MSW address spaces connected to the primary Data Object Broker indicate that they are drained, the primary Data Object Broker initiates a shutdown.
− Status of the system that is usually retrieved from the REDOLOG data set upon initialization.
10. Once the primary Data Object Broker has written all the necessary data to the Coupling Facility and shuts down, it releases the enqueue obtained in step 3 above.
11. The selected secondary Data Object Broker comes out of the wait entered in step 5 and starts a standard TIBCO Object Service Broker initialization; however, instead of reading the REDOLOG data set for restart information, it reads all the data written to the Coupling Facility in step 9.
12. When the secondary Data Object Broker completes its initialization, it sets itself as the new primary Data Object Broker.
13. All MSW address spaces reconnect their active sessions to the new primary Data Object Broker and send any held messages and connections to the new primary Data Object Broker.The following commands are used to control multiple Data Object Brokers and Message Switches. For details, see Chapter 16, Operator Commands.
• These commands support Message Switch address spaces; their functions are the same as when applied to Data Object Brokers.
•
•
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |