Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved


Chapter 5 Viewing Logs : Overview

Overview
TIBCO BusinessConnect provides several logs which are used to store messages processed through the system. These logs are:
Audit log   This log is used to store information about the messages and documents processed by TIBCO BusinessConnect. Using the audit log, one can follow the processing states of inbound or outbound documents.
Non-repudiation log   This log is used to provide proof of the delivery of messages. Non-repudiation depends on authentication using digital signatures. Incoming messages which have been digitally signed are authenticated and stored in the non-repudiation database.
Resend log   This log displays the audit log transactions eligible to be resent.
Using the Log Viewer
To search for transaction records and access the log, do the following:
1.
Click the BusinessConnect > Log Viewer link in the left panel.
2.
Audit   Select this to display the audit log search options. See Audit Log. If you select the protocol link instead the protocol radio button, the audit log will be selected by default.
Non-Repudiation  Select this to display the non-repudiation search options. Non-Repudiation Log.
Resendable Transaction  Select this to display the resendable transactions log search options. See Resend Log.
Resend History   Select this to display the resendable transaction history. See Resend Log.
3.
Invoke a search by following the description provided in TIBCO BusinessConnect Trading Partner Administration.
Status Codes
Table 4 contains a list of the status codes that can appear in the transaction details for all log types, a description of what the status code means, and TIBCO BusinessConnect B2BPlugin for CMI that supports this status code.
Table 4 Status Codes 
The individual summary rows are completed and no further audit trail is pending. It also means that the transaction has completed successfully if there were no acks were expected.
ERROR CONFIGURATION
There were problems encountered in parsing the EDI document due to syntactic errors in the document.
There were errors encountered in digitally signing/authenticating or encrypting/decrypting the EDI document due to bad/wrong public or private keys.
ERROR TRANSPORT
The transaction could not be sent due to problems contacting the partner through the transport that was configured to be sent.
RECEIPT PENDING
Indicates that the transaction that was sent is waiting for a transport level receipt from the partner. Business acknowledgements cannot be reconciled even if they are received before the receipt is received. Only occurs when AS1 or AS2 transport is used.

Copyright © Cloud Software Group, Inc. All Rights Reserved
Copyright © Cloud Software Group, Inc. All Rights Reserved