About the Metering Simulator
Integration Server includes a metering simulator that writes transaction information to the metering log. Integration Server writes one entry per invocation of a top-level, user-defined service. Integration Server does not aggregate data across multiple invocations of the same service into a single log message.
Note:
The metering log exists only after application of a fix that includes PIE-85053 (IS_10.15_Core_Fix8). Prior to PIE-85053, the metering simulator wrote transaction information to the server log.
The metering simulator (and the webMethods Metering Agent) generates metrics for execution of top-level user-defined services only. The metering simulator runs independently of webMethods Metering. The metering simulator only enables the logging of data for services that would be metered and therefore generate transaction data. Enabling the metering simulator does NOT result in actual reporting of the measured transaction data nor does it result in charges.
The metering simulator has the following main use cases:
Your site has a subscription, transaction-based license but you want access to critical metering data that is not reported with
webMethods Metering. Specifically, the metering simulator provides the names of the top-level services that generate the transactions and the number of transactions resulting from each top-level service execution. The logs generated by metering simulator can be key to understanding your usage data. For example, if you see a
webMethods Metering report that indicates your site ran a million transactions last month, you may want to know the source of those transactions: which
Integration Server generated the most transactions and which services are long-running and contributing the most transactions. Using the metering logs created while the metering simulator is running can help you determine the answer to these questions.
The metering simulator uses the same transaction duration as webMethods Metering Agent. The duration is defined in the TxnTimer field of the Integration Server license key and is determined by your license and contract with Software AG.
Your site has the traditional perpetual license instead of a transaction-based license and you are considering moving to the transaction-based pricing model. Enabling the metering simulator for a period of time, and then analyzing the resulting data may provide guidance on how many transactions per month your site would need. The period of time for which you enable the simulator should reflect a typical transaction load. Because the license key will not include a TxnTimer field, the metering simulator reports metering data based on a transaction duration of 3 seconds.