Ogledujete si pomoč za različico :

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 Quick start is for learning the capabilities of AEM Forms. An additional licence for AEM Forms is required to install AEM Forms add-on package.

AEM Forms add-on package provides the complete functionality of AEM Forms, such as, creating and managing adaptive forms, adaptive documents, formssets, and HTML5 forms. It also enables  integration of AEM Forms with Adobe Analytics, Adobe Sign services, document services, and many more services.

Opomba:

If you planning to use AEM Forms Document Security or AEM Forms Process Managment engine, install AEM Forms Workflow (AEM Forms on JEE). For information, about Installing, Upgrading, and Clustering AEM Forms on JEE, see AEM Forms Help and Tutorials.

Preparing your server environment

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 Author and a Publish instance. For detailed steps, see Installing an Author instance and Installing a Publish instance article.
  • start the Author and Publish instance. For detailed steps, see the Starting AEM article.
  • 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

Download and Install AEM Forms add-on package

Opomba:

The bundles are listed at http://[server]:[port]/system/console/.  

You can download AEM Forms add-on package from AEM package share. Perform the following steps to download the add-on package:

  1. Log in to the Author instance as an administrator and open the package share. The default URL of the package share is http://[server]:[port]/crx/packageshare.

  2. In package share, search AEM 6.2 Forms add-on packages, click on 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.

  3. 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 on package name, and click Install.

  4. After the package is installed, you are prompted to restart the AEM instance. Do not immediately restart the server. Before restarting the AEM server, ensure that all the bundles, but the Signatures bundle, are in active state. If all the bundles are not active, wait, and check the status of the bundles after for a few minutes.

    Opomba:

    The bundles are listed at http://[server]:[port]/system/console/.  

Configuring replication agents to define the publish instance URL 

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. 

    1. Access the CRX Package Share at http://[hostname]:[port]/crx/packageshare/login.html. Download the AEM Forms add-on package to your operating system.

    2. Log in to AEM portal at http://[hostname]:[port]. The default user name is admin and the password is admin.

    3. 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.

      Access the Tools interface on the Author instance at http://[hostname]:[port]/miscadmin.

  1. Select Replication, then Agents on Author in the left panel. On the right panel, you see various agents configured for the Author instance.

  2. On the right panel, Select New and click New Page. The Create Page dialog displays.

  3. Set the Title and Name and select Replication Agent.

  4. Click Create to create new agent.

  5. Double-click the new agent item to open the configuration panel.

  6. Click Edit. The Agent Settings dialog appears.

    1. 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.
    2. 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.
    3. In the Extended tab,enter the method POST in HTTP Method Section.
    4. In the Triggers tab, select On Receive and click OK.
  7. Click OK to save the settings.

  8. On the agent configuration panel, click Test Connection. A successful connection indicates that the configuration is done correctly.

Opomba:

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.

Opomba:

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.

Opomba:

For Author clusters, these steps need to be performed on one Author instance (preferably a master instance).

Configuring the reverse replication agents

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. 

  1. Log in to Tools user interface at http://[hostname]:[port]/miscadmin

  2. Select Replication, then Agents on author in the left panel. On the right panel, you see various agents configured for the Author instance.

  3. On the right panel, Select New, and click New Page. The Create Page dialog appears.

  4. Set the Title and Name and then select Reverse Replication Agent.

  5. Click Create to create new agent.

  6. Double-click the new agent item to open the configuration panel.

  7. Click Edit. The Agent Settings dialog displays.

    1. 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.
    2. 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.
    3. In the Extended tab,enter the method POST in HTTP Method Section.
    4. In the Triggers tab, select On Receive and click OK.
  8. The tabs Proxy and Extended are optional. Click OK to complete and save this configuration

  9. Wait for few seconds so that page is refreshed. Click "Test Connection" link on the page to check if the configuration is successful or not.

Opomba:

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.

Opomba:

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.

Configuring Dispatcher for AEM Forms

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:

Configure access 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:

  1. Open the dispatcher.any file for editing.

  2. 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.

    Opomba:

    Search /filter to locate the filter section. To know more about filters, see Dispatcher documentation.

  3. Save and close the file.

Configure the referrer filter service

  1. Log in to the Apache Felix configuration manager as an administrator. The Default URL of the configuration manager is http://[server]:[port_number]/system/console/configMgr

  2. In the Configurations menu, select the Apache Sling Referrer Filter option.

  3. In the Allow Hosts field, enter host name of the dispatcher to allow it as a referrer and click Save. The format of the entry is http://[server]:[port].

Configuring the DocAssurance service  

The DocAssurance service and Assembler service are enabled only after bootdelegate RSA and BouncyCastle libraries. Perform the following steps to bootdelegate the libraries:

  1. Stop the AEM instance.

  2. Navigate to the [AEM installation directory]\crx-quickstart\conf\ folder and open the sling.properties file for editing.

    Opomba:

    If you use [AEM installation directory]\crx-quickstart\bin\start.bat
    to start AEM, then edit the sling.properties located at
    [AEM_root]\crx-quickstart\

  3. Add the following properties to the sling.properties file:

    sling.bootdelegation.class.com.rsa.jsafe.provider.JsafeJCE=com.rsa.*
    sling.bootdelegation.class.org.bouncycastle.jce.provider.BouncyCastleProvider=org.bouncycastle.* 
  4. Save and close the file. Restart the AEM instance.

Za ta izdelek je bila izdana neprenosljiva licenca za priznanje avtorstva, nekomercialno uporabo in skupno rabo pod enakimi pogoji 3.0  Objav v storitvah Twitter™ in Facebook ne urejajo pogoji pogodbe Creative Commons.

Pravna obvestila   |   Pravilnik o zasebnosti v spletu