General Properties for Transacted JMS Triggers

Property

Description

Name

Name of the JMS trigger.

Enabled

Specifies whether the JMS trigger is enabled or disabled.

Select...

To...

True

Enable the JMS trigger

False

Disable the JMS trigger

Note:

If you disable a SOAP-JMS trigger that acts as a listener for one or more provider web service descriptors, Designer will not retrieve any messages for those web service descriptors.

Transaction type

Indicates whether or not the JMS trigger receives and processes messages as part of a transaction.

Value

Description

NO TRANSACTION

The JMS trigger does not receive and process message as part of a transaction.

XA TRANSACTION

The JMS trigger receives and processes messages as part of an XA transaction.

LOCAL TRANSACTION

The JMS trigger receives and processes messages as part of a local transaction.

Note:

Designer sets the transaction type value based on the transaction type specified for the JMS connection alias associated with the JMS trigger.

Execution User

Specifies the name of the user account whose credentials Integration Server uses to execute a service associated with the JMS trigger. You can specify a locally defined user account or a user account defined in a central or external directory.

Reuse

Specifies whether this element can be dragged from the CentraSite Registry Explorer view to a BPM process or CAF project.

When this property is set to public, you can drag the asset to a BPM process or CAF project.

When this property is set to private (the default), you cannot drag the asset to a BPM process or CAF project.

All published assets are available for Impact Analysis, whether they are public or private.

Although changing the public/private status will immediately change whether or not you can drag an element to a BPM process or CAF project, the element's status in CentraSite will not change until the next publication of assets to CentraSite.