Jump to

• Request
• Response

Modify This Transaction Params

post

/management/weblogic/{version}/edit/partitions/{name}/resourceGroups/{name}/JMSSystemResources/{name}/JMSResource/connectionFactories/{name}/transactionParams

Modify this transaction 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 transaction params model.

Root Schema : Transaction Params

Type: object

Show Source

• transactionTimeout(optional): integer(int64)
  Minimum Value: 0

  Maximum Value: 2147483647

  Default Value: 3600

  The timeout value (in seconds) for all transactions on connections created with this connection factory.

  If a transacted session is still active after the timeout has elapsed, the transaction is rolled back. A value of 0 indicates that the default value will be used. If you have long-running transactions, you might want to adjust the value of this attribute to allow transactions to complete.

• XAConnectionFactoryEnabled(optional): boolean
  Default Value: false

  Indicates whether a XA queue or XA topic connection factory is returned, instead of a queue or topic connection factory. An XA connection factory can be used to create an XAConnection, which in turn may be used to create an XASession, which in turn may be used to obtain an XAResource for use inside a transaction manager.

  In addition, this attribute indicates whether or not a connection factory creates sessions that are JTA aware. If true, the associated message producers and message consumers look into the running thread for a transaction context. Otherwise, the current JTA transaction will be ignored.

  Note: Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions.

{
    "type":"object",
    "properties":{
        "XAConnectionFactoryEnabled":{
            "default":false,
            "type":"boolean",
            "description":"<p>Indicates whether a XA queue or XA topic connection factory is returned, instead of a queue or topic connection factory. An XA connection factory can be used to create an <code>XAConnection</code>, which in turn may be used to create an <code>XASession</code>, which in turn may be used to obtain an <code>XAResource</code> for use inside a transaction manager. </p><p>In addition, this attribute indicates whether or not a connection factory creates sessions that are JTA aware. If true, the associated message producers and message consumers look into the running thread for a transaction context. Otherwise, the current JTA transaction will be ignored. </p><p><i>Note:</i> Transacted sessions ignore the current threads transaction context in favor of their own internal transaction, regardless of the setting. This setting only affects non-transacted sessions. </p>"
        },
        "transactionTimeout":{
            "default":3600,
            "minimum":0,
            "maximum":2147483647,
            "type":"integer",
            "format":"int64",
            "description":"<p>The timeout value (in seconds) for all transactions on connections created with this connection factory.</p><p>If a transacted session is still active after the timeout has elapsed, the transaction is rolled back. A value of 0 indicates that the default value will be used. If you have long-running transactions, you might want to adjust the value of this attribute to allow transactions to complete.</p>"
        }
    },
    "description":""
}

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