Copyright © Cloud Software Group, Inc. All Rights Reserved

Recording Error Events to Central Logger

The Central Logger consumes the event messages published by the Core Engine and stores them in the database for reporting purposes.

You can enable the Core Engine to publish all events, including successful and failed transactions, to the Central Logger by setting the tibco.clientVar.ASG/Logging/errorReportingEnabled property in the ASG_CONFIG_HOME/asg.properties file.

With TIBCO API Exchange Gateway , you can also selectively publish the error events to the Central Logger and store the failed transactions. This helps to reduce the volume of transactions stored in the Central Logger database.

Publishing Error (Failed) Transactions

To selectively publish the error transactions to the Central Logger, do the following:

1.	Open the ASG_CONFIG_HOME/asg.properties file for editing.

2.	Set the properties as shown below:

   tibco.clientVar.ASG/Logging/errorReportingEnabled=true

   tibco.clientVar.ASG/Logging/reportingEnabled=false

   tibco.clientVar.ASG/Logging/clLogLevel=1

3.	Save the file and close the editor.

The failed transactions are stored in the following tables:

•	ASG_TRANSACTIONS

•	ASG_TRANSACTIONS_DETAILS

•	ASG_TRANSACTIONS_KEYS

•	ASG_TRANSACTIONS_MESSAGES

If the detail level logging is disabled (that is, tibco.clientVar.ASG/Logging/clLogLevel property is set as 0 in ASG_CONFIG_HOME/asg.properties file), then the failed transactions are stored in the following tables:

•	ASG_TRANSACTIONS

•	ASG_TRANSACTIONS_KEYS

The tibco.clientVar.ASG/Logging/reportingEnabled property takes precedence over tibco.clientVar.ASG/Logging/errorReportingEnabled property. Therefore, if you set tibco.clientVar.ASG/Logging/reportingEnabled property as true, the Core Engine publishes all types of the messages, and the Central Logger records both success and failure type transactions.

Copyright © Cloud Software Group, Inc. All Rights Reserved