Continuous Queue Performance; Configuring Message Beans; Websphere Application Server - IBM BJ0NJML - Service And Asset Management Integration Manual

Continuous Queue Performance

Configuring Message Beans

WebSphere Application Server

JMS Queue Configuration
<max-beans-in-free-pool>3</max-beans-in-free-pool>
</pool>
<destination-jndi-name>jms/maximo/int/queues/cqin</
destination-jndi-name>
<connection-factory-jndi-name>jms/maximo/int/cf/intcf</
connection-factory-jndi-name>
</message-driven-descriptor>
<transaction-descriptor>
<trans-timeout-seconds>600</trans-timeout-seconds>
</transaction-descriptor>
<jndi-name>JMSContQueueProcessor-1</jndi-name>
</weblogic-enterprise-bean>
-->
You can improve performance by increasing the number of message-driven beans
for a particular queue and by introducing additional application servers in a
cluster. Because messages are processed in a multi-threaded mode, errors can
occur because of the random order of processing.
The following examples describe errors that can occur. In both scenarios, the
integration error management processing can successfully reprocess the error
before the system administrator can review it.
For example, you are batch loading a large volume of item and inventory
messages in the continuous queue, and multiple inventory records exist for the
same item number. If an inventory message for Item A is processed before the
item message that adds Item A to the system is processed, the inventory message
produces an error because Item A does not exist. Processing continues with the
next message.
Eventually, the item message for Item A is processed and Item A is added to the
system. The failed message can then be successfully processed. In this case, the
error is corrected without manual intervention.
This type of situation can occur when you load related messages in the
continuous queue at the same time. Such a situation is more likely to occur when
the volume of transactions is high but also can occur whenever two messages
process related data concurrently.
For example, two messages try to update the same system record at the same
time. One message succeeds and the other fails. However, the error management
processing of the system must process the second message after the first update is
completed.
Server-specific extensions control the maximum number of beans that you can
create. By default, the server is configured to have five message-driven beans.
To configure the number of beans on your WebSphere Application Server:
1
In the administrative console, select JMS activation specification.
Continuous Queue
167