Jump to

• Request
• Response

Modify This Message Logging Params

post

/management/weblogic/{version}/edit/JMSSystemResources/{name}/JMSResource/uniformDistributedTopics/{name}/messageLoggingParams

Modify this message logging params.

Request

Supported Media Types

• application/json

Path Parameters

• name: string
  The name property of the instance in the collection.
• version: string
  The version of the WebLogic REST interface.

Header Parameters

• X-Requested-By: string
  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 message logging params model.

Root Schema : Message Logging Params

Type: object

Show Source

• messageLoggingEnabled(optional): boolean
  Default Value: false

  Specifies whether the module logs information about the message life cycle.

• messageLoggingFormat(optional): string
  Default Value: oracle.doceng.json.BetterJsonNull@6607ffd6

  Defines which information about the message is logged.

  Valid values are:

  • %header% - All JMS header fields are logged.

  • %properties% - All user-defined properties are logged.

  • JMSDeliveryTime - This WebLogic JMS-specific extended header field is logged.

  • JMSRedeliveryLimit - This WebLogic JMS-specific extended header field is logged.

  • foo - Any valid JMS header field or user-defined property is logged.

  When specifying multiple values, enter them as a comma-separated list. The %header% and %properies% values are not case sensitive. For example, you could use "%header%,%properties%" for all the JMS header fields and user properties. However, the enumeration of individual JMS header fields and user-defined properties are case sensitive. To enumerate only individual JMS header fields you could use "%header, name, address, city, state, zip"

  Note: The JMSMessageID field is always logged and cannot be turned off. Therefore, if the Message Logging Format is not defined (i.e., null) or is defined as an empty string, then the output to the log file contains only the JMSMessageID of the message. Gets the message-logging-format element.

• templateBean(optional): array Template Reference
  Title: Template Reference

  Read Only: true

  Contains the template reference.

  Finds the template bean for this destination.

{
    "type":"object",
    "properties":{
        "messageLoggingEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Specifies whether the module logs information about the message life cycle.</p>"
        },
        "messageLoggingFormat":{
            "default":null,
            "type":"string",
            "description":"<p>Defines which information about the message is logged.</p><p>Valid values are:</p><ul><li><p><b>%header%</b> - All JMS header fields are logged.</p></li><li><p><b>%properties%</b> - All user-defined properties are logged.</p></li><li><p><b>JMSDeliveryTime</b> - This WebLogic JMS-specific extended header field is logged.</p></li><li><p><b>JMSRedeliveryLimit</b> - This WebLogic JMS-specific extended header field is logged.</p></li><li><p><b><i>foo</i></b> - Any valid JMS header field or user-defined property is logged.</p></li></ul><p>When specifying multiple values, enter them as a comma-separated list. The <code>%header%</code> and <code>%properies% </code> values are <i>not</i> case sensitive. For example, you could use <code>\"%header%,%properties%\"</code> for all the JMS header fields and user properties. However, the enumeration of individual JMS header fields and user-defined properties are case sensitive. To enumerate only individual JMS header fields you could use <code>\"%header, name, address, city, state, zip\"</code></p><p><b>Note:</b> The <code>JMSMessageID</code> field is always logged and cannot be turned off. Therefore, if the Message Logging Format is not defined (i.e., null) or is defined as an empty string, then the output to the log file contains only the <code>JMSMessageID</code> of the message. Gets the <code>message-logging-format</code> element.</p>"
        },
        "templateBean":{
            "readOnly":true,
            "title":"Template Reference",
            "type":"array",
            "items":{
                "type":"string",
                "description":""
            },
            "description":"Contains the template reference. <p>Finds the template bean for this destination.</p>"
        }
    },
    "description":""
}

Nested Schema : Template Reference

Type: array

Title: Template Reference

Read Only: true

Contains the template reference.

Finds the template bean for this destination.

Show Source

• Array of: string

{
    "readOnly":true,
    "title":"Template Reference",
    "type":"array",
    "items":{
        "type":"string",
        "description":""
    },
    "description":"Contains the template reference. <p>Finds the template bean for this destination.</p>"
}

Security

• Admin: basic
  Type: basic

  Description: A user in the Admin security role.
• Deployer: basic
  Type: basic

  Description: A user in the Deployer security role.

Back to Top

Response

200 Response

Back to Top