Configuring TIBCO BusinessWorks

You can configure BusinessWorks (BW) to publish tracing messages by using a Rendezvous transport. These tracing messages record the progress of the various steps in the business processes under test. HCL OneTest™ API can be configured to listen to these messages in order to produce fully detailed reports, including timings and coverage (that is, how much of the BW project is tested).

Since the tracing uses Rendezvous messaging, you must understand the Rendezvous configuration options or seek advice from your TIBCO administrator. The configuration of BW engine tracing could result in the publication of many messages. Messages are published for all processes, even processes that are not started by HCL OneTest API. A multicast service can be used to avoid any unnecessary burden on the network or other downstream systems. Refer to the TIBCO Designer and TIBCO BusinessWorks documentation for full details of the tracing configuration.

To produce full reports, you must meet the following requirements:
  • You must have a TIBCO BusinessWorks project in the Logical view of Architecture School
  • You must have a TIBCO BusinessWorks TRA file in the Physical View of architecture School

HCL OneTest API creates a coverage report when a suite is run. The suite must contain a scenario where the execution environment binds the TIBCO BW project to the TIBCO BW TRA file. This happens automatically when the BW project is imported into HCL OneTest API. A copy of the TRA file must be copied somewhere within the HCL OneTest API project area (on disk) to make the project more portable when you are sharing it with other users.