|
|
|
|
|
|
Using Reliable Queuing with the TEDG
The BEA Tuxedo and BEA TOP END systems support reliable queues that can pass messages between components. The BEA Tuxedo /Q facility and the BEA TOP END Recoverable Transaction Queuing (RTQ) facility allow messages to be passed using queues to store messages before processing. Both /Q and RTQ guarantee that once a message is successfully placed on a queue, it will be delivered to the server. Full transaction semantics are supported for both queuing and processing the message.
The TOP END Domain Gateway (TEDG) supports the enqueuing of messages between BEA Tuxedo and BEA TOP END systems. Transactional enqueuing of messages between systems is also supported. The queue itself is part of the native system on which it was created. All the administrative aspects of managing the queue and dequeuing messages are also part of the native system.
The TEDG does not support dequeuing from a queue in a remote system because the /Q and RTQ capabilities and interfaces on the dequeuing side are quite different. BEA Tuxedo /Q provides the tpdequeue(3c) function for explicitly dequeuing a message; there is no equivalent within RTQ. The RTQ facility dequeues messages automatically and delivers them to the intended BEA TOP END service. The destination service address is supplied as part of enqueuing the message (see tp_rtq_put(3T) in the BEA TOP END Programmer's Reference Manual).
The relationship between the queues and the services is arbitrary. /Q provides a system-supplied service, TMQFORWARD(5), that can be configured to dequeue messages automatically and forward them to standard BEA Tuxedo servers through the tpcall(3c) function. The destination service name must match the queue name. In a TEDG environment, the server to which these messages are sent after automatic dequeuing may be in the same system or a remote system, depending on the TEDG configuration and appropriate server programming.
We assume that you already have a BEA Tuxedo /Q queue or a BEA TOP END RTQ queue and the administrative tools and servers associated with the queue. The Using the ATMI /Q Component
and the BEA TOP END Recoverable Transaction Queuing Guide describe the value of queuing, discuss the task of designing a system in which queuing is used, and explain how to set up and manage queues.Common Queuing Capabilities Supported by the TEDG
While /Q and RTQ offer similar basic capabilities, each also offers several unique features. The capabilities offered by the TEDG represent the common subset of the features of the two systems:
Unsupported BEA Tuxedo /Q Capabilities
The TEDG does not support the following BEA Tuxedo /Q features:
Unsupported BEA TOP END RTQ Capabilities
The TEDG does not support the following BEA TOP END RTQ features:
See Also
|
|
|
|
|
|
Copyright © 2001 BEA Systems, Inc. All rights reserved.
|