TIBCO configuration

TIBCO Designer

When you are testing with TIBCO Designer, which starts a BW engine internally, create or edit properties.cfg and place it in the top level of the Designer installation (for example, C:\tibco\designer\5.6). Alternatively, you can create the file in a different location and refer to it. See "Setting Custom Engine Properties for the Testing Environment" in your TIBCO BusinessWorks documentation for more details.

The content of a sample file is shown:

Trace.Task.*=true
Trace.Info.Publish=true
Trace.Warn.Publish=true
Trace.Error.Publish=true
Trace.Debug.Publish=true

Trace.Info.Publish.Subject=<mysubjectpart>.Info
Trace.Warn.Publish.Subject=<mysubjectpart>.Warn
Trace.Error.Publish.Subject=<mysubjectpart>.Error
Trace.Debug.Publish.Subject=<mysubjectpart>.Debug

You might find that 'Trace.Task.*=false' is present in the TRA file. If so, it must be commented out or set to true.

Typically you would set <mysubjectpart> to be the machine name, but the full subject can be anything valid for Rendezvous if it matches the HCL OneTest™ API configuration.

Test against a deployed BW engine

The tracing configuration that is shown (in TIBCO Designer) must be added to the deployed BW TRA, and the BW engine must be restarted. On Windows™, this file might typically be found in the following location:

C:\tibco\tra\domain\MYDOMAIN\application\hotair\hotair_archive.tra

Trace messages are sent on the BW default RV transport, but it is possible to specify alternate Rendezvous transport settings, as illustrated:

Trace.Info.Publish.Service=7878
Trace.Info.Publish.Network=eth0;239.1.1.1
Trace.Info.Publish.Daemon=tcp:myserver:7575
Trace.Warn.Publish.Service=7878
Trace.Warn.Publish.Network=eth0;239.1.1.1
Trace.Warn.Publish.Daemon=tcp:myserver:7575
Trace.Error.Publish.Service=7878
Trace.Error.Publish.Network=eth0;239.1.1.1
Trace.Error.Publish.Daemon=tcp:myserver:7575
Trace.Debug.Publish.Service=7878
Trace.Debug.Publish.Network=eth0;239.1.1.1
Trace.Debug.Publish.Daemon=tcp:myserver:7575