Transaction reports allows you to capture and track the number of submitted forms, processed documents, and rendered documents. The objective behind tracking these transactions is to make an informed decision about the product usage and rebalancing investments in hardware and software. For more information, see AEM Forms Transaction Reports Overview.
Transaction reports feature is available as part of the AEM forms add-on package. For information about installing the add-on package on all the author and publish instances, see Installing and configuring AEM forms. Once you have the AEM forms add-on package installed, do the following:
- AEM Forms transaction reports do not support topologies that contain only publish instances.
- Before using transaction reporting, ensure that the reverse replication is enabled for all the publish instances.
- Transaction data is reverse-replicated from a publish instance to only corresponding author or processing instance. The author or processing instance cannot further replicate data to another instance.
Transaction reports use reverse replication to consolidate count of transactions from publish instances to author instances. Set up the reverse replication on all the publish instances. For detailed instructions to setup reverse replication, see replication.
Transaction reports are disabled by default. You can enable the reports from AEM Web Console. to Enable transaction reports in an AEM Forms environment, perform the following steps on all the author and publish instances:
Only members of the fd-administrator group can view transaction reports. To allow a user to view transaction reports, make users member of the fd-administrator group. For instructions about making a user a member of an AEM group, see User, Group and Access Rights Administration.
Transactions are cached in-memory before being stored to the repository. By default, the caching period (Transaction Flush Period) is set to 60 seconds. Perform the following steps to change the default caching period:
Reverse replication copies transaction data to the default outbox of the author instances. You can place transaction data in a custom outbox. Perform the following steps to specify a custom outbox:
You can view transaction reports on author or publish instances. The transaction report on the author instance provides an aggregated sum of all the transactions that take place on the configured author and publish instances. The transaction report on the publish instance provides a count of transactions that take place only on the underlying publish instance. Perform the following steps to view the report:
AEM Forms displays transaction reports since the configured date, as shown in a summary report below:
- Use the Reset the date to today options to reset transaction records. When you reset the date to today, all previous transaction records are lost. When you reset the date on an author instance, the change does not affect transaction reports on the Publish instances and conversely.
- Use the Show transactions of only Publish instances to view all the transactions that occurred only on the configured publish instance or publish farm.
- Use the categories: Document Processed, Documents Rendered, and Forms Submitted to view corresponding transactions. For the type of transactions accounted in these categories, see Billable Transaction Reports APIs.
Transaction reporting places all the information displayed in the report and some additional information in the logs. The information provided in the logs is helpful for the advanced users. For example, logs divide transactions into multiple granular categories in comparison to three consolidated categories displayed in the report. The logs are at /crx-quickstart/logs/aem-forms-transaction.log.