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 DevOps Test Integrations and APIs (Test Integrations and APIs) 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 Test Integrations and APIs. 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.

Test Integrations and APIs 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 Test Integrations and APIs. A copy of the TRA file must be copied somewhere within the Test Integrations and APIs project area (on disk) to make the project more portable when you are sharing it with other users.