You can use Adobe LiveCycle ES4 SP1 to manage various type of forms along with their associated resources, if any. These assets are together stored in the crx repository at a configurable location /content/dam/lcapplications. When you upgrade from LiveCycle ES4 SP1 to AEM forms on JEE, these assets are migrated at /content/dam/formsanddocuments.

The asset migration takes place after a successful upgrade or when an LiveCycle ES4 SP1 LCA (LiveCycle Archive) is imported to AEM forms on JEE. By default, the synchronization scheduler is configured to run after every 3 minutes. If the synchronization scheduler detects assets in a LiveCycle applications, in the last configured Shadow Node Root, then before initiating the synchronization, it migrates the assets from the repository location to /content/dam/formsanddocuments.   

Märkus.

If a LiveCycle application (at last configured Shadow Node Root) and a folder in AEM forms (/content/dam/formsanddocuments) share an identical name, the application with the identical name is not migrated. An error “application(s) could not be migrated due to conflicts. Kindly migrate these applications manually from AEM Forms UI” is logged.

Märkus.

The migration of the assets takes place only from the last active shadow node root path.

Märkus.

Assets and folders containing the special characters Hash (#), Square Brackets ([ ]), and semi-colon (;) in the name cannot be synced to CRX repository. So, such assets and folders are not synchronized.

Synchronization scheduler

By default, the synchronization scheduler runs after every 3 minutes to synchronize all the assets modified and updated in the repository via LiveCycle Workbench 11. Applications containing forms and resources are visible in the AEM forms user interface once the synchronization process is complete. You can perform the following steps to change interval of the synchronization scheduler:  

  1. Log in to AEM Configuration Manager. The URL of Configuration Manager is http://[Server]:[Port]/lc/system/console/configMgr

  2. Locate and open the FormsManagerConfiguration bundle.

  3. Specify a new value for the Synchronization Scheduler Frequency option.
    The unit of the frequency is minutes. For example, to configure the scheduler to run after every 60 minutes, specify 60.

Manually synchronizing assets

You can use the Synchronize Assets from Repository option to manually synchronize the assets. The assets synchronization takes place only after you migrate or discard the assets. Perform the following steps to manually synchronize the assets:

Märkus.

If the thumbnails of a few assets are not generated after performing an upgrade from LiveCycle ES4 SP1 to AEM forms on JEE, perform the Manual synchronization to generate the thumbnails.

AEM forms user interface
Figure 1 - AEM forms user interface

Step 1

Log in to AEM forms. The default URL is http://[Server]:[Port]/lc/aem/forms/


Synchronization dialog box
Figure 2 - Synchronization dialog box

Step 2

Click the icon on the toolbar.

  • If you do not have any assets at last configured path then the dialog box shown in figure 2 appears. Click Start to initiate the synchronization.

Migration and synchronization dialog box
Figure 3 - Migration and synchronization dialog box

  • If you have assets at last configured Shadow Node Root, then the dialog box shown in figure 3 appears. In the dialog box, click Migrate Assets. The assets are migrated to AEM forms. The assets are synchronized after a successful migration.

    The applications containing assets are visible in the forms user interface once the synchronization process is complete.
  • If you want to permanently delete the assets, click Discard Assets

Resolving conflicts during asset migration

If an application at the old shadow root node has name identical to a general folder present at /content/dam/formsanddocuments, the asset migration for such applications would fail. The user would be presented with an error dialog box. The dialog box would list the applications which have identical names. 

To resolve the issue, delete the conflicting general folder from AEM forms UI, and then Manually Synchronize the assets.

Resolving conflicts during asset synchronization

There are two ways an application could be getting synced to AEM Forms from Livecycle workbench.

1) One manually synchronizes all applications.

2) One creates an application or uploads a livecycle archive in workbench. This application is automatically synced without any user interaction.

In both the above mentioned cases, there could be a conflict scenario if the application being synced has a name identical to any of the general folders already present in AEM Forms. In the first case, a dialog will appear... and bla. In the second case, an error "An asset.... level " is logged in the server logs.

In order to resolve these conflicts: 

1) Delete the general folder from AEM Forms and manually sync assets.

2) Delete the application from workbench and create another application with a different name. This will automatically get synced to the AEM Forms.

If the LiveCycle application being synced from Workbench has name identical to a general folder, the asset synchronization for such applications would fail. The user would be presented with an error dialog box. The dialog box would list the applications which have identical name. To resolve the issue,

  • delete the conflicting general folder from AEM forms UI, and then Manually Synchronize the folders.
  •  In such cases, perform one of the following tasks to manually resolve the conflict:
Migration and synchronization dialog box
Figure 3 - Migration and synchronization dialog box

If the syncronisation fails:

  • Delete the conflicting application and recreate the application with a different name in LiveCycle Workbench.

Conflicts in asset synchronization dialog box
Figure 5 - Conflicts in asset synchronization dialog box

If the newly created application and a folder at /content/dam/formsanddocuments has identical name, then the dialog box shown in figure 5 appears. An error " An asset with the same name as this application already exists at root level." is logged. 


See töö on litsentseeritud Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported litsentsiga  Süsteemi Creative Commons tingimused ei kehti Twitter™-i ja Facebooki postitustele.

Juriidilised märkused   |   Privaatsuspõhimõtted veebis