Administration Console Online Help

Previous Next Open TOC in new window
Content starts here

Web Service: Configuration: Ports

Configuration Options     Related Tasks     

This page lists message buffering, reliable messaging, atomic transaction, and persistence configuration that are associated with the endpoints and operations of this Web service. The operations are listed below the endpoints; click on the + sign to view them.

Configuration Options

Name Description
Ports and Operations

Name of the Web service endpoint (port) or operation for which you can edit buffering, reliable messaging, atomic transaction, and persistence configuration.

Reliable Message Configuration Customized

Flag that specifies whether Web service reliable messaging is configured on this endpoint in the Web service descriptor or deployment plan. If not enabled, the Web service reliable messaging configuration on the server will be used.

Note that this flag does not reflect other forms of reliable message configuration such as WS-RM policy directly specified in WSDL.

Reliable Message Base Retransmission Interval

String value in 'Duration' format. The interval of time that must pass before a message will be retransmitted to the RM destination (in the event a prior transmission failed). Defaults to 'P0DT8S' (8 seconds). Applies to RM source.

Reliable Message Enable Retransmission Exponential Backoff

A boolean flag indicating that the retransmission interval will be adjusted using the exponential backoff algorithm [Tanenbaum]. Defaults to false. Applies to RM source.

Reliable Message Non-buffered Source

A boolean flag indicating that any RM source hosted within the current service will send non-buffered. Defaults to false.

Reliable Message Non-buffered Destination

A boolean flag indicating that the RM destination represented by the current service will receive non-buffered. Defaults to false.

Reliable Message Acknowledgement Interval

String value in 'Duration' format. Defaults to 'P0DT0.2S' (200 milliseconds). Applies to RM source and RM destination.

Reliable Message Inactivity Timeout

String value in 'Duration' format. If during this duration, an endpoint (RM source or RM destination) has received no application or control messages, the endpoint MAY consider the RM Sequence to have been terminated due to inactivity. Defaults to 'P0DT600S' (600 seconds). Implementations of RM source and RM destination are free to manage resources associated with the sequence as they please, but in general, there are no guarantees that the sequence will be useable by either party after the inactivity timeout expires. Applies to RM source and RM destination.

Reliable Message Sequence Expiration

Duration expression (String), defaults to 'P1D' (1 day). This is the expiration time for a sequence regardless of activity. Applies to RM source and RM destination.

Reliable Message Buffer Retry Count

Used only for JAX-RPC services. JAX-WS services should set this on BufferingConfigBean instead.

Number of times the service will attempt to retry processing of a reliable request. Note that this processing refers to the incoming request for a service operation, and not any outgoing request to an RM destination (as is the case with BaseRetransmissionInterval, etc.). Defaults to 3. Applies to RM destination.

Minimum value: 0

Reliable Message Buffer Retry Delay

Used only for JAX-RPC services. JAX-WS services should set this on BufferingConfigBean instead.

String value in 'Duration' format defining an amount of time to wait between retries of an incoming reliable request. Defaults to 'P0DT5S' (5 seconds). Applies to RM destination.

Buffering Configuration Customized

Flag that specifies whether message buffering is configured on this endpoint in the Web service descriptor or deployment plan. If not enabled, the Web service message buffering configuration on the server will be used.

Buffering Retry Count

The number of times a buffered request or response can be retried before it is abandoned (and moved to any error queue defined for the buffer queue)

Minimum value: 0

Buffering Retry Delay

The amount time between retries of a buffered request and response. Note, this value is only applicable when RetryCount > 0. String value in 'Duration' format. Defaults to 'P0DT30S (30 seconds).

Buffering Request Queue Enabled

A boolean flag indicating whether buffering is enabled (request buffering if this is the request queue, or response buffering if this is the response queue). Defaults to false.

Buffering Request Queue JNDI Name

Get the name of this buffering queue. This name is the JNDI name for the queue.

Buffering Request Queue Connection Factory JNDI Name

The JNDI name of the connection factory to use when buffering messages onto this queue. Defaults to the 'default' JMS connection factory.

Buffering Request Queue Transaction Enabled

A boolean flag indicating whether transactions should be used when buffering a message onto or consuming a message off of this queue. Defaults to false.

Buffering Response Queue Enabled

A boolean flag indicating whether buffering is enabled (request buffering if this is the request queue, or response buffering if this is the response queue). Defaults to false.

Buffering Response Queue JNDI Name

Get the name of this buffering queue. This name is the JNDI name for the queue.

Buffering Response Queue Connection Factory JNDI Name

The JNDI name of the connection factory to use when buffering messages onto this queue. Defaults to the 'default' JMS connection factory.

Buffering Response Queue Transaction Enabled

A boolean flag indicating whether transactions should be used when buffering a message onto or consuming a message off of this queue. Defaults to false.

Atomic Transaction Customized

Flag that specifies whether Web service atomic transactions is configured on this endpoint in the Web service descriptor or deployment plan. If not enabled, the Web service atomic transaction configuration on the server will be used.

Atomic Transaction Enabled

A boolean flag that specifies whether WS-AT is enabled. Defaults to true.

Changes take effect after you redeploy the module or restart the server.

Atomic Transaction Flow Type

Transaction flow type supported. Valid values include: MANDATORY, SUPPORTS, or NEVER. Defaults to SUPPORTS.

Changes take effect after you redeploy the module or restart the server.

Atomic Transaction Version

Version of WS-AT that is supported. Valid values include: WSAT10, WSAT11, WSAT12, or DEFAULT. Defaults to DEFAULT, which specifies WSAT1.0 support on the client side, and WSAT10, WSAT11, and WSAT12 support on the server side.

Changes take effect after you redeploy the module or restart the server.

Default Logical Store Name

Name of the logical store to use, by default, for persistence within this service.

Related Tasks


Back to Top