About webMethods Metering

Software AG provides a subscription, usage-based pricing model for many of the company’s products, including Integration Server. The webMethods Metering utility uses a local webMethods Metering Agent installed with a product to collect data based on the webMethods product usage and then sends the data to the webMethods Metering Server which handles the billing aspect of the product usage. The criteria for transaction metrics to be reported to webMethods Metering include being on one of the supported versions, applying the most recent fixes, and having a license key installed that is associated with a transaction-based contract.

Integration Server regularly checks the status of the local webMethods Metering Agent. During start up, Integration Server checks the license to see if it is transaction-based. If so, Integration Server gathers status about the following:

The local webMethods Metering Agent configuration in Integration Server_directory \common\metering\conf\metering.agent.properties

The webMethods Metering Agent log files contained in Integration Server_directory \common\metering\storage. Integration Server verifies the contents of these log files and checks the format of the entries. The webMethods Metering Agent log files contain the transaction information that is sent to the webMethods Metering Server.

If any of the above status checks fail, Integration Server writes an error message to the error log and server log. Integration Server Administrator displays a notification about the failed status check. Integration Server writes successful status check messages to the server log when the 0176 Metering server log facility is set to Trace.

After completing the local webMethods Metering Agent status checks during start up, Integration Server performs a "dry run" of sending data to the webMethods Metering Server. During a dry run, Integration Server simulates a connection to the webMethods Metering Server. If the dry run fails, Integration Server writes error message to the error log and server log. Integration Server Administrator displays a notification about the failed dry run. If the dry run succeeds, Integration Server writes success messages to the server log when the 0176 Metering server log facility is set to Trace.

After the initial dry run executes during start up, Integration Server executes the system task Metering Agent Diagnostic Log at the interval determined by the watt.server.meteringAgent.logInterval. The default interval between dry runs is 60 minutes.