When the transaction volumes are low in BusinessConnect environment, the time stamp can be used to identify a specific inbound transaction between Gateway Server logs into Interior Server logs.

If the transaction volumes are high in a BusinessConnect environment, how can I identify a specific inbound transaction between Gateway Server logs and Interior Server logs
 

How to identify an inbound transaction between Gateway Server and Interior Server

All

When TIBCO BusinessConnect Gateway Server sends an inbound message to TIBCO BusinessConnect Interior Server, the message ID is added in an INFO level entry in trace logs, which makes the inbound message ID in Gateway Server associated with the message ID in Interior Server.

This implementation is applicable to all supported business protocols and makes tracing an inbound message much easier.

For example: GatewayServer TxID: 56B53034-B00B-430E-966B-B6FF3FED86AE Sending Message To Interior Server With ID: A9BFCA95-8AC2-4BDA-A9D8-74AAA866B8B4

The message ID "A9BFCA95-8AC2-4BDA-A9D8-74AAA866B8B4" from Gateway Server logs can be used to search the Interior Server logs for a specific transaction.


Excerpt from Gateway Server log
-----------------------------------------------
[2019-02-14 10:19:32,441(INFO )]GatewayServer TxID: 4DE58D5D-DBB8-45DD-8CBE-6D50E0BE2B59 Sending Message To Interior Server With ID: 10316C4F-BC62-4089-9642-BCCB40846AD9


Excerpt from Server Server log
--------------------------------------------
2019 Feb 14 10:19:32:510 GMT -0800 BW.BusinessConnect-Interior_Server Debug [bw.logger] BW-EXT-LOG-300002 Job-1032.1032.10316C4F-BC62-4089-9642-BCCB40846AD9.<IS-Host-Name>-Interior-Server DMZ - MSH job map: null <==> Job-1032.1032.10316C4F-BC62-4089-9642-BCCB40846AD9.<IS-Host-Name>-Interior-Server 

In addition to this, if you want to track the status of this specific transaction in Interior Server logs, you may want to get the Job-ID such as Job-1032 and follow that Job in the Interior Server logs