Configuring Transaction Logger Destination

Field	Description
Mode	Specifies whether the logger is to write entries to the destination synchronously or asynchronously. Synchronous: In this mode, the logger writes entries directly to the destination. Asynchronous: In this mode, the logger writes entries to a queue, then later writes the entries from the queue to the destination. Each logger has its own queue.
Guaranteed	Provides data about guaranteed delivery transactions. You can use guaranteed delivery log entries to do the following: Track when transactions start and their current status. See the names of guaranteed delivery processes that are running. Track whether the processes completed successfully or failed. The default value is No.
Destination	Specifies whether the logger is to write entries to a file or database. Database: If this option is selected, the logger writes entries to the database. Note: You must ensure that in webMethods Integration Server, a pool alias is associated to the ISCoreAudit functional alias. For more information on pool alias, see webMethods Integration Server Administrator’s Guide. File: If this option is selected, the logger writes entries to the file in Integration Server_directory\instances\instance_name\logs\APIGateway directory. The default value is file.
Maximum queue size	Specifies the maximum number of entries the queue can hold. Specify numerals only (for example, do not include commas or periods). The default value is 100000 records. Choose a value that accommodates your system’s average volume for log entries. If your logging volume has sudden spikes, the queue can usually catch up by writing the pending entries during lulls. If the queue size is reached, then any additional log entries would be lost. Ensure to check the availability of disk space or memory of API Gateway server before you change the default value.
Maximum retries	Specifies the maximum times the logger must retry writing the entry to the destination if the first attempt fails because of a transient error. A transient error is an error that arises from a temporary condition that might be resolved or corrected quickly, such as the unavailability of a resource due to network issues or failure to connect to a database. The default value is 3.
Wait between retries	Specifies the waiting time before the logger can reconnect and rewrite the eateries to the destination in case of failure. The default value is 5 seconds.