WAS v8.5 > Tune performance > Tune Service integration > Tune messaging engines

Set tuning properties by editing the sib.properties file

Use this task to set tuning properties for the service integration environment by editing the sib.properties file

We can set the following tuning properties to improve the performance of components in the service integration environment.

Properties for a messaging engine

sib.trm.retry

The messaging engine to messaging engine connection retry interval, in seconds. The retry interval is the time delay left between attempts to contact neighboring messaging engines with which communications exist. The default retry interval is 30 seconds.

Properties for the component of a messaging engine that manages the data store

sib.msgstore.discardableDataBufferSize

The size in bytes of the data buffer the messaging engine uses to contain data for which the quality of service attribute is best effort nonpersistent. Default is 320000, which is approximately 320 kilobytes.

The discardable data buffer contains all data for which the quality of service attribute is best effort nonpersistent. That data comprises both data that is involved in active transactions, and any other best effort nonpersistent data the messaging engine has neither discarded nor consumed. The messaging engine holds this data entirely within this memory buffer and never writes the data to the data store. When the messaging engine adds data to the discardable data buffer, for example when the messaging engine receives a best effort nonpersistent message from a client, the messaging engine might discard data already in the buffer to make space. The messaging engine can discard only data not involved in active transactions. This behavior enables the messaging engine to discard best effort nonpersistent messages.

Increasing the size of the discardable data buffer allows more best effort nonpersistent data to be handled before the messaging engine begins to discard messages.

sib.msgstore.cachedDataBufferSize

The size in bytes of the data buffer the messaging engine uses to contain data for which the quality of service attribute is better than best effort nonpersistent and that is held in the data store. Default is 320000, which is approximately 320 kilobytes.

The purpose of the cached data buffer is to optimize the performance of the messaging engine by caching in memory the data the messaging engine might otherwise have to read from the data store. As it writes data to the data store and reads from the data store, the messaging engine attempts to add that data to the cached data buffer. The messaging engine might discard data already in the buffer to make space.

sib.msgstore.transactionSendLimit

Maximum number of operations the messaging engine includes in each transaction. For example, each JMS send or receive is an operation that counts towards the transaction send limit. The default value is 100.

To set these properties by editing the sib.properties file...

1. cd profile_root/properties directory, where profile_root is the directory in which profile-specific information is stored.

2. If the directory does not contain a sib.properties file, then copy the template sib.properties files from the app_server_root/properties directory, where app_server_root is the root directory for the installation of WAS.
3. Using a text editor, open the sib.properties file and add the name and value of the property to set. The format is name=value. For example sib.trm.retry=60

Related

Set tuning properties of a messaging engine
Controlling the memory buffers used by a messaging engine
Tune the JDBC data source of a messaging engine
Tune messaging engines

Reference:

Service integration custom properties

+

Search Tips   |   Advanced Search