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 that the messaging engine uses to contain data for which the quality of service attribute is best effort nonpersistent. The 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 involved in active transactions, and any other best effort nonpersistent data that 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 that is 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 that 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. The 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 that 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

The maximum number of operations that 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 is 100.

(ZOS) Properties for the delivery of messages to message-driven beans

(ZOS) sib.ra.zosMessageLockTimeout

The number of seconds that a message is locked in the messaging engine after that message has been submitted to Workload management (WLM) for z/OS for delivery to a message-driven bean.

WLM allocates the message to a servant region, which creates a connection to the messaging engine. The servant region then consumes the message and passes it to the onMessage method of the message-driven bean.

If the servant region fails to connect to the messaging engine and consume the message before passing it to the message-driven bean, the message remains locked until the timeout value is reached. When the timeout is reached, the message is unlocked and delivery is retried.

During startup of an application server, if WLM delivers a message to a servant region before the infrastructure required to connect to the messaging engine is available, that servant region might fail to connect to a messaging engine. Connection failures of this type are indicated by CWSIV1052W entries in the job log of the servant region. If we see such entries in the job log, and we have locked messages, consider using this property to make the Message Lock Timeout shorter.

The default value of this property is 300 seconds.

To set these properties by editing the sib.properties file, complete the following steps:

Tasks

1. Navigate to the 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. Use a text editor, open the sib.properties file and add the name and value of the property that to set. The format is name=value. For example sib.trm.retry=60

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

Service integration custom properties