WTCtBridgeGlobal
Description
This interface provides access to the WTC tBridge Global configuration attributes. The methods defined herein are applicable for tBridge configuration at the WLS domain level.
Syntax
<WTCtBridgeGlobal AllowNonStandardTypes="String DefaultReplyDeliveryMode=( "PERSIST" | "NONPERSIST" | "DEFAULT" ) DeliveryModeOverride=( "PERSIST" | "NONPERSIST" ) JmsFactory="String JmsToTuxPriorityMap="String JndiFactory="String Name="String Notes="String Retries="number RetryDelay="number Timeout="number Transactional="String TuxErrorQueue="String TuxFactory="String TuxToJmsPriorityMap="String Type="String UserId="String WlsErrorDestination="String
/>
Parent Elements
Attributes
AllowNonStandardTypes Defines a flag used to specify if non-standard data types are allowed to pass through the tBridge. Standard types are: ASCII text (TextMessage, STRING), or BLOB (BytesMessage, CARRAY).
- NO: Non-standard types are rejected and placed onto a specified error location.
- YES: Non-standare types are placed on the target location as BLOBs with a tag indicating the original type.
Admin Console field label: Allow Non Standard TypesRequired: noDefault: NO DefaultReplyDeliveryMode Defines 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_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.
Admin Console field label: Default Reply Delivery ModeRequired: no DeliveryModeOverride Defines the delivery mode to use when placing messages onto the target location.
- Overrides any delivery mode associated with a message.
- If not specified, the message is placed on the target location with the same delivery mode specified from the source location.
Admin Console field label: Delivery Mode OverrideRequired: no JmsFactory Defines the name of the JMS connection factory. Example: weblogic.jms.ConnectionFactory Admin Console field label: JMS Factory JmsToTuxPriorityMap Defines the mapping of priorities from JMS to Tuxedo. The are 10 possible JMS priorities(0=>9) which can be paired to 100 possible Tuxedo priorities(1=>100). A mapping consists of a "|" separated list of value-to-range pairs (jmsvalue:tuxrange) where pairs are separated by ":" and ranges are separated by "-".Examples0:1 | 1:12 | 2:23 | 3:34 | 4:45 | 5:56 | 6:67 | 7:78 | 8:89 | 9:100OR 0:1-10|1:11-20|2:21-30|3:31-40|4:41-50|5:51-60|6:61-70|7:71-80|8:81-90|9:91-100 Admin Console field label: JMS To Tux Priority MapRequired: no JndiFactory Defines the name of the JNDI lookup factory. Example: weblogic.jndi.WLInitialContextFactory Admin Console field label: JNDI Factory Name The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration. Admin Console field label: NameRequired: no Notes Optional information that you can include to describe this configuration. Required: no Retries Defines the number of attempts to redirect a message before putting the message in the specified error location and logging an error. Admin Console field label: RetriesDefault: 0Minimum: 0Maximum: 231-1 RetryDelay Defines the minimum amount of time (milliseconds) to wait before redirecting a message after a failure. During this time, no other messages are redirected from the thread. Other threads may continue to redirect messages. Admin Console field label: Retry DelayDefault: 10Minimum: 0Maximum: 231-1 Timeout Defines the effective length of a timeout for an entire redirection (seconds) when placing a message on the target location. 0 indicates an infinite wait. Admin Console field label: TimeoutDefault: 60Secure value: 60Minimum: 0Maximum: 231-1 Transactional Defines a flag that specifies the use of transactions when retrieving messages from a source location and when placing messages on a target location.
- If YES, transactions are used for both operations.
Note: Transactional is not supported in this release.
- If NO, transactions are not used for either operation.
Admin Console field label: TransactionalRequired: noDefault: NO TuxErrorQueue Defines the name of the Tuxedo queue used to store a message that cannot be redirected to a Tuxedo/Q source queue. This queue is in the same queue space as the 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.
Admin Console field label: Tuxedo Error QueueRequired: no TuxFactory Defines the name of the Tuxedo connection factory. Example: tuxedo.services.TuxedoConnection Admin Console field label: Tuxedo Factory TuxToJmsPriorityMap Defines the mapping of priorities to map from Tuxedo to JMS. The are 100 possible Tuxedo priorities(1=>100) which can be paired to 10 possible JMS priorities(0=>9). A mapping consists of a "|" separated list of value-to-range pairs (tuxvalue:jmsrange) where pairs are separated by ":" and ranges are separated by "-".Examples:1:0 | 12:1 | 23:2 | 34:3 | 45:4 | 56:5 | 67:6 | 78:7 | 89:8 | 100:9OR 20:0-1 | 40:2-3 | 60:4-5 | 80:6-7 | 100:8-9 Admin Console field label: Tux To JMS Priority MapRequired: no Type Returns the type of the MBean. Required: no UserId Defines a user identity for all messages handled by the tBridge 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.
- The argument user may be specified as either a user name or a user identification number (uid).
Admin Console field label: User IDRequired: no WlsErrorDestination Defines 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.
Admin Console field label: WLS Error DestinationRequired: no