webMethods and Intelligent Business Operations 10.2 | API Gateway User's Guide | API Gateway Administration | Destination Configuration | Configuring Transaction Logger Destination
 
Configuring Transaction Logger Destination
You have to configure transaction logger as a destination to receive the API Gateway transaction event logs. The transaction log data is written to a file or a database based on the configurations. The events are sent to the log file for the Log Invocation policy.
* To configure transaction logger destination
1. Select Username > Administration.
2. Select Destinations.
3. Select Transaction logger.
4. Provide the following information:
Field
Description
Name
The default name of the transaction log, API Gateway Transaction Logger.
Enable
Click the Enable activation toggle button to enable the logger to start writing the log entries to the database or the file.
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 milliseconds.
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.
5. Click Save to save the specified transaction log configuration value.
Note: For these modifications to take effect, you must restart the API Gateway server.
You can click Cancel to revert to the last saved changes or to abandon all the changes if the values are not saved.
Post-requisites:
After performing the events configurations, you must select Transaction logger as a Destination in the Policies properties page for each policy, to receive the transaction event logs for the assigned policies.
Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release