Configuring a BWPM client to publish non-persistent messages so as to avoid storage issues or network traffic.

Configuring a BWPM client to publish non-persistent messages so as to avoid storage issues or network traffic.

book

Article ID: KB0089377

calendar_today

Updated On:

Products Versions
TIBCO BusinessWorks ProcessMonitor -
Not Applicable -

Description

Description:
Description
=============
BWPM Client needs to send non-persistent messages on the EMS server to avoid storage issue or network traffic over any external storage, such as SAN, etc.




Issue/Introduction

Configuring a BWPM client to publish non-persistent messages so as to avoid storage issues or network traffic.

Resolution

A BWPM Client can publish non-persistent messages by setting the following properties in the deployed tra file (if the BW engine is deployed) or the BWengine.tra file if the project is not deployed or for future deployment. This property was introduced in BWPM 2.2.0, so you have to upgrade to BWPM 2.2.0 or higher for this property to take effect

*****
tibco.clientVar.nJAMS/DataProvider/JMS/deliveryMode=NON_PERSISTENT
*****

There following are other properties which may help reduce network traffic.

******
tibco.clientVar.nJAMS/logMode=exclusive
tibco.clientVar.nJAMS/compress=true
tibco.clientVar.nJAMS/publishSources=false
tibco.clientVar.nJAMS/DataProvider/InstantPush=false
******
Powered by Wolken Software