bea.com | products | dev2dev | support | askBEA
 Download Docs   Site Map   Glossary 
Search
e-docs > WebLogic Server > WebLogic Server Configuration Reference > WTCtBridgeGlobal

WebLogic Server Configuration Reference

 Previous Next Contents Index View as PDF  

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

<!ELEMENT WTCtBridgeGlobal EMPTY >
<!ATTLIST WTCtBridgeGlobal
   AllowNonStandardTypes      CDATA                    "NO"
   DefaultReplyDeliveryMode   (PERSIST | NONPERSIST | 
                               DEFAULT)                #IMPLIED
   DeliveryModeOverride       (PERSIST | NONPERSIST)   #IMPLIED
   JmsFactory                 CDATA                    #REQUIRED
   JmsToTuxPriorityMap        CDATA                    #IMPLIED
   JndiFactory                CDATA                    #REQUIRED
   Name                       CDATA                    #REQUIRED
   Notes                      CDATA                    #IMPLIED
   Retries                    CDATA                    "0"
   RetryDelay                 CDATA                    "10"
   Timeout                    CDATA                    "60"
   Transactional              CDATA                    "YES"
   TuxErrorQueue              CDATA                    #IMPLIED
   TuxFactory                 CDATA                    #REQUIRED
   TuxToJmsPriorityMap        CDATA                    #IMPLIED
   UserId                     CDATA                    #IMPLIED
   WlsErrorDestination        CDATA                    #IMPLIED
>

Parent Elements

The WTCtBridgeGlobal element is a child of the Domain element.

Attributes

Table 90-1 WTCtBridgeGlobalMBean Element Attributes

Attribute

Description

Range of Values and Default

Console Label

Allow-Non-Standard-Types

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.

Default: "NO"

Allow Non Standard Types

Default-Reply-Delivery-Mode

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.

Valid values:

  • "PERSIST"

  • "NONPERSIST"

  • "DEFAULT"

Default Reply Delivery Mode

Delivery-Mode-Override

Defines the delivery mode to use when placing messages onto the target location.

  • li>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.

Valid values:

  • "PERSIST"

  • "NONPERSIST"

Delivery Mode Override

Jms-Factory

Defines the name of the JMS connection factory. Example: weblogic.jms.ConnectionFactory


JMS Factory

Jms-To-Tux-Priority-Map

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 "-".

Examples

0:1 | 1:12 | 2:23 | 3:34 | 4:45 | 5:56 | 6:67 | 7:78 | 8:89 | 9:100

OR

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


Jms To Tux Priority Map

Jndi-Factory

Defines the name of the JNDI lookup factory. Example: weblogic.jndi.WLInitialContextFactory


JNDI Factory

Name

The name of this configuration. WebLogic Server uses an MBean to implement and persist the configuration.


Name

Notes

Optional information that you can include to describe this configuration.


Notes

Retries

Defines the number of attempts to redirect a message before putting the message in the specified error location and logging an error.

Default: 0

Minimum: 0

Maximum: 2147483647

Retries

Retry-Delay

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.

Default: 10

Minimum: 0

Maximum: 2147483647

Retry Delay

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.

Default: 60

Minimum: 0

Maximum: 2147483647

Timeout

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.

  • If NO, transactions are not used for either operation.

Default: "YES"

Transactional

Tux-Error-Queue

Defines the name of the Tuxedo queue used to store a message that connot 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.


Tuxedo Error Queue

Tux-Factory

Defines the name of the Tuxedo connection factory. Example: tuxedo.services.TuxedoConnection


Tuxedo Factory

Tux-To-Jms-Priority-Map

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:9

OR

20:0-1 | 40:2-3 | 60:4-5 | 80:6-7 | 100:8-9


Tux To Jms Priority Map

User-Id

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. li>The argument user may be specified as either a user name or a user identification number (uid).


User Id

Wls-Error-Destination

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.


WLS Error Destination

 

 

Back to Top Previous Next