Outbound Messages (Send, SendReceive)
Caching of WebSphere MQ Transport business services can improve outbound performance by eliminating the need to connect to the queue for each message. Caching is disabled by default because it is not usable in every situation. Follow these tips to enable caching:
Cache in client sessions only. Do not use caching if your transport will be called within the Workflow Process Manager (WfProcMgr) component. The threading model of this component is not compatible with the WebSphere MQ APIs.
To enable caching for a business service, set the Cache property to
TRUEin Siebel Tools, then update and publish the Siebel runtime repository.If you need to call the WebSphere MQ Transport in Workflow Process Manager and in a client session, then make a separate copy of the service (one cached and one uncached) for each situation.
Caching occurs on a per-queue basis and only one connection is kept open at a time. If a single session is going to talk to multiple queues, then consider making a copy of the transport for each outbound queue.