AEM 6.4 has reached the end of extended support and this documentation is no longer updated. For further details, see our technical support periods. Find the supported versions here.
In AEM forms, an application is a container for storing assets that are required for implementing a AEM forms solution. Examples of assets are form designs, form fragments, images, processes, DDX files, form Guides, HTML pages, and SWF files. During the development phase of a project, Workbench users can deploy applications directly from the Applications view in Workbench. Once deployed, these applications appear in administration console, on the Applications tab on the Application Management page.
When an application is complete and ready for deployment to a production server, the Workbench user packages the application into a AEM forms application file (.lca). Then an administrator uses administration console to import and deploy the application file, using the Applications tab on the Application Management page.
You can also use thearchives tab on the Application Management page to import LCAs that were created using workbench 8.x.
There is a known issue that LCA files from a future release are not necessarily backward compatible. While it may be possible to view and import LCA files from a future release of AEM forms (for example, a preview release), doing so is not supported and may result in aberrant behavior.
Use the Applications tab to import and manage applications that were created in Workbench. Application administrators can also export the runtime configuration for an application. Exporting the runtime configuration eliminates the need to manually reconfigure settings in the production environment before starting deployed applications. The runtime configuration file contains:
In administration console, click Services > Applications and Services > Application Management.
Click Browse and select the .lca file to import and click Preview. The Preview Application page displays information about the application.
(Optional) To see a list of the assets contained in the application, click View Assets.
(Optional) To deploy the assets to the runtime, select Deploy Assets To Runtime When Import Is Complete. If you do not select this option, you can deploy the assets later.
Click Import. The application appears on the Applications tab.
Log into the CRX repository with administrator credentials.
Navigate to content/dam/lcapplications
The imported applications display in the lcapplications node.
Click on one of the imported applications.
The Properties tab on the right displays the properties of the selected CRX node.
The syncState property indicates the state of synchronization of data between the AEM forms server and the CRX repository. As soon as the import process begins this state is set to 0 (zero). This state indicates the data is currently not synchronized. When the data is synchronized, the state is set to 1.
You can deploy applications that you have imported, or that Workbench users imported from Workbench.
You can undeploy applications from the runtime.
Undeploy the application before removing it from the server.
If an application administrator exported the runtime configuration for an application, you can import it into the deployed application. You can import it using either the administration console or via scripted LCA deployment.
You can export the runtime configuration information for deployed applications.
You can also use a scripted deployment tool to deploy application files, including a settings.xml file that specifies the following settings:
Scripted deployment eliminates the need to manually reconfigure settings in the production environment before starting deployed applications.