As a transitional step, this site will temporarily be made Read-Only from July 8th until the new community launch. During this time, you can still search and read articles and discussions.

While the community is read-only, if you have questions or issues requiring TIBCO review/response, please access the new TIBCO Community and select "Ask A Question."

You will need to register or log in or register to engage in the new community.

B2B Transaction Lifecycle Management using TIBCO LogLogic®

Last updated:
8:27am Nov 11, 2019

Back to HomePage


TIBCO LogLogic® provides the industry's first enterprise-class, end-to-end log management solution. Using LogLogic log management solutions, IT organizations can analyze and archive network log data for the purpose of compliance and legal protection, decision support for network security remediation, and increased network performance and improved availability.


This page contains a particular usecase that was resolved for TIBCO BusinessConnect™ using TIBCO LogLogic® platform.

The Problem

In TIBCO BusinessConnect™, there exist three sets of information regarding any inbound or outbound transactions: 1) the Gateway Server log, 2) the Interior Server log, and 3) the Audit database. This is because a B2B transaction typically undergoes those steps in BusinessConnect™.

For example, an inbound transaction first goes through the Gateway Server, where the identify of the trading partner is verified and the transport information is stripped. Then, the payload is processed by the Interior Server, where the transaction is validated and the payload is translated into a format that the destination application can understand. As the transaction undergoes validation and translation, a state machine writes to the Audit database of all successful events and exceptions. Finally, the transformed payload is passed on to the private process (usually running on TIBCO BusinessWorks™). Going the other way, the reverse it true. A payload is passed from the private domain to the Interior Server, where it is translated into the trading partner's agreed upon format and any validation information is built. Then it is passed to Gateway Server, where the appropriate transport layer is added, and sent out to the destined trading partner.

As a result, any Operational IT user wanting to easily find any event or error related to a particular transaction will have to search three different machines, making it an inefficient process.

Solution

  1. Changes in BusinessConnect 6.4 were made such that related transactional data in the Gateway Server log, the Interior Server log, and the Audit database are tied to a single transaction ID.
  2. Further, log data are now written to follow a common format that TIBCO LogLogic® can recognize. TIBCO LogLogic is TIBCO's log management platform that collects, stores, and correlates user activity, event data, and more.

B2B Transaction Lifecycle Management using TIBCO LogLogic

Benefits

TIBCO BusinessConnect customers can now use TIBCO LogLogic to ingest log data from TIBCO BusinessConnect's Gateway and Interior servers and transactional data from the Audit database. LogLogic correlates the system activity and event data under common transaction IDs, and stores them in a common place. The newly revamped TIBCO LogLogic UI provides graphical visualization and advanced search capabilities for operationalizing the data. This makes it a lot easier for customers to have a bird's-eye view of all B2B transactions across their lifecycle, and to quickly find transaction details in case of errors or exceptions.

To Do

Interested in B2B Transaction Lifecycle Management? Ask your solution consultant about TIBCO LogLogic. If you already have TIBCO LogLogic license, ask your professional service consultant about how to configure LogLogic to create BusinessConnect "devices" and database, point to those devices, configure the regex data models, and enable BusinessConnect data collection.