1. RESTful Edit Management Interface for Oracle WebLogic Server
  2. Tasks
  3. WT Ct Bridge Global

Get A Create Form For This WT Ct Bridge Global

get

/management/weblogic/{version}/edit/WTCServers/{name}/WTCtBridgeGlobalCreateForm

This resource returns a pre-populated WT ct bridge global model that can be customized then posted (using the POST method) to the WTCtBridgeGlobal optional singleton resource to create a new WT ct bridge global if it currently does not exist.

Request

Path Parameters
Query Parameters
  • The 'excludeFields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields whose name is not on the list will be returned. If not present, all fields are returned (unless the 'fields' query parameter is specified). Note: 'fields' must not be specified if 'excludeFields' is specified.
  • The 'fields' query parameter is used to restrict which fields are returned in the response. It is a comma separated list of field names. If present, only fields with matching names are returned. If not present, all fields are returned (unless the 'excludeFields' query parameter is specified). Note: 'excludeFields' must not be specified if 'fields' is specified.
Security
Back to Top

Response

Supported Media Types

200 Response

Returns this WT ct bridge global.

This method can return the following links:

  • rel=create uri=/management/weblogic/{version}/edit/WTCServers/{name}/WTCtBridgeGlobalCreateForm

    The optional singleton resource for this create form resource.

Body ()
Root Schema : WT Ct Bridge Global
Type: object
Show Source
  • Default Value: NO
    Allowed Values: [ "Yes", "No" ]

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

  • Default Value: DEFAULT
    Allowed Values: [ "PERSIST", "NONPERSIST", "DEFAULT" ]

    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.

  • Default Value: NONPERSIST
    Allowed Values: [ "PERSIST", "NONPERSIST" ]

    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.

  • Read Only: true
    Default Value: false

    Return whether the MBean was created dynamically or is persisted to config.xml

  • Read Only: true

    Return the unique id of this MBean instance

  • Default Value: weblogic.jms.XAConnectionFactory

    The name of the JMS connection factory.

    Example:weblogic.jms.ConnectionFactory

    Constraints

    • legal null

  • The mapping of priorities from JMS to Tuxedo. The default JMS To Tux Priority Map is: 0:1 | 1:12 | 2:23 | 3:34 | 4:45 |5:56 | 6:67 | 7:78 | 8:89 | 9:100

    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

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

  • Default Value: weblogic.jndi.WLInitialContextFactory

    The name of the JNDI lookup factory.

    Example:weblogic.jndi.WLInitialContextFactory

    Constraints

    • legal null
  • Read Only: true

    The user-specified name of this MBean instance.

    This name is included as one of the key properties in the MBean's javax.management.ObjectName

    Name=user-specified-name

    Constraints

    • legal null

  • Optional information that you can include to describe this configuration.

    WebLogic Server saves this note in the domain's configuration file (config.xml) as XML PCDATA. All left angle brackets (<) are converted to the xml entity <. Carriage returns/line feeds are preserved.

    Note: If you create or edit a note from the Administration Console, the Administration Console does not preserve carriage returns/line feeds.

  • Minimum Value: 0
    Maximum Value: 2147483647
    Default Value: 0

    The number of attempts to redirect a message before this Tuxedo queuing bridge places the message in the specified error location and logs an error.

    Range of Values: Between 0 and a positive 32-bit integer.

  • Minimum Value: 0
    Maximum Value: 2147483647
    Default Value: 10

    The minimum number of milliseconds this Tuxedo queuing bridge waits before redirecting a message after a failure.

    Note: During this waiting period, no other messages are redirected from the thread. Other threads may continue to redirect messages.

    Range of Values: Between and a positive 32-bit integer.

  • Items
    Title: Items

    Return all tags on this Configuration MBean

  • Minimum Value: 0
    Maximum Value: 2147483647
    Default Value: 60

    The number of timeout seconds for an entire redirection when this Tuxedo queuing bridge places a message on the target location. A value of specifies an infinite wait.

    Range of Values: Between and a positive 32-bit integer.

    Constraints

    • secure default : 60
  • Default Value: NO
    Allowed Values: [ "Yes", "No" ]

    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.

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

  • Default Value: tuxedo.services.TuxedoConnection

    The name of the Tuxedo connection factory.

    Example:tuxedo.services.TuxedoConnection

    Constraints

    • legal null

  • The mapping of priorities to map from Tuxedo to JMS. The default JMS To Tux Priority Map is: 1-10:0 | 11-20:1 | 21-30:2 | 31-40:3| 41-50:4| 51-60:5 | 61-70:6 | 71-80:7 | 81-90:8 | 91-100:9

    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

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

  • Read Only: true

    Returns the type of the MBean.

    Constraints

    • unharvestable

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

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

Nested Schema : Items
Type: array
Title: Items

Return all tags on this Configuration MBean

Show Source
Back to Top