Deployment Topology

AEM Forms add-on package is an application deployed onto AEM. You require only a minimum of one AEM Author and AEM Publish instance to run AEM Forms data capture capabilities. The following topology is suggested to run AEM Forms AEM Forms data capture capabilities. For detailed information about the topology, see Architecture and deployment topologies for AEM Forms.

recommended-topology

System Requirements

Before you begin to install and configure data capture capability of AEM Forms, ensure that:

  • Hardware and software infrastructure is in place. For a detailed list of supported hardware and software, see technical requirements.

  • Installation path of the AEM instance does not contain white-spaces.

  • An AEM instance is up and running. For Windows users, install the AEM instance in elevated mode. In AEM terminology, an “instance” is a copy of AEM running on a server in the author or publish mode. You require at least two AEM instances (one Author and one Publish) to run AEM Forms data capture capabilities:

    • 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 over the internet or an internal network.
  • Memory requirements are met. AEM Forms add-on package requires:

    • 15 GB of temporary space for Microsoft Windows-based installations.
    • 6 GB of temporary space for UNIX-based installations.
  • Replication and reverse replication for the author and publish instances is set. For details, see Replication.

  • For UNIX-based systems:

    • Install the following 32-bit packages from the installation media:
expat
fontconfig
freetype
glibc
libcurl
libICE
libicu
libSM
libuuid
libX11
libXau
libxcb
libXext
libXinerama
libXrandr
libXrender
nss-softokn-freebl
OpenSSL
zlib
NOTE
  • If OpenSSL is already installed on the server, upgrade it to the latest version.
  • Create libcurl.so, libcrypto.so, and libssl.so symlinks pointing to the latest version of the libcurl, libcrypto, and libssl libraries respectively.