webMethods blog for performance tuning from webMethods control parameters
Sep 10, 2012 23:21 0 Comments Administration Tomas

 

Use the below control parameters to decide your webMethods performance fine tuning

 

watt.server.broker.producer.multiclient

 

Specifies the number of sessions for the default client. The default client is the Broker

client that the Integration Server uses to publish documents to the Broker and to retrieve

documents delivered to the default client. When you set this parameter to a value greater

than 1, the Integration Server creates a new multi–session, shared state Broker client

named clientPrefix_DefaultClient_MultiPub, to use for publishing documents to the

Broker. Using a publishing client with multiple sessions can lead to increased

performance because it allows multiple threads to publish documents concurrently. The

default is 1 session.

 

watt.server.broker.replyConsumer.multiclient


Specifies the number of sessions for the request/reply client. The request/reply client is

the Broker client that the Integration Server uses to send request documents to the Broker

and to retrieve reply documents from the Broker. Increasing the number of sessions for

the request/reply client can lead to improved performance because it allows multiple

requests and replies to be sent and retrieved concurrently. The default is 1 session.

 

watt.server.control.triggerInputControl.delays


which corresponds to Poll delay Interval). By setting this to a specific value say X ms, you can force the trigger to keep polling the Broker after every X ms indefinitely until a document is available. 

 

watt.server.control.triggerInputControl.delayIncrementInterval


which corresponds to poll delay Interval Increment.

 

Prev Next
About the Author
Topic Replies (0)
Leave a Reply
Guest User

You might also like

Not sure what course is right for you?

Choose the right course for you.
Get the help of our experts and find a course that best suits your needs.


Let`s Connect