> # Tuxedo Queuing Bridge: General

> Configuration Options Related Tasks Related Topics

> Use this page to define the general configuration for this Tuxedo queuing bridge.

> #### Configuration Options

> 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 `YES` means that transactions are used for both operations; a value of `NO` means that transactions are not used for either operation. Note: Transactional is not supported in this release. MBean Attribute: `WTCtBridgeGlobalMBean.Transactional`
> 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 `WlsErrorDestination` for any reason, an error is logged and the message is lost. MBean Attribute: `WTCtBridgeGlobalMBean.WlsErrorDestination`
> 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. MBean Attribute: `WTCtBridgeGlobalMBean.TuxErrorQueue`
> 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. MBean Attribute: `WTCtBridgeGlobalMBean.DeliveryModeOverride`
> Default Reply Delivery Mode | The reply delivery mode to associate with a message when placing messages onto the target location. Usage Notes: Use when messages are being redirected to Tuxedo/Q from JMS and the `JMS_BEA_TuxGtway_Tuxedo_ReplyDeliveryMode` property is not set for a message. If the `defaultReplyDeliveryMode` and `JMS_BEA_TuxGtway_Tuxedo_ReplyDeliveryMode` are not set, the default semantics defined for Tuxedo are enforced by the Tuxedo/Q subsystem. MBean Attribute: `WTCtBridgeGlobalMBean.DefaultReplyDeliveryMode`
> User ID | 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. Note: The `user` argument may be specified as either a user name or a user identification number (uid). MBean Attribute: `WTCtBridgeGlobalMBean.UserId`
> Allow Non Standard Types | Specifies whether non-standard data types are allowed to pass through this Tuxedo queuing bridge. A value of `NO` means that non standard types are rejected and placed onto a specified error location; a value of `YES` means 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). MBean Attribute: `WTCtBridgeGlobalMBean.AllowNonStandardTypes`

> Related Tasks

> - Create queuing bridge connections
> - Delete queuing bridge connections
> - Configure connections for queuing bridges
> - Configure connection factories for queuing bridges
> - Configure priority mapping for queuing bridges

> Related Topics

> - How to Configure the Oracle Tuxedo Queuing Bridge