You're viewing help content for version:
- 6.4
- 6.3
- Older Versions
Caution:
This article is applicable if you are installing AEM Forms on OSGi. For information, about Installing, Upgrading, and Clustering AEM Forms on JEE stack, see AEM Forms Help and Tutorials.
Adobe Experience Manager Forms is an application deployed onto AEM. It extends engaging web and mobile experiences to enterprise forms and documents, allowing organizations to complete complex digital interactions while improving user experiences and extending business reach.
The out-of-the-box AEM Forms functionality included in AEM Quickstart is for learning capabilities of AEM Forms. You require an additional license to use AEM Forms add-on package in a production environment.
AEM Forms add-on package provides the complete functionality of AEM Forms, such as adaptive forms, adaptive documents, forms sets, and HTML5 forms. It also enables integration of AEM Forms with Adobe Analytics, Adobe Sign services, and document services.
Note:
If you planning to use AEM Forms Document Security, then install AEM Forms on JEE. For information, about Installing, Upgrading, and Clustering AEM Forms on JEE, see AEM Forms Help and Tutorials.
Before you begin to install and configure AEM Forms, ensure that:
- hardware and software infrastructure is in place. For complete listed of supported hardware and software, see the Technical Requirements article.
- the installation path of the AEM Quickstart does not contain
white-spaces . - set up an AEM instance. It involves setting up Author and Publish instances. In AEM terminology an "instance" is a copy of AEM running on a server. AEM installations usually involve at least two instances, typically running on separate machines:
- Author: An AEM instance used to create, upload and edit content and to administer the website. Once content is ready to go live, it is replicated to the publish instance.
- Publish: An AEM instance that serves the published content to the public.
For detailed steps about installing and starting Author and Publish instances, see Deploying and Maintaining.
- AEM Forms add-on package requires:
- 15 GB of temporary space for Microsoft Windows-based installations.
- 5.4 GB of temporary space for Linux, AIX, and CentOS-based installations.
- AEM Forms add-on package requires additional 32-bit libraries to run on Red Hat Enterprise Linux, SUSE Enterprise Linux, and CentOS. If you are using Red Hat Enterprise Linux, SUSE Enterprise Linux, or CentOS, install the following RPM packages from the installation media of the respective operating system:
- expat-2.0.1-9.1.el6.i686.rpm
- libxcb-1.5-1.el6.i686.rpm
- freetype-2.3.11-6.el6_0.2.i686.rpm
- libXau-1.0.5-1.el6.i686.rpm
- libSM-1.1.0-7.1.el6.i686.rpm
- zlib-1.2.3-25.el6.i686.rpm
- libICE-1.0.6-1.el6.i686.rpm
- libuuid-2.17.2-12.el6.i686.rpm
- glibc-2.12-1.25.el6.i686.rpm
- libXext-1.1-3.el6.i686.rpm
- nss-softokn-freebl-3.12.9-3.el6.i686.rpm
- fontconfig-2.8.0-3.el6.i686.rpm
- libX11-1.3-2.el6.i686.rpm
- libXrender-0.9.5-1.el6.i686.rpm
- libXrandr-1.3.0-4.el6.i686.rpm
- libXinerama-1.1-1.el6.i686.rpm
- Install 32-bit and 64-bit libraries:
- libicudata.so.42
- libicui18n.so.42
- libicuuc.so.42
- Install 32-bit curl libraries:
- libcurl.so
- libcurl.so.4
- libcurl.so.3
AEM Forms searches 32-bit libraries in the listed order. Ensure that at least one library is installed.
Note:
- You can use same libraries across all supported unix-based operating systems. The .rpm name and version is dependent on undelying operating system.
- If the above-listed libraries are saved with a different name, create a symlink to the library with the name listed above.
You can download AEM Forms add-on package from AEM package share. Perform the following steps to download the add-on package on Author and Publish instances:
-
In package share, search AEM 6.3 Forms add-on packages, click the package applicable to your operating system, and click Download. Read and accept the license agreement and click OK. The download starts. Once downloaded, the word Downloaded appears next to the package.
Alternately, you can also use the hyperlinks listed in the AEM Forms releases article to manually download a package.
-
After the download completes, click Downloaded. You are redirected to package manager. In the package manager, search the downloaded package, and click Install.
If you manually download the package via direct link listed in the AEM Forms releases article, click Upload Package, select the downloaded package, and click upload. After the package is uploaded, click package name, and click Install.
Note:
After the package is installed, you are prompted to restart the AEM instance. Do not immediately stop the server. Before stopping the AEM Forms server, wait until the ServiceEvent REGISTERED and ServiceEvent UNREGISTERED messages stop appearing in the [AEM-Installation-Directory]/crx-quickstart/logs/error.log file and the log is stable.
Also ensure that all the bundles except the following are active. You can check the bundles at http://[server]:[port]/system/console/bundles. You can safely ignore the state of the following bundles:
- Adobe Correspondence Management Migration Bundle
- Adobe LiveCycle FormsManager Core Bundle
- Forms Common Service Bundle
- Adobe Correspondence Management Migration Bundle
On the Author instance, to configure replication agents for each Publish instance. These agents replicate content from the Author instances to all the Publish instances. Follow these steps on the Author instance.
-
Access CRX Package Manager at
http ://[hostname]:[port]/crx/packmgr /index.jsp. Upload and install the package downloaded in Step 1. To know more about package installation, see How to Work with Packages. -
- In the Settings tab, enter a description, check Enabled, select Serialization Type as Default, set the Retry Delay to 60000, leave Agent User Id as Blank, and set the Log Level as Info.
- In the Transport tab, enter the required URI for the Publish instance http://[hostname]:[port]/bin/receive?sling:authRequestLogin=1 and set User and Password. The default credentials are admin/admin.
- In the Extended tab,enter the method POST in HTTP Method Section.
- In the Triggers tab, select On Receive and click OK.
Note:
In case, you have only one Publish instance you can use the default Replication Agent named as publish. You need to edit it for specifying Publish URI in the Transport tab as mentioned in the Step 7.b. In this case, you do not need to create a new replication agent.
Note:
In case, you have a publish farm, comprised of multiple non-clustered publish instances, you need to create a replication agent for each Publish instance as mentioned in Steps 1-9. For each such replication agent, Title and Name should be significant and unique, so the identification of the corresponding Publish instance can be simpler. Each such replication agent has a different URI in the Transport tab pointing to a particular Publish instance. For multiple publish instances, you can also create replication agents by copying the default agent publish and then editing Name and URI in transport tab of the created agent. If you are not using the default Replication Agent, disable it, so an unnecessary replication attempt can be avoided.
Note:
For Author clusters, these steps need to be performed on one Author instance (preferably a master instance).
On the Author instance, you need to configure reverse replication agents for each Publish instance. These agents replicate content from the Publish instance to the Author instance.
-
- In the Settings tab, enter a description, check Enabled, select Serialization Type as Default, set the Retry Delay to 60000, leave Agent User Id as Blank, and set the Log Level as Info.
- In the Transport tab, enter the required URI for the Publish instance http://[hostname]:[port]/bin/receive?sling:authRequestLogin=1 and set User and Password. The default credentials are admin/admin.
- In the Extended tab, enter the method POST in HTTP Method Section.
- In the Triggers tab, select On Receive and click OK.
Note:
In case, you have only one Publish instance you can use the default Reverse Replication Agent named as publish_reverse. You need to edit it for specifying Publish URI in the Transport tab as mentioned in the Step 7.b. In this case, you do not need to create a new Reverse Replication Agent.
Note:
In case, you have a publish farm, comprised of multiple non-clustered publish instances, you need to create a reverse replication agent for each Publish instance as mentioned in Steps 1-9. For each such reverse replication agent, Title and Name should be significant and unique, so the identification of the corresponding Publish instance can be simpler. Each such replication agent has a different URI in the Transport tab pointing to a particular Publish instance. For multiple publish instances, you can also create replication agents by copying the default agent publish and then editing Name and URI in transport tab of the created agent. If you are not using the default Replication Agent, disable it, so an unnecessary replication attempt can be avoided.
Dispatcher is caching and load balancing tool for AEM. AEM Dispatcher also helps to protect AEM server from attacks. You can increase the security of your AEM instance by using the Dispatcher in conjunction with an enterprise-class web server. If you use Dispatcher, then perform the following configurations for AEM Forms:
By default, the configuration of AEM Dispatcher is stored in the dispatcher.any text file. Add a filter for AEM Forms to the configuration file:
-
Navigate to the filter section and add the following filter to the filter section:
/0025 { /type "allow" /glob "* /bin/xfaforms/submitaction*" } # to enable AEM Forms submission
For detailed information about filters, see Dispatcher documentation.Note:
Search /filter to locate the filter section. To know more about filters, see Dispatcher documentation.
AEM Forms requires RSA and BouncyCastle libraries to be installed with AEM Forms add-on package. Perform the following steps to boot delegate these libraries:
-
Specify paths to the directories for system fonts, Adobe server fonts, and customer fonts in the respective fields.
Customer Fonts Customer Fonts Customer Fonts Customer Fonts Note:
Your right to use fonts provided by parties other than Adobe is governed by the license agreements provided to you by such parties with those fonts, and is not covered under your license to use Adobe software. Adobe recommends that you review and ensure that you are in compliance with all applicable non-Adobe license agreements before using non-Adobe fonts with Adobe software, particularly with respect to use of fonts in a server environment.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.