JMS Export bindings support event sequencing. In order for events
to be handled in the order in which they are received you need to configure
properties of the binding.
Before you begin
Event sequencing for JMS Export bindings is not supported in a clustered
environment.
Why and when to perform this task
To enable event sequencing for JMS Export bindings you must do
two things:
- limit the number of concurrent message-driven beans (MDBs) that are processing
incoming messages
- prevent failed messages from being routed to an exception destination,
which would break the order of event processing.
To enable event sequencing configure the JMS Export binding using
the administrative console. When using the SIB JMS Resource Adapter, set the maxConcurrency custom
property on the ActivationSpec to a value of 1 to limit
the number of MDBs that are processing incoming messages. Determine which
SIB destination is being used as the receive destination and remove the exception
destination.
Steps for this task
- Limit the number of concurrent MDBs that are processing incoming
messages.
- In the navigation pane of the administrative console, expand
Resources and click Resource Adapters.
- In the content pane, click SIB JMS Resource Adapter.
- Under Additional properties, click J2C activation specification
and select the Export activation spec. The name of the activation
specification is defined when the Export binding is installed. See related
topics for the naming convention.
- Under Additional properties, click J2C activation specification
custom properties
- Set the maxConcurrency to 1. Click
the value field and enter a value of 1, then click OK.
- Save the changes to your master configuration.
- Determine which SIB destination is being used as the receive destination.
- In the navigation pane of the administrative console, expand
Resources and click Resource Adapters.
- Set the scope to Server. In the top portion of the
content pane, click Server and then click Apply.
- In the content pane, click SIB JMS Resource Adapter.
- Under Additional properties, click J2C administered objects.
- Select the administered object used by your SCA JMS binding.
- Under Additional properties, click J2C administered objects
custom properties.
- Note the value of the QueueName property, which is the SIB destination
used as the receive destination.
- Remove the exception from the receive destination.
- In the navigation pane expand Service integration and click
Buses.
- Select the bus used by your JMS Export binding. The
default name for the bus is SCA.APPLICATION.bus-id.Bus,
but you may have configured a different bus value in the binding file.
- Select the receive destination used by SCA JMS binding
- In the Exception Destination section, select None.
- Save the changes to your master configuration.
Result
Event sequencing is enabled for your binding.
Note: Removing the exception
destination means that any failure will stop all incoming messages.