Modify This Destination Key

post

/management/weblogic/{version}/edit/JMSInteropModules/{name}/JMSResource/destinationKeys/{name}

Modify this destination key.

Request

Supported Media Types
Path Parameters
Header Parameters
  • The 'X-Requested-By' header is used to protect against Cross-Site Request Forgery (CSRF) attacks. The value is an arbitrary name such as 'MyClient'.
Body ()

Must contain the modified destination key model.

Root Schema : Destination Key
Type: object
Show Source
  • Read Only: true

    Return the unique identifier of this bean instance.

  • Default Value: String
    Allowed Values: [ "Boolean", "Byte", "Short", "Int", "Long", "Float", "Double", "String" ]

    The expected property type for this destination key.

    Gets the "key-type" element

  • Read Only: true

    The name of this entity, represented in XML as an attribute.

    Many of the elements within the JMS module are named entities. All of the named entities encased by a type in the XML file must be unique. This is the identifier used to delineate a particular entity within the JMS module.

    This attribute cannot be modified externally from the module (for example, with a deployment plan) because it may be used inside the module referentially.

    Constraints

    • legal null
  • Optional information that you can include to describe this named JMS descriptor bean.

    JMS module saves this note in the JMS descriptor file 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.

  • Default Value: JMSMessageID

    Specifies a message property name or the name of a message header field on which to sort messages. Message header field keys ignore the key type and reference message header fields rather than message properties.

    Note: For better performance, use message header fields as sorting keys, rather than message properties.

    Range of Values:

    The JMS Property name (including user properties) or message header fields that can be sorted on are:

    • JMSMessageID

    • JMSTimestamp

    • JMSCorrelationID

    • JMSPriority

    • JMSExpiration

    • JMSType

    • JMSRedelivered

    • JMSDeliveryTime

    • JMS_BEA_Size

    • JMS_BEA_UnitOfOrder

    This attribute is not dynamically configurable. Gets the "property" element

  • Default Value: Ascending
    Allowed Values: [ "Ascending", "Descending" ]

    The direction (Ascending or Descending) in which this key will sort messages.

    Selecting the Ascending option for the JMSMessageID property implies a FIFO (first in, first out) sort order (the default for destinations). Select the Descending option for a LIFO (last in, first out) sort order.

    This attribute is not dynamically configurable.

    Gets the "sort-order" element.

Security
Back to Top

Response

200 Response

Back to Top