Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 9 Viewing Logs : Audit Logs

Audit Logs
The audit log is used to store information about the messages and documents processed by TIBCO BusinessConnect Services Plug-in.
The entire AESchema is stored in the fields REQUEST_FROM_PP and SEND_TO_PP fields in the audit log, since this is required for the resend.
You can use the audit log to follow the processing states of inbound or outbound documents. Some of the types of information stored in the audit log include: sent and received documents; document originator; trading partner name; processing status; and validation errors.
For more information about audit logs, see TIBCO BusinessConnect Trading Partner Administration Guide, Audit Logs.
When doing searches, remember that the asterisk (*) is not considered to work as a wildcard, but represents a part of a name.
Configure an Audit Log for the Services Plug-in
To configure an audit log for the Services Plug-in:
1.
Click BusinessConnect > Log Viewer.
2.
On the Log Viewer page, click radio button next to EZComm.
3.
Click the Audit tab, and configure the audit log search.
Table 34 lists the options to select for the audit log.
From the Date Range list, you can select the period to search:
If Custom is selected from the Date Range list, additional editable fields for Start and End of the search period become available.
Advanced Filters
4.
Click Add, the Advanced Filters page is displayed.
Table 35 lists the options to select in the Advanced section of the audit log.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
For the Initiator, this value is true for any type of transaction (Notify , Synchronous Request Response, or Asynchronous Request Response). For the Responder, this value is always false. This value is true for outgoing requests, while for incoming requests and for outgoing responses this value is false.
Boolean search using: is, contains, is not, is not like.
The user transactionID column displays the transaction ID received from the private process on the Initiator side.
Boolean search using: is, contains, is not, is not like.
Boolean search using: is, contains, is not, is not like.
5.
6.
Select any of the available criteria from the Group by list:
To learn more about these options, see TIBCO BusinessConnect Trading Partner Administration Guide.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved