Difference between revisions of "Jms-enqueue"
Line 1: | Line 1: | ||
− | The ''jms- | + | The ''jms-enqueue'' element allows you to perform a enqueue on a JMS destination. It is used by [[Channel]] and [[routed-dequeue]]. |
GVBuffer fields will be made available through the JMS message properties: | GVBuffer fields will be made available through the JMS message properties: |
Revision as of 15:59, 27 December 2012
The jms-enqueue element allows you to perform a enqueue on a JMS destination. It is used by Channel and routed-dequeue.
GVBuffer fields will be made available through the JMS message properties:
Field | JMS |
---|---|
system | SYSTEM |
service | SERVICE |
id | ID |
retCode | RET_CODE |
properties | p$<property name> (only GVBuffer properties with names that are valid Java identifier are managed) |
It has the attributes:
Attribute | Type | Description |
---|---|---|
type | fixed | This attribute must assume the value enqueue. |
class | fixed | This attribute must assume the value it.greenvulcano.gvesb.virtual.j2ee.JMSEnqueueOperation. |
name | required | Operation name. Used in the Flow section to associate workflow nodes to VCL operations. |
connection-factory | required | JMS connection factory JNDI name. |
destination-name | required | Destination JNDI name. Set appropriately the destination-type parameter. |
destination-type | optional | Destination type. Default: queue. The attribute's admitted values are:
|
transacted | optional | Specifies whether the enqueue has to open his own transaction or fall in a global transaction.
|
acknowledge-type | optional | In transactional enqueue acknowledgment is managed by the application server. This parameter is meaningful only for non-transactional enqueue and can take the following values:
|
delivery-mode | optional | Specifies whether the JMS server must file on a persistent store the message before returning to the caller. Sending messages persistent slightly affects the performance but provides greater guarantees of delivery. The possible values for this parameter are:
|
priority | optional | Message priority. The messages with higher priority will be received before messages with lower priority. The priorities set for JMS ranging from 0 (lowest priority) to 9 (highest priority). The default priority of JMS messages is 4. |
time-to-live | optional | Lifetime of sent messages, in milliseconds. Upon expiration of the time-to-live the JMS server is allowed to discard the message without delivering it. If not specified it is assumed a time-to-live of one year. |
use-vcl-pool | optional | Indicates whether to use connection pooling capabilities of the VCL. Set to false if the container provides pooling capabilities. Default: true |
invalidate-conn-on-pool-insertion | optional | Indicates whether connections should be marked as invalid before reinsertion on the pool. Is significant only if the pooling feature is enabled. Default: false |
ref-dp | optional | Name of Data Provider to use. This Data Provider will return the JMS Message to send. |
dump-message | optional | If true the message to be enqueued is dumped on log file, at DEBUG severity level. Default false |
Its subelements are:
- Description
- JNDIHelper
- ServiceAlias
- XAHelper
{{#w4grb_rate:}} <w4grb_ratinglist latestvotes items="5" nosort/>