Persistence is the method to store content on the physical storages. It defines the actual data structure and storage mechanism for the data. MicroKernels act as persistence managers in AEM Forms. AEM Forms supports persistence (MicroKernals) of type TarMK, MongoMK, and RDBMK. You can choose a persistence type for AEM Forms depending upon the purpose and deployment type (Single-Server, Farm, or Cluster) of an AEM Forms instance.
LiveCycle ES4 SP1 uses TarPM persistence to store content.
The following table lists all the supported persistence types along with various parameters to help you choose a persistence type for your environment:
|Installation Type / Cost||TarMK||MongoMk||RDBMK|
|Cluster Setup||Not Supported||Supported||Supported|
|License Cost||Included with AEM||Separate license required||Separate license required|
TarMK is designed for performance, while MongoMK and RDBMK are designed for scalability. Adobe highly recommends TarMK as the default persistence technology for all AEM Forms deployment scenarios, for both Author and Publish instances, except in the use cases outlined in section Choosing Mongo or a Relational Database Microkernel over TarMK.
A scalable (clustered) AEM Forms environment is a set of two or more horizontally configured active author instances. You can choose to run more than one author instance if a single server, supporting all concurrent authoring activities, is no longer sustainable.
Only MongoMK and RDBMK persistence type are supported for a scalable (clustered) AEM Forms on JEE environment. The number of servers or the size of scalable environment varies for every installation. For a list of considerations and examples, see the Recommended Deployments and or Architecture and deployment topologies for AEM Forms article. You can also contact AEM Forms support for detailed information on capacity planning for AEM Forms with RDBMK and TarMK.