Create a WTC Queuing Bridge Connection
Configuration Options Related Tasks Related Topics
Use this page to create a new WTC queuing bridge connection.
Name Description Transactional
Specifies whether this Tuxedo queuing bridge should use transactions when retrieving messages from a source location and when placing messages on a target location.
A value of
YESmeans that transactions are used for both operations; a value of
NOmeans that transactions are not used for either operation.
Note: Transactional is not supported in this release.
WLS Error Destination
The name of the location used to store WebLogic Server JMS messages when a message cannot be redirected.
If not specified, all messages not redirected are lost. If the message cannot be placed into
WlsErrorDestinationfor any reason, an error is logged and the message is lost.
Tuxedo Error Queue
The name of the Tuxedo queue used to store a message that cannot be redirected to a Tuxedo/Q source queue.
If not specified, all messages not redirected are lost. If the message cannot be placed into the
TuxErrorQueue, an error is logged and the message is lost.
Note: This queue is in the same queue space as the source queue.
Delivery Mode Override
The delivery mode to use when placing messages onto the target location.
If this value is not specified, the message is placed on the target location with the same delivery mode specified from the source location.
Note: This value overrides any delivery mode associated with a message.
Default Reply Delivery Mode
The reply delivery mode to associate with a message when placing messages onto the target location.
Use when messages are being redirected to Tuxedo/Q from JMS and the
JMS_BEA_TuxGtway_Tuxedo_ReplyDeliveryModeproperty is not set for a message.
JMS_BEA_TuxGtway_Tuxedo_ReplyDeliveryModeare not set, the default semantics defined for Tuxedo are enforced by the Tuxedo/Q subsystem.
The user identity for all messages handled by this Tuxedo queuing bridge for ACL checks when security is configured.
All messages assume this identity until the security/authentication contexts are passed between the subsystems. Until the security contexts are passed, there is no secure method to identify who generated a message received from the source location.
userargument may be specified as either a user name or a user identification number (uid).
Allow Non Standard Types
Specifies whether non-standard data types are allowed to pass through this Tuxedo queuing bridge.
A value of
NOmeans that non standard types are rejected and placed onto a specified error location; a value of
YESmeans that non-standard types are placed on the target location as BLOBs with a tag indicating the original type.
Note: Standard types are: ASCII text (TextMessage, STRING), or BLOB (BytesMessage, CARRAY).