Steps for Building a Transacted JMS Trigger

Building a transacted JMS trigger is a process that involves the following basic stages.

Stage 1 Create a new JMS trigger on Integration Server.
Stage 2 Specify a JMS connection alias with a transaction type of XA TRANSACTION or LOCAL TRANSACTION.
Stage 3 Specify the destination (queues or topics) on the JMS provider from which you want to receive messages. You also specify any message selectors that you want the JMS provider to use to filter messages for the JMS trigger.

If this a SOAP-JMS trigger, you can specify one destination only.
Stage 4 For a standard JMS trigger, create routing rules and specify the services that Integration Server invokes when the JMS trigger receives messages.

SOAP-JMS triggers do not use routing rules.
Stage 5 Set the following JMS trigger properties:
  Property name... Description
  Enabled Enables or disables a JMS trigger as follows:
  • If set to True, enables a JMS trigger that is currently disabled.
  • If set to False, disables a JMS trigger that is currently enabled.

For more information, see Enabling or Disabling a JMS Trigger.
  Execution user Name of the user account whose credentials Integration Server uses to execute a service associated with the JMS trigger.

For more information, see Assigning an Execution User to a JMS Trigger.
  Message processing Specifies whether Integration Server should process messages serially or concurrently. When set to:
  • Serial, Integration Server processes messages received by the trigger one after the other.
  • Concurrent, Integration Server processes multiple messages for the trigger at one time.

For more information, see About Message Processing.
  Fatal error handling > Suspend on error Specifies whether you want Integration Server to suspend the trigger when a trigger service ends with an error. Select True or False.

For more information, see Fatal Error Handling for Transacted JMS Triggers.
  Transient error handling Specifies how Integration Server responds when a transaction is rolled back due to a transient error that occurs during processing of a transacted JMS trigger. When the On transaction rollback property is set to:
  • Recover only, Integration Server recovers the message after a transaction is rolled back due to a transient error. This is the default.
  • Suspend and recover, Integration Server suspends the JMS trigger and recovers the message after a resource monitoring service indicates that the resources needed by the trigger service are available.

For more information, see Transient Error Handling for Transacted JMS Triggers.
  Exactly once Specifies whether you want the trigger to process persistent messages once and only once. Set Detect duplicates to True to configure exactly once processing.

For more information, see Configuring Exactly-Once Processing for a JMS Trigger.
  Permissions In Designer, select the ACLs that you want to assign for each level of access as follows:
  • For the List ACL permission, specify the ACL whose allowed member can see that the element exists and view the element’s metadata (input, output, etc.).
  • For the Read ACL, specify the ACL whose allowed member can view the source code and metadata of the element.
  • For the Write ACL, specify the ACL whose allowed member can lock, check out, edit, rename, and delete the element.
  • For the Execute ACL, specify the ACL whose allowed member can execute the service. This level of access only applies to services and web service descriptors.
Stage 6 Test and debug the JMS trigger. For more information, see Debugging a JMS Trigger.