Weblogic Server; Message Caching - IBM BJ0NJML - Service And Asset Management Integration Manual

Continuous Queue

WebLogic Server

Message Caching

168
2
Select intjmsact.
3
Specify a value in the Maximum Concurrent End Points field.
By default, the WebLogic Server is configured to have three message-driven
beans. Use the values shown in bold to configure the number of message-driven
beans in the weblogic-ejb-jar.xml file:
<!-- MEA MDB
<weblogic-enterprise-bean>
<ejb-name>JMSContQueueProcessor-1</ejb-name>
<message-driven-descriptor>
<pool>
<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>
-->
Start with a relatively low amount of message-driven beans, for example two to
three message-driven beans. You then determine whether that amount provides
proper support for the volume of messages in your system. You can incrementally
increase the number of message-driven beans until you are satisfied with the
processing performance of the messages in the continuous queue.
The number of message-driven beans and the volume of messages processing in a
queue can use enough system resources to affect your application users. If you
continue to increase the amount of message-driven beans, this change may have
little or no impact on message processing performance. You can resolve some
system performance issues by clustering your servers and isolating the inbound
message processing to a specific server cluster.
Continuous queue processing uses a property called Maximum Batch Size. The
property is under the Activation Specification definition. The batch size controls
the number of messages that the system receives from the messaging engine in a
single batch.
If three message-driven beans are enabled, and the batch size is 10, a maximum of
30 messages are cached. Test with different values to ensure that the value that
you set does not impact application users or server processes.
An unlimited number of messages can be processed when you set the Batch Size
value to -1 on a WebLogic Server environment.
If you plan to use a WebSphere Application Server error queue, use the default
value for the batch size.
Integration Guide