Best Practices Changing the Batch Size Changing the Batch Interval

16 Tuning WebLogic Message Bridge 16-1 16 Tuning WebLogic Message Bridge The following sections provide information on various methods to improve message bridge performance: ■ Section 16.1, Best Practices ■ Section 16.2, Changing the Batch Size ■ Section 16.3, Changing the Batch Interval ■ Section 16.4, Changing the Quality of Service ■ Section 16.5, Using Multiple Bridge Instances ■ Section 16.6, Changing the Thread Pool Size ■ Section 16.7, Avoiding Durable Subscriptions ■ Section 16.8, Co-locating Bridges with Their Source or Target Destination ■ Section 16.9, Changing the Asynchronous Mode Enabled Attribute

16.1 Best Practices

■ Avoid using a Messaging Bridge if remote destinations are already highly available. JMS clients can send directly to remote destinations. Use messaging bridge in situations where remote destinations are not highly available, such as an unreliable network or different maintenance schedules. ■ Use the better performing JMS SAF feature instead of using a Messaging Bridge when forwarding messages to remote destinations. In general, a JMS SAF agent is significantly faster than a Messaging Bridge. One exception is a configuration when sending messages in a non-persistent exactly-once mode.

16.2 Changing the Batch Size

When the Asynchronous Mode Enabled attribute is set to false and the quality of service is Exactly-once, the Batch Size attribute can be used to reduce the number of transaction commits by increasing the number of messages per transaction batch. The best batch size for a bridge instance depends on the combination of JMS providers used, the hardware, operating system, and other factors in the application Note: A Messaging Bridge is still required to store-and-forward messages to foreign destinations and destinations from releases prior to WebLogic 9.0. 16-2 Performance and Tuning for Oracle WebLogic Server environment. See Configure transaction properties in Oracle WebLogic Server Administration Console Help.

16.3 Changing the Batch Interval

When the Asynchronous Mode Enabled attribute is set to false and the quality of service is Exactly-once, the BatchInterval attribute is used to adjust the amount of time the bridge waits for each batch to fill before forwarding batched messages. The best batch interval for a bridge instance depends on the combination of JMS providers used, the hardware, operating system, and other factors in the application environment. For example, if the queue is not very busy, the bridge may frequently stop forwarding in order to wait batches to fill, indicating the need to reduce the value of the BatchInterval attribute. See Configure transaction properties in Oracle WebLogic Server Administration Console Help.

16.4 Changing the Quality of Service