Configuring the Lazy Communication 

Use

The lazy communication mechanism is used automatically by the Cluster Manager to quickly exchange large amounts of information between two server processes without using the message server as an intermediary.

By default, lazy communication is enabled only for a predefined list of services (the list is stored in the lazy.exclusive.list property) and is disabled for the remaining services.

You can enable a mechanism by which lazy communication is activated when a previously defined amount of objects is transferred between two parties for a defined time interval.

We recommend that you do not modify the default lazy communication settings unless you are officially advised to do so by SAP support.

Procedure

...

       1.      Start the J2EE Engine Visual Administrator.

       2.      Choose Server → Kernel → Cluster Manager → Properties tab.

You can configure the lazy communication on servers only.

       3.      To add or remove a service from the list of services for which lazy communication is always enabled, select the lazy.exclusive.list property and modify its value.

       4.      To enable the mechanism by which lazy communication is enabled according to the amount of information exchanged for a definite period of time, modify the following properties:

                            a.      Specify true as the value of the lazy.transparent.switch property.

                            b.      Use lazy.time.piece to specify the time interval in milliseconds for which the quantity of messages defined by the lazy.threshold property has to be exchanged between two parties in order to open a lazy connection.

If two parties open a connection, and if they succeed in exchanging more messages than the size defined by the lazy.threshold property for the time defined, then a lazy connection will be opened.

                            c.      Use lazy.threshold to specify the size of the messages that must be sent during a time interval equal to the value set in the lazy.time.piece property.

                            d.      Use lazy.autoclose.timeout to specify the time for which the lazy connection will be open after the last large message is transported.

After this timeout, the Cluster Manager closes the connection.

If you specify zero (0) as a value, the lazy connection will be permanently open (infinite timeout.)

                            e.      Use lazy.message.pool.size to specify the size of the pool where the currently unused message objects are stored.

       5.      Choose  Save Properties to save your changes.

 

See also:

Cluster Manager Properties in the Reference Manual